Skip to content
The platform

Build on it

Planned

Consent infrastructure your platform can call directly.

DotCensus is meant to be three things at once: a dashboard for a site owner, an API for a developer, and an embedded consent layer inside another product. The same Consent Core serves all three.

How it helps

Why teams rely on Developer & Platform

1

State you can read

A runtime API for the current state, plus events when it changes, so your own code can gate itself instead of being intercepted.

2

Configuration you can automate

Sites, scans, policies and manifests through a versioned REST API — which is what makes managing two hundred client sites possible.

3

Native where it counts

A website builder that declares what its components load can have consent generated with the site rather than retrofitted onto 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