PromptEnhance Privacy Policy

1. Scope and developer

This Privacy Policy describes how the PromptEnhance Chrome extension ("PromptEnhance," "the extension") handles information. PromptEnhance is published by Digital Gods ("we," "us," or "our").

This policy covers the extension itself. AI providers, local AI software, GitHub, and websites where you use the extension operate under their own terms and privacy policies.

2. Information the extension accesses or handles

Selected text and generated text

PromptEnhance's content script runs on web pages so the extension can detect a text selection inside an editable text field and display the Enhance button. The extension temporarily accesses the exact text you select. When you click Enhance, it sends that selected text, together with PromptEnhance's built-in prompt-enhancement instruction, to the AI service you configured. The generated response is returned to the page and replaces the selected text.

Selected text is website content and user-generated content. It may contain personal or sensitive information if you choose to include that information. Do not enhance text that you do not want the selected AI provider to process.

AI service configuration and authentication information

The extension stores the following configuration in chrome.storage.local:

• the selected AI provider;
• the selected model identifier;
• the API key entered for each provider; and
• a loopback base URL for Ollama or LM Studio, if configured.

API keys are authentication information. A key is sent directly to the applicable provider to authenticate model-list and enhancement requests. The developer does not receive the key.

Information PromptEnhance does not collect

PromptEnhance does not intentionally read, collect, or store surrounding page content, page URLs, browsing history, cookies, passwords entered on websites, unselected form content, keystroke history, location, payment information, contacts, or files. The extension does not create a PromptEnhance account.

PromptEnhance does not contain analytics, advertising, tracking pixels, crash reporting, or telemetry. If a provider request fails, diagnostic information may appear locally in Chrome's extension developer console. The extension does not send those diagnostics to us.

3. Why the information is used

PromptEnhance handles information only to provide its single user-facing purpose:

• detecting an explicit selection in an editable field and showing the Enhance button;
• sending the selected text to the AI provider or local AI server chosen by the user;
• receiving the enhanced text and inserting it in place of the selection;
• listing models available under the user's configured provider account; and
• remembering the user's provider, model, API key, and local-server settings between browser sessions.

We do not use extension data for advertising, profiling, credit decisions, marketing, unrelated product development, or training AI models.

4. Where processing happens and who receives data

Cloud providers

When you select a cloud provider, PromptEnhance connects directly from the extension to that provider over HTTPS. We do not proxy the request through a Digital Gods server. The provider receives the selected text, PromptEnhance's built-in enhancement instruction, the model identifier, the API credential, and ordinary network metadata such as an IP address and request time.

OpenRouter is a routing service. If you choose it, OpenRouter may transfer your request to an underlying model provider. The particular provider depends on the model and routing options associated with your OpenRouter account. Review OpenRouter's model-provider data policies before use.

Local providers

