Permissions

Ad blocker browser permissions explained

An ad blocker asks for broad browser permissions because it must see and cancel network requests before ads, trackers, and malicious domains load. ProBlocker uses those permissions only for local blocking. It does not collect browsing history, page content, form fields, passwords, URLs visited, search queries, or telemetry.

Why ProBlocker requests "Read and change site data"

Browsers use broad wording for extension permissions. For an ad blocker, this permission is required to see network requests on the pages you visit and cancel requests that match ad, tracker, pop-up, or malware-domain rules.

ProBlocker does not use this access to read page text, private messages, passwords, payment fields, or form entries. The extension checks request URLs against filter lists and blocks matching requests before they download.

Permission-by-permission breakdown

Permission Why it is needed What ProBlocker does not do
Read and change site data Inspect and cancel ad, tracker, pop-up, and malware-domain requests Read passwords, forms, private messages, or page content for collection
declarativeNetRequest Let Chromium browsers apply blocking rules internally Send browsing activity to ProBlocker servers
Storage Save local settings such as allowlisted sites and filter-list state Sync personal browsing data to a remote account
Alarms Schedule filter-list update checks Track when or where you browse

How filter-list updates work

ProBlocker periodically downloads public filter-list files such as EasyList and EasyPrivacy. These update checks fetch rule files; they do not include your browsing history, the pages you visit, or an account identifier.

For more detail, read what ProBlocker connects to or how manual filter-list updates work.

How to verify the claims

  1. Review the permissions your browser lists for the extension at install time and in its extension settings
  2. Read the data-use disclosure on the Chrome Web Store or Firefox Add-ons listing
  3. Open your browser's developer tools and inspect the extension's network requests: only filter-list downloads should appear
  4. Compare what you observe with the privacy policy

Reporting a vulnerability

If you discover a security vulnerability in ProBlocker, please report it privately through the contact page rather than in a public review or forum post.

Permissions FAQ

An ad blocker must inspect outgoing network requests before they finish loading. Broad browser permissions let ProBlocker compare each request against filter rules and cancel ad, tracker, pop-up, and malware-domain requests before content downloads.