Prove
BetaKeep the thing the receipt refers to.
Configuration changes constantly. Every published banner, policy pack and manifest version is retained, so a receipt from before a redesign still resolves to the experience that produced it.
Version History
- Immutable published versions
- Banner & policy history
- Manifest history
- Version comparison
How it helps
What you get with Version History
Published means immutable
A new configuration publishes a new version instead of editing the one receipts already point at.
Readable side by side
Compare what changed between two versions, and when.
The point of the exercise
Without this, a receipt is a timestamp attached to something that no longer exists.
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 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