When you select Ollama or LM Studio, PromptEnhance sends the request to a loopback address on your own device (for example, http://localhost:11434 or http://localhost:1234). Prompt text and responses do not leave the device through PromptEnhance in this configuration. The loopback connection may use HTTP because it remains on the local device. Your installation and configuration of Ollama or LM Studio are governed by those products' terms and settings.

5. Storage and retention

• Selected text and AI responses: PromptEnhance holds them only in memory for the active enhancement request and does not write them to extension storage or maintain a history. The resulting text remains in the website field where the user requested the replacement, subject to the website's own data practices.
• Provider settings and API keys: These remain in Chrome's local extension storage until the user changes them, clears the extension's stored data, or removes the extension. They are not synchronized by PromptEnhance and are not separately encrypted by the extension.
• Developer systems: We do not receive or retain prompts, responses, API keys, configuration, or extension usage logs because PromptEnhance has no developer-operated backend or telemetry.

A cloud AI provider may retain request content and technical metadata under its own terms, account plan, security requirements, and user-controlled settings. Provider retention periods can change and are not controlled by PromptEnhance. Users should review the current provider materials linked above. With OpenRouter, users should also review the policy of the underlying model provider.

As of the effective date of this policy, the providers describe their standard practices as follows:

• Anthropic: Standard Anthropic API inputs and outputs are deleted from its backend within 30 days, subject to zero-data-retention arrangements and longer retention for policy enforcement or legal obligations.
• OpenAI: OpenAI API abuse-monitoring logs may contain prompts and responses and are retained for up to 30 days by default, unless law requires longer retention or the user's account has an approved modified-monitoring or zero-data-retention control.
• Google Gemini: Practices differ between unpaid and paid API service and any approved zero-data-retention configuration. Google states that unpaid-service content may be used to improve its services and may be reviewed by humans, while paid-service prompts and responses are not used for product improvement and are logged for a limited period for abuse prevention and legal compliance.
• OpenRouter: OpenRouter states that prompt and response content is not stored unless the account owner opts into input/output logging or use of inputs/outputs; it retains request metadata. If private input/output logging is enabled, OpenRouter currently states that content is retained for at least three months and may remain longer until deletion is requested. The underlying model provider has its own retention policy.

6. Sharing, sale, and transfers

We do not sell, rent, license, or trade user data. We do not share data with advertisers, data brokers, analytics companies, or other third parties. PromptEnhance transfers selected text and authentication information only to the service the user selected, as necessary to provide prompt enhancement or retrieve that account's available model list.

The developer does not permit humans to read extension user data because the developer never receives that data. Personnel of a selected provider may access request content where permitted by that provider's terms, for example for abuse prevention, support, or legal compliance.

7. Security

Cloud-provider requests use HTTPS encryption in transit. Local-provider requests are restricted by the extension to loopback hosts on the user's device. API keys and settings are isolated in Chrome's extension storage and are sent only to the configured provider endpoint when needed.

No system can guarantee absolute security. Users should secure their Chrome profile and operating-system account, use provider keys with the narrowest practical permissions and spending limits, rotate any key they believe has been exposed, and avoid selecting confidential text unless the selected provider is appropriate for that information.

8. User choices, access, correction, and deletion

• Access or correct local settings: Open PromptEnhance's Options page to view or replace the active provider, model, API key, and local base URL.
• Delete local extension data: Remove PromptEnhance from Chrome, or clear the extension's stored site data using Chrome's extension or browser-data controls.
• Revoke authentication: Revoke or rotate an API key in the applicable provider's account dashboard.
• Provider data requests: Contact the selected cloud provider to request access, correction, or deletion of information that provider controls. We cannot retrieve or delete data held by a provider because requests use the user's own provider account and do not pass through our systems.

You may also contact us using the address in Section 11. Because we do not receive extension data, we generally have no prompt, response, API-key, or usage record to access, correct, or delete.

9. Privacy-policy page hosting

This privacy-policy page is hosted using GitHub Pages. This page does not include developer-added analytics, advertising, tracking pixels, web forms, or third-party scripts. GitHub may process standard website-access data, such as IP address, device information, referring page, and request time, under the GitHub General Privacy Statement. Visiting this page is separate from using the PromptEnhance extension; the extension does not send prompts or extension usage data to GitHub.

10. Chrome Web Store Limited Use disclosure

PromptEnhance's use and transfer of user data is limited to providing and improving its single purpose of user-requested prompt enhancement. PromptEnhance's use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

11. Contact

For privacy questions or requests, contact Digital Gods at: support@digitalgods.ai.

If you contact us, we will use the information in your message only to respond to your request, protect the extension or users, and meet legal obligations. We retain privacy correspondence only as long as reasonably necessary for those purposes.

12. Changes to this policy

We may update this policy when PromptEnhance's features, data practices, providers, or legal obligations change. We will post the revised policy at this URL and update the "Last updated" date. If a change materially affects how the extension handles user data, we will provide any additional notice or consent required by the Chrome Web Store policies or applicable law.