Privacy Badger reaches Safari on Mac, not yet on iPhone
EFF’s tracker-blocking extension is available for Safari on macOS, starting with Safari 26.5. Check compatibility before installing, and use a site-specific exception if something stops working.

Generated image · SecuFocus
At a glance
Key points
Use Safari on a Mac? EFF now offers Privacy Badger for that browser, requiring Safari 26.5 or later. The release does not cover Safari on iPhone. The extension targets online tracking; if it breaks a site, EFF provides a way to disable it for that site alone.
Check which Safari, on which device
The Electronic Frontier Foundation (EFF) announced on October 19 that its free Privacy Badger extension is now available for Safari on macOS. It requires Safari 26.5 or later. Check the version on the Mac where you plan to use it before looking for the extension.
The announcement does not extend to every Apple device. EFF says it will look into Safari on iOS after addressing early feedback on the Mac release. The post offers neither an available iPhone version nor an iPhone release date.
What it adds, according to EFF
EFF describes Privacy Badger as an addition to Safari’s built-in privacy features. According to the organisation, the extension prevents trackers from loading that Safari’s default browsing mode still allows to load. Some embedded videos, comment sections and other widgets may be replaced with click-to-activate placeholders.
That can visibly change a page: an element waiting for your click is not necessarily broken. These are EFF’s descriptions. SecuFocus has not installed this first Safari release or measured its blocking performance. They are not grounds for promising anonymous browsing.
Keep exceptions limited to the affected site
Start from EFF’s official announcement and its Mac App Store link. Once the extension is enabled, try a few sites you regularly use, including ones with sign-in or embedded video. Leave your existing privacy protections in place during the check.
If a site stops working properly, EFF points to two controls in the extension’s popup: “Disable for this site” and “Report broken site”. Use the site-specific exception rather than switching blocking off everywhere. Before adding more extensions, check whether that one adjustment resolves the problem.
Check and explore
Sources for this article
Numbers connect each reference to the passages that use it. Dates show when the documentation was consulted.
This article draws on the sources above. The exercises are for you to try on your devices; SecuFocus does not present them as tests carried out by its editorial team. Interfaces and features can change. Method and corrections.
Cite this article
Keep this reference with the article when you save or share it.