Prove
BetaSaying no later has to actually stop things.
When a visitor withdraws or narrows consent, the runtime state changes immediately — services stop being released, signals update outward — and a new evidence event records the change without touching the original record.
Withdrawal
- Immediate runtime update
- Outbound signal update
- New evidence event
- Original record preserved
How it helps
What you get with Withdrawal
Immediate, not next page
The state applies in the current page, not the next navigation, because that is what a person just asked for.
Signals follow
Connected platforms receive the update through the same adapters that carried the original grant.
Append, never overwrite
The earlier receipt remains, which is what makes the history defensible.
Consent Ledger
The rest of Consent Ledger
Versioned evidence of what was shown, what was chosen and what was enforced.
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 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