Cookie Nope is a Chrome extension that detects cookie-consent interfaces and attempts to reject optional cookies according to the user's settings. Its normal cookie-detection and rejection work is performed locally in the browser.
Information handled by Cookie Nope
To provide its features, Cookie Nope may process the following information:
- Website address information: the domain and current page URL of websites on which Cookie Nope operates.
- Cookie-consent interface information: visible text, controls, labels and structural information from webpages and eligible embedded frames, solely to identify consent interfaces and safe refusal controls.
- User settings: options such as automatic operation, rejection method, confirmation/toast preferences, late-banner monitoring, custom rejection phrases and Allowed websites.
- Local operational information: successful-action counts, the most recent successful action, quick-allow prompt history and update-check state.
- User-prepared feedback: when the Feedback feature is opened, Cookie Nope can prepare a report containing the current website, the user's message and feedback type. If the optional diagnostics box remains selected, the prepared report also contains the extension version, rejection method, automatic-mode state, toast setting, green-success-icon setting, platform and browser user-agent string.
- User-submitted cookie-failure reports: when the user deliberately chooses Send report, Cookie Nope sends the current page URL, extension version, selected rejection method and report timestamp.
Cookie Nope does not intentionally store or transmit passwords, authentication credentials, payment-card details, cookie values, complete page HTML, ordinary form-field contents or a separate history of the user's general web browsing.
Local website processing
Cookie Nope runs on ordinary HTTP and HTTPS webpages, including eligible embedded frames, so it can recognise cookie-consent interfaces and operate refusal controls. This page information is processed locally for Cookie Nope's stated browser function and is not sent to IF Designs during normal automatic rejection.
Cookie Nope does not use website information for advertising, behavioural profiling, credit decisions, sale to data brokers or unrelated purposes.
Chrome storage and synchronisation
Cookie Nope uses Chrome extension storage for its settings and operational state.
- Chrome sync storage is used for settings, custom rejection phrases and Allowed websites. If Chrome Sync is enabled for the user's browser profile, Google Chrome may synchronise this information through the user's Google account.
- Chrome local storage is used for information such as successful-action counts, the last successful action, quick-allow prompt history and update state. This information is intended to remain local to the browser profile unless Chrome itself provides otherwise.
Recognised-site HTTPS check
For a catalogue of recognised mainstream websites, Cookie Nope may make a live HTTPS request to the site's own origin before offering the optional quick-allow prompt. The extension first attempts a HEAD request and may fall back to a GET request whose response body is cancelled after the headers are received.
The extension configures this check with credentials omitted, no referrer, no-store caching and HTTPS. This request goes to the website being checked, not to IF Designs.
Cookie-failure reports
Cookie-failure reporting is optional and user initiated. The extension displays a confirmation dialog before a report is sent.
The report payload contains only:
- the current page URL;
- the installed Cookie Nope version;
- the selected rejection method; and
- the time the report was submitted.
After the user chooses Send report, the report is transmitted over HTTPS to IF Designs' Cloudflare Worker reporting endpoint. By submitting the report, the user is asking IF Designs to receive and review that information solely for troubleshooting, abuse prevention and improving Cookie Nope.
The normal report payload does not contain page contents, cookie values, form data, passwords or unrelated browsing history. Cookie Nope v2.1 also contains developer diagnostic tooling capable of describing consent-banner frames and controls, but the public build does not attach those diagnostics to the normal Send report action.
IF Designs' current reporting service stores submitted cookie-failure reports in its private Cloudflare-backed report system. Cloudflare may also process standard network connection metadata, such as an IP address, as part of delivering and protecting the HTTPS request. Cookie Nope itself does not add an IP address to the report payload.
Feedback
The Feedback feature is different from the cookie-failure reporting service. Cookie Nope prepares feedback locally and does not automatically send it to IF Designs.
The user can copy the prepared feedback report to the clipboard or choose Open email app. The latter opens an email draft containing the prepared report using the device's configured email handling. Any subsequent sending is performed by the user through their email application or email provider, whose own privacy terms then apply.
The optional diagnostics included in a prepared feedback report are shown in the Feedback interface and can be excluded by clearing the diagnostics checkbox before copying or opening an email draft.
Data sharing and external services
Cookie Nope does not sell user data and does not share user data with advertising networks, data brokers or analytics providers.
Limited information may be processed by:
- Google Chrome / Chrome Sync: for browser extension storage and optional synchronisation when enabled by the user.
- Cloudflare: for the user-initiated cookie-failure reporting endpoint and its associated private report storage.
- The user's email provider: only when the user chooses to send feedback using an email application.
- The website being checked: when Cookie Nope performs the optional recognised-site HTTPS security check described above.
Users may also deliberately open external blockchain explorer pages or cryptocurrency payment links from Cookie Nope's support interface. These actions happen only after the user selects the relevant control. Cookie Nope uses static receiving addresses and does not receive or store the user's wallet credentials, private keys or transaction history.
Permissions and access
Cookie Nope v2.1 requests browser access needed for its stated functionality, including storage, current-tab interaction, script execution and navigation/frame handling. It operates on ordinary webpages so it can detect cookie interfaces, and it is permitted to contact its Cloudflare reporting endpoint for reports that the user deliberately submits.
These permissions are used to provide Cookie Nope's cookie-rejection, per-site, reporting, feedback, settings and update-related functions and are not used to build an advertising or browsing profile.
Data retention and deletion
Settings and Allowed websites remain in Chrome extension storage until the user changes or resets them, removes the extension, or clears the relevant browser data. Local operational information can likewise be removed by clearing extension/browser data or removing the extension.
User-submitted cookie-failure reports are retained only for legitimate troubleshooting, development, security and abuse-prevention purposes and are deleted when they are no longer reasonably required for those purposes.
A user who wants to request deletion of a previously submitted cookie-failure report can use the IF Designs support page. Providing the reported page URL and approximate submission date/time may be necessary to identify the relevant report because Cookie Nope does not attach a user account identifier to the report payload.
Security
Cookie Nope v2.1 is a Manifest V3 extension. Its executable code is packaged with the extension and it does not download or execute remote code. User-initiated reporting and recognised-site checks use HTTPS.
Children
Cookie Nope is a general browser utility and is not directed specifically at children.
Changes to this policy
Material changes to this policy or to Cookie Nope's data handling will be reflected in an updated policy and, where required, in the extension interface or Chrome Web Store listing.
Contact
Privacy questions, report-deletion requests and other 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.