Adapt
BetaThe rules of the experience, in one object.
A policy pack sets the consent mode, default states, which controls must be present, how browser signals are treated, renewal periods and disclosure requirements — and names the framework adapter versions it expects.
Jurisdiction Engine
- Opt-in / opt-out mode
- Default states
- Signal handling rules
- Renewal & disclosure rules
How it helps
What you get with Jurisdiction Engine
Explicit defaults
What is true before a visitor decides is stated rather than emergent, which is the difference between an opt-in site and one that thinks it is.
Signals have defined effect
How a browser opt-out signal is treated is part of the policy, because the answer differs by region.
Adapters are pinned
A policy names the framework versions it was written against, so an adapter upgrade is a deliberate change.
Policies & Jurisdictions
The rest of Policies & Jurisdictions
Serve different consent models and disclosures from one versioned policy engine.
Regional Experiences
Preview and test what a visitor in each configured region actually sees.
Learn moreCookie Policy
Generate the disclosure from the current inventory, editable and never presented as legal advice.
Learn morePolicy Versioning
Published policies are immutable; changes publish a new version.
Learn morePolicy Generator
AI drafts plain-language descriptions and suggests updates when the inventory changes; you approve them.
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