Enforce
PlannedOne file that says what may run, when, and why.
The manifest is the contract between discovery and enforcement: for each service, its vendor, category and purpose, the execution mode, the cookies and storage it uses, the signals it maps to, and the version this all belongs to.
Consent Manifest
- Service → vendor → purpose
- Execution mode
- Cookies & storage
- Signal mapping
How it helps
What you get with Consent Manifest
Versioned, like a policy
A manifest version is what a receipt points at, so an old decision stays interpretable after the site changes.
Generated where possible
A website builder emits it from the components it inserted. A standalone site derives it from the scan plus your review.
Readable by machines and people
The same structure drives the runtime and the disclosure — which is how the two stay consistent.
Control & Blocking
The rest of Control & Blocking
Hold, gate or release services according to the visitor's actual choice.
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 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