Privacy Policy — Privacy Shield

01

What Privacy Shield does

Privacy Shield is a Chrome extension that automatically blocks tracking scripts, advertising pixels, and data broker requests on every website you visit. It uses Chrome's built-in declarativeNetRequest API to cancel network requests to known tracker domains before they leave your device.

The extension also displays a popup showing which trackers were blocked on the current page, your privacy score, and the categories of trackers detected. This information is derived entirely from local processing — no external service is involved.

02

Data we never collect

Privacy Shield does not collect any of the following:

Browsing history — URLs you visit are never recorded or transmitted anywhere.
Personal information — No name, email, IP address, or any identifying data is collected.
Page content — The extension never reads, accesses, or transmits the content of any webpage you visit.
Search queries — No search terms or form inputs are accessed.
Cookies or credentials — No cookies, passwords, or session tokens are read or stored.
Analytics or telemetry — No usage data, crash reports, or feature metrics are sent anywhere.

03

Data stored locally on your device

Privacy Shield stores two minimal pieces of data entirely on your device using Chrome's local storage APIs. Neither is ever transmitted off your device.

What	Where	Why	Cleared when
ON/OFF preference One boolean value	chrome.storage.local	Remember if you turned blocking on or off	You uninstall the extension
Matched rule IDs Integers, no URLs	chrome.storage.session	Show blocked tracker count in the popup	Tab closes or browser restarts

The matched rule IDs are integer numbers (e.g. 14, 37, 92) that correspond to tracker entries in the bundled block list. They contain no URLs, no site names, and no user-identifiable information.

04

Permissions explained

Privacy Shield requests four Chrome permissions. Here is exactly why each is needed:

declarativeNetRequest — Enables the 111 blocking rules. Without this, no tracker can be blocked.
declarativeNetRequestFeedback — Reads which rule IDs matched on the current tab so the popup can display blocked tracker names. No URLs or content are read.
storage — Stores the ON/OFF preference locally and caches matched rule IDs per tab temporarily.
tabs — Reads the active tab's URL to display the hostname in the popup header (e.g. "nytimes.com") and to key the session cache by tab ID.

05

No remote code, no external servers

Privacy Shield contains no remote code. All JavaScript is bundled inside the extension package. There are no external script tags, no CDN imports, no eval() calls, and no connections to any server operated by the developer.

The only network operations the extension performs are blocking outgoing requests from the websites you visit — it never makes outgoing requests of its own.

06

Third-party services

Privacy Shield does not integrate with, send data to, or use any third-party analytics, crash reporting, advertising, or data services. There are no SDKs, no tracking pixels, and no external dependencies in the extension code.

07

Children's privacy

Privacy Shield does not collect any personal information from anyone, including children under the age of 13. The extension is a passive blocking tool with no user accounts, no data submission, and no communication features.

08

Changes to this policy

If this privacy policy is updated, the new version will be published at this URL with an updated effective date. Since the extension collects no personal data, material changes are unlikely. Any change that affects data handling will be noted prominently at the top of this page.

09

Contact

Questions about this policy?

If you have any questions about how Privacy Shield handles data, open an issue on the GitHub repository or contact via the Chrome Web Store developer page.

Open GitHub Repository