Enforce
BetaCatch the tags you did not know to list.
Known script and domain signatures are held at the point of insertion until the visitor's state permits them — which covers the ordinary case of a marketing tag added by someone who did not tell the person who configured consent.
Automatic Blocking
- Known script signatures
- Domain rules
- Hold until permitted
- Unknown surfaced for review
How it helps
What you get with Automatic Blocking
Signature-driven
The same knowledge base the scanner uses decides what to hold, so discovery and enforcement agree.
Safe by construction
An unknown script is surfaced for review rather than silently allowed because it did not match a rule.
Interception has limits
Automatic blocking is the fallback for sites we do not control. Where a cleaner path exists, use it — the next two capabilities are that path.
Control & Blocking
The rest of Control & Blocking
Hold, gate or release services according to the visitor's actual choice.
Native 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 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