Skip to content
The platform

Adapt

Beta

One policy engine for different privacy expectations.

Privacy rules and technical standards change on someone else's schedule. A policy pack turns the behaviour you want into a versioned object, so updating it does not mean rewriting your runtime or re-testing your site from scratch.

How it helps

Why teams rely on Policies & Jurisdictions

1

Behaviour as configuration

Opt-in or opt-out, default states, required controls, signal handling, renewal and disclosure rules — a policy object, not a code path.

2

Published policies are immutable

A change publishes a new version. Receipts point at versions, so history cannot be quietly rewritten.

3

Configuration, not legal advice

You choose which model applies where, on your own legal advice. The product implements that choice and keeps evidence of it.

Know 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