/ Privacy

Who does your page talk to, before anyone agrees?

Analytics, pixels and tags load from your HTML long before most consent banners have even appeared. This scan reads your page source and names what it finds: the trackers, the consent platform, and the gap between them.

This is a static read of your page's HTML: it reports what the source names, not what fires at runtime. Whether a tracker actually waits for consent is a timing question that needs a full audit in a real browser.

  • The full audit

    A rendered pre-consent and post-consent network diff in a real browser: what fired, when, and with which cookies. The document your DPO actually needs.

    Ask about an audit
  • One compliance house

    Accessibility, AI transparency and privacy are the same discipline: measure, fix, keep it true. The AI Act check next door works the same way.

    Check your AI
  • Keep it clean

    Sites regress: a marketing tag lands, a plugin updates, a tracker sneaks past the banner. Monitoring catches it the day it happens.

    See plans
/ What this checks

What the privacy check reads in your page source, and what the three verdicts mean.

When you press the button, our server requests the address, without running JavaScript, and reads at most 3 MB of the returned HTML. It collects the host of every absolute src or href attribute, drops your own domain and its subdomains, and compares the rest against a list of 28 tracker hosts covering analytics, advertising and social pixels. The same attributes are searched for the signatures of 14 consent platforms. Every other third-party host is counted as functional, as content or CDN, or as unplaced. Without an email address nothing is saved; with one, the address, the URL and the verdict are stored and passed to our staff.

The verdict follows three rules. No listed tracker host in the source gives Nothing to act on. A tracker host together with a recognised consent platform gives Worth a review, because the source alone cannot show whether the platform holds anything back. A tracker host with no recognised platform gives Action needed. When the result has a line about what fired before consent, the page was also opened in a real browser with nothing clicked: that line names the trackers actually contacted and counts third-party cookies, and any tracker contacted there turns the verdict into Action needed, with or without a consent platform.

Reading attributes has blind spots in both directions. A tracker added by an inline snippet or injected by a tag manager has no src attribute of its own and is missed. A consent tool outside the 14 signatures counts as absent. One address is checked, not the site, and nothing here observes what happens after a visitor accepts or refuses. Treat either warning as a reason to open the browser's network panel on a fresh visit and watch what loads before you touch the banner.

Do I need a cookie banner if I only use Google Analytics?
In the EU and the UK, storing or reading information on a visitor's device needs prior consent unless it is strictly necessary for the service the visitor asked for. Most regulators do not treat analytics cookies as strictly necessary, so a standard Google Analytics setup needs consent before it loads. Some national authorities exempt narrowly configured audience measurement; check the guidance of the authority in your country.
What is a consent management platform (CMP)?
A consent management platform is the software behind a cookie banner. It shows the visitor the choices, records what they agreed to, and is supposed to keep tags and scripts that need consent from loading until that agreement exists. Installing one is not enough: each tag has to be wired to it, otherwise the banner is displayed while the trackers load regardless.
How can I see which trackers load on my website before consent?
Open the site in a private window, open the browser's developer tools, select the network panel and reload without touching the banner. Every request listed at that point was made before consent. Sort by domain and look for analytics, advertising and social media hosts. The storage or application panel shows which cookies have already been set and by which domain.

What this is, and is not

The scan is a measurement of what a page's source names. It is not a compliance ruling and not legal advice; consent timing and cookie behaviour need a rendered audit.