BannerBye 作者： Kreatrix B.V.
Cookie banners, killed before they load. Set your privacy once. BannerBye handles the rest — automatically, on every site. No accounts. No tracking.
扫码在 Android 版 Firefox 中打开此扩展
扩展元数据
屏幕截图
关于此扩展
🎥 Watch BannerBye in action: https://www.youtube.com/watch?v=9nqDeUcslK0
——————————————————————
Cookie banners, killed before they load.
Every website wants your "consent." Every page asks you to choose between accept, reject, or wade through a 30-page settings menu. The banners take over the screen. The "reject" button is hidden. You click "accept" because you want to read the article. Then the next site asks you again. And the next.
BannerBye stops it. Set your privacy once, and the extension handles every cookie banner before it reaches you — silently, automatically, on every site.
──────────────────────
HOW IT WORKS
BannerBye uses three independent signal layers, applied in order, so it works whether the site uses a known consent platform, a custom banner, or nothing at all:
──────────────────────
WHAT MAKES BANNERBYE DIFFERENT
▸ Privacy by absence. We collect nothing. No accounts. No analytics. No telemetry. No usage tracking. There is no business model that depends on knowing what you do online.
▸ Local-only data. The extension stores your settings on your own device, in your browser's storage. Nothing is sent to a server. Nothing leaves your machine.
▸ One network request — public data only. Once a day, the extension fetches a static JSON file from bannerbye.com containing updated button labels in different languages. The request contains no identifying information about you.
▸ Open about permissions. Every permission the extension uses is listed and explained on our privacy page. We use the minimum required to do the job.
──────────────────────
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, A/B tests, or feature flags.
▸ It does not phone home with crash reports or performance data.
▸ It does not contain third-party advertising or tracking SDKs.
▸ It does not sell, share, or rent any data — there is no data to sell, share, or rent.
──────────────────────
WHAT YOUR BROWSER'S PERMISSION WARNING MEANS
When you install BannerBye, your browser shows a permission warning along the lines of "this extension can read and change all your data on the websites you visit." That same warning appears for every extension that needs access to page content. It describes what BannerBye is technically capable of doing, NOT what it actually does.
What BannerBye actually does on every page:
▸ Reads the page DOM to detect cookie banners
▸ Sends a "no consent" signal (GPC, IAB TCF)
▸ Auto-clicks "Reject all" on custom consent UIs
What BannerBye does NOT do:
▸ Read passwords, credit cards, or phone numbers
▸ Read or store your browsing history
▸ Send anything to our servers, except hostname when you tap "Report broken site" (see below)
▸ Track you across sites or build user profiles
▸ Run analytics, telemetry, or crash reporting
The full source code is open and auditable: github.com/BannerBye/BannerBye (MIT license). You don't have to trust this listing — read the code.
──────────────────────
ONE EXCEPTION: REPORT BROKEN SITE
The popup has a "Report broken site" button. It is the one situation where data leaves your device, and only when you tap it.
If you tap it, BannerBye sends the following to our private inbox:
▸ The hostname of the tab (e.g. zalando.nl) — no URL paths, no query strings
▸ The BannerBye version you're running
▸ Your browser's User-Agent string
▸ Your IP address
▸ Anything you typed in the optional textarea
We use these reports to find and fix sites where BannerBye stops working. They are not shared, not joined with any other data, and not used for anything else.
This is a one-tap user action, not background telemetry. Full details at https://bannerbye.com/privacy
──────────────────────
CONTROL
The popup gives you one tap on/off, plus per-site pausing for the rare case a site doesn't work without consent (some video players, some paywalled articles). Your pause list is local; you can clear it anytime.
──────────────────────
LEGAL
BannerBye respects the Global Privacy Control standard, the IAB TCF v2.2 specification, and rejects on your behalf in line with GDPR and ePrivacy. The extension does not bypass authentication, paywalls, or DRM — it only answers the consent question that every site asks.
──────────────────────
LEARN MORE
Site: https://bannerbye.com
Privacy: https://bannerbye.com/privacy
Contact: hello@bannerbye.com
Cookie banners, killed. Before they load.
——————————————————————
Cookie banners, killed before they load.
Every website wants your "consent." Every page asks you to choose between accept, reject, or wade through a 30-page settings menu. The banners take over the screen. The "reject" button is hidden. You click "accept" because you want to read the article. Then the next site asks you again. And the next.
BannerBye stops it. Set your privacy once, and the extension handles every cookie banner before it reaches you — silently, automatically, on every site.
──────────────────────
HOW IT WORKS
BannerBye uses three independent signal layers, applied in order, so it works whether the site uses a known consent platform, a custom banner, or nothing at all:
- Global Privacy Control (GPC) — the extension adds the official "Sec-GPC" header to your browser's outgoing requests, telling websites you do not consent to the sale or sharing of your personal data. This is a public web standard, recognised by laws in California, Connecticut, and Colorado, and increasingly across the EU.
- IAB TCF v2.2 signal — when a site uses the Transparency & Consent Framework (the standard most major European publishers and ad tech vendors use), BannerBye answers the consent call on your behalf with a "reject all" string, before the banner has a chance to render.
- Auto-click fallback — for sites with custom-built consent UIs (most Dutch e-commerce, news, and forum sites), the extension reads the visible button labels and clicks the "Reject all" or "Necessary only" option for you. The list of recognised buttons is updated daily without needing a new release.
──────────────────────
WHAT MAKES BANNERBYE DIFFERENT
▸ Privacy by absence. We collect nothing. No accounts. No analytics. No telemetry. No usage tracking. There is no business model that depends on knowing what you do online.
▸ Local-only data. The extension stores your settings on your own device, in your browser's storage. Nothing is sent to a server. Nothing leaves your machine.
▸ One network request — public data only. Once a day, the extension fetches a static JSON file from bannerbye.com containing updated button labels in different languages. The request contains no identifying information about you.
▸ Open about permissions. Every permission the extension uses is listed and explained on our privacy page. We use the minimum required to do the job.
──────────────────────
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, A/B tests, or feature flags.
▸ It does not phone home with crash reports or performance data.
▸ It does not contain third-party advertising or tracking SDKs.
▸ It does not sell, share, or rent any data — there is no data to sell, share, or rent.
──────────────────────
WHAT YOUR BROWSER'S PERMISSION WARNING MEANS
When you install BannerBye, your browser shows a permission warning along the lines of "this extension can read and change all your data on the websites you visit." That same warning appears for every extension that needs access to page content. It describes what BannerBye is technically capable of doing, NOT what it actually does.
What BannerBye actually does on every page:
▸ Reads the page DOM to detect cookie banners
▸ Sends a "no consent" signal (GPC, IAB TCF)
▸ Auto-clicks "Reject all" on custom consent UIs
What BannerBye does NOT do:
▸ Read passwords, credit cards, or phone numbers
▸ Read or store your browsing history
▸ Send anything to our servers, except hostname when you tap "Report broken site" (see below)
▸ Track you across sites or build user profiles
▸ Run analytics, telemetry, or crash reporting
The full source code is open and auditable: github.com/BannerBye/BannerBye (MIT license). You don't have to trust this listing — read the code.
──────────────────────
ONE EXCEPTION: REPORT BROKEN SITE
The popup has a "Report broken site" button. It is the one situation where data leaves your device, and only when you tap it.
If you tap it, BannerBye sends the following to our private inbox:
▸ The hostname of the tab (e.g. zalando.nl) — no URL paths, no query strings
▸ The BannerBye version you're running
▸ Your browser's User-Agent string
▸ Your IP address
▸ Anything you typed in the optional textarea
We use these reports to find and fix sites where BannerBye stops working. They are not shared, not joined with any other data, and not used for anything else.
This is a one-tap user action, not background telemetry. Full details at https://bannerbye.com/privacy
──────────────────────
CONTROL
The popup gives you one tap on/off, plus per-site pausing for the rare case a site doesn't work without consent (some video players, some paywalled articles). Your pause list is local; you can clear it anytime.
──────────────────────
LEGAL
BannerBye respects the Global Privacy Control standard, the IAB TCF v2.2 specification, and rejects on your behalf in line with GDPR and ePrivacy. The extension does not bypass authentication, paywalls, or DRM — it only answers the consent question that every site asks.
──────────────────────
LEARN MORE
Site: https://bannerbye.com
Privacy: https://bannerbye.com/privacy
Contact: hello@bannerbye.com
Cookie banners, killed. Before they load.
评分 0（1 位用户）
权限与数据
更多信息