Updated privacy overview -

Privacy with visible boundaries, not vague promises.

AIChemy keeps saved prompts, templates, provider credentials, and most preferences in user-controlled browser or extension space, separates account operations from provider-side processing, and explains what data leaves your device when you submit an improve request.

Local encrypted keys

Web API keys persist in encrypted browser-local storage, plain settings records stay sanitized, and extension-side copies use encrypted local storage.

Privacy control plane

A reactive map of every trust boundary

Signal
AES
Keys

Web provider credentials are stored locally in encrypted browser storage and omitted from plain settings records.

Hover or tap each node to inspect exactly where responsibility changes hands.

Summary

Core privacy commitments

Identity only

Account identity

If you sign in, AIChemy stores the account identity needed to run authenticated features, plan checks, and support/admin workflows. Prompt content and provider credentials are not treated as account profile fields.

User-controlled

Saved prompt history

Web prompt history is saved in browser-side history when enabled. Extension history stays in extension-local storage unless the web app reads it through the allowed-origin bridge.

Scoped credentials

Provider settings

Web API keys and supported provider credential metadata 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.

Provider applies

AI provider processing

Improve requests are processed by AIChemy routes and your selected AI provider. Provider terms and data policies apply to the prompt, context, and credential you choose to send.

Boundaries

What stays local, transient, or server-side

Server-side account records

  • AIChemy keeps account identity plus the service state required for authenticated features, plan limits, moderation/support workflows, and admin operations.
  • 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, context assets, and request-carried provider credentials are processed to complete the improve request you submit; they are not retained as account profile data.

Local and transient data

  • Model/provider selections, workload warnings, and plan checks are used to operate the request path, with saved preferences kept on the user side when possible.
  • Security, rate-limit, 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

Boundary visualizer

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.

Active phase
01 / 04
Reactive
User boundary

You choose what to send

You submit prompt content and optional improve controls such as desired output, target audience, project context, context assets, or risk level.

AIChemy can normalize, score, and return your improve result, but prompt content, context assets, and the selected credential pass through AIChemy's improve route so the chosen provider can process the request. Review your provider's own privacy terms before sending sensitive, regulated, or confidential material.

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 supported credential metadata are encrypted in user-scoped browser storage, plain settings records are sanitized, and Reset Settings removes both settings and encrypted credential records.
  • Server-side records are limited to account identity and service state needed to operate the platform; they do not include a retained prompt-content vault or retained provider credentials.
  • Local encryption protects stored browser or extension records at rest in that local environment, but it should not be read as a hardware-backed, zero-knowledge, or compliance-certification claim.

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.
  • Provider credentials are not embedded into the extension session token; they are stored separately when needed for provider calls.

What this does not mean

This page intentionally avoids unsupported compliance claims. The product uses concrete controls like encrypted local credential storage, sanitized plain settings records, encrypted extension storage, origin validation, rate limiting, and server-signed extension sessions; those controls do not prove broader certifications or guarantees beyond the implemented behavior.

Code quality

Security expressed in implementation

Sensitive values stay scoped

Provider keys and supported credential metadata 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, workload policy, 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.

Privacy here is tied to actual product behavior: encrypted local web credentials, plain settings sanitization on load/reset, explicit extension trust boundaries, sanitized API errors, no-store handling on sensitive responses, workload-aware request handling, and user-controlled saved history.

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.
  • Review provider privacy terms before sending sensitive prompts or context assets to a third-party model.
  • 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.

aichemy@proton.meDocumentation