Privacy with locked-down defaults, not vague promises.
AIChemy keeps saved prompts, templates, and most preferences in user-controlled browser or extension space, purges web provider secrets from browser storage, and clearly separates account operations from provider-side processing.
Web API keys persist in encrypted browser-local storage, plaintext settings records stay sanitized, and extension-side copies use encrypted local storage.
A reactive map of every trust boundary
Web provider keys are encrypted in user-scoped browser storage; plaintext legacy copies are removed from settings storage.
Hover or tap each node to inspect exactly where responsibility changes hands.
Summary
Core privacy commitments
Account identity
If you sign in, AIChemy stores the account identity needed to run authenticated features; prompt content and provider credentials are not retained as account profile data.
Saved prompt history
Web prompt history is saved in browser-side history when enabled, and extension history stays in extension-local storage unless accessed through the allowed-origin bridge.
Provider settings
Web API keys and provider OAuth identifiers are encrypted in user-scoped browser storage; plain settings records stay sanitized. Extension provider settings are stored through AES-GCM helpers and cleared with the extension session.
AI provider processing
Improve requests are processed by AIChemy routes and your selected AI provider. Provider policies apply to the data you choose to send.
Boundaries
What stays local, transient, or server-side
Server-side account records
- AIChemy keeps account identity plus the minimal service state required for enabled account features; prompt text and provider credentials are not stored as account records.
- Prompt history, templates, provider settings, and most preferences are user-space data stored in the browser or extension context rather than a server-side prompt vault.
- Prompt content and one-request provider credentials are processed only to complete the improve request you submit; they are not retained as account profile data.
Local and transient data
- Model/provider selections and plan checks are used to operate the request path, with saved preferences kept on the user side when possible.
- Security and error signals are used to protect the app and diagnose failures without turning prompt content into retained user records.
- Extension-side pending prompts, history items, session tokens, and provider settings stay in extension-local storage through encrypted local helpers.
Processing
How improve requests flow
Improve request data path
Move across the live path to see where your input starts, where AIchemy normalizes it, where provider processing begins, and when saved history becomes explicit storage.
You choose what to send
You submit prompt content and optional improve controls such as desired output, target audience, project context, or risk level.
Storage
Storage and retention
- Web history exists in browser-side storage so saved improvements can be reopened later, and it can be disabled or cleared from product controls.
- Extension history is stored locally in the extension context and can be requested, cleared, or deleted only through allowed AIChemy-origin bridge flows.
- Web provider API keys and OAuth identifiers are encrypted in user-scoped browser storage, plaintext legacy copies are removed from settings storage, and Reset Settings removes both settings and encrypted credential records.
- Server-side records are limited to account identity and minimal service state; they do not include retained prompt content or retained provider credentials.
Extension
Extension privacy and security
Extension behavior
- The extension uses AES-GCM encrypted local storage helpers for pending prompts, history, sessions, and provider settings.
- Internal extension messages validate the sender as the extension itself.
- External extension messaging is limited to the allowed AIChemy web origins.
- The extension uses a server-signed session flow rather than unsigned local auth tokens.
What this does not mean
This page intentionally avoids unsupported compliance claims. The codebase shows concrete controls like encrypted web key storage, plaintext legacy secret removal, encrypted extension storage, origin validation, rate limiting, and server-signed extension sessions; it does not prove broader certifications or guarantees beyond those implemented controls.
Code quality
Security expressed in implementation
Sensitive values stay scoped
Provider keys and OAuth identifiers are encrypted in web browser storage, extension-sensitive values use AES-GCM helpers locally, and extension JWTs omit provider credentials.
Trust boundaries are explicit
Extension messaging checks sender identity and allowed origins, while authenticated web routes handle authorization, rate limits, and provider calls per request.
Public errors stay sanitized
Sensitive API surfaces preserve sanitized public errors and no-store response behavior where the app requires it.
Controls
Your controls
- Manage encrypted provider credentials in Settings and use Reset Settings to remove the user-specific settings and encrypted credential records.
- Delete saved history where the product offers history management.
- Clear extension-side stored data through extension and session reset flows.
- Contact us if you need help understanding or removing stored account-related data.
Contact
Questions about privacy
If you have questions about this page, account metadata, saved history, or how AI provider processing interacts with AIChemy, contact us and include enough context for us to help.