PrivacyShield Privacy Policy

Our Promise  
PrivacyShield has no server. It makes zero network requests, has no analytics, no telemetry, and no cloud sync. Everything stays on your device, in your browser's local storage. 

What We Store
PrivacyShield stores only the following, locally on your device:

• Your preferences (blur intensity, idle timeout, theme)

• Per-site settings (which sites have auto-detect on, CSS selectors for Pick & Blur)

• A local activity log (event counts and category names only — never the actual sensitive values you blurred or copied)

• An optional idle-lock PIN, stored as a PBKDF2-SHA-256 hash with a random salt — the plaintext PIN never touches storage

What We Never Store

• The contents of detected sensitive items (card numbers, SSNs, API keys, emails)

• Clipboard contents

• Browsing history, full URLs, or query strings

• Any identifier that could track you across sessions or devices

Network Activity
Zero. PrivacyShield makes no fetch, XMLHttpRequest, WebSocket, or sendBeacon calls. All fonts and icons are bundled locally. There is no update server, analytics endpoint, or error reporter. You can verify this yourself: open Chrome DevTools → Network tab, use any feature — nothing goes out. 

Permissions Explained

• storage — Save preferences and settings locally on your device

• activeTab — Act on the tab you explicitly trigger PrivacyShield on

• scripting — Inject the blur stylesheet into pages

• clipboardWrite — Clear or redact the clipboard when you copy a secret (Clipboard Guard feature, off by default)

• alarms — Wake the extension at start/end of Scheduled Privacy windows

• all URLs (host permission) — Required so PrivacyShield works on every site you visit; page content is only read locally to apply the blur features you enable

Your Control
Open the extension → Options → Privacy Audit to see exactly what is stored, export the activity log as JSON, or wipe all PrivacyShield data from your device in one click. 

Contact - Questions? Email: supportprivacyshield@gmail.com

Changes - This policy changes only when the extension's behaviour changes. Material changes are documented in the extension's changelog. 

Last updated - June 2026