Privacy policy

What is stored

• Account

  Your email address and a securely hashed password. The password itself is never stored.

• API keys

  A SHA-256 hash of the key, plus a short readable prefix and the last four characters so you can identify it. The full key is never stored and cannot be recovered.

• Payments

  The order id, plan, amount, status, chosen payment method and the provider reference. Card and bank credentials never reach this server; payment is handled entirely by the payment provider.

• Usage

  For each request: the key it used, the model id, the outcome, the latency, and the timestamp. This is used for accounting, for showing you your usage, and for detecting abuse.

• Sessions

  A signed cookie holding your user id and role. It is HTTP-only and expires after seven days.

• Audit

  Administrative actions, payment notifications and sign-in events, with the originating IP address.

What is not stored

The content of your prompts and the models' responses are not written to this server's database or logs. They pass through the gateway in memory while the request is being served and are forwarded to the model provider, which handles them under its own policy. Store nothing in a prompt that you would not send directly to that provider.

Who sees it

The model provider receives your request in order to answer it. The payment provider receives the order id and amount in order to process the payment. No data is sold and no advertising or analytics tracker is embedded in this site.

Retention

Account, key and order records are kept while the account exists, because they are the record of what was bought. Usage records are kept so that usage history remains meaningful. Deleting an account removes its keys and order references; payment records may be retained where required for accounting.

Your choices

You can revoke any key at any time from the dashboard, which stops its use immediately. To delete the account itself, use the contact address on the account page.

Security

Passwords use scrypt with a per-account salt. Keys are stored only as hashes. Payment confirmation is verified server-to-server with the payment provider rather than being trusted from a notification payload. Access to the administrative console is restricted to accounts with the administrator role, and every privileged action is recorded.