BannerBye app analytics for September 13

Cookie banners, killed. Before they load. Every website wants your "consent." The banners take over the screen, the "reject" button is hidden, and you click "accept" because you want to read the article. Then the next site asks again. 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 five 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. 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. Autoconsent ruleset — the open-source Autoconsent rules (by DuckDuckGo, MPL-2.0) describe the refuse path for hundreds of consent platforms, including the "settings → reject all" detour. Loaded only on pages that need them. 4. Consent-platform handlers — for the most common platforms (OneTrust, Cookiebot, Usercentrics, TrustArc, Didomi) BannerBye also answers the consent API directly. 5. Auto-click fallback — for custom-built consent UIs, the extension reads the visible button labels and clicks "Reject all" or "Necessary only" for you. This list updates without needing a new release. Where a site offers "consent or pay" instead of a free refuse option, BannerBye leaves that choice to you. —————————————————————— 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) ▸ Refuses on your behalf — 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.