Compare / I Don't Care About Cookies
One hides the banner. The other tells the site you already said no.
I Don't Care About Cookies is one of the most familiar names in this category. Daniel Kladnik built the original; Avast acquired it in September 2022. A separate, community-maintained fork — "I still don't care about cookies" — keeps an open-source version alive, with roughly 200,000 users, a 4.3 rating and listings in 23 languages, based on Chrome Web Store data checked in August 2026.
Both versions do the same core job: they hide the cookie banner with CSS after it loads. That's a real convenience, but it's a different job than what BannerBye does — and the difference matters for what the website on the other end actually receives.
| BannerBye | I Don't Care About Cookies | |
|---|---|---|
| How it works | Sends a reject signal before the banner renders | Hides the banner with CSS after it has already loaded |
| Tells the site you refused | ✓ — GPC + IAB TCF | — visually hidden only |
| Sends GPC signal | ✓ | — |
| Open source | ✓ MIT, fully public | Partial — community fork is open; the Avast-owned original's commercial handling is less transparent |
| Maker | Kreatrix B.V., independent | Avast/Gen (original); separate community maintainer (fork) |
| Zero telemetry | ✓ | Unclear for the Avast-owned version |
| Platforms | Chrome, Firefox, Edge, Safari (iOS, iPadOS, macOS) | Chrome, Firefox and other Chromium browsers |
| Fixes broken sites | ✓ self-healing, usually within hours | Depends on maintainer update cadence |
| Price | Free (Chrome, Firefox, Edge) · one-time €1.99 on Safari | Free |
Based on publicly available extension documentation, source code and Chrome Web Store listings, September 2026.
I Don't Care About Cookies wins on reach: it's been around longer, and the community fork covers 23 languages against BannerBye's current smaller rollout. If all you want is the banner gone visually, it does that reliably.
The gap is what happens after the banner disappears. Hiding with CSS doesn't tell the website anything — some sites interpret a missing response as consent once a timer runs out, which defeats the point of refusing in the first place. BannerBye answers instead, using the same GPC and IAB TCF signals regulators and ad-tech platforms already recognise, so the "no" is legally legible to the site, not just invisible to you.
The Avast acquisition is also worth knowing about if privacy is the reason you're looking at this category at all. Avast's Jumpshot subsidiary was found selling detailed user browsing data in 2020, reported publicly at the time. That's a fact about the company, not a claim about what this specific extension does today — but it's the kind of thing worth weighing when you're choosing a tool whose whole purpose is protecting your data.
Get BannerBye
The original extension was acquired by Avast in September 2022, a company with a publicly documented history of data collection — most notably the Avast/Jumpshot browsing-data sale, reported in 2020. A community-maintained fork, "I still don't care about cookies," keeps an open-source version going separately from Avast.
BannerBye is independent of both, publishes its full source code on GitHub, and sends zero telemetry.
Not on its own. GDPR requires an affirmative signal that consent was refused. CSS-hiding removes the banner from view, but the site itself may never receive an actual answer — some default to treating a missing response as acceptance after a timeout.
BannerBye sends the GPC header and an IAB TCF v2.2 reject string before the page renders — protocol-level answers the site's own consent system is built to understand.
Not recommended. Both extensions try to act on the same banner element, which can cause flicker or conflicting behaviour on some sites. Pick one.