Privacy

A short summary for developers. The privacy policy is the full text and the one that applies. These lists cover our own systems; models labelled Official DeepSeek API are run by DeepSeek, which keeps what you send them (see "Official DeepSeek API models" below).

What we never store

• Your prompts and the model's outputs. They pass through memory while a request runs and are gone when it ends. They are not written to our database, our cache or our logs. The privacy policy describes the one narrow exception.
• Your IP address. It is held in memory only, to apply limits while the request runs. The trial and bonus checks below keep only a keyed hash of your network prefix; the privacy policy lists every exception.
• Your identity. Accounts are random 16-digit numbers. There is no KYC, and no email address is required.

What we store

• Request metadata, for 30 days: time, API key, model, token counts, cost, status, latency and time to first token. After 30 days it is rolled up into daily totals per model.
• Account data: a keyed hash of your account number, balance, ledger entries (deposits, usage, bonuses), invoices, API key hashes and, per key, its spend caps, expiry date, lifetime spend and last-used time (to within a few minutes).
• Trial check: a keyed hash (HMAC) of your IPv4 /24 or IPv6 /48, for 30 days and not linked to your account. It stops the same network from claiming the free trial twice. The prefix itself is not stored.
• Bonus check: each invoice stores the HMAC of your IPv4 /24 or IPv6 /48 with your account for up to 30 days. When a deposit bonus is granted, a separate copy that isn't linked to your account is kept for 90 days, so each network gets the bonus once per 90 days.
• Recovery email, if you add one: a keyed hash for lookup and an encrypted copy for sending recovery links, low-balance alerts you turn on (with the alert amount and when the last one went out), and notices that we replied to your support ticket.
• Support tickets, if you open one: the subject and the messages you and we write, until 180 days after the ticket closes. A ticket we answered closes after 14 days without a reply from you.

Where requests run

Our abliterated models run on dedicated GPUs operated by our infrastructure provider under a zero-data-retention configuration. /v1/responses is always stateless on our side: store is forced to false, so no response is kept for later retrieval.

Traffic reaches our servers through Cloudflare, which terminates TLS and protects the service against DDoS attacks. Prompts and outputs pass through it only in transit, and it doesn't cache or keep them for us.

Safety screening

Every request on every model passes an automated in-memory safety check, and a blocked request returns 400 content_policy_violation. What it blocks is in the acceptable use policy; what a blocked request leaves behind is in the privacy policy.

Official DeepSeek API models

Models labelled Official DeepSeek API are DeepSeek's stock models. We don't run them: after our gateway, the request goes to DeepSeek's official API.

• Prompts and outputs for these models are sent to DeepSeek, processed and stored in the People's Republic of China under the DeepSeek Privacy Policy, and may be used by DeepSeek to train its models. DeepSeek offers no zero-data-retention option. Our no-storage promise covers our own systems only.
• Each request carries a pseudonymous per-account identifier (a keyed hash, the same for all your keys), which DeepSeek uses to keep its prompt cache and content-safety handling separate per customer. Any user or user_id you send is replaced by it. DeepSeek doesn't get your account number, API key or IP address from us.
• DeepSeek may also decline some requests on its side under its Terms of Use.

If any of that matters for a workload, use one of our abliterated models instead.

Cookies

The website sets only the session cookie (__Host-sid) and, when you follow a referral link, the referral cookie (ref). There are no analytics or tracking scripts. The API sets no cookies.