CookieComply

Reject all doesn't mean what you think

Record what the browser actually sets before the banner, after Accept, and after Reject. Do it from an AI agent over MCP or the Chrome add-on; you get a GDPR cookie report.

Three-state capture

shop.northwind.eu

Ready
BeforeAcceptReject
  • session_id
    Essential
  • _ga
    Analytics
  • _fbp
    Marketing
  • _gid
    Analytics

Same capture from an agent or Chrome

  • GDPR cookie reports, not banner fluff
  • Runs from your AI agent over MCP
  • Chrome add-on if you scan by hand

Cookie audits fail on guesswork

Tools change. Spreadsheets rot. When a regulator asks what you collect, "we think we are fine" is not an answer.

  • Tracking after Reject all

    Ads and analytics can still run after a visitor says no.

    Consent bannerReject all

    Visitor chose essentials only.

    • Meta ads pixelStill loaded
    • Google AnalyticsStill loaded
    • Ad network cookieStill loaded

    They clicked reject. Tracking scripts ran anyway.

  • Lists that go stale

    Last quarter's spreadsheet cannot keep up when marketing adds a new tool.

    Cookie list (Excel)
    • Login sessionUp to date
    • Google AnalyticsUp to date
    • New ads toolUp to date

    Marketing added a tool. Nobody updated the list.

  • Legal stuck waiting

    Counsel needs a clear inventory, not another incomplete export.

    Request from legalWaiting

    Need: full cookie inventory

    • Cookie namesNot started
    • Purpose per cookieNot started
    • Vendor / partyNot started

    Legal asked for a full cookie list.

    Got an incomplete export back.

    Still missing what each cookie does.

From the live page to a report legal can open

01

Capture before, Accept, and Reject

Agent over MCP or the Chrome add-on on the live page. You leave with a cookie report legal can defend.

extension · CookieComply

CookieComply

Cookie compliance scanner

StatusNot Started
Current cookies0

Before consent

StatusNot Started
Cookies found0

What they allowed

  • Essential
  • Marketing
  • Analytics
  • Preferences

After Accept

StatusNot Started
Cookies found-

02

Keep every scan in one place

Know which sites you checked, what finished, and open any result for the full report.

app · dashboard

Recent scans

Status updates when each analysis finishes

URLStatus
  • shop.northwind.eu
    processing
  • docs.acme.io
    completed
  • checkout.lumen.app
    completed

Open any row for the full report and export.

03

See risk before legal asks

Overall risk, clear warnings, and each cookie explained in language your team already uses.

app · scan detail

shop.northwind.eu

Scan finished · ready for GDPR review

Risk Level: High

Needs attention

Marketing cookies appeared before consent was recorded.

What we found

  • _fbp

    .shop.northwind.eu · Marketing

    Risk Level: High

  • _ga

    .shop.northwind.eu · Analytics

    Risk Level: Medium

  • session_id

    shop.northwind.eu · Essential

    Risk Level: Low

04

Confirm the unsure cases

AI suggests a category. You approve the edge cases before the report leaves your desk.

app · cookie review

Review unsure cookies

Confirm suggestions before you share the report

Essential4Functional2Analytics3Marketing1Preference1Needs a check2

  • IDE

    .doubleclick.net

    Checking…Uncategorized

    Confirmed

  • li_sugr

    .linkedin.com

    Checking…Uncategorized

    Confirmed

Two ways in: agent or Chrome

Your agent can drive the capture over MCP, or you click through it in Chrome. Either path records before the banner, after Accept, and after Reject.

Access token

cc_live_••••••••••••

Settings → Connect AI

Agent path · token → MCP → three-state capture → report

Common questions

I need this handled

Prefer a fixed-price project instead of running scans yourself? Soft path only — subscriptions stay the main offer on Pricing.

See subscription plans — Pro, Assurance, and Agency for ongoing domains.

Run a scan before legal asks again

Mint a token and let your agent drive the capture, or install the Chrome add-on and click through one yourself. Same GDPR cookie report either way.