Verify
PlannedPress refuse, then watch.
The test drives the actual refusal flow you configured and then records what still executes. A banner that writes a refusal into the ledger while the pixel keeps firing is the failure this catches.
Reject-path Testing
- Scripted refusal flow
- Post-refusal observation
- Per-service findings
- Evidence per finding
How it helps
What you get with Reject-path Testing
Uses your flow
Whatever the refusal path is on your site, including a two-step preference centre, the test walks it.
Silence is the pass
The expected result is nothing happening, which is exactly the result no one checks by hand.
Names the offender
A failure names the service and the request, so the fix is obvious rather than investigative.
Privacy Health
The rest of Privacy Health
Continuously test whether the site's real behaviour still matches its configuration.
Pre-consent Testing
A fresh session checks which technologies execute before any choice is made.
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