Cookie Nope is a Chrome extension that helps users manage cookie-consent choices and related privacy controls. It can automatically reject optional cookie choices, apply supported regional privacy opt-outs and, for Pro users, provide additional privacy tools such as Maximum Privacy, local privacy activity history and Cookie Inspector & Cleaner.
Most of Cookie Nope's day-to-day website analysis is performed locally in the browser. Some features deliberately use external services, including account authentication, Pro entitlement checks, subscription management and user-submitted feedback or cookie-failure reports. Those uses are described below.
Information Cookie Nope handles
Depending on the features you use, Cookie Nope may handle the following categories of information:
- Website and browsing-context information: the current website domain and URL, together with visible text, controls, labels, consent-management structures and eligible embedded-frame information needed to identify cookie-consent and privacy controls.
- Extension settings: options such as automatic operation, rejection preference, regional privacy settings, Allowed websites, custom reject phrases, Pro feature switches, per-site privacy overrides and retention preferences.
- Local operational information: successful-action counts, the most recent action, current-site outcome records, quick-allow prompt history, site breakage memory, local Pro activity-log entries and privacy-audit history.
- Account information: an email address, Supabase user identifier, email-confirmation state and authentication/session information when you create or use a Cookie Nope account.
- Subscription and entitlement information: whether the account has Free or Pro access, enabled entitlement features, entitlement expiry or paid-through information and subscription status needed to provide Pro functionality.
- User-submitted feedback and reports: information you deliberately send through the Feedback or Report cookie failure controls.
- Cookie information, only when Cookie Inspector is enabled: cookie names, a local preview of cookie values, domains, paths, security flags, SameSite/session information, expiry information, cookie-store/partition information and Cookie Nope's local classification of the cookie.
Website processing and browsing activity
Cookie Nope operates on ordinary HTTP and HTTPS webpages, including eligible embedded frames, so that it can find consent interfaces and apply the privacy choices selected by the user. This necessarily involves processing information about the website being visited and parts of the page interface.
During normal automatic operation, this webpage and consent-interface information is processed locally and is not sent to IF Designs for advertising, behavioural profiling, sale to data brokers, credit decisions or unrelated purposes.
Cookie Nope does not maintain a server-side record of the user's general browsing history as part of its normal automatic rejection function.
Chrome storage and local history
Cookie Nope uses Chrome extension storage to remember settings and provide its features.
- Chrome sync storage: settings such as Allowed websites, custom rejection phrases and Pro preferences may be stored in Chrome's synchronised extension storage. If Chrome Sync is enabled, Google Chrome may synchronise those settings through the user's Google account and browser profile.
- Chrome local storage: operational data such as action counts, latest action, site outcome records, quick-allow history, local activity logs, tracker/privacy-audit history, breakage memory, account session information and cached Pro entitlement information is stored locally in the browser profile.
Cookie Nope restricts access to its local extension storage to trusted extension contexts where Chrome supports that control, so ordinary webpage content scripts cannot read the stored account session.
Cookie Nope Pro accounts and Supabase
Cookie Nope Free does not require a paid subscription. A Cookie Nope account is used for Pro account and entitlement functions.
Account authentication is provided through Supabase. When a user creates an account, signs in, confirms an email address or resets a password, the relevant account information is sent over HTTPS to Supabase's authentication service.
The extension stores the session tokens required to keep the user signed in in Chrome local extension storage. Passwords are submitted directly to the Supabase authentication service and are not stored by Cookie Nope itself.
Cookie Nope also contacts its Supabase-backed entitlement service to verify whether a signed-in account has Pro access. The extension may receive and cache a signed entitlement containing information such as the tier, enabled features, expiry information and subscription status. This is used only to enable and maintain the user's Free or Pro feature access.
Stripe payments and subscriptions
Cookie Nope Pro subscriptions are processed by Stripe. Choosing to upgrade opens Stripe Checkout, and subscription management — including cancellation — is handled through Stripe's Customer Portal.
Payment-card and billing details entered during checkout are handled by Stripe. Cookie Nope does not directly collect or store full payment-card details in the extension.
IF Designs and its Supabase-backed account service receive or use the subscription and entitlement information needed to determine whether Pro access is active, such as subscription status and paid-through/expiry information. Stripe may retain billing and transaction information according to its own privacy policy and legal obligations.
Deleting a Cookie Nope account and cancelling a Stripe subscription are separate actions. Account deletion removes the Cookie Nope account and its server-side Pro entitlement data, but users with an active paid subscription should manage cancellation through Stripe's Customer Portal.
Cookie Inspector & Cleaner
Cookie Inspector & Cleaner is an optional Cookie Nope Pro feature. It is off by default and requests Chrome's optional cookies permission only when the user enables the feature. When the feature is disabled, Cookie Nope asks Chrome to remove that optional permission.
Cookie Inspector reads cookies only after the feature has been enabled and the user uses the Cookie Tools controls. Depending on the chosen scope, it can inspect cookies for the current website or across sites available to the Chrome cookies API.
The Inspector can display cookie metadata and up to the first 80 characters of a cookie value locally in the extension interface. It may classify cookies as likely advertising, analytics, social-marketing or other categories and can remove cookies selected by the user. If the optional high-confidence automatic cleanup setting is enabled, Cookie Nope may remove cookies that its local classifier identifies with high confidence after a confirmed rejection.
Cookie Inspector cookie values and the detailed list of inspected cookies are processed locally by the extension and are not sent to IF Designs by the Inspector or Cleaner feature.
Pro activity log, privacy audits and local history
Cookie Nope Pro includes optional local history tools. These may record website domains together with privacy actions, consent-management platform information, outcomes, methods and technical details. The Pro activity log can be configured for approximately 7, 30 or 90 days of local retention and can be cleared by the user.
Privacy audits use locally inspected cookie information to calculate a technical privacy-footprint score. Audit history can include the website hostname, cookie count, score, rating and category counts. These audit records are stored locally and can be cleared from Cookie Nope.
Activity logs can be exported by the user as CSV or JSON files. Exporting creates a local download; it does not upload the log to IF Designs.
Feedback
The Feedback function is optional and user initiated. Nothing is sent until the user presses Send feedback.
A feedback submission can contain:
- feedback type, such as bug, suggestion or other;
- the current website URL;
- the message written by the user;
- the installed Cookie Nope version;
- the selected rejection method;
- the time the feedback was submitted; and
- if the diagnostics option remains selected: automatic-mode state, page-toast setting, green-success-icon setting, operating platform and browser user-agent string.
The user can deselect the diagnostics option before sending. Feedback is sent over HTTPS to IF Designs' Cloudflare-based private reporting service so it can be reviewed for support, bug fixing and product improvement.
Cookie-failure reports
The Report cookie failure function is also optional and user initiated. Cookie Nope asks for confirmation before sending a report.
The normal cookie-failure report contains:
- the current page URL;
- the installed Cookie Nope version;
- the selected rejection method; and
- the report timestamp.
The report is sent over HTTPS to IF Designs' Cloudflare-based private reporting service. It does not include the page's full contents, cookie values, passwords, form contents or an unrelated browsing history.
By deliberately sending feedback or a cookie-failure report, the user consents to IF Designs reviewing the specific information submitted for support, troubleshooting, abuse prevention and improving Cookie Nope.
Cloudflare reporting service
IF Designs uses Cloudflare to receive user-submitted feedback and cookie-failure reports. Cloudflare may process standard connection and security metadata, such as an IP address, as part of delivering, protecting and operating the HTTPS service. Cookie Nope does not add an IP-address field to its normal report payload.
Recognised-site HTTPS check
For a catalogue of recognised mainstream websites, Cookie Nope may make a credential-free request to the site's own HTTPS origin before offering its optional quick-allow prompt. The request is configured with credentials omitted, no referrer and no-store caching. The response body is not used for browsing analysis.
This request goes to the website being checked, not to IF Designs. The website will therefore receive the normal network information needed to serve that request.
Other external links
Cookie Nope may contain optional support links, including blockchain explorer or cryptocurrency payment links. Those services open only after the user chooses the relevant control. Cookie Nope does not receive or store wallet private keys or cryptocurrency account credentials.
Who information may be shared with
Cookie Nope does not sell user data and does not share user data with advertising networks, data brokers or analytics providers.
Information may be processed by the following parties only as required for the features described in this policy:
- Google Chrome / Google: Chrome extension storage and optional Chrome Sync.
- Supabase: account authentication, account management, password recovery, Pro entitlement verification and related account backend functions.
- Stripe: Pro checkout, payment processing, subscription management and cancellation through Stripe's Customer Portal.
- Cloudflare: receiving and protecting user-submitted feedback and cookie-failure reports.
- The website being checked: when the recognised-site HTTPS check is used.
Browser permissions
Cookie Nope v3.0 requests browser permissions needed for its stated functions, including extension storage, active-tab interaction, script execution, web-navigation handling and host access to ordinary HTTPS websites. These permissions let Cookie Nope detect and operate consent/privacy controls and maintain its per-site behaviour.
The Chrome cookies permission is optional and is requested only when a Pro user enables Cookie Inspector. Cookie Nope does not use its permissions to build an advertising profile or sell browsing information.
How information is used
Cookie Nope uses information only to:
- provide cookie-consent rejection and privacy-control features;
- remember the user's settings and per-site choices;
- provide optional Pro privacy, history and Cookie Inspector tools;
- authenticate accounts and verify Pro entitlement;
- process and manage Pro subscriptions through Stripe;
- respond to feedback and investigate reported failures;
- maintain security, reliability and abuse prevention; and
- improve Cookie Nope's user-facing functions.
Cookie Nope does not use personal or sensitive user data for personalised advertising, retargeting, data brokerage, credit-worthiness decisions or unrelated commercial profiling.
Retention and deletion
- Chrome sync/local data: remains until changed, reset, cleared by the browser/user, overwritten by Cookie Nope's built-in limits, or removed when the extension/browser data is cleared.
- Pro activity log: uses the user-selected local retention period of 7, 30 or 90 days and can be cleared at any time.
- Account data: remains while the Cookie Nope account exists. Cookie Nope provides an account-deletion function that removes the account and server-side Pro entitlement data.
- Stripe billing/subscription data: is managed by Stripe and may be retained by Stripe or related backend systems as required to operate the subscription and meet legal, tax, fraud-prevention or accounting obligations.
- Feedback and failure reports: are retained only for support, troubleshooting, development, security and abuse-prevention purposes and are deleted when they are no longer reasonably required for those purposes.
Users may request help with deletion or privacy questions through the IF Designs support page or the support contact published with Cookie Nope's Chrome Web Store listing.
User controls
Cookie Nope provides controls to change or reset settings, clear local activity/history data, disable optional Pro tools, remove the optional Cookie Inspector permission, sign out, reset a password and delete the Cookie Nope account.
Stripe subscription cancellation is managed through Stripe's Customer Portal. Account deletion does not itself cancel an active Stripe subscription.
Security
Cookie Nope v3.0 is a Manifest V3 extension. Its executable code is packaged with the extension and it does not download and execute remote JavaScript. Network requests used for account services, entitlements, billing setup and user-submitted reporting use HTTPS.
Cookie Nope stores only the session information needed to keep a user signed in and uses a signed entitlement mechanism to verify Pro access. No privileged Supabase service credential or Stripe secret key is shipped in the extension.
Children
Cookie Nope is a general browser privacy utility and is not directed specifically at children.
Changes to this policy
IF Designs may update this policy when Cookie Nope's features, service providers or data handling change. Material changes will be reflected in an updated policy and, where required, in the extension interface or Chrome Web Store listing.
Contact
Privacy questions, data-deletion requests and support enquiries can be raised through the IF Designs support page or the support contact published with Cookie Nope's Chrome Web Store listing.
Chrome Web Store Limited Use
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
In particular, IF Designs limits use of personal and sensitive user data to providing or improving Cookie Nope's disclosed user-facing features and related security/reliability purposes. IF Designs does not sell that data, use it for personalised advertising or transfer it to data brokers. Human review is limited to data a user deliberately submits for support/feedback, information needed for security or abuse investigation, information required by law, or appropriately aggregated/anonymised internal information.