Privacy Policy
Last updated 2 September 2026
The short version
We do not store your prompts or the model responses. By default we keep metadata only — tokens used, time taken, status code. If you need the content for debugging, turn it on yourself in settings and off again whenever you want.
What we store
- Account: the email address and name Google gives us when you sign in, plus your Google account id so we can recognise you next time. We never see or store a password — sign-in happens entirely at Google.
- Sign-in history: the time, IP address and browser of each sign-in, and of any signup we refused. It is what stops one person quietly running several accounts, and you can read your own list in Settings.
- API keys: an HMAC-SHA256 hash and the last 4 characters, nothing else. Even we cannot show a full key again — that is why you have to copy it at creation time.
- Request metadata: model, dialect, status code, tokens, cost, latency, attempts, and IP address (for abuse control).
- Sessions: session id, user agent, IP and expiry, so you can log out of any device.
Third-party providers
Your request is sent to an upstream AI provider, so the content reaches them and their policy applies to it. We never pass along your email or account id — only the model request is forwarded.
Security
Provider keys are stored AES-256-GCM encrypted and never reach the browser. All traffic runs over HTTPS. Every query takes its user id from the session, never from the request body, so one account cannot reach data belonging to another.
Cookies
There is exactly one cookie — nextai_session — and it is required for login (httpOnly, secure, sameSite=lax). No advertising or tracking cookies, no third-party analytics.
Deleting your data
Settings lets you delete your own account. Deleting it revokes every key and session and removes your email and name. Request logs and ledger rows are kept for accounting, but nothing identifiable is left in them.