Prove
PlannedSame organization, several domains.
Where a group runs several domains and the policy permits it, a decision can be shared across them rather than asked again per hostname. What browsers allow here changes, so the capability is bounded and described precisely.
Cross-domain Consent
- Verified domain groups
- Shared decision
- Browser-constrained
- No cross-device identity
How it helps
What you get with Cross-domain Consent
Domains you control
Verified ownership, not an open mechanism for linking unrelated sites.
Constrained by browsers
Third-party storage restrictions define what is possible; the product works inside them rather than around them.
Not cross-device identity
This shares a decision between your domains. It is not profile synchronization, and is not described as such.
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 moreWithdrawal
Withdrawing updates the runtime immediately and writes a new evidence event.
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