Compare / Hush
One tool for one browser, updated on an app-release schedule. The other works everywhere and fixes itself within hours.
Hush, from solo developer Oblador AB, is a well-regarded Safari content blocker for iOS, iPadOS and macOS — open source under MIT, no known telemetry, and a 4.4 rating on the App Store. It's built on Apple's Content Blocker API: a declarative, no-JavaScript-runtime approach that's fast and battery-friendly.
That same API is also what limits it. Content blockers hide elements — they don't send a consent signal — and their rules can only be updated by shipping a new version of the app through App Store review.
| BannerBye | Hush | |
|---|---|---|
| How it works | Sends a reject signal before the banner renders | Hides banner elements via Apple's Content Blocker API |
| Sends GPC signal | ✓ | — not supported by the Content Blocker API |
| Open source | ✓ MIT | ✓ MIT |
| Zero telemetry | ✓ | ✓ none known |
| Platforms | Chrome, Firefox, Edge, Safari (iOS, iPadOS, macOS) | Safari only (iOS, iPadOS, macOS) |
| Rule updates | Self-healing — reported sites fixed automatically, usually within hours | Only via a new App Store release — no remote rule fetch |
| Maintained by | Kreatrix B.V., a product company | A solo developer |
| Price | Free (Chrome, Firefox, Edge) · one-time €1.99 on Safari | One-time App Store purchase |
Based on publicly available extension documentation, source code and App Store listings, September 2026.
Hush is a genuinely good Safari tool, and its use of Apple's native Content Blocker API is a sound engineering choice — declarative rules are fast and don't run a JavaScript engine on every page. If you only ever use Safari, it's a reasonable pick.
The catch is exactly that API's constraint: it can hide, not answer, and its rule list can only change when a new version of the app ships through App Store review. Some user reviews describe reported sites staying broken for months, which tracks with a solo maintainer working within that release cycle — not a criticism of effort, just a structural limit of the platform and the team size. BannerBye's self-healing pipeline exists specifically to remove that lag: a broken site is usually fixed within hours, not app-store cycles, and the same preference works across every browser you actually use, not just Safari.
Get BannerBye
No. Hush is built on Apple's Content Blocker API and only runs in Safari, on iOS, iPadOS and macOS.
BannerBye covers Chrome, Firefox and Microsoft Edge as well as Safari, so the same preference follows you across every browser and device.
Hush's rules can only update through an App Store app release, since Apple's Content Blocker API doesn't support fetching rules remotely — there's no way to push a fix without shipping a new version of the app.
BannerBye's rule list updates independently of any app release: a reported site is reviewed and, once approved, the fix reaches every user automatically, usually within hours.
No. Hush works by hiding banner elements through Apple's declarative content-blocking rules, which don't support sending custom headers like GPC.
BannerBye sends the GPC header on every outgoing request, in addition to the IAB TCF reject string.