Cookie banners, killed.
Before they load.

Browsers can block cookies, but cookie banners are the prompts asking for consent — not the cookies themselves. Block cookies and you'll still see 50 banners a day.

Firefox has a "Cookie Banner Reduction" feature, but it only covers a small list of domains in Strict mode. Chrome and Safari have nothing built in. "Do Not Track" is a deprecated header that virtually no site respects anymore.

BannerBye works on every site through three legally recognised signals: the GPC header, the IAB TCF reject string, and a pattern-based auto-click for custom banners. The banner never renders in the first place.

No. Safari's built-in privacy features are defensive — they limit cookies, hide trackers, and wipe history. None of them prevent cookie banners from appearing.

• Private Browsing wipes cookies after you close the tab, but you still see every banner while browsing.
• Block pop-ups stops JavaScript pop-up windows. Cookie banners are overlay-modals inside the page — different beast.
• Prevent Cross-Site Tracking limits how sites follow you, but doesn't change what they ask you.
• Block All Cookies doesn't hide banners; sites still display them. And many sites break (no login, no cart).
• Hide Distracting Items (iOS 18+) lets you manually hide a banner per website, but Safari doesn't tell the website you said no — which leaves a legal gray area.

BannerBye works one level above all of this. It sends a legal "no" via GPC and IAB TCF before the page renders. The banner never has to appear, and the website knows your answer.

Safari makes tracking harder. BannerBye makes the asking stop.

GDPR gives you the right to refuse non-necessary cookies. In practice, that right disappears the moment a banner appears — most people tap "accept" just to make it go away. BannerBye restores the right by answering for you, using three legally recognised signals.

GPC (Global Privacy Control) — a header that tells every website "I do not consent to the collection or sale of my personal data." Legally binding under CCPA and increasingly enforced across EU jurisdictions.

IAB TCF v2.2 reject string — the standard consent format used by most cookie banner providers. BannerBye generates a valid string that refuses every data-processing purpose the website might request.

Auto-click fallback — for the rare websites that ignore GPC and IAB. BannerBye finds the reject button and clicks it before you see it.

Because the answer arrives before the page renders, the website receives your privacy notice before it can collect anything. Strictly necessary cookies (login sessions, shopping carts) still work — that's how GDPR is designed. What stops is the surveillance hiding behind "personalised experience." No data collection, no tracking pixels, no notice you have to dismiss. Just the content you came for.

Under EU data protection law, you have the right to clear information about what data websites collect, why, and how long they may keep it. Most banners bury that information in a "settings" menu three taps deep. BannerBye helps by blocking every non-necessary tracker on the web — no menu, no manual review, no personal data leaking to third parties you never heard of. The blocking happens before the site knows you're there.

Every request for information from a website's cookie system gets a standard "no." The blocking is silent — you'll never see a notification, but the data you would have leaked stays with you. This gives you clear information about which cookies matter and lets data protection defaults handle the rest.

If a specific website blocks the extension or breaks, one tap on "Report broken site" helps our system fix it — usually within a day.

No. The extension reads the page in your browser only to find cookie banners. Nothing is sent to our servers — except the hostname when you tap "Report broken site," and only then.

The full source code is open and auditable on GitHub: github.com/BannerBye/BannerBye. Search the repo for "tracker" or "analytics" — you won't find any.

It handles the vast majority of cookie banners through three independent layers: GPC (legally binding in several US states), IAB TCF reject (used by most major European publishers), and a pattern-based auto-click for custom banners.

For the rare website where it doesn't work, one tap on "Report broken site" in the popup tells us. Our daily-updated rule list reaches every user within hours — no extension update needed.

Global Privacy Control. A web standard that tells every website you visit: "I do not consent to the sale or sharing of my data." It's legally binding in California, Connecticut, and Colorado, and increasingly enforced across the EU.

BannerBye adds the GPC header to every outgoing request your browser makes. You set your preference once. No clicks needed.

Yes. Free, no account, no ads, no upsell. The extension is MIT-licensed open source.

If we ever introduce paid features, the core (killing cookie banners on every site) will always stay free.

iPhone and iPad: yes, via Safari (App Store). Android: yes on Firefox via the Mozilla add-on. Chrome for Android doesn't support extensions — that's a Google limitation, not ours.

No — by design. BannerBye is a privacy tool, not an auto-accept tool. We always reject because that's what makes us a privacy tool in the first place.

If you'd rather always accept: don't install BannerBye. Just tap "OK" on banners like you already do — your browser already defaults to accept-friendly behaviour. Automating "accept" via an extension is also legally questionable under GDPR, since consent has to be freely given.

There is no toggle in the popup. The choice is made at install: install BannerBye, and your privacy preference is set to "reject" for every site, forever.

That's Apple's standard warning for every Safari extension that needs access to page content. It describes what the extension is technically capable of, not what BannerBye actually does. Chrome and Firefox show similar warnings for the same reason.

BannerBye reads the page structure to find cookie banners and taps "Reject all." It does not read passwords, credit cards, or browsing history. Full breakdown on the privacy policy.

Cookie banners started as a legal requirement — under GDPR, websites need permission before dropping tracking cookies. But most banners are designed to be annoying on purpose. A giant "Accept" button, a tiny "Reject" link, three menus deep before you can say no. Consumer-protection studies often show that a properly built banner would help users deliver a 90%+ rejection rate. Most banners deliver the opposite.

The reason is money. Every rejection means one less profile for online ad-targeting, one less data point sold to marketing networks. So banners are engineered to exhaust you until you accept. This is why the average person clicks "accept all" 40+ times a week — not because they want personalised ads, but because they want their time back.

BannerBye ends the exhaustion. It handles every type of cookie banner using the same three signals — GPC, IAB TCF, and pattern-based auto-click. One install, one preference, done. No more choosing between your privacy and your patience.