Privacy Policy
Effective date: August 11, 2026
This policy covers the Adblocker Zero browser extension (for Chrome, Firefox, Edge and Safari) and the website adblockerzero.com. The short version: the extension collects no data at all — and this page spells out exactly what that means.
The extension: zero data collection
Adblocker Zero does not collect, transmit, sell or share any data. Specifically, it has:
- No browsing history collection. The pages you visit are never recorded or sent anywhere.
- No telemetry or analytics. The extension contains no analytics library, no crash reporter, no usage tracking of any kind.
- No accounts. There is nothing to sign up for and no identifier that could link activity to you.
- No remote configuration or logging. We run no servers that receive anything from the extension.
- No paid whitelisting. No advertiser can pay to be let through, and no "acceptable ads" data program exists.
All blocking happens locally: filter rules are evaluated inside your browser, and your settings (on/off state, trusted sites, custom filters, blocked-request counters) are stored on your device using the browser's extension storage. If your browser syncs extension data between your own devices, that sync is operated by your browser vendor under its own policy — we never see it.
The one network request the extension makes
To keep blocking effective, the extension periodically downloads fresh copies of its filter lists (EasyList, EasyPrivacy, Peter Lowe's list and the uBlock Origin lists) from raw.githubusercontent.com, where the Ghostery project publishes maintained mirrors. This is a plain file download: it contains no personal information, no identifiers and no cookies. Like any web request, the server necessarily sees your IP address to deliver the file — GitHub's handling of such requests is described in its own privacy statement. You can trigger the same download manually with the "Update now" button.
Why the extension asks for broad permissions
Ad blocking technically requires a few sensitive-sounding browser permissions. Here is what each one is for:
| Permission | Why it's needed |
|---|---|
| Access to all websites | Ads appear on every site, so the blocker must be allowed to filter requests and hide ad elements everywhere. It reads pages only to apply filters — nothing is recorded. |
| declarativeNetRequest | Lets the browser itself block ad and tracker requests natively (Chrome, Edge, Safari) without the extension seeing your traffic. |
| webRequest (Firefox) | Firefox's blocking mechanism: requests are matched against filter rules locally and blocked before they load. |
| storage | Saves your settings and cached filter lists on your device. |
| tabs / webNavigation | Detects which site is open so the per-site toggle and badge counter work. |
| alarms | Schedules the daily filter-list refresh. |
| scripting / userScripts | Injects the cosmetic-filtering styles and anti-adblock scriptlets into pages, locally. |
This website
adblockerzero.com is a static site. It sets no cookies and hosts no advertising. It is served through Cloudflare, which processes standard technical request data (such as IP address) to deliver the site securely. We use Google Analytics 4 to count page views and installs in aggregate (pages viewed, referrer, approximate region, browser type); this data is never linked to your identity by us and is not used for advertising. The extension itself never loads any analytics, on any page, ever.
Children's privacy
Neither the extension nor the website is directed at children, and neither knowingly collects personal information from anyone, children included — the extension collects none at all.
Changes to this policy
If we ever change how the extension or website handles data, we will update this page and change the effective date above. Because the extension collects nothing, we expect changes to be rare.
Contact
Questions about privacy? Email [email protected].