Skip to content
The platform

Verify

Beta

Don't just configure consent. Test that it works.

A configuration that was correct in March can be wrong in June because a plugin updated, a campaign added a pixel, or a developer shipped an embed. Privacy Health visits the site in fresh, refused and accepted states and compares what happens with what you declared.

How it helps

Why teams rely on Privacy Health

1

The test that matters is the refusal

Anyone can verify that tags fire after acceptance. Whether they stay silent after a refusal is the question nobody checks.

2

Findings, not a score

Each result names the service, the state it fired in and the rule it broke. A single number would be easier to print and useless to act on.

3

Not a compliance certificate

Health measures whether the site behaves as configured. It does not certify that your configuration satisfies any law, and the product never labels it that way.

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