Privacy Badger

What Is Privacy Badger?

You can block ads all day and still get followed. The bigger problem is third-party tracking—the same ad-tech and analytics companies watching what you read, shop for, and click across unrelated sites. Privacy Badger is built for that problem: stopping third parties from loading in your browser when they behave like cross-site trackers.

This extension is for people who want practical privacy protection without spending hours curating filter lists. It runs in your browser, blocks or restricts known tracking domains, and gives you quick per-site controls when something breaks. It’s also for users who care who’s behind the tool: it’s produced by the Electronic Frontier Foundation (EFF), a nonprofit known for digital rights work. (privacybadger.org)

What makes it distinctive is the behavioral angle. EFF positions Privacy Badger as different from classic list-based blockers because it’s designed to discover trackers based on behavior (and not only via hand-maintained domain lists). In practice today, that “learning” story has evolved over time, but the core goal remains: reduce third-party surveillance rather than merely hide ads. (eff.org)

Privacy Badger Features and Performance

Privacy Badger’s main job is blocking (or restricting) third-party resources that appear to track you across sites. According to EFF’s own technical design notes, it watches for tracking behaviors such as third parties receiving or setting cookies, using certain kinds of “supercookies” (like HTML5 local storage), performing specific fingerprinting-related JavaScript API calls, or using the Beacon API—then treats repeated cross-site behavior as “cross site tracking.” Once a domain crosses a threshold, Privacy Badger can escalate how it handles that domain. (github.com)

Instead of only offering “block” vs “allow,” Privacy Badger uses a three-state control model in its UI: block, cookie block (a middle mode meant to reduce breakage), and allow. In “cookie block” mode (the “yellow list” / cookie-block list behavior), Privacy Badger may still allow the resource to load while stripping its access to cookies/local storage and trimming or removing the referrer header depending on request type. This is a key design choice: it tries to keep pages functional while still cutting off obvious cross-site identifiers. (github.com)

Privacy Badger also pushes preference signals that are meant to reduce tracking at the policy layer, not just the technical layer. The Chrome Web Store listing says Privacy Badger sends Global Privacy Control (GPC) and Do Not Track (DNT) signals. EFF’s site also states that Privacy Badger sends GPC alongside DNT by default. Whether a site honors those signals is up to the site (and applicable law), but the extension at least makes sure the signals are emitted.

On performance: Privacy Badger’s own EFF one-pager explicitly claims that blocking trackers can also block many ads and “speeds up your connection to most websites.” That’s plausible because fewer third-party requests usually means less work for the browser, but it’s not a benchmark claim you should treat like a lab result. In real-world use, any speed change will depend on how tracker-heavy the sites are and what else you’re running (built-in browser protections, other extensions, DNS blocking, etc.). (eff.org)

Compatibility is primarily “where the extension runs.” EFF’s own one-pager lists availability for Chrome, Firefox, Firefox for Android, Edge, and Opera. This is an extension—not a VPN, not a system-wide network filter—so its protection is scoped to the browser(s) where you install it. If you’re expecting device-wide coverage (all apps, all browsers), this isn’t that.

Pricing and Plans

Privacy Badger’s pricing is simple: it’s free. (This matches your verified database spec.) (privacybadger.org)

There are no paid tiers, subscriptions, or multi-device plans to compare because it’s not a commercial SaaS product. Installation is done through browser extension channels (for example, Chrome Web Store for Chrome) and through EFF-provided links for some other browsers. (privacybadger.org)

Refund policies don’t apply in the normal “subscription product” sense because there’s nothing to buy.

Privacy and Security Assessment

Who runs it / jurisdiction: Privacy Badger is made by EFF. EFF is a US-based nonprofit organization; that implies US jurisdiction and US legal environment considerations (subpoenas, court orders, etc.). That said, Privacy Badger is a browser extension, not a hosted VPN service holding centralized traffic logs. The more relevant question is usually: what data does the extension send out, and can it be audited? (privacybadger.org)

Open-source posture: Privacy Badger’s code is published publicly, and its README states it’s licensed under GPL v3 or later. Open source doesn’t automatically mean “secure,” but it does make third-party review possible and makes supply-chain verification easier than closed-source extensions.

