Data & trust
Privacy
In plain sight.
Updated 2 October 2026
What we keep, what we erase, and where the code does it. A clear view of the network’s protections—and their limits.
Network inference is not invisible to the host. See who can read a prompt
What gets erased
Content is temporary. Billing records remain after the text is cleared.
- Prompt in the queue
- At pickup
- Your prompt is erased from our database the moment a host picks up the job.
- Unclaimed job
- 3 min
- If no host picks it up within 3 minutes, the job expires. Cleanup fails the job and erases the prompt.
- Completed reply
- 10 min
- Replies expire 10 minutes after the job finishes. Cleanup erases them, whether they have been read or not.
No chat logs. No transcripts. A guest chat lives in your browser tab. Close the tab and it’s gone.
We don’t log request bodies. No request logging is set up, and our API code doesn’t log prompts.
What we keep
Each job leaves a billing record: the API key id, the model, token counts, timestamps, status, and which host ran it.
More detail
Once cleanup has cleared the text, that record does not hold your prompt or the reply. Payments and payouts are recorded for the ledger.
To stop abuse, the guest chat counts requests per IP address in server memory. That count is not written to the database.
What the host sees
The host runs the model, so its machine reads your prompt in plain text while the job runs. There is no way around that today.
Our server also handles your prompt on its way to the host.
If something must never leave your device, run the model on your own machine.
More detail
We can’t see inside a host’s machine. We can’t stop a host from logging what it runs.
The pool has no hardware attestation (TEE) yet.
Protections available today
In-browser redaction
The guest chat replaces emails, phone numbers, card numbers, IBANs, US SSNs, IP addresses, crypto addresses and API keys with placeholders like [EMAIL_1] before sending. The originals stay in your tab and are put back into the reply's text, never into its links or code. It is on by default.
More detail
It works on patterns. It can’t find names, street addresses or other plain words, so leave those out. Code is covered too. Private network addresses like 192.168.1.20 are left as they are.
Redaction runs in the guest chat on this site. The API and the ow CLI send exactly what you give them.
Encrypted prompts at rest
More detail
Prompts waiting for a host are stored encrypted once every host serving that model has upgraded (the ow CLI with a key, or the browser host). Otherwise they're stored as today until a host picks them up. An API caller can require this by sending owt.sealed: true in the request body, or the header x-owt-sealed: 1, and gets a 409 sealed_unavailable error instead of a plaintext fallback. The host still decrypts and sees the prompt. Replies are not encrypted.
Paying without an identity
API keys need no account. No email, no name, no phone number.
Sign-in with X is optional. It only syncs and recovers your keys.
More detail
Shielded ZEC
You can pay with shielded ZEC. The payment is matched by a memo, not by who you are.
USDC · Base
USDC on Base is public on chain. Use ZEC if you want the payment unlinked from you.
How each claim is enforced
Every rule above is in public code. You can read it yourself. Open a claim to see its implementation and source.
Prompt erased when a host picks up the job
claimJob sets prompt = '' in the same query that hands the job to the host.
Unclaimed prompt expires after 3 minutes
releaseStale fails the job and blanks prompt and output (STALE = 3 minutes).
Reply expires 10 minutes after completion
releaseStale blanks output once the job is 10 minutes past finished, read or not (READ_TTL).
Billing keeps metadata only
After the text is blanked, the job row holds key id, host id, model, token counts, timestamps and status.
No request-body logging
wrangler.toml configures no observability or Logpush. API handlers don’t log prompts.
Guest chat stays in your tab
The conversation is React state only. Nothing is written to browser storage.
Redaction happens in your browser
Placeholders are swapped in before the request is built. The map never leaves the tab.
Keys without an account
openCaller mints a key without a user id.
Shielded ZEC payments
ZEC quotes are a shielded address and a memo; the desk settles by memo.
Encrypted prompts, once every host has a key
createJob seals the prompt to each live host’s key; only a matching host can claim it.