Prompt content is not stored
There is no database column for prompt or completion text, and it is not written to receipts, usage, the ledger, payment tables, or logs. Conversation history in the browser chat lives in your browser only; reloading clears it. No analytics or fingerprinting SDKs.
We do retain (metadata, not content)
| Data | What |
|---|---|
| Wallet + keys | wallet record; API keys are stored hash-only with a short prefix |
| Usage | request id, model, token counts, cost, latency, status, provider — no content |
| Ledger / invoices / transfers | amounts, rail identifiers (subaddress/reference), rate, status, txid — for accounting |
| Receipts | signed digests + usage + provider; no prompt/response |
Logs
Structured logs use a strict allowlist; forbidden fields (prompt, response, authorization, api_key, token, secret) are dropped even if passed.
Payment metadata
Your account is a pseudonym (wallet id / key hash). Payment records keep rail identifiers and amounts for accounting and idempotency. Crypto settlement is on public chains and inherently public.
Honest limits
- An upstream inference provider (a third-party GPU host) processes your prompt to produce the response; "we don't retain it" does not mean no third party ever sees it.
- Prompts are held in memory only during execution.