Privacy policy
Short version: the extension has no server to send anything to, and no code that could. Long version below.
Last updated:
What is collected
Nothing. CookieMan does not collect, transmit or store personal data. There
is no account system, no identifier, no crash reporting and no analytics SDK. The extension
source contains no fetch or XMLHttpRequest calls — you can verify
that in the public repository.
How your cookie data is handled
Cookie values are read from the browser cookies API when the popup opens, rendered in the popup, and discarded when it closes. They are not written to disk, cached or copied anywhere by the extension. Data leaves your machine only when you copy or download an export, and then only to wherever you put it.
What is stored locally
Exactly one entry in chrome.storage.local, under the key
settings, holding two values:
theme— light, dark or systemlocale—enorru
Nothing else is written: no cookie names, no cookie values, no domain history, no usage counters. The entry lives on your device and is removed when you uninstall the extension.
Permissions, and why each one exists
| Permission | Purpose |
|---|---|
cookies | Read, create, modify and delete cookies — the core function. |
storage | Save the three preferences listed above. Never cookie data. |
tabs / activeTab | Resolve the current tab's domain so the right cookies are listed and counted. |
host access (<all_urls>) | Chrome scopes the cookies API by host. Without broad host access the extension cannot read cookies for the site you are on, or export across domains. |
There is no webRequest permission, no content script injected into pages, and no
remotely-hosted code — all three are ruled out by the Manifest V3 packaging.
Third parties
None in the extension: no analytics, no advertising, no error tracking, no fonts or scripts loaded from other domains.
This website
The site is static and carries no tracking scripts or cookie banners, because it sets no cookies. The hosting provider keeps standard server access logs (IP address, user agent, requested URL) for operational and security purposes, as any web host does. The online converter processes everything in your browser — the page has no upload endpoint.
Handling exports safely
A session cookie is a credential. If you export one, treat the file like a password: keep it out of shared documents and chat, and delete it when you are finished. See the guidance in the transfer guide.
Contact and changes
Questions or a privacy concern: open an issue on GitHub. If this policy changes, the updated date at the top of the page changes with it.