Last updated September 1, 2026

Privacy Policy

This policy explains how Prompt Optimizer handles prompts, model requests, accounts, usage records, payments, and support messages.

Prompts sent for optimization

When you run the optimizer, the prompt, selected options, and optional context are sent from your browser to our Cloudflare Worker and then to the model provider configured for the service. The provider generates the result. Free runs are not saved to a user workspace by Prompt Optimizer; however, infrastructure or model providers may process request data under their own terms and retention policies. Do not submit API keys, passwords, payment-card numbers, health information, or confidential third-party material.

Saved workspace data

When workspace features are enabled for your account, saved prompts, versions, variables, test cases, and evaluation results are stored in the service database so you can use them across sessions. You may delete saved assets through the available account controls or contact support@prompt-optimizer.app. We will describe any retention period and deletion behavior for backups before those features are released.

Accounts and usage records

OAuth sign-in provides an account identifier, email address, display name, avatar where available, provider identity, and technical sign-in information. The service stores date-based usage counts, credit transactions, order status, and subscription entitlement data to enforce limits and provide paid access. Anonymous usage may use a hashed request fingerprint containing network and browser signals; the hash is used for quota enforcement and is not a readable prompt.

Technical logs

Hosting and infrastructure systems may process an IP address, browser information, request time, URL, request ID, response status, security events, and error details. For optimizer requests, operational records are intended to keep provider, model, token counts, latency, cost, and error category rather than the complete prompt. Debugging samples must be minimized and redacted.

Payments

Checkout is handled by the payment provider shown on the pricing page. We receive the account, order, product, amount, currency, payment status, subscription reference, and provider identifiers needed to grant credits, handle cancellations, respond to refunds, and prevent duplicate webhook processing. We do not receive or store your full payment-card number through the website.

Cookies, analytics, and advertising

The current release uses browser storage for the sign-in session and does not intentionally include behavioral advertising, Google AdSense, or third-party tracking pixels on the optimizer. The hosting layer and authentication or payment flows may use essential cookies or similar technical identifiers where required. If analytics or advertising is enabled later, this policy will be updated before the relevant scripts are activated, including applicable consent controls and third-party disclosures.

Your choices

You can avoid submitting sensitive material, clear browser storage, sign out, request deletion, or contact us about a privacy concern. Account deletion may require identity confirmation and may be subject to legal, payment, fraud-prevention, or backup-retention requirements. Send requests to support@prompt-optimizer.app; never include a password or full payment-card number.

Changes to this policy

As the prompt workspace, model providers, analytics, and payment features change, this policy may be updated. The date at the top indicates the current version. Material changes will be reflected before the affected processing begins where required.