Get in Touch About the Cookie Checker

What to Include in a Bug Report

Email [email protected] with enough detail to reproduce the problem.

For checker bugs

If the checker labels a cookie with the wrong purpose, misses a Set-Cookie header you can see in the response, or fails to spot a consent platform that is clearly on the page, send:

• The URL you checked and, for cookie disputes, the cookie name and what it is actually for.
• What the report showed versus what you expected. For a missing tracker host, the host name and what company runs it.
• Your browser and device, if the browser tab is the part misbehaving.

Adding a cookie or a host to the lists

The known-cookie table and the tracker-host table are hand maintained and will always be behind the real world. If a widely used cookie or host is missing, a short note with the name, the vendor and a link to the vendor's own documentation gets it added in the next update.

For everything else

Questions about how the classification works, corrections to the flags guide, or a note that something written here is out of date all go to the same address. Requests for scheduled monitoring, accounts, legal opinions or a compliance certificate will get a friendly no; the about page explains the boundaries. How submitted URLs are handled is covered in the privacy policy.

There is no form on this page on purpose: a form needs spam protection, and spam protection means loading a third-party script, which would be a strange thing for a cookie checker to do.

Replies usually go out within a few days. If your message includes a URL for debugging, it gets read and then deleted, not kept as data.