Privacy Policy — GriGsi browser extension
Last updated: May 2026
This page is the extension-focused privacy disclosure used for the Chrome Web Store and similar listings. GriGsi’s broader website, Spaces, payments, and operator practices are described in the full policy at grigsi.com/privacy.html.
1. Overview
GriGsi (sometimes listed as “Community” in store metadata) is a browser extension that helps you verify domains and email addresses before you visit or use them, and surfaces trust and safety context on pages you browse. This policy describes what data the extension collects, how we use it, and your choices.
1a. Single purpose (Chrome Web Store)
One narrow purpose: GriGsi provides on-page trust and safety context for the websites you visit—community-backed signals about domains and identities, participation with votes where offered, and optional non-promotional notices (for example a minimal strip used only for trust/safety messaging from the operator or community rules).
Domain checks, email verification prompts, voting, optional surveys about risk topics, optional organisation (Spaces) flows where enabled, and the optional on-page strip are parts of the same trust-and-safety pipeline. The extension is not designed to inject third-party advertisements or unrelated promotional content on web pages.
2. Data we collect
Local storage (on your device only):
- Hashes of domains and emails you have marked as trusted or warned against (not stored as plain text for that purpose)
- Your preferences (for example which features are enabled)
- Licence or subscription state, if you use paid features
Data sent to our servers:
- Hashes (for example SHA-256) of domains or emails when you vote Trust or Warn—so we can maintain community trust signals without treating raw values as the default identifier for that layer
- Operational signals the extension needs to function: for example extension version, vote-related counters, lightweight heartbeats or rate-limit metadata as described in the full site policy
- When you use optional flows (for example reporting that a trust/safety overlay was shown, or sending a suggested minimum display count for operator configuration), we may store small numeric or aggregate records tied to those features—see the full site policy for retention windows
3. What we do not collect (extension scope)
- We do not use the extension to build a sellable marketing profile of your browsing
- We do not sell your data to third parties
- We do not collect your name, email, or phone through the extension unless you explicitly provide them (for example during licence activation outside normal hash-only voting)
4. Permissions (why the extension asks for them)
The published store manifest may request, among others:
- storage — save trusted hashes, preferences, and local state
- tabs, webNavigation, activeTab — run domain awareness and prompts in the context of pages you use
- host permissions (broad hosts where required) — so checks and trust UI can run on sites where you type or navigate
- alarms, notifications — scheduled refresh or user-visible notices tied to trust/safety features
- clipboardWrite — only in user-initiated flows where copying is expected
- tts — optional spoken prompts where enabled
- windows — open or manage extension UI windows when needed
No remotely executed extension code. Executable logic ships inside the extension package. Network responses are treated as data (JSON/API), not as code to eval inside the extension security model.
5. Third parties
- Our servers — trust votes, configuration, optional Spaces/signalling as applicable
- Payment processors (for example Stripe or PayPal) if you purchase a licence—their policy governs payment fields you enter on their pages
6. Your choices
- Disable domain, email, or other checks in extension Options where available
- Uninstall the extension at any time—local extension storage is removed with the extension
- Request deletion or export of server-side data where applicable by contacting us (see below)
7. Contact
For privacy questions about the extension, use the contact channel listed on the Chrome Web Store listing for GriGsi, or the contact section on grigsi.com/privacy.html.