A website privacy check comes down to five observable facts: which cookies and trackers are written before the visitor consents; whether a consent banner with an equal Reject option is shown; whether data-collection forms carry a consent checkbox and a policy link; whether an up-to-date privacy policy is published; and whether data leaves for services in other jurisdictions. Each item takes minutes to verify in a browser — or one automated scan.
Free online tool — compliance checker: instant results, no signup.
An auditor cares less about the policy text than about the site's behaviour: processing must start after consent, not before. In practice the order is reversed — analytics counters, ad pixels and chat widgets initialise on page load and ship visitor identifiers to third parties before the banner even appears.
Open the site in an incognito window with DevTools → Application → Cookies visible. Touch nothing in the banner. Everything that appears in the cookie list and on the Network tab before your first click is processing-before-consent. Then repeat after pressing Accept and compare: the difference shows what the banner actually controls versus what loads unconditionally.
# Quick third-party host list from the console:\nperformance.getEntriesByType('resource')\n .map(r => new URL(r.name).hostname)\n .filter((h, i, a) => a.indexOf(h) === i && h !== location.hostname)A manual check covers one page and one scenario. The compliance scanner does the same in a real browser across multiple pages and three scenarios — no action, banner accepted, banner rejected — then folds the observations into an A–F grade with 152-FZ and GDPR projections and a per-page fix list. For a quick single-page registry-and-cookie check there is the 152-FZ aggregator.
Regulators fine sites for processing personal data without consent — and a site starts processing earlier than it seems: analytics, pixels and widgets write cookies the moment the page loads. The scanner shows the auditor's view: what leaves for third parties before consent, whether the banner works, and whether forms collect data correctly.
Three sessions per page: no action, banner accepted, banner rejected.
Service catalogue: who receives visitor data and in which country.
The policy link and consent element are checked next to the form, not in the footer.
Report with an HMAC integrity stamp — hand it to your lawyer or contractor.
preparing for an audit
technical facts for an opinion
client site handover
consent regression monitoring
Scheduled re-checks with an alert when pre-consent trackers appear on your site.
Sign up freeNo. Both the manual and the automated check record technical facts: what is written, what is shown, how forms are built. It is the groundwork for counsel, not a substitute.
With the most measurable item: move counter and pixel initialisation into the consent banner's accept callback. That usually clears the bulk of before-consent findings.
After every new widget, tag manager or marketing pixel — they change the picture silently. A standing watch does this automatically and alerts on a grade drop.
Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.