Enforce
PlannedThe most reliable block is the tag you never wrote.
Where DotCensus is integrated into a framework or a website builder, a service is simply not initialized until the Consent Core permits it. Nothing to intercept, nothing to race, nothing to miss.
Native Blocking
- Framework gating
- Builder-time decisions
- No DOM interception
- Post-publish verification
How it helps
What you get with Native Blocking
No interception race
Generic blocking fights the page's own loading order. Native gating does not enter the race at all.
Known before publish
A builder knows which services a page contains while it is being built, so the correct state is decided before anyone visits.
Verified anyway
The published site is still scanned — custom code and external tags do not go through the builder.
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 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