Skip to content

Instantly share code, notes, and snippets.

@Kwisses

Kwisses/purity-shield-privacy-policy.md

Created May 27, 2026 07:59
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save Kwisses/4eee4bfbdd4509e40271e63fec8ec4b5 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save Kwisses/4eee4bfbdd4509e40271e63fec8ec4b5 to your computer and use it in GitHub Desktop.
Download ZIP
Purity Shield Privacy Policy
Raw
purity-shield-privacy-policy.md

Privacy Policy

Effective date: 2026-05-27

This Privacy Policy explains how Purity Shield handles information.

1. Overview

Purity Shield is designed to block explicit web content and protect blocking settings behind a password. The extension works locally in your browser and does not send browsing activity to an external server.

2. Information Stored Locally

Purity Shield may store the following information in Chrome extension storage on your device:

  • Protection settings.
  • Blocked category settings.
  • Custom blocked keywords.
  • Custom blocked websites.
  • Allowed websites.
  • Password hash metadata.
  • Local analytics such as blocked rule, blocked category, blocked host, event time, and block type.

Purity Shield does not store your raw password. New or changed passwords are stored as a PBKDF2-SHA-256 hash with a salt.

3. Browsing Data

To perform blocking, Purity Shield checks page URLs, search query text, and limited page text against the extension’s local rules. This processing happens locally in the browser.

Purity Shield does not transmit browsing data, blocked URLs, page contents, search terms, analytics, custom rules, or settings to an external server.

4. Analytics

Purity Shield includes local-only analytics to help users understand blocking activity. Analytics are stored on your device and may include blocked host, matched rule, category, block type, and timestamp. Full blocked URLs are not persistently stored.

5. Data Sharing

Purity Shield does not sell, rent, or share user data with third parties. It does not use remote analytics services, advertising networks, or tracking services.

6. Remote Code

Purity Shield does not load or execute remote code. All extension scripts are packaged with the extension.

7. Data Retention and Deletion

Data remains in Chrome extension storage until you modify settings, clear extension/site data, uninstall the extension, or use a future built-in clearing feature if provided.

8. Permissions

Purity Shield requests permissions needed for its content-blocking purpose:

  • storage: saves settings and local analytics.
  • webNavigation: checks page navigations before blocked pages load.
  • Host access to websites: allows the extension to inspect URLs and limited page text for local rule matching.

9. Children’s Privacy

Purity Shield is a general browser extension and does not knowingly collect personal information from children.

10. Changes to This Policy

This Privacy Policy may be updated as the extension changes. The effective date will be updated when material changes are made.

11. Contact

For privacy questions, please reach out to privacy@kwistech.ca.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment