Verify
PlannedConfiguration drift is normal. Not noticing is the problem.
Scans on a schedule, with alerts when something changes: a new service, a changed category, a failing state test. Consent decays quietly, and the only defence is looking regularly.
Continuous Monitoring
- Scheduled scans
- Change alerts
- Failing-check alerts
- Trend over time
How it helps
What you get with Continuous Monitoring
Scheduled, per site
Frequency by plan and by how often the site actually changes.
Alert on change
Notification when something appears or a check starts failing, rather than a report nobody opens.
Trend, not snapshot
Results over time, which is what shows whether the estate is improving.
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 moreReject-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 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