Privacy Policy

1. What we collect

When you create an account through Clerk (our authentication provider), we store your Clerk user ID, email address, and display name. We also collect:

• Request logs — model used, token counts, latency, cost, and status for each API call. Prompt and response text are stored unless you enable zero-retention mode.
• Credit transactions — purchase amounts, usage deductions, refunds, and balances.
• API keys — we store a SHA-256 hash of your API key, never the raw key.
• Semantic memories — when enabled, we embed conversation snippets to provide contextual recall in future sessions.

2. How we use your data

• Authenticate you and manage your account
• Route requests to LLM providers and track credit usage
• Provide optimization recommendations based on your usage history
• Detect abuse and enforce rate limits
• Improve service reliability and performance

3. Zero-retention mode

You can enable zero-retention mode in your account settings. When active, we skip storage of prompt text, response text, and semantic memories. Request metadata (model, tokens, cost, latency) is still logged for billing accuracy.

4. BYOK (Bring Your Own Key) privacy

If you provide your own provider API keys, they are encrypted at rest using Fernet (AES-128-CBC) before storage. BYOK requests are routed directly to the provider — they never pass through OpenRouter or any intermediary. When using BYOK, no credits are deducted and billing is handled entirely by your provider account.

5. Third-party services

We share data with the following services as necessary:

• Clerk — authentication and user management. Subject to Clerk's Privacy Policy.
• Stripe — payment processing. Subject to Stripe's Privacy Policy.
• LLM providers (OpenAI, Anthropic, Google, xAI, DeepSeek via OpenRouter or direct) — your prompts are sent to these providers to generate responses. Each provider has its own data handling policies.
• Railway — infrastructure hosting.

6. Data retention

Request logs and credit transactions are retained indefinitely for billing and optimization purposes, unless you request deletion. Semantic memories can be cleared from your settings at any time. When you delete your account, we run a full data purge covering request logs, memories, transactions, and optimization data.

7. Cookies and local storage

We use Clerk's session cookies for authentication. We do not use advertising cookies or third-party trackers. Local storage may be used for UI preferences (e.g., sidebar state, selected model).

8. Training data opt-in

We do not use your data for model training by default. You may opt in to contribute anonymized prompt/response pairs for service improvement via your account settings. This is separate from zero-retention mode — you can have retention on but training off.

9. Your rights

• Access — request a copy of the data we hold about you.
• Deletion — request full purge of your account and associated data.
• Correction — update your profile information via Clerk.
• Portability — export your request history from the dashboard.

10. Security

All traffic is encrypted in transit via TLS. BYOK keys are encrypted at rest. API keys are hashed with SHA-256. We run on Railway's managed infrastructure with automatic security patches.

11. Changes to this policy

We may update this policy from time to time. Material changes will be communicated via email or an in-app notice. Continued use of LLMWise after changes constitutes acceptance.

12. Contact

For privacy questions or data requests, email privacy@llmwise.ai.