Last updated: June 2026 · Effective immediately upon installation
Short version: Chat Privacy Shield does not collect, store, transmit, or share any personal data. Everything stays on your device.
Nothing. Chat Privacy Shield does not collect any personal information, usage data, analytics, or telemetry of any kind.
The extension does not have access to the content of your messages, contacts, or any data from WhatsApp Web beyond what is visually rendered on your screen.
Your preferences (blur level, enabled features, panel visibility) are saved exclusively using chrome.storage.local. This means your settings are stored locally on your device and are never transmitted to any external server — not to us, not to Google, not to anyone.
This data is limited to extension settings and contains no personally identifiable information.
storage — Required to remember your privacy settings between browser sessions. Data stays on your device only.
commands — Required to register keyboard shortcuts (Ctrl+Shift+H, Ctrl+Shift+K). No keylogging is performed; Chrome handles this natively.
host_permissions (web.whatsapp.com) — Required to inject the visual blur/hide CSS into WhatsApp Web. The extension only reads the DOM to apply visual filters and does not read, parse, or transmit message content.
Chat Privacy Shield does not integrate with, send data to, or communicate with any third-party service. There is no backend server, analytics platform, or tracking system of any kind.
Chat Privacy Shield is an independent open-source project. It is not affiliated with, endorsed by, or connected to WhatsApp LLC, Meta Platforms Inc., or Google LLC in any way.
This extension does not knowingly collect any information from anyone, including children under the age of 13.
If this policy is updated, the new version will be published in the Chrome Web Store listing and in the extension's GitHub repository. Continued use of the extension after changes constitutes acceptance of the updated policy.
Questions or concerns about this privacy policy can be directed to the project's GitHub repository via the Issues tab.