We collect nothing.
That's the policy.

The short version

• No accounts. No sign-up. Nothing to log into.
• No analytics. No telemetry. No usage tracking.
• No personal data leaves your browser. Ever.
• Your settings live on your own device, in your browser's storage.
• The extension talks to one URL, only to fetch a public list of cookie-banner button labels. That request contains no identifying information.

What BannerBye does

BannerBye is a browser extension that prevents cookie consent banners from interrupting you. It works in three ways, in this order:

• Global Privacy Control (GPC). The extension adds a Sec-GPC: 1 header to outgoing requests, telling websites you do not consent to the sale or sharing of your data. This is a public web standard and is added by your browser, not transmitted to BannerBye.
• IAB TCF v2.2 signal. When a site uses the IAB Transparency & Consent Framework, the extension answers consent calls on your behalf with a "reject all" string before the banner can render.
• Auto-click fallback. For sites with custom banners, the extension reads the visible button labels in the page and clicks the "reject" or "necessary only" option for you. This happens entirely inside your browser.

What BannerBye stores — and where

The extension stores a small amount of data, all locally, on your own device:

• Settings (extension on/off, per-site pause list) — saved in chrome.storage.sync, which means your browser may sync them across your own signed-in devices. BannerBye never sees this sync.
• Cached rules (the public list of button labels, see below) — saved in chrome.storage.local on your device only.

That's it. No browsing history, no visited URLs, no clicks, no timestamps, no IDs. None of this data is sent anywhere by the extension.

The one network request

Once a day, the extension fetches a static JSON file from https://bannerbye.com/rules.json. That file contains an updated list of "reject" button labels in different languages, so the extension keeps working when websites change their banners.

The request is a plain GET. It sends no extension ID, no user ID, no settings, no browsing data, no headers we control beyond what your browser adds for any HTTP request. The server logs the request the same way any web server logs any visitor: an IP address and a user agent string, retained briefly by the hosting provider for abuse protection. Those logs are not used by BannerBye for any purpose, are not joined with any other data, and are not shared.

What BannerBye does not do

• It does not read the content of pages you visit beyond the cookie banner itself.
• It does not collect or transmit form data, passwords, or anything you type.
• It does not run analytics scripts, A/B tests, or feature flags.
• It does not phone home with crash reports or performance data.
• It does not sell, share, or rent any data, because there is no data to sell, share, or rent.
• It does not contain third-party advertising or tracking SDKs.

Permissions explained

Browser extension stores show a list of permissions the extension requests. Here is why each one is needed:

• storage — to save your on/off setting and per-site pause list locally.
• tabs, activeTab — to know which site you are on so the popup can show the correct status and let you pause it on this site.
• declarativeNetRequest — to add the GPC header. This API runs entirely inside your browser; the extension does not see the requests it modifies.
• scripting — to inject the cookie-banner handler into the pages you visit.
• alarms — to schedule the once-a-day fetch of the public rules file.
• <all_urls> host permission — required because cookie banners can appear on any site.

Children

BannerBye does not collect data, so it does not knowingly collect data from children. The extension is suitable for any age permitted to use the underlying browser.

Changes to this policy

If we ever change what the extension does in a way that affects this page, we will update the "Last updated" date above and post a note on the homepage. We will not retroactively start collecting data from existing users.

Contact

Questions, doubts, corrections, or a direct request to delete data we don't have: hello@bannerbye.com.

Legal basis (for the EU readers)

Because BannerBye does not process personal data, GDPR's processing rules do not apply to the extension itself. Your browser's local storage is yours; you can clear it at any time by removing the extension. The hosting provider for bannerbye.com processes server logs as a "legitimate interest" controller for abuse protection, retained briefly and not shared.