01
Overview
ShieldBlock Pro does not collect, transmit, or sell any personal data — ever. All blocking, filtering, and statistics happen locally on your device. There is no backend server, no analytics, and no telemetry of any kind.
$ shieldblock --audit privacy✓ telemetry ............... none✓ external servers ........ none✓ trackers in this page ... 0✓ data collected .......... 0 bytes✓ processing .............. 100% on-deviceaudit passed — nothing leaves your browser
ShieldBlock Pro ("the Extension") is a browser extension for Google Chrome and Mozilla Firefox that blocks advertisements, trackers, cookie banners, and streaming-platform ads. This Privacy Policy describes how the Extension handles information when you use it.
This policy is written to be readable, complete, and verifiable: every category of stored data and every outbound network request the Extension can make is listed on this page. By installing or using ShieldBlock Pro, you agree to the practices described here. Curious who builds it? About the developer & the project is at the end of this policy.
02
Data Stored on Your Device
ShieldBlock Pro stores a small amount of non-personal, operational data using the browser's built-in storage APIs (chrome.storage.local and IndexedDB). This data exists only on your device, is accessible only to the Extension, and is never transmitted anywhere.
| Data | Purpose | Storage |
|---|---|---|
| Settings & preferences | Remember which features are enabled (YouTube, Twitch, cookie blocking, anti-fingerprinting, etc.) | local only |
| Block statistics | Counts of blocked ads/trackers and estimated time saved, shown in the popup; daily counts are kept for 30 days to draw the 7-day chart | local only |
| Whitelist & per-site rules | Sites you exclude from blocking, and your per-site allow/block matrix choices | local only |
| Filter list cache | Cached copies of downloaded filter lists so they don't need to be re-fetched on every browser start | local only |
| Custom rules | Element-picker selections, filters you type yourself, and custom filter list subscriptions you add | local only |
| Diagnostic log | A log of extension events (sync results, errors) shown in the popup's Log tab for troubleshooting; stored in on-device IndexedDB and never sent anywhere | local only |
None of the above is tied to your identity, browsing history, or any other personal attribute, and none of it leaves your machine.
03
Data Never Collected
ShieldBlock Pro does not collect, store, or transmit any of the following — not anonymized, not aggregated, not at all:
- Browsing history or URLs you visit
- Page content, keystrokes, or form input
- IP address or geolocation data
- Device identifiers or hardware fingerprints
- Usernames, passwords, or authentication tokens
- Cookies or session data from sites you visit
- Crash reports, telemetry, or usage analytics
- Which ads were blocked on which sites
The Extension has no backend server, no analytics pipeline, no telemetry endpoint, and no remote database. There is no account system and no usage tracking of any kind.
04
Permissions Explained
ShieldBlock Pro requests the following browser permissions. Each one is required for a specific blocking feature; none is used to collect data.
| Permission | Why it's needed |
|---|---|
| storage | Save your settings, whitelist, statistics, and filter cache locally in your browser |
| declarativeNetRequest | Block ad and tracker requests using the browser's built-in, privacy-preserving blocking engine — rules are evaluated by the browser itself, so the Extension never needs to read your traffic |
| declarativeNetRequestFeedback | Count how many requests were blocked on the current tab so the badge and statistics work; this match information stays in the browser |
| scripting | Inject the cosmetic filtering CSS and ad-removal scripts that hide ad elements on pages |
| tabs | Read the current tab's address so the popup can show per-site controls and apply your whitelist |
| webNavigation | Detect page navigations so cosmetic filters are applied at the right moment and per-page counters reset |
| alarms | Schedule the 12-hour filter list refresh, the 6-hour safe-browsing refresh, and pause timers |
| contextMenus | Provide the right-click "Hide this element" picker |
| host_permissions | <all_urls> — ads and trackers appear on every site, so blocking rules and content scripts must be able to run everywhere. Scripts only look for ad elements; they do not read or report page content. |
05
Storage, Retention & Deletion
All Extension data lives in chrome.storage.local and on-device IndexedDB. It is not synced to any server, cloud, or browser account. Retention is bounded by design: daily statistics older than 30 days are pruned automatically, and filter caches are overwritten on each sync.
You are in full control and can delete everything at any time:
- Reset statistics — from the Extension popup, reset block counts whenever you like
- Clear the log — the popup's Log tab can wipe the on-device diagnostic log
- Uninstall — removing ShieldBlock Pro (chrome://extensions → Remove) permanently deletes all of its local data, including IndexedDB
06
Network Requests & Third-Party Services
The Extension never talks to a ShieldBlock server — none exists. The complete list of outbound connections it can make is below. All of them are standard HTTPS GET requests for public files, carry no user identifiers or browsing data, and use conditional caching (ETags) so unchanged lists aren't re-downloaded.
Filter list updates (every 12 hours)
Blocking rules are downloaded from public, community-maintained filter projects:
- EasyList, EasyPrivacy & Fanboy Social — easylist.to and easylist-downloads.adblockplus.org
- uBlock Origin filter lists (filters, annoyances, badware, unbreak) — github.com/uBlockOrigin via raw.githubusercontent.com
- AdGuard filter lists (base, tracking protection, annoyances, regional) — adguard.com via filters.adtidy.org
- Peter Lowe's Ad and tracking server list — pgl.yoyo.org
- Regional & specialty lists (French, German, Russian, Polish, Korean, Turkish, Chinese, Spanish, Italian, Dutch, Japanese, Arabic, Czech/Slovak, Indonesian, Hebrew, Vietnamese, Nordic, NoCoin anti-mining, Anti-Adblock Killer) — hosted on the projects' public GitHub repositories and easylist-downloads.adblockplus.org
Safe Browsing feeds (every 6 hours, optional)
The malware/phishing warning feature downloads two public threat feeds: URLhaus by abuse.ch (malware distribution domains) and OpenPhish (phishing domains). Checking happens entirely on your device against the downloaded list — the URLs you visit are never sent to anyone. This feature can be switched off in settings.
User-initiated requests only
- Custom filter lists — if you subscribe to an extra filter list URL, the Extension fetches that URL on the same schedule
- Update check — the popup's manual "check for updates" fetches a small version file from GitHub (raw.githubusercontent.com)
These third-party servers see only what any web server sees for a routine file download (your IP address and browser User-Agent); their own privacy policies govern those connections. The Extension adds no identifiers of its own to any request.
07
Your Rights (GDPR / CCPA)
EU/EEA & UK (GDPR): The Extension processes no personal data on any server, so there is nothing held about you to access, rectify, export, or erase remotely. Everything the Extension knows lives on your device under your direct control, and the deletion options in section 05 satisfy erasure instantly and completely. The data controller is Bronson Bissell — see About the Developer.
California (CCPA/CPRA): ShieldBlock Pro does not sell or share personal information, and never has. No opt-out is necessary because there is nothing to opt out of.
ShieldBlock Pro doesn't just respect privacy signals — it can send them for you: the privacy settings include attaching Global Privacy Control (GPC) and Do Not Track headers to your browsing.
08
Children's Privacy
ShieldBlock Pro does not knowingly collect any data from anyone, including children under the age of 13. Because no personal data is collected from any user of any age, the Extension complies with the Children's Online Privacy Protection Act (COPPA) by design.
09
Policy Changes
If this Privacy Policy is updated, the new version will be published at this URL with an updated "Last updated" date at the top of the page. Continued use of the Extension after a policy update constitutes acceptance of the updated terms.
This policy will never be materially changed to permit collection of personal data without prominent advance notice — and any such change would be a different product, not an update.
10
Contact
Questions or concerns about this Privacy Policy can be directed to the developer:
- Via the Chrome Web Store support page for ShieldBlock Pro
- Directly at guns.lol/therealzombiekil
- On GitHub: github.com/therealzombiekill
11
About the Developer & the Project
Who we are
Bronson Bissell — independent developer. ShieldBlock Pro is designed, built, and maintained by one person, not a company. There are no investors, no ad-tech partnerships, and no "premium data tier". For the purposes of data-protection law (see Your Rights), Bronson Bissell is the data controller for the Extension — although, as this policy explains, no personal data ever reaches the developer.
The project started as a personal tool to make YouTube and Twitch watchable again, and grew into a full content blocker: 30+ auto-updating filter lists, cookie consent auto-reject, anti-fingerprinting, URL tracking-parameter cleaning, and ad handling for streaming platforms — all of it running entirely inside your browser.
ShieldBlock Pro is free, with no account and no paywall. That is also the honest answer to "why should I trust this policy": there is no business model that needs your data. A privacy tool that monetized browsing data would defeat its own purpose, so the Extension is engineered to function with nothing to collect. You can reach the developer at guns.lol/therealzombiekil or on GitHub.