Bad Cookie is provided by MORE. Creative Studio ("we", "us" or "our"). This policy explains how the Bad Cookie Chrome extension handles information. For questions or privacy requests, contact hello@morecreativestudio.com.
What Bad Cookie does
Bad Cookie helps you review cookies and related privacy indicators in Chrome, block requests matching its included tracking rules, and remove cookies or supported website data you choose. Cookie and exposure assessments take place on your device. The extension does not send cookie values or assessment data to us or to third parties.
Cookie information
After you give consent and grant Chrome site access, Bad Cookie can access cookies Chrome makes available within that permission scope. Setup requests access to HTTP and HTTPS websites across your browser profile. Selecting the current-site inventory view does not revoke broader site access you have already granted.
The information used includes cookie names, domains, paths, expiry or session status, Secure, HttpOnly, SameSite and host-only attributes, cookie-store and partition information, and cookie-value length.
Chrome supplies cookie values with accessible cookie objects. Bad Cookie reads their character length and discards the values before assessment, messaging or display. The extension does not retain, log, display or transmit those values, or copy them into another cookie.
Bad Cookie uses the remaining metadata to display your inventory, identify review priorities and related indicators, filter results, and carry out removal actions you initiate.
Website context and exposure checks
When you open the Exposure Dashboard, Bad Cookie may inspect permitted open pages and frames. It uses origins, URL paths, embedding context and tab-to-cookie-store information to relate browser settings and cookie information. This frame check does not collect query strings, URL fragments or page text.
It may read effective camera, microphone and location permission settings. These checks do not activate your camera, microphone or location, and an allowed setting does not prove that a website used them.
Bad Cookie may also inspect counts of Local Storage and Session Storage entries, IndexedDB databases, Cache Storage entries and service workers. It checks for the identifier names _uuid, device_id and visitor_identity. Only those selected names and the relevant metadata leave the inspected page for local assessment; storage values do not.
This release does not inventory other installed extensions.
Observing cookie returns
With current consent and site access, Bad Cookie observes cookie removal and return events, including while its side panel is closed. It retains a bounded record of cookie identities and event information without cookie values. This helps identify an observed return after removal; it does not establish who recreated the cookie, why it returned or whether tracking resumed.
Request blocking
Tracking-request blocking is enabled by default on a fresh installation. You can turn it off during setup before continuing, or change it later in Danger Zone. Existing saved choices are preserved on updates.
Chrome applies the extension's included rules to matching third-party requests. Blocking can continue while the panel is closed and after Chrome restarts, while the extension and blocker remain enabled. It does not require cookie-scan site access. Bad Cookie stores the blocker preference and site recovery exceptions locally and does not collect request-match telemetry.
Blocking does not stop every tracking method or remove information already collected by websites. Reload open pages after changing the setting.
Removing cookies and website data
Individual cookie deletion targets the cookie you select. Domain Purge can request additional Chrome permission to remove supported cookies, HTTP cache, Local Storage and IndexedDB within the confirmed scope. Cookie removal can cover the site's cookie scope, while other storage removal uses the operation's supported website origins.
Total Purge can remove supported unprotected website data in the current browsing mode: cookies, HTTP cache, Cache Storage, IndexedDB, Local Storage, service workers and website file systems.
These actions can sign you out, reset website preferences and remove locally stored website content. They do not delete your saved passwords or browsing history, data in other browser profiles, protected browser origins, or information held on a website's servers or elsewhere. Operations can fail or complete only partly, and Chrome does not always expose enough information to verify the final result. Websites may create new data afterwards.
Storage and retention
Cookie inventory and operation results are held for the active interface or operation rather than saved as a persistent cookie database. Frame and permission results are held for the active assessment and are not saved as browsing history.
Cookie lifecycle evidence is held in Chrome session storage, with a rolling 30-minute observation window and a limit of 500 identities. Old evidence is pruned on subsequent events or reads, rather than erased by a timer at exactly 30 minutes. Continuing activity can extend an identity record. Aggregate coverage information can remain for the browser session. Lifecycle evidence is cleared when consent is removed or becomes invalid. Chrome also clears session storage on browser restart or extension reload, update or disable.
Consent records, inventory preferences, onboarding confirmations, blocker preferences and site recovery exceptions are stored locally until the relevant setting changes or extension storage is cleared. Temporary setup and interface state may remain in session storage until it expires or the session ends. Bad Cookie does not use Chrome storage sync for this information.
Sharing and Limited Use
We do not receive or sell the extension's cookie or exposure assessment data. We do not use it for advertising, behavioural profiling or data brokerage. Because this data stays on your device, our staff do not have remote access to it.
Bad Cookie's use of information complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Information accessed by the extension is used only for the features described in this policy.
This release does not create a Bad Cookie account, use Google sign-in, or perform payment-provider or licensing network checks.
Website visits and support messages
Visiting our website or contacting support is separate from the extension's local assessment. If you contact us, we receive the contact details, message and attachments you choose to send. Please do not send passwords, cookie values, authentication tokens or unredacted sensitive information.
Our website and support privacy notice explains how the website and support services handle information, including relevant service providers, retention and privacy rights. The extension does not automatically attach your cookie inventory or assessment data to a support request.
Your choices and privacy requests
You can decline site access, review or revoke it in Chrome's extension settings, turn request blocking off, disable Bad Cookie or uninstall it. Closing the panel or revoking site access does not by itself turn off the separate request blocker.
We cannot retrieve or remotely erase assessment information held only in your browser. You control that information on your device. To ask about information you have sent us through support, or to raise a privacy concern, contact hello@morecreativestudio.com. We will handle requests in accordance with applicable law.
Changes to this policy
We will update this page and its effective date when our practices change. Where required, we will provide additional notice or obtain consent before a new use of information begins.