1. Who we are and what this covers
WISPR operates the website at wispr.xyz, the API at api.wispr.xyz, the dashboard, the enclaves that run the catalogue models and the sharding, and the relay exits. This policy covers all of them. It describes what data exists in our systems, why, for how long, and who can see it.
2. Accounts
Two kinds. Email accounts: we store a hash of the email address and a hash of the password, so that a password reset link can be sent and nothing else. Anonymous accounts: a username is generated for you and a twelve word recovery phrase is generated in your browser. The account key is derived from the phrase on your device. We store the username and a public key. The phrase never leaves your machine, so nobody can restore an anonymous account for you, including us.
We never ask for a name, a phone number, a wallet address or an identity document.
3. What we store, exactly
The following is the complete list of records our systems write to disk. Nothing else is kept.
| Record | Fields | Why | Kept |
|---|---|---|---|
| Account | email hash and password hash, or username and public key; balance; stake status; default model and exit region; creation time | to sign you in and bill usage | until you delete the account |
| Keys | name, hash of the key, monthly budget, per request cap, created | to accept requests and enforce the budgets you set; the plaintext key is never stored | until revoked |
| Usage counters | per key and per day: request count, token counts, cost, number of resharded refusals, model ids | to show you usage and to bill at provider price | 90 days, then deleted |
| Shard shapes | per request: number of shards, their classes (such as identity or financial), model ids, token counts, outcome | to improve the routing policy | 90 days; never contains text, identifiers or model output |
| Payments | top ups: rail, amount, fee, chain transaction hash or processor payment id; x402 settlement ids | to credit top ups once and only once | while the account exists, then 12 months for accounting |
| Note nullifiers | the nullifier hash of each redeemed deposit note and the account it credited | to prevent a note being redeemed twice | permanently; a hash, not linkable to the depositing wallet |
4. What we never store
- Prompts and replies. The gateway receives ciphertext addressed to the enclave. The enclave decrypts in memory, pseudonymises, splits, routes, rebuilds and encrypts the answer back to you. No service in our system writes a request body or a response body to disk, to a log, or to a queue.
- Receipts. The signed receipt is returned to you and kept by your client. The dashboard keeps it in your browser if you let it. We do not keep a copy.
- Your recovery phrase or password. They never leave your device. Only a hash or a signature reaches us.
- Your identity. No name, phone, wallet or document is collected at any point.
- IP addresses on the API. The gateway does not log the client address. Rate limiting uses the key hash.
- Cookies, trackers or analytics. The website and the dashboard set no cookies and load no analytics or advertising scripts. Preferences live in your browser's local storage and are never sent to us.
5. The website server
The static website is served by a web server whose access log records the time, the requested path, the status code, the referrer and the browser string. It does not record the client address. The log is kept for 7 days for abuse control, then deleted by rotation. The dashboard page is static too: once loaded it talks only to the API, which is covered by section 4.
6. Who can see what
| Party | Sees | Never sees |
|---|---|---|
| The enclave | the whole request, in memory, inside Intel TDX, with a published measurement your client can check | anything after the reply is sent |
| Catalogue models | their shard, inside WISPR hardware | other shards, your account, your address |
| Frontier providers | one shard with typed placeholders, sent from a WISPR exit under a WISPR account | names, amounts, addresses, the rest of the task, who you are |
| WISPR gateway | ciphertext to the enclave, your key hash, token counts | request or reply content |
| WISPR staff | account record, balance, usage counters, shard shapes | prompts, replies, IP addresses |
| Payment rails | a card and an account id, or a public chain transaction | a prompt; deposit notes exist so the paying wallet cannot be tied to the account that spends |
| Relay exit hosts | the destination host and an encrypted connection to it | bodies; exits never write to disk |
7. The enclave claim, precisely
Pseudonymising, splitting, routing, rebuilding and the catalogue models themselves run inside Intel TDX enclaves hosted on Phala. Each enclave publishes a measurement of its code. Our SDKs fetch it, compare it with the measurement they pin, and refuse to send a request to an enclave whose measurement differs. We, the operator, cannot read the enclave's memory. This protects you against us and against anyone who takes over our servers. It does not protect you against a flaw in the TDX hardware itself. A privacy claim that does not name its limits is not worth reading.
8. Third parties we rely on
- Frontier model providers receive pseudonymised shards under our accounts. Each has its own retention policy for what it receives. Sharding exists so that what they receive is useless alone.
- Phala hosts the confidential VMs. It can see that VMs run and what they cost, not what is inside them.
- Payment rails. Card payments go through a processor that sees the card and an account id. Crypto top ups arrive on public chains; a conversion service may see the sending wallet and the destination address.
- Fonts load from Google Fonts. That server sees the request for the font file, including the client address. The dashboard works without it.
9. Legal requests
We can be compelled to hand over what we hold, and only what we hold. Section 3 is that list. We cannot produce prompts, replies, receipts, passwords, phrases or identities because we do not have them. Where the law allows, we publish a note on the blog when a request is received.
10. Your controls
- Delete the account at any time from Settings. The account record, keys and balance are removed.
- Keys can be revoked and re-created at will; usage history is per key.
- Receipts stay in your browser or your client; turn storage off in Settings and nothing is kept anywhere.
- Verify the enclave yourself with
npx wispr attestorGET /v1/attest.
11. Changes
If this page changes, the date at the top changes and the diff is posted on the blog. If the software ever does something this page does not describe, the software is wrong and we will fix the software, not the page.
12. Contact
Questions about this page go to hello@wispr.xyz. Reports of a privacy bug get the same address and a fast reply.