Trust
What we keep, and what the hosts keep
We keep one row of counts per call so we can bill you, and never the words. Each model’s host has its own answer, said plainly below.
Checked 26 October 2026
The one row we keep
| Field | Example | Kept |
|---|---|---|
| Time | 2026-10-26 14:02:11 UTC | Yes |
| Key | sk-nokeep-…a9F2 and its name | Yes |
| Model | deepseek-v4.1-flash-uncensored | Yes |
| Tokens | 412 in, 286 out | Yes |
| Credits | 1 | Yes |
| Status | 200 | Yes |
| Your messages | — | Never |
| The reply | — | Never |
That row is everything we store about a call, for 30 days, then it is deleted. The console shows your rows as they are stored, and exports them.
Keys and accounts
- A key is stored as its SHA-256 fingerprint and its last four characters. The key itself is never stored.
- An account is an account key, made when you buy credits. There is no email, name or password.
- Payments go through our payment processor, which keeps what a card payment needs.
What each model’s host keeps
| Model | Its host |
|---|---|
| DeepSeek V4.1 Flash Uncensored | Runs on a private tier that stores no prompts or replies. |
| GLM 5.3 Flash Uncensored | The host deletes each prompt within ten minutes of the reply, and its GPUs belong to independent operators. When nothing at all may be kept, use DeepSeek. |
The hard-limit check
Before a call runs, an automated check reads the newest message, with the instructions and the recent turns as context, against the hard limits. It returns a yes or no. What it read is not stored.