Ad Block Pro
Privacy Policy
Last updated: March 8, 2026
TL;DR: Ad Block Pro does not collect, share, or sell any personal data. All data stays on your device.
Overview
Ad Block Pro ("we", "our", "the extension") is committed to protecting your privacy. This policy explains what data we collect, how we use it, and your rights.
Data We Collect
The extension stores the following data locally on your device only:
- Blocked request counts: Aggregate numbers of blocked ads, trackers, and scripts (e.g., "150 ads blocked today")
- Whitelist settings: Domains you choose to allow ads on
- Extension preferences: Toggle state, UI settings
- License status: Whether your license is active (verified locally via Gumroad API)
Data We Do NOT Collect
- Browsing history or specific URLs visited
- Personal information (name, email, address)
- Page content or search queries
- Passwords or form data
- Device identifiers or fingerprints
Third-Party Services
The only external service the extension communicates with is:
- Gumroad (api.gumroad.com) — solely for license key validation when you activate a Pro license. Only the license key you enter is sent. No browsing data is shared. See Gumroad's Privacy Policy.
- Filter list CDN — We use pre-bundled ad-blocking filter lists (EasyList, EasyPrivacy). No external requests are made for filter updates.
Permissions Explained
- declarativeNetRequest: Required to block ad and tracker network requests
- declarativeNetRequestFeedback: Required to count and display how many requests were blocked
- storage: Required to save your settings and blocked ad counts locally
- tabs: Required to show per-tab blocking stats and badge counts
- activeTab: Required to access the currently active tab when you interact with the extension
- webNavigation: Required to reset the badge counter when you navigate to a new page
- host permissions (<all_urls>): Required for content scripts to remove ad containers and bypass timers on all websites
Data Security
All data is stored locally using Chrome's built-in encrypted storage APIs. We employ Content Security Policy headers, HTTPS-only external communication, and no use of eval() or dynamic code execution.
GDPR & CCPA Compliance
Since we do not collect personal data, GDPR and CCPA requirements for data access, deletion, and portability are automatically satisfied. No consent is required for the minimal local-only data we store.
Children's Privacy
The extension does not knowingly collect data from children under 13.
Changes to This Policy
We may update this policy to reflect changes in our practices. Significant changes will be communicated through the extension's update notes.
Contact
For questions about this privacy policy, contact: ja358288@gmail.com
Comments
Post a Comment