How Complicer verifies consent.
Most tools check whether a cookie banner exists. We test whether it actually works — and we only claim it works when the evidence proves it. When we cannot prove behaviour, we tell you exactly why instead of overclaiming.
After the click, we watch for observable proof.
After we click a consent control, we look for observable proof that the site acted on the choice. Any one of these four signals confirms a path. Select a signal to see what it proves.
After we click, the consent banner is gone from the page. The site acted on the choice instead of re-prompting.
Verification is granted only when Reject and Accept were both clicked — and each is confirmed by at least one signal.
An accept-only banner cannot be verified. A click with no confirming signal cannot be verified. Undefined or missing confirmation fails the gate — silent absence is not consent. The rule is enforced in code, identically for every audit, so the same evidence always produces the same verdict.
Every reason we say “cannot verify”.
When the rule is not met, we never fall back to a vague pass or fail. Each audit records exactly one of these reasons so you — and your regulator — know what was and was not proven. Select a reason to see the exact report wording.
How the evidence is sealed.
Every verdict ships with a tamper-evident evidence bundle. The chain proves the evidence is authentic, unaltered, and existed at audit time — retained for seven years.
See it on your own site.
Run a free audit and get the verdict — Verified, cannot-verify with the reason, or not proven — backed by signed evidence.