Environment Guard

What it does - Group an application's production, staging, development and custom environments into profiles. - Match environments by hostname, path, port or wildcard URL pattern. - Show a colour-coded page edge, an environment marker, or both. - Open environment-specific dashboards, logs, admin tools and runbooks from the page or popup. - Block configured destructive actions or require the environment name for confirmation. - Pause an environment, profile or the complete extension. How to use it 1. Open the extension on a website and select "Configure this site". 2. Create an application profile and add an environment. 3. Add the current site or enter a URL pattern. 4. Choose the page edge and marker you want to display. 5. For production, optionally enable action protection and choose "Always block" or "Confirm with environment name". 6. Add quick links for environment-specific tools if useful. Patterns accept: - `app.example.com` — one exact host - `*.staging.example.com` — the root host and all subdomains - `localhost:3000/*` — a host and port - `example.com/admin/*` — a host and path - `*` — every HTTP and HTTPS page When patterns overlap, the first enabled matching environment in profile order wins. Prefer mutually exclusive patterns so the result stays obvious. Privacy Environment Guard processes the current page URL and, on configured sites, accessible control text, attributes, clicks and form submissions. This happens locally to identify an environment, display its indicator and guard configured actions. Profile and environment names, URL patterns, colours, action terms, CSS selectors and quick-link URLs remain in Chrome's local extension storage until they are changed, reset or the extension is uninstalled. User-requested backups contain the same configuration. The extension does not store, sell, share or transmit page content, attempted actions or confirmation text. Access to all sites lets it display indicators and guard actions on configured pages; unmatched pages receive no UI or action handling. The extension has no accounts, analytics, advertising, remote scripts or external API calls. Information received through Chrome APIs is used only for Environment Guard's stated purpose and in accordance with the Chrome Web Store User Data Policy, including the Limited Use requirements. The privacy policy was last updated on 26 July 2026. [Contact the developer](https://nicholasgriffin.dev/contact) with privacy questions. Chrome blocks extensions from protected pages such as `chrome://` URLs and the Chrome Web Store. Limitations - URL matching is deterministic and first-match-wins. Overlapping patterns should be avoided. - Action detection relies on accessible text and configured selectors. Icon-only or canvas controls need selectors. - Actions without a DOM click or form submission, and content in cross-origin iframes, cannot be protected. - Confirmation replays normal DOM activation and may not work on sites that require a trusted browser event. Environment Guard is an extra safeguard, not a replacement for access controls, backups or deployment protections.