Skip to content

The platform

Eight modules. One consent engine.

The same module taxonomy you see when you log in, with 42 individually addressable capabilities inside it — each carrying the state it is actually in today.

Why one engine

One engine, or five disconnected tools.

A scanner that does not talk to the blocker, a banner that does not know the inventory, and logs that cannot name the policy they were written under is how consent ends up looking correct and behaving incorrectly. These eight modules share one state, one manifest and one version history.

  • Scan & Tracker Intelligence
  • Consent Experience
  • Control & Blocking
  • Signals & Advertising
  • Consent Ledger
  • Policies & Jurisdictions
  • Privacy Health
  • Developer & Platform

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