DuckDuckGo Privacy Essentials is a free and open-source browser extension for Firefox, Chrome, Edge, and Opera that applies DuckDuckGo's web tracking protections inside the browser, and it is aimed at everyday users who want privacy protection without changing browsers, as well as developers who want to read and audit the code under the Apache-2.0 licence.

What it is

The project is the DuckDuckGo Privacy Essentials browser extension, maintained in the duckduckgo/duckduckgo-privacy-extension repository and written in JavaScript. It is published under the Apache-2.0 licence, with the licence text held in LICENSE.md. The codebase produces builds for Firefox, Chrome, Edge, and Opera, each distributed through its own browser store listing. The Safari counterpart is deliberately kept elsewhere: that code is an Xcode project at duckduckgo/privacy-essentials-safari, and the Safari extension is installed from the App Store rather than from the repository.

The concrete problem it solves is that tracking protection in a browser is usually either left at default settings or assembled from several separate blockers that the user has to configure and reconcile. DuckDuckGo Privacy Essentials puts those protections into one extension whose behaviour is documented on the Web Tracking Protections help page, which explains how each protection works and how the protections overlap across the company's browser extensions and apps. When a protection breaks a page, the user does not have to search for a support channel: the extension popup carries an anonymous "Report Broken Site" link, which replaces the usual routine of finding a contact form or posting in a forum to get a site fixed.

Key capabilities

• Web tracking protections delivered through extensions for Firefox, Chrome, Edge, and Opera, with an accompanying help page describing how the protections overlap.
• An anonymous "Report Broken Site" link in the extension popup, which is the documented route for reporting pages broken by protection.
• Store distribution across four channels: Firefox on addons.mozilla.org, Chrome on the Chrome Web Store, Edge on Microsoft Edge Add-ons, and Opera on addons.opera.com.
• Instructions for other Chromium-based browsers such as Vivaldi, which can generally install the Chrome build instead of waiting for a dedicated package.
• Repository CI through the GitHub Actions workflow at .github/workflows/checks.yml, whose badge is shown at the top of the README.
• A separate Safari Xcode project, duckduckgo/privacy-essentials-safari, for users on macOS who need the Safari build.
• Search-engine questions routed to the DuckDuckGo help pages rather than to the extension issue tracker.

Who uses it and how

• Individual users on Firefox, Chrome, Edge, or Opera who want tracking protection without adopting a different browser as their daily driver.
• Users of secondary Chromium-based browsers, such as Vivaldi, who install the published Chrome build because no separate listing exists for their browser.
• macOS users who want the same protections in Safari and therefore install the App Store build produced from the separate Xcode repository.
• End users reporting breakage directly from the popup, which feeds anonymous broken-site reports back to the maintainers.
• Contributors who hit the project through CONTRIBUTING.md, using the "Reporting bugs" section for defects and the "Development" section for build instructions.

Getting started

Install the extension from the store listing for the browser in use: Firefox on addons.mozilla.org, Chrome on the Chrome Web Store, Edge on Microsoft Edge Add-ons, or Opera on addons.opera.com. Building from source is covered in CONTRIBUTING.md, under the Development section.

How it compares

No list of paid products this project replaces is provided in the facts, and no comparable tools are named either, so it stands alone in this registry.

When to use it — and when not to

There is no server to operate here: the extension runs in the browser, so a self-hoster has no database, object storage, or SMTP to run and no hosted deployment to maintain, which makes adoption cheap but also means there is nothing to self-host in the first place. Do not pick this project if the requirement is Safari parity inside one repository, since Safari lives in a separate Xcode project, or if new features are needed, because the README states that new feature pull requests are not being accepted. The honest limitation is that the repository carries a large number of open issues at 198 and a README that stays thin on internals, so the practical support surface is bug fixes and the help pages rather than an expanding feature set.