Last updated: July 30, 2026
ByeBar is built by Matt Ivan. This policy describes how the extension handles information on your device.
Summary
Nothing is sent to ByeBar. ByeBar does not collect, transmit to the developer, or sell your personal data. There is no telemetry.
What is stored on your device
ByeBar saves settings using the browser's device-local extension storage API. This includes:
- Whether blocking is enabled globally or overridden for a site
- Per-site feature overrides for cookie decline, newsletter overlays, and optional legal dialogs
Settings, including browsing hostnames used for site overrides, are not placed in browser sync. The Local diagnostics preference also stays in device-local extension storage. When diagnostics are enabled, up to 100 rule/result decisions are kept only in the current page's memory. They contain no page text, are never sent to the developer, and clear on reload, when diagnostics are disabled, or when you clear them.
What ByeBar does on web pages
ByeBar runs content scripts in eligible top-level pages to hide intrusive overlays and to click confirmed decline/accept buttons when you have those options enabled. Embedded frame contents are not processed. It evaluates limited page text locally to recognize an overlay, but does not store that text, use it for analytics, intercept network traffic, or block ads.
Third parties
ByeBar does not embed third-party analytics or advertising SDKs. Optional links in the popup (for example, filing a GitHub issue) open only when you click them and do not include the active site. The public website is hosted on GitHub Pages. Cloudflare may provide DNS/proxying and site-delivery analytics when enabled; those services are separate from the extension and never run in extension pages.
Contact
Questions or concerns: Support (GitHub Issues linked from that page)