Prove
BetaA consent decision with the context preserved.
A boolean in a database says somebody agreed to something, once. A receipt says which banner they saw, under which policy, over which service inventory, and what was granted — which is the question that actually gets asked later.
How it helps
Why teams rely on Consent Ledger
Receipts point at versions
Banner version, policy version and manifest version travel with the decision, so an old receipt stays interpretable after the site changes.
Minimal by design
A pseudonymous subject key rather than a durable visitor profile. A privacy product that quietly builds one is the wrong shape.
Change adds, never rewrites
A withdrawal creates a new event and leaves the original record intact. Evidence that can be edited is not evidence.
What's included
Every service in Consent Ledger
Each one is a page of its own — because someone searching for a specific capability is not searching for an overview of the group it belongs to.
Consent Receipts
A structured record of each decision, with the versions that gave it meaning.
Learn moreVersion 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 moreThe rest of the platform
The rest of the graph
Scan & Tracker Intelligence
See the cookies, trackers, storage and services actually running on your site.
Learn moreConsent Experience
Branded, accessible consent and preference experiences that belong on your site.
Learn moreControl & Blocking
Hold, gate or release services according to the visitor's actual choice.
Learn moreSignals & Advertising
Translate one visitor choice into the signals connected platforms understand.
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