How a scan works
- Install the Chrome add-on and open the page under review. CookieComply records what a real browser session loads, with no script on the site.
- Compare before the banner, after Accept, and after Reject. That is how you catch marketing tags that never waited for a valid choice.
- Pull a classified inventory with purpose, risk notes, and draft consent language into a compliance review.
- Re-run after a CMP, GTM, or vendor change instead of trusting the policy page still matches production.
What's in a report
- Cookie name, party, and plain-language purpose
- Risk notes when marketing tools appear before consent
- Recommended actions for engineering and legal
- Draft consent text you can edit for your banner or policy
Who usually runs it
In-house privacy teams preparing for reviews. Agencies auditing a portfolio of client domains. E-commerce and product folks checking checkout and PDP after a CMP change. Anyone who already paid for a banner and still needs to know whether Reject actually sticks.
What it is not
CookieComply is not a consent banner and does not block trackers for your visitors. Keep a CMP for on-site consent UX. Use CookieComply when you need a current audit of what the page actually sets.
Your first scan
- Create an account and install the Chrome add-on.
- Open the site under review and run a scan.
- Share the report from your CookieComply workspace.
- If you prefer an agent instead of clicking: wire hosted MCP on /integrations.