Terms of Service

Beta terms · last updated 14 October 2026 · tos-2026-10-14

⚠️ Read this first — this is a plain-language template, not lawyer-drafted terms. It was written by the person who built the product, in the same spirit as the rest of it: say what is actually true, and flag what you are unsure about. It has not been reviewed by a solicitor. Before this Service is offered commercially, or as soon as real money or real business risk is involved, have a qualified lawyer in your jurisdiction review and replace it. That sentence is here because a compliance product that secretly ships unreviewed legal terms would be a bad joke.

1. Who we are and what these terms cover

FixMyCookies ("the Service", "we", "us") is a technical tool that inspects websites for cookie- and consent-related behaviour and provides an embeddable consent banner. These terms are an agreement between you ("you") and the operator of FixMyCookies. By using the Service, you accept them.

The Service is currently in beta and is provided free of charge. Free access is deliberate while the hosted product is unfinished; it is not a trial with a countdown, and there is nothing to cancel.

2. What the Service is, and what it is emphatically not

FixMyCookies is a technical measurement tool. It is not a law firm, it does not provide legal advice, and no output from it — including any report, score, grade, finding or consent receipt — is a legal opinion, a compliance certification, or a guarantee of anything.

3. Acceptable use — the important part

The Service fetches and analyses websites you ask it to. That capability can be misused, so:

You are solely responsible for your use of the Service and for any claim arising from the sites you point it at.

4. Beta service — availability, change and removal

5. Your content and data

6. The embeddable banner

The consent banner script is provided for you to host on your own site. You are responsible for how it is configured and deployed, including any consent categories you define and any policy page you link to. We supply the mechanism; you decide what your site actually does with a visitor's choice.

7. Intellectual property

The Service, its source code, its finding rules and its documentation remain the property of their author. These terms grant you a limited, non-exclusive right to use the Service; they do not transfer ownership. Third-party service names and trademarks referenced in reports (for example Google Analytics or Meta Pixel) belong to their respective owners and are used only to describe what a scan observed. Their appearance is not an endorsement, and implies no relationship with us.

8. Limitation of liability

To the fullest extent permitted by law, the operator of FixMyCookies is not liable for any indirect, incidental, special or consequential loss, or for lost profits, lost business, regulatory fines or penalties, arising out of or connected with your use of the Service — and by using a tool that reports on regulatory exposure, you acknowledge that you understand the risk you are measuring is yours, not ours. Because the Service is provided free of charge, our total aggregate liability is limited to £0.

Nothing in these terms excludes liability that cannot lawfully be excluded, including for death or personal injury caused by negligence, or for fraud.

9. Indemnity

You agree to indemnify and hold harmless the operator of FixMyCookies against claims arising from your use of the Service, including claims brought by the owner of a site you scanned without a legitimate reason.

10. Changes to these terms

These terms may change while the Service is in beta. Material changes will be reflected in the version number and date at the top of this page. Continued use after a change means you accept the updated terms.

11. Governing law

These terms are governed by the laws of Scotland, and the Scottish courts have exclusive jurisdiction over any dispute arising from them.

12. Developer error log

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.

13. Contact

Questions, corrections, or a security report: hello@fixmycookies.com. If you have found a security problem in the Service, please tell us before telling anyone else, and we will say publicly when it is fixed.