Privacy Policy

Effective 2026-08-23 · Draft pending legal review

What we collect

• Account: your GitHub account id and username, via GitHub sign-in. Nothing else from your GitHub account.
• Provider keys: if you use the vault, keys are envelope-encrypted at rest and decrypted only in memory to serve your requests. In passthrough mode we never store them.
• Usage metadata: model name, token counts, estimated cost, latency, and status per request, so you can see your own usage.
• What we never store: the content of your prompts and completions. Request and response bodies pass through and are gone.

What we share

Your requests go to the model provider you chose, under your key and their privacy terms. We add nothing and sell nothing. No advertising, no third-party trackers, no third-party analytics scripts on this site.

Where data lives

Infrastructure runs on Fly.io (US regions). Backups of account and usage data are encrypted at rest and retained on a rolling basis.

Retention and deletion

Account and vault data persist until you delete them. Deleting your account revokes your gateway keys, destroys the encryption material for your vaulted keys, and removes your sessions. Usage metadata is retained for service operation; a fixed retention window will be published here when finalized.

Security

Keys are hashed (gateway keys) or envelope-encrypted (provider keys); transport is TLS everywhere; logs are scrubbed of key material by tested policy.

Contact

Privacy questions: [SUPPORT CONTACT — to be published before public launch].