Privacy Policy
Data we hold
| Category | Examples | Purpose |
|---|---|---|
| Account | email, display name, password hash (Argon2id) | sign-in, support, invoicing |
| Billing | ledger entries, payment references, fee amounts | balances, receipts, tax records |
| Usage metadata | model id, token counts, cost, latency, status, key prefix | metering, budgets, analytics |
| Security | IP address, request id, audit events | abuse prevention and investigation |
Prompts and outputs
Requests are forwarded to the provider you select through an HTTP proxy. That provider's retention policy applies to the request there. Choose providers whose policies meet your needs; provider-level zero-retention options exist for several of them.
Playground conversations live in your browser's local storage and are cleared when you press Clear.
Cookies
We set a single first-party cookie, zf_rt, an HttpOnly, SameSite=Lax refresh token scoped to /api/v1/auth. It is not used for advertising or analytics, and no third-party scripts are loaded by this site.
Retention
- Sessions and reset tokens: 30 days / 24 hours, then deleted.
- Webhook events: 30 days, then deleted.
- Usage logs and ledger entries: kept while the account exists so that invoices can be reproduced; ledger rows are immutable by design.
Your rights
You can export your usage as CSV at any time from the console, change or reset your password, enable two-factor authentication, and delete your account once your balance is zero. Deletion anonymises your profile and revokes all keys; we retain billing records where law requires it.
Security
Passwords are hashed with Argon2id; API keys are stored only as salted hashes; all traffic is served over TLS in production with a strict Content-Security-Policy and HSTS. See our security notes for the full control list.
Privacy requests: privacy@zettaforge.dev