Privacy with visible controls, not vague promises.
This page describes what the current AIChemy web app and extension actually store, process, and send to AI providers, with clear boundaries between our product behavior and provider-side processing.
Web provider credentials stay in the client-side provider settings flow instead of being moved into server environment variables.
A reactive map of every trust boundary
Web-side provider keys stay client-side, keeping the normal provider configuration boundary local to the user experience.
Hover or tap each node to inspect exactly where responsibility changes hands.
Summary
Core privacy commitments
Account data
If you sign in, AIChemy stores the account/session data required to provide the dashboard and authenticated features.
Saved prompt history
Prompt history is feature-driven. If you save or sync history, that data can be stored so you can access it later.
Provider settings
On the web app, your AI provider keys stay client-side. In the extension, sensitive provider settings are stored locally through encryption helpers.
AI provider processing
Improve requests are sent to your selected AI provider. Their policies apply to the data you choose to send through them.
Collection
What we collect
Information you provide
- Account profile data from sign-in providers when you create or use an account.
- Saved history, templates, support requests, and configuration choices when you choose to store them.
- Prompt content and related improve fields when you submit an improve request.
Operational data
- Model/provider selections, plan checks, and rate-limit data needed to operate the service safely.
- Security and error information needed to protect the app and diagnose failures.
- Extension-side pending prompts and history items when you use the extension workflow.
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 so saved improvements can be reopened later. If you remove history entries, they should no longer appear in normal app history views.
- Extension history is stored locally in the extension context and can also be cleared from the extension-side flow.
- Settings and templates are retained only as needed to provide those features for your account or local extension usage.
- Operational security or abuse-prevention data may be retained as needed to protect the service.
Extension
Extension privacy and security
Extension behavior
- The extension uses encrypted local storage helpers for sensitive stored values instead of writing them as plain local data.
- 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 technical controls like 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 are not moved into server environment variables for normal web use, and extension-sensitive values use AES-GCM helpers locally.
Trust boundaries are explicit
Extension messaging checks sender identity and allowed origins, while authenticated web routes handle authorization per route.
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 your provider configuration in Settings.
- 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, your saved history, or how AI provider processing interacts with AIChemy, contact us and include enough context for us to help.