This website sets one cookie, and only after you click something, and it is the record of that click. There is no analytics, no advertising, no tracking pixel, no social embed, and no font or script loaded from anyone else. You can verify all of that in your browser's network tab, and we would rather you did than took our word for it.
| Thing | Do we do it? |
|---|---|
| Third-party analytics | No |
| Advertising or tracking pixels | No |
| Social media embeds | No |
| Web fonts from a CDN | No — system fonts only |
| Cookies before you choose | None |
| Cookies after you choose | One: your consent choice, stored on your device |
| Server logs | Host-level request logs (IP, URL, user agent) kept by the hosting provider for security and abuse prevention |
Rate limiting uses a keyed hash of the requesting address, truncated. It is enough to count requests and not enough to recover an address from. We do not store raw IP addresses alongside scan results.
When the consent banner is installed on a site, it can send a signed record of the choice a browser made. That record contains the categories chosen, the time, the method (banner, settings, or a browser privacy signal), the policy version, and the site it came from. It does not contain the visitor's name, email, or raw IP address, and it is not linked to an identity.
Each receipt is signed with HMAC-SHA256 so that altering it after the fact is detectable. A receipt is evidence that a browser reported a choice. It is not proof that a person understood anything, and it is not a legal certificate.
We do not sell or share data with advertisers or data brokers. Data is processed by our hosting provider on our behalf, and that is the extent of it. If that ever changes, this page changes first.
Scan results and consent receipts are kept while the beta operates, so that reports stay shareable and receipts remain verifiable. You can ask for anything relating to you to be deleted using the address below.
Under UK GDPR and EU GDPR you have the right to access, correct, delete, restrict or object to processing of your personal data, and to data portability. Because we hold very little that is personal, most requests are answered quickly. Write to the address below and we will tell you honestly whether we hold anything about you — including if the answer is no.
The Service refuses to scan private, loopback and internal network addresses, and applies its own target checks to every redirect hop, so it cannot be turned into a way to reach someone else's internal systems. The operator surface is token-gated and, without a token, answers only to the local machine. Passwords are not collected because there are no accounts.
If you find a security problem, please tell us before telling anyone else. We will confirm it, fix it, and say so.
When any function of this app fails — whether or not you are shown an error message — a record is written to a developer error log. It exists so a defect can be reproduced and fixed, and so that when the app does show you an error it can also tell you how to get past it.
A record contains only what identifies the failing function: the app name
and version, the surface it failed on, the app function that failed,
a stable error code, a severity, the error's type name, the error text after
mechanical redaction, the innermost code location, and a coarse platform bucket such
as chrome/windows.
A record does not contain your user id or account, any session or visitor id, your email address, your IP address, the full user-agent string, a page's query string or referring page, or the content of your files, messages or prompts. There is no field for any of these, and the storage behind the log has no column that could hold one. The log answers which app function is failing, never who hit it.
Credentials, API keys, bearer tokens, JWTs, email addresses, IP addresses, local account names in file paths, and query strings are removed mechanically before a record leaves your device. Records are retained for 90 days, applied to the whole table by age.
How to stop the transmission. Enable Do Not Track in
your browser (or Global Privacy Control), call OrbitErrors.optOut() on
any surface that loads the error contract, or block POST /api/dev-errors
with a content blocker. Records already written to the local file on your own machine
stay there. Because the log identifies nobody, we cannot locate and delete
“your” records on request — there is nothing to search by.
Material changes to this notice will change the date at the top. The beta is small and the notice is short, and we would rather keep it readable than comprehensive-looking.
hello@fixmycookies.com — it reaches a person. If you are in the UK or EU and are unhappy with our response you have the right to complain to your data protection authority.