Build on it
PlannedPrivacy by construction.
A builder knows exactly which analytics, embeds and marketing services it inserted. If each component declares its vendor, purposes, storage and load mode, the Consent Manifest can be compiled with the site — before anyone visits it.
Website Builders
- Component privacy metadata
- Build-time manifest
- Gated component output
- Post-publish verification
How it helps
What you get with Website Builders
Declared, not discovered
The hardest part of consent on an existing site is finding out what is there. A builder never has that problem.
Correct from the first visitor
Components start in the right state at publish time instead of being corrected after the first scan.
Still verified
The published site is scanned anyway, because custom code and external tags never went through the builder.
Developer & Platform
The rest of Developer & Platform
SDK, API, webhooks, CMS integrations and native website-builder support.
JavaScript SDK
Read the state, subscribe to changes, open preferences and gate your own code.
Learn moreREST API
Versioned endpoints for sites, scans, trackers, manifests, policies and integrations.
Learn moreWebhooks
Signed events for scans, discovered trackers, published policies and failing health checks.
Learn moreCMS Integrations
WordPress, Shopify and Webflow over the same core API and runtime.
Learn moreAgency Management
Client organizations, reusable policies, roles, fleet reporting and site handover.
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