Verify
BetaWhat runs before anyone says yes?
A clean session with no stored decision, loading the site the way a first-time visitor does, recording everything that executes before the dialogue is answered.
Pre-consent Testing
- Fresh-session scan
- Per-service results
- Per-page attribution
- Timeline of execution
How it helps
What you get with Pre-consent Testing
Clean state every time
No cached decision, no warm profile — otherwise the test quietly measures a returning visitor.
Per-service results
Which service fired, on which page, at which point in the load.
The common failure
This is where most sites fail, usually because of something added months after the banner was configured.
Privacy Health
The rest of Privacy Health
Continuously test whether the site's real behaviour still matches its configuration.
Reject-path Testing
A scripted run refuses consent and verifies the restricted services stay silent.
Learn moreUnknown Trackers
Surface unclassified third parties and new storage as soon as they appear.
Learn moreContinuous Monitoring
Scheduled scans and change detection, so drift surfaces without being looked for.
Learn moreReports
Dashboard and export of before-consent, refused and accepted behaviour with signal diagnostics.
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