Privacy Policy

Last updated: October 2026  ·  Effective immediately upon installation

Overview

Env Guard processes the current page URL locally to check whether it matches one of your environment rules. It does not send browsing URLs or page content to the developer or to analytics services, and it does not keep a history of visited pages. Rules and settings are stored with Chrome's sync storage and may be synced by Google according to your Chrome sync settings. Env Guard has no developer-operated server or analytics.

Data stored

Env Guard stores the rules and settings you choose, including:

• A URL pattern or regular expression you provide
• An environment label (e.g. Production, Staging)
• A border color (hex value)
• A border width (number in pixels)
• Global display preferences, such as border thickness, pulse effect, and whether cues are enabled

This data is saved using Chrome's built-in chrome.storage.sync API. Env Guard reads these saved values locally to apply your chosen cues. If Chrome Sync is enabled, Google may sync this data across your signed-in Chrome profiles under your Chrome sync settings. The Env Guard developer does not receive this data.

Permissions explained

Env Guard requests the following permissions, each with a specific and limited purpose:

• storage — to save and retrieve your environment rules using chrome.storage.sync.
• tabs — to identify the active tab and notify it when rules change. Env Guard does not use this permission to read tab titles or URLs.
• scripting — the extension uses a content script declared in its package to display the cue. It does not dynamically inject scripts into pages.
• host permissions (<all_urls>) — because environment rules can match any domain including internal tools, staging servers, or custom production URLs. The extension's declared content script checks the current page URL against your rules locally. It does not read page content, modify page content, or send the URL elsewhere.

No data collection

Env Guard does not:

• Send personal information or page URLs to the Env Guard developer
• Record a browsing history or retain a list of visited URLs
• Use analytics or telemetry of any kind
• Send data to developer-operated servers, analytics, or advertising services
• Display advertisements
• Monetize your data in any way

Third-party services

The extension uses no third-party libraries, CDNs, analytics, or developer-operated services at runtime. Chrome's sync service may process your saved rules and settings when Chrome Sync is enabled, as described above.

Open source

Env Guard is open source. You can review the full source code on GitHub to verify these claims independently.

Changes to this policy

If this policy ever changes, the updated version will be posted at this URL and the "Last updated" date above will be revised. Continued use of the extension after changes are posted constitutes acceptance of the updated policy.

Contact

If you have questions about this privacy policy, please open an issue on the GitHub repository.