PRIVACY POLICY - COOKIE EDITOR
Last Updated: October 2026
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. INTRODUCTION & PRIVACY PROMISE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Cookie Editor ("we", "our", or "the extension") is committed to protecting your privacy. We believe that privacy is a fundamental right, especially when using browser developer and security tools.
Our core commitment is simple:
• Cookie Editor DOES NOT collect, store, transmit, or monetize any of your personal data.
• Cookie Editor DOES NOT send your cookies, browsing history, or private tokens to any remote server or third party.
• 100% of cookie operations happen exclusively within your local browser sandbox.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2. PERMISSIONS EXPLAINED: WHAT THEY DO & WHY WE NEED THEM
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
When you install Cookie Editor, the browser prompts you to grant specific permissions. Here is a transparent explanation of each permission requested:
a) "cookies"
• Purpose: This permission allows the extension to interact with Chrome's native cookie storage API (`chrome.cookies`).
• Why it is needed: It enables the core functionality of the tool — reading existing cookies on the website you are viewing, updating cookie values, creating new cookies, and deleting cookies when you request it.
b) "activeTab"
• Purpose: Provides temporary access to the active browser tab when you click the extension popup icon.
• Why it is needed: The extension needs to know the domain and URL of the active webpage (e.g. `example.com`) so it displays only the cookies relevant to the website you are currently inspecting.
c) Host Permissions ("*://*/*" or "Access your data on all websites")
• Purpose: Grants the extension programmatic access to execute cookie API calls on any HTTP and HTTPS website.
• Why it is needed: Under Google Chrome's Manifest V3 architecture, the `chrome.cookies` API strictly prohibits an extension from reading or modifying cookies on any domain unless that domain is explicitly matched in the extension's host permissions. Because Cookie Editor is a generic, multipurpose developer utility designed to work on whichever website you choose to inspect (including local development servers like `localhost`), broad host permissions are mandatory.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
3. ARE ALL THESE PERMISSIONS STRICTLY NECESSARY?
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
YES. Every requested permission is strictly required by Chromium's extension security architecture for Cookie Editor to operate:
• Could we remove the Host Permissions ("*://*/*")?
No. Under Chromium's API rules, `chrome.cookies.getAll()`, `chrome.cookies.set()`, and `chrome.cookies.remove()` fail with a security permission error if the target website's host is not declared in `host_permissions`. Because we cannot predict which website you will visit or develop on (whether it's `github.com`, `reddit.com`, or your own web app on `localhost:3000`), the extension must have access to match any host you navigate to.
• Does the extension run continuously in the background or monitor your browsing?
No. Cookie Editor contains NO background trackers, content scripts, or monitoring agents. The extension only executes logic when you explicitly click on the extension icon in your browser toolbar to inspect cookies.
• Could we remove "activeTab"?
Without `activeTab`, the extension would not be able to identify which URL you are currently visiting to filter cookies for you.
We have audited all permissions and removed any unnecessary permissions (such as `storage`), keeping only the absolute minimum required to fulfill the extension's purpose.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
4. DATA COLLECTION, TRANSMISSION & THIRD PARTIES
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
• Personal Information: NONE collected.
• Cookie Contents & Tokens: Stored and read only locally in your browser. They are NEVER sent over the network or logged anywhere.
• Analytical Tracking & Telemetry: NONE. We do not use Google Analytics, Sentry, Mixpanel, or any third-party telemetry tools.
• Advertising: Cookie Editor contains NO ads, affiliate links, or sponsored scripts.
• Data Selling / Sharing: We have never sold, rented, or shared user data with any third party, and we never will.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
5. COOKIE EXPORTING & USER RESPONSIBILITY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
When you use the "Export" or "Copy to Clipboard" feature, Cookie Editor formats your cookies as text (JSON, Netscape, or Header string) and places it on your system clipboard or downloads it as a file on your device.
Please be mindful: cookies often contain sensitive session identifiers and authentication tokens. Do not share exported cookie files or clipboard strings with untrusted individuals.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
6. CONTACT & UPDATES
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
This Privacy Policy may be updated occasionally to reflect new browser security requirements or features. Any updates will be published along with extension updates in the Chrome Web Store.
If you have any questions, feedback, or security concerns, feel free to contact the extension developer via the Chrome Web Store support page.