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 extension manifest for declared permissions
  2. Search the source code for analytics libraries, telemetry calls, and remote logging
  3. Inspect background scripts for network requests outside filter-list updates
  4. Compare the published extension package to the public repository

Source code: github.com/theproblocker/adblocker.

Reporting a Vulnerability

If you discover a security vulnerability in ProBlocker, please report it privately through the repository security page rather than opening a public issue.

ProBlocker security reporting on GitHub →

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.