For website builders & platforms
Give every generated website a consent layer that already knows what the site contains.
A builder knows which analytics, embeds and marketing services it inserted. Let the components declare their privacy impact, compile the Consent Manifest with the site, and gate them from the first visitor.
Your toolkit
Developer & PlatformSDK, API, webhooks, CMS integrations and native website-builder support.Control & BlockingHold, gate or release services according to the visitor's actual choice.Scan & Tracker IntelligenceSee the cookies, trackers, storage and services actually running on your site.Privacy HealthContinuously test whether the site's real behaviour still matches its configuration.
Why it fits
Built for how website builders & platforms really work
1
Declared at build time
Component metadata — vendor, purposes, storage, load mode — compiles into a manifest before publish.
2
Correct from the first visit
No retrofit, no first-scan correction, no window where the site was wrong.
3
Verified afterwards anyway
Custom code and external tags never went through the builder, so the published site is still scanned.
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