BannerBye

Stop clicking cookie banners. BannerBye refuses them before they load — on every site, automatically. No account, no tracking, nothing to configure.

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 four independent signal layers, applied in order:

1. Global Privacy Control (GPC) — 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. Recognised by laws in California, Connecticut, Colorado, and increasingly across the EU.

2. IAB TCF v2.2 signal — when a site uses the Transparency & Consent Framework, BannerBye answers the consent call on your behalf with a "reject all" string, before the banner has a chance to render.

3. Consent-platform handlers — BannerBye recognises the most common consent management platforms (OneTrust, Cookiebot, Usercentrics, TrustArc, Didomi) and answers their consent API directly, before the banner renders.

4. Auto-click fallback — for sites with a custom-built consent UI that matches no known platform (many 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. This list updates daily without needing a new release.

——————————————————————

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.

▸ Your settings live on your iPhone or iPad, in Safari's storage. Nothing is sent to a server. ▸ The extension talks to one URL once a day, only to fetch a public list of cookie-banner button labels. No identifying information. ▸ Every permission is documented at bannerbye.com/privacy. ▸ No third-party advertising or tracking SDKs.

——————————————————————

WHAT SAFARI'S PERMISSION DIALOG MEANS

When you install BannerBye, Safari shows a standard permission dialog warning that the extension "can read sensitive information on web pages, including passwords, phone numbers, and credit cards, and your browsing history on the current tab's web page when you use the extension."

This text is identical for every Safari extension that accesses page content. It tells you what BannerBye is technically capable of, NOT what BannerBye 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) ▸ Recognises known consent platforms and auto-clicks "Reject all" — on known and custom banners

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" ▸ Track you across sites or build user profiles ▸ Run analytics, telemetry, or crash reporting

Full source code is open and auditable: github.com/BannerBye/BannerBye (MIT license).

——————————————————————

CONTROL

The popup gives you one-tap on/off, plus per-site pausing for the rare case a site doesn't work without consent. Your pause list stays local; clear it any time.

——————————————————————

WORKS WITH

▸ Safari on iPhone and iPad ▸ iOS 17 / iPadOS 17 and later

——————————————————————

LEARN MORE

Site: https://bannerbye.com Privacy: https://bannerbye.com/privacy Contact: hello@bannerbye.com

Cookie banners, killed. Before they load.