Contact

Questions about a guide, a step that does not match your browser, a correction, or a topic you would like covered, this is the page. Send a message with the form below, or write directly to contact@cookieeditor.net.

What to include in your message

A short message with the right details gets a useful answer much faster than a long one without them. If your question is about following a guide, it helps to say which guide you were reading (its title or URL), which browser you are using and its version (shown in the browser's About screen), whether you are on desktop, Android or iPhone/iPad, and what you saw instead of the expected step. If Cookie-Editor itself is involved, its version appears on the browser's extensions page. A screenshot of the panel is welcome, but crop or cover any cookie values first.

What never to send

Please do not include cookie values, session tokens, passwords, or exports of your cookies in any message, to this site or to anyone else offering help. A sign-in cookie value works like a password while the session lasts, and nobody needs it to help you. Every problem described on this site can be diagnosed from the cookie's name, its website, and what the browser did, never from the secret value itself. Messages containing live session values are deleted unread for your protection. The full explanation is in Why You Should Never Share Your Sign-In Cookies.

What this site can and cannot help with

This site documents the Cookie-Editor extension and general cookie behaviour, so questions about the guides, about understanding a cookie field, or about which guide fits your problem are exactly right here. Some things live elsewhere, and you will get help faster by going straight there. Problems with the extension itself, a bug, a feature request, or a version that misbehaves, belong with the extension's project: the store listing for your browser links to the project's support routes and its public code repository, where the developers actually read reports. Problems with a browser, an update that changed a menu, a profile that will not sync, belong with the browser maker's support pages. And problems with a particular website's sign-in or checkout can only be fixed by that website; no cookie editor can repair a session the site itself has ended.

Corrections

Spotted an out-of-date step, a changed store layout, or a wrong detail? Corrections are genuinely welcome. Say which page, what the guide says, and what your browser shows instead. Every correction is checked against the official store listings and documentation before the guide is changed, so the fix is verified rather than swapped from one guess to another.

Suggesting a topic

New guides grow out of reader questions. If you have a cookie problem or a testing task that the current guides do not cover, describe the situation, the browser, what you tried, and what happened. Topics that help many readers become guides in the relevant category; even when they do not, you will get a reply pointing at the closest existing guide.

Response times

Messages are read in batches, so please allow a few working days for a reply. The contact form below is a front-end form until a form endpoint is connected; email to the address above is the working route today, and it reaches the same inbox.

Writing for a team, a classroom or a newsroom

If you teach web development, testing or digital literacy and you use these guides with a group, you are welcome to link to them and to set the exercises exactly as written; they were designed around test pages and harmless preferences with groups in mind. If you adapt an exercise for your own materials, a link back is appreciated. For teams standardising on Cookie-Editor for QA work, the most useful starting points are Using Cookie Editor to Test Website Preferences Like a QA Pro and the Privacy & Testing category, which together set the working rules your team should share, separate profiles, named test cookies, logged changes, and exports treated as sensitive files.

Reusing words or illustrations from this site

Short quotations with a clear link back are fine, as the Terms of Use describe. Republishing a full guide, or lifting the illustrations as your own artwork, is not. If you run a publication and want to syndicate a guide properly, write and ask; the answer is usually quick, and an authorised copy can be supplied with the illustrations at full size. If you have found this site's content copied wholesale somewhere else, a message with the address is genuinely appreciated.

Business and partnership enquiries

If you are writing about something other than a guide, a product team whose tool genuinely belongs in a comparison these guides already make, a publication discussing syndication, an educator planning course material, say so in the first line so the message reaches the right reading pile. Two kinds of business mail are answered with a polite no every time, without exception: offers to place paid links or sponsored content inside guides, and offers to sell this site traffic, rankings or 'authority' services. Documentation that can be bought is not documentation, and readers can always tell. Everything else legitimate is read with interest.

If you do not hear back

Occasionally a reply lands in a spam folder, or a message arrives without a working return address. If a fortnight passes with no answer to a message that matters, send it again with 'second attempt' in the subject line; duplicates sent in good faith are never a problem here.

A final word on tone

Messages here are answered by the people who write the guides, in the same plain style as the guides themselves. Short messages are fine, imperfect English is fine, and questions that turn out to be answered by an existing guide are fine too; you will simply be pointed at it, kindly, with the section that fits your case marked.

The form is a front-end demonstration until a form endpoint is connected; email is the working contact route.