Free check · Cookies · Updated
Does my website set cookies before consent?
Many sites do: an analytics tag, an ad pixel or a tag manager often runs the moment the page loads, before the banner gets a click. To find out, load the page in a fresh browser, click nothing and look at what was stored and requested. Enter your address below and PrivaScan does exactly that in real Chrome, listing every cookie, storage write and tracker request it saw before consent.
Scan your page now
Real Chrome, nothing clicked: everything it finds happened before consent.
What “before consent” means
The ePrivacy Directive (Art. 5(3)) allows storing or reading information on a visitor’s device only with consent, unless it is strictly necessary for the service the visitor asked for. The EU Court of Justice added in Planet49 (C-673/17, 1 October 2019) that consent must be an active choice — a pre-ticked box is not consent. In practice:
- Fine without consent: a login or session cookie, the shopping cart, a cookie that remembers the visitor’s consent choice
- Needs consent first: analytics (such as _ga), advertising and social pixels (such as _fbp), session recording, most embedded third-party widgets
Check it by hand
Five minutes in your browser’s developer tools:
- Open a private window, press F12 and go to Network; tick “Preserve log”.
- Load your page and do not touch the banner. Everything that happens now happens before consent.
- Under Application → Cookies, look for identifiers such as _ga, _gid, _fbp or _gcl_au; in Network, look for requests to google-analytics.com/g/collect, facebook.com/tr or googletagmanager.com.
- Click “Reject all”, clear the network log and reload. Whatever advertising or analytics traffic remains runs despite the refusal.
- Check that the visitor can change the choice later as easily as they made it.
What the free PrivaScan scan reports
PrivaScan loads the page in real Chrome and clicks nothing, so everything it records happened before consent:
- Cookies, localStorage and IndexedDB writes, with the vendor behind each one
- Tracker requests, including CNAME-cloaked trackers that hide behind your own subdomain
- Whether a consent banner is present and whether Google Consent Mode signals “denied”
- Where the data goes: each third party’s jurisdiction and measured server location
- An A–F risk grade, each finding mapped to the article it touches, with a how-to-fix note
Common causes of cookies before consent
- The tag manager fires tags on page view instead of on the consent event
- A plugin or theme adds Google Analytics or a pixel on its own, bypassing the banner
- Embeds (YouTube, Google Maps, Google Fonts) contact third parties as soon as the page loads
- The banner stores the visitor’s choice but is not connected to the tags
Frequently asked questions
Which cookies are allowed without consent?
Only those strictly necessary for the service the visitor asked for — login, cart, security, remembering the consent choice. Analytics and advertising cookies are not strictly necessary, even if they are useful to you.
My banner blocks everything. Why does the scan still find trackers?
Usually a tag fires outside the banner’s control (see the causes above). PrivaScan also recognises Google Consent Mode: when the page signals denied consent and no identifier is stored, the finding is rated lower, because that is the set-up remediation guides recommend.
Can PrivaScan test the “Reject all” button?
Yes, in the site-wide crawl on Monitor and Compliance: when a banner is found, PrivaScan clicks “Reject” (through the consent tool’s interface or the button), reloads and documents in the PDF report which trackers still fire.
Is a clean scan proof that my site is compliant?
No. A scan shows what a browser can observe on the pages tested. Whether a legal basis exists is for you and your DPO to judge — the report is evidence, not legal advice.
Can ChatGPT or Claude run the scan for me?
Yes, on every plan including the free one. PrivaScan supports MCP, so a connected assistant can read your sites, scans and trackers and, at the level you allow, re-scan a site. Anything that uses your plan waits for your yes in the chat.
See what your page does before consent
One page, free, no account. Monitoring and site-wide evidence when you need them.
Related
- Guide: stop Google Analytics before consent
- Guide: gate Google Tag Manager behind consent
- Does my website load Google Fonts from Google?
- Use PrivaScan from ChatGPT or Claude
- Plans and the site-wide “Reject” test
Sources
- Directive 2002/58/EC (ePrivacy), EUR-Lex
- EU Court of Justice, Planet49 (C-673/17)
- Regulation (EU) 2016/679 (GDPR), EUR-Lex
PrivaScan is automated: it reports what a browser can observe on the pages it tested. This page is general information, not legal advice.