One-Click Cookie Rejector — Privacy Policy

Last updated: June 20, 2026

1. Overview

One-Click Cookie Rejector is a browser extension that automatically detects and rejects cookie consent banners. This privacy policy explains what data the extension collects, how it is used, how it is stored, who it is shared with, and how you can control it.

2. Data We Collect

2.1 Local Data (stored on your device only)

The following data is stored exclusively in your browser's local storage and never leaves your device:

• Extension settings: whether the extension is enabled or disabled, strict mode toggle, hide-only mode toggle, notification preferences, and debug mode toggle.
• Whitelist and blacklist: domain names you have added to your skip or always-process lists. These are domain names only (e.g., "example.com") — no URLs, page content, or personal identifiers.
• Usage statistics: a count of how many cookie banners have been rejected or hidden, and the domain names where this occurred. No page content, browsing history, URLs beyond the domain name, or timestamps beyond the date of last interaction are stored.

2.2 Data Transmitted for the Optional Pro Upgrade

The core cookie detection and rejection engine does not transmit any data. However, if you voluntarily choose to purchase the optional Pro upgrade, the following data is transmitted:

• Email address: sent securely via HTTPS POST to our backend server for payment processing and license verification.
• Full name: sent securely via HTTPS POST to our backend server for payment processing.
• License token: a cryptographic token stored locally and sent via HTTPS POST to verify your Pro status. This token is generated from your email and a server-side secret — it does not contain your browsing data.

No other data is collected or transmitted at any time.

3. How Data Is Used

• Local settings are used solely to control how the extension behaves on websites you visit.
• Whitelist/blacklist are used to determine which websites should be skipped or always processed.
• Statistics are used to display counts in the extension popup and options page. They are not used for analytics, advertising, or any purpose beyond showing you a local counter.
• Email and name (Pro only) are used exclusively for payment processing via PayBlis and generating your license token. They are not used for marketing, analytics, or any other purpose.

4. How Data Is Stored

• Local data is stored in your browser's chrome.storage.local and persists until you uninstall the extension or clear your browser data.
• Server-side data (Pro only): your email, name, license token, payment plan, and payment status are stored in a JSON file on our backend server. This data is retained for as long as your license is active.
• Statistics stored locally are automatically pruned to keep only the 100 most recently processed domains to prevent unbounded storage growth.

5. Who Data Is Shared With

5.1 No Sharing for Core Features

The core cookie detection and rejection engine does not share any data with anyone. All local data stays on your device.

5.2 Third Parties Involved in Pro Payments

If you purchase the Pro upgrade, the following third parties are involved:

• PayBlis (pay.payblis.com): Payment processor. Your email and name are sent to PayBlis to process your payment. PayBlis handles payment card data directly — this extension never sees, collects, or stores your payment card information. Refer to PayBlis's privacy policy for their data handling practices.
• Our backend server (one-click-cookie-rejector.onrender.com, hosted on Render.com): Receives your email and name via HTTPS POST to create the payment, verify your license, and check your subscription status. This server stores your email, name, license token, plan type, and payment status.

No other third parties receive any data from this extension.

6. Data Security

• All data transmitted to our backend server uses HTTPS (TLS encryption).
• Sensitive data (email, name) is transmitted in the POST request body, never in URLs or headers.
• License tokens are signed with HMAC-SHA256 to prevent tampering.
• Our backend server does not log request bodies containing user data.

7. Data Retention and Deletion

• Local data: Deleted when you uninstall the extension or clear your browser data.
• Server-side data (Pro only): Your email, name, and license data are retained on our server for as long as your license is active. If you wish to have your data deleted from our server, contact us at the support email below and we will delete it within 30 days.

8. Your Rights and Control

• You can disable the extension at any time using the toggle in the popup.
• You can clear all locally stored data by going to chrome://extensions, finding One-Click Cookie Rejector, clicking "Details", and then "Clear data".
• You can disable notifications in the extension settings.
• The Pro upgrade is entirely optional — all core features work without it and without transmitting any data.

9. Children's Privacy

This extension is not directed at children under 13. We do not knowingly collect personal information from children.

10. Changes to This Policy

We may update this privacy policy from time to time. Changes will be posted on this page with an updated date.

11. Contact

For questions or data deletion requests, contact us at: oneclickcookierejector@gmail.com