Enforce
BetaThe choice matters only if the website obeys it.
A banner that records a refusal while the pixel fires anyway is worse than no banner: it documents the problem. DotCensus turns consent into execution rules — hold, release, gate or configure, per service.
How it helps
Why teams rely on Control & Blocking
Hold by default, release on consent
Known technologies are held until their category is allowed, rather than started and apologised for afterwards.
Gating beats blocking, where it is available
A framework or builder that never emits the tag is more reliable than intercepting one that is already loading.
Failure is defined
Under an opt-in configuration, a runtime that cannot reach its config must not fall open. The failure behaviour is specified and tested, not incidental.
What's included
Every service in Control & Blocking
Each one is a page of its own — because someone searching for a specific capability is not searching for an overview of the group it belongs to.
Automatic Blocking
Hold known scripts and domains until their category is allowed.
Learn moreNative Blocking
In supported builders and frameworks, the service is never emitted until it is allowed.
Learn moreScript Control
Explicit controls: consent categories on tags, deferred sources, tag-manager triggers and SDK callbacks.
Learn moreContent Gating
Privacy-aware placeholders for video, maps, chat and scheduling embeds.
Learn moreConsent Manifest
A machine-readable map from service to purpose, vendor, rule and signal.
Learn moreThe rest of the platform
The rest of the graph
Scan & Tracker Intelligence
See the cookies, trackers, storage and services actually running on your site.
Learn moreConsent Experience
Branded, accessible consent and preference experiences that belong on your site.
Learn moreSignals & Advertising
Translate one visitor choice into the signals connected platforms understand.
Learn moreConsent Ledger
Versioned evidence of what was shown, what was chosen and what was enforced.
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