Remote configuration / update behavior: EFF’s own site states that after installation, browsers may connect to Fastly IPs on startup because EFF uses Fastly as a CDN, and Privacy Badger checks a configuration resource (pbconfig) to keep information fresh even when the extension itself hasn’t been updated. EFF also states it does not set cookies or retain IP addresses for those queries. This is an important transparency point: some network activity is expected, and EFF documents why it happens. (privacybadger.org)

How it decides what to block: EFF’s design document describes a heuristic approach: the extension observes third-party tracking behaviors and, once a threshold is reached, blocks the tracker—except for domains on a “yellow list,” where it cookie-blocks to reduce breakage. It also allows users to override decisions with per-domain rules using its slider UI. The design doc also describes detection for things like pixel cookie sharing and Beacon API usage. (github.com)

Notable controversy / change in approach: Privacy Badger’s “learning” approach has had safety concerns. Reporting from 2020 described EFF changing defaults so the local-learning approach would be off by default due to a technique that could be abused to track users (a fingerprinting risk tied to per-user learned lists). A later EFF GitHub discussion explains that the extension has always been responsible for learning, but when/where learning happens has changed over time, and points readers to EFF’s “Badger Swarm” evolution summary. Bottom line: the project has adjusted design choices in response to security research and abuse risk, and that history matters when you evaluate the “it learns” marketing line.

Audits / independent verification: In reputable public materials reviewed for this write-up, there wasn’t a clearly documented, named third-party security audit specific to Privacy Badger that could be cited as an “audit completed on date X by firm Y.” Because that’s uncertain, it’s not claimed here.

Strengths and Limitations

Strengths

• Focused on tracker behavior, not just ads. EFF’s documentation emphasizes blocking third-party trackers (and it often blocks ads as a side effect). That’s the right priority if your goal is less surveillance rather than cosmetic ad removal. (privacybadger.org)

• Practical breakage controls. The three-state per-domain controls (block / cookie-block / allow) exist specifically to balance privacy with usability, and EFF documents the “yellow list” approach as a breakage-reduction mechanism. (github.com)

• Sends GPC and DNT signals. Even when tracking scripts are blocked, preference signals can matter for compliance workflows and for sites that choose to respect them; Privacy Badger explicitly sends both.

• Open-source codebase. GPL licensing and public development on GitHub make it reviewable and easier to scrutinize than opaque extensions.

Limitations

• It’s not system-wide. It’s a browser extension, so it won’t stop tracking inside other apps or at the network level.

• You will hit breakage sometimes. EFF’s own FAQ-style content includes guidance for disabling the extension per-site and reporting broken sites—because breakage can happen when third-party resources are blocked. (privacybadger.org)

• Not a silver bullet for first-party tracking. Privacy Badger targets third-party trackers. If you’re logged into a service, that service can still track what you do on its own properties through normal account/server-side mechanisms.

• Its learning story has changed over time. Past changes to defaults were driven by concerns about abuse and fingerprinting risk. If you installed it expecting fully local, personalized learning by default, that expectation may not match the current design philosophy.

Who Should Use Privacy Badger?

Good fit if you are:

1. A “set it and forget it” privacy user who mainly wants to reduce third-party tracking across the web, with minimal configuration.
2. Someone who values nonprofit stewardship and open source and prefers a tool with published design documentation and a public code repository. (privacybadger.org)
3. A user who wants GPC/DNT sent automatically without relying on per-site settings or obscure browser flags.

Not a great fit if you are:

1. Trying to block all ads everywhere with maximum aggressiveness. Privacy Badger may block many ads, but its stated purpose is tracker blocking; dedicated list-based ad blockers are typically the primary tool for strict ad removal.
2. Needing mobile, system-wide protection across apps. This is an extension and won’t cover non-browser traffic; coverage depends on whether your mobile browser supports the extension (EFF lists Firefox for Android, not “all mobile browsers”).
3. Highly sensitive about browser extension permissions. Privacy-protection extensions often need broad access to function; if you’re unwilling to grant an extension wide site access, you’ll have a hard time getting meaningful tracker blocking at all.