Trust

We keep the usage, not the conversation.

Your prompts stay in memory while the model answers, and we never store them. Follow one request, step by step, from your app to the reply.

How a request flows

Six steps. We write down what it cost, never what you said.

  1. 01TLS ends at the edge

    The request body is decrypted in memory only.

    memory
  2. 02Key and balance check

    We check your key and balance, and set aside the most the request could cost until it finishes.

    disk
  3. 03Content check and routing

    The input is checked only for what the law forbids, such as child sexual abuse material; a blocked request gets a 400 and isn't charged. Then it goes only to a GPU we run or a provider with a no-logs policy, never anywhere else. That's strict mode, on by default for every key.

    memory
  4. 04Inference

    On our GPUs, the prompt sits in memory while tokens are generated, and is freed afterwards. A provider runs it under no-logs terms.

    memory
  5. 05Stream back

    Tokens go straight to your connection, checked for what the law forbids as they stream. They aren't written to disk.

    memory
  6. 06Usage written

    A meter, not a transcript: key, model, tokens and cost, folded into hourly, then daily, then weekly totals. No prompt, no reply, no IP address.

    disk
> refactor auth… Your app Disk Edge TLS API GPU or provider VRAM In memory Your text on disk 0 B

Where your data goes

Every part of a request, and every place it could end up.

  • In memory only
  • Hashed
  • Kept
  • Never there
Part of the requestThe edgeOur APIGPU memoryProviderDiskLogs
Your prompt Decrypted in memory Checked; its system prompt and first message hashed, in memory with a TTL Held while it runs, then freed For some models, under no-logs terms Never Never
The reply Encrypted back to you Checked as it streams through Generated, then freed For some models, under no-logs terms Only a finished video: encrypted, for an hour Never
Your API key In memory Checked against its hash Never sent Never sent SHA-256 and last 4 Never
Your IP address Used to connect Seen in memory, then dropped Never sent Never sent, nor your headers Never Never
Your account Not known Found from the key Never sent Never sent: ID fields stripped Your account record, and the cost set aside while it runs Never
Usage: key, model, tokens or units, cost Not known Counted Counted Counted, for some models Dated to the hour, then merged into totals Never
↑↓ moveEnter openEsc close