No identity to collect, no KYC to leak

A key, not an identity

When you press Generate my access key we create a random 16-digit number. That key is your sign-in and your API credential. We immediately store a SHA-256 hash of it and return the plain value to you exactly once.

Because only the hash is kept, nobody — including us — can read your key back. If you lose it, the account is unrecoverable by design. Rotating the key invalidates the old one everywhere and signs out every other device.

What is on disk

Stored: a random account id, a SHA-256 key hash, the last four digits of the key as a display hint, your prepaid USD balance, and usage metadata — model id, token counts, cost, latency and timestamp. Request content is archived server-side for abuse prevention and support, together with the caller IP and user agent; retention is configurable by the operator.

Never stored: email address, name or username, phone number, password, KYC documents or identity records, uploaded files, advertising or analytics cookies.

How requests are handled

A chat request is forwarded to the upstream provider and the response is streamed back to you. The provider sees the prompt as it would with any direct API call. Alongside the billing metadata, the request content and the caller IP are archived server-side for abuse prevention and support, and are visible to the operator.

Requests are proxied over TLS to your upstream model provider. We do not add identifiers to the prompt.

https://uncensoredai.dev

Deletion and third parties

Ask on Telegram from the account in question and we remove the account row, its sessions and its usage log. There is nothing else tied to you.

No analytics scripts, no advertising pixels and no data brokers. The only outbound call is to your upstream model provider.