SafePrompt Guard Privacy Policy

Overview

SafePrompt Guard is a local-first Chrome extension that helps users detect sensitive prompt content before it is sent to supported AI tools. The extension is designed to run in the browser without a backend service or account system.

What the extension processes

On supported sites, SafePrompt Guard may process prompt text locally in order to detect risky content before send. This may include passwords, credentials, tokens, API keys, secrets, internal references, customer-specific terms, URLs, hosts, private IP addresses, emails, and similar text content entered by the user.

What the extension stores locally

The extension stores data on the device using chrome.storage.local.

• Extension settings such as whether scanning is enabled.
• Total detection count used by the toolbar popup.
• The latest warning summary shown in the popup.
• Local DB learned values manually added by the user.

What the extension does not do

• It does not send prompt content to a SafePrompt Guard backend.
• It does not require an account or authentication system.
• It does not use external detection APIs in the default release.
• It does not sell user data.
• It does not transfer user data to third parties for unrelated purposes.

Supported sites

At the time of this policy, the extension runs only on these supported sites:

• chatgpt.com
• chat.openai.com
• claude.ai
• gemini.google.com
• perplexity.ai

User controls

Users can remove learned Local DB values from the extension popup or the Local DB console. Users can also disable scanning from the extension popup.

Support

Support for SafePrompt Guard is handled through GitHub Issues: https://github.com/stiliyan-dev/safeprompt-guard/issues

If you submit information through GitHub Issues, that submission is governed by GitHub's own services and policies in addition to this extension policy.

Changes to this policy

This policy may be updated if the extension's behavior changes, such as adding optional online checks or new storage behavior. Material updates should be reflected in the Chrome Web Store disclosures and on this page.