Services
Custom SoftwareCRMs, portals, dashboards + internal tools. Automation + IntegrationsConnected workflows + automatic hand-offs. DataCollect, clean + monitor business data. AIAgents, assistants + knowledge systems. WebWebsites, performance + conversion.
Company
AboutWorkJournalFree tools
Start a project →
UK cookie & tracking audit · real consent-state testing

See what happens before they click.

Enter a website and ZappFlow opens clean browser states to test what loads before a choice, what happens after Reject and Accept, whether preferences persist, whether consent can be withdrawn and what the site says in its cookie/privacy notices.

✓ No signup✓ Real browser states✓ PDF report
Run the audit

Test the consent journey properly.

This audit uses the same evidence model and conservative finding policy as ZappFlow’s internal cookie-compliance scanner. It tests the entry page in isolated browser contexts, checks mobile first-layer controls and samples up to three same-site cookie/privacy notices. You can enter example.com or https://example.com.

This is a UK-focused automated technical review, not legal advice or a legal compliance certificate. It tests remotely observable cookie, storage, tag and consent behaviour against the evidence rules used by ZappFlow’s current scanner. Some exceptions, purposes and legal conditions still need human confirmation.

3/3
Free audit allowance reachedYou’ve used today’s three free cookie audits.

Want another site checked, or want the cookie/tracking implementation fixed? ZappFlow can take it from here.

Your free audits will reset automatically.

ZF
Live browser audit

Testing consent behaviour.

01 / 07

Opening isolated browser contexts so one consent choice cannot contaminate another.

Before any choiceRunning
Reject / refuseQueued
AcceptQueued
Granular controlsQueued
WithdrawalQueued
Mobile controlsQueued
Policy evidenceQueued
After the audit

Consent is behaviour, not just a banner.

The important question is what the site actually loads before and after a choice. That is why the audit tests clean browser states rather than only reading a cookie table.

If the behaviour is wrong, we can trace the tags and consent logic that cause it and rebuild the implementation around the choices the site presents.

Fix the tracking setup →
Common questions

Cookie and tracking audit FAQ

Answers about the browser-state testing, UK focus and the limits of an automated technical cookie review.

What does the cookie audit actually test?

It observes browser storage, tags, requests and consent behaviour before a choice, after Reject, after Accept and where possible after withdrawal. That helps show whether the technical behaviour changes with the consent choice.

Does this tool provide legal advice or certify cookie compliance?

No. It provides technical evidence about what the browser did. Purpose, lawful basis, policy wording and jurisdiction-specific legal conclusions still need appropriate human or legal review.

Why test Reject and Accept in separate browser sessions?

Fresh browser states reduce contamination from earlier choices. That makes it easier to compare what appears before consent and what changes after each decision.