Pre-consent risk
Verify that no tracking technology fires before your banner gets a reply so you can say yes to privacy with confidence.
No credit card required ? Instant insights
Pre-Consent Tracking Detection watches for cookies, pixels, and scripts that fire before a visitor agrees to anything.
The analysis distinguishes between legitimate platform behavior and unauthorized trackers that evade notice in your consent banner.
Regulators treat pre-consent drops as high-risk privacy breaches, especially when compliance statements say tracking is blocked until consent.
Customers, partners, and auditors want proof that you do not leak personal data without permission, and this detection gives you an unambiguous log.
We run a headless browser, wait for the consent prompt, and capture every resource before the user clicks, replaying the same session in different geographies.
CookieInspector flags cookies, local storage entries, and network handshakes so you can see which scripts misbehave before consent is granted.
How we differ
The detection pairs aggressive instrumentation with human-readable reports, letting you fix pre-consent leaks long before a regulator calls.
Pre-consent tracking is any cookie, pixel, or third-party request that fires before the visitor accepts the consent banner. Under GDPR/ePrivacy it's the single most common violation — and the one regulators and complainants look for first.
CookieInspector loads your site in a real browser and records every cookie, script, and network request in the window before any consent is given — then flags each one that shouldn't be there. You get a timestamped list of exactly what leaked pre-consent.
ePrivacy Article 5(3) requires consent before storing or reading non-essential cookies. Anything that fires pre-consent is processing without lawful basis — the evidence used in fines and complaints. Detecting it is how you prove (or fix) compliance.
Related tools & guides