Prove
BetaWhat was shown, what was chosen, under which policy.
Each decision produces a record: a pseudonymous subject key, a timestamp, the region and policy pack, the banner and manifest versions, the categories and purposes granted or denied, any framework strings, any browser privacy signal, and a proof hash.
Consent Receipts
- Pseudonymous subject key
- Policy, banner & manifest versions
- Granted & denied categories
- Proof hash
How it helps
What you get with Consent Receipts
Pseudonymous by default
No durable identifier, and no raw IP kept as a matter of course — where an address is needed for routing or abuse control, retention and transformation are disclosed rather than glossed.
Self-explaining
The versions travel with the record, so reading it in two years does not require reconstructing the site from memory.
Exportable
Structured export for the occasions when someone needs the evidence outside the dashboard.
Consent Ledger
The rest of Consent Ledger
Versioned evidence of what was shown, what was chosen and what was enforced.
Version History
Historical banners, policies and manifests kept so old receipts stay readable.
Learn moreRenewal
Flag or re-ask for consent when a configured period lapses or the policy materially changes.
Learn moreWithdrawal
Withdrawing updates the runtime immediately and writes a new evidence event.
Learn moreCross-domain Consent
Share a decision across domains you control, within technical and policy limits.
Learn moreKnow what runs before you ask visitors to trust it.
Start with a scan of what your website loads today. The list is usually longer than the team expects, and that is the useful part.
No code to install for a scan Public pages only DotCensus runs on DotCensus