AsalePrivacy & data
Exactly what leaves your machine, exactly what does not, and what we do with the little that does.
What the client sends
Four things, and no others:
| Sent | Why |
|---|---|
| A random device ID (a UUID) | To route work to this machine |
| A heartbeat every 30 seconds | To know the device is online |
| The capacity you have chosen to list | To match you with buyers |
| The token counts each served request used | To settle it |
That is the whole list.
What the client does not send
- No device fingerprint. The ID is a random UUID generated on first run, not derived from your hardware.
- No IP geolocation. Your country, if you set one, is a profile field you filled in.
- No local scan results. The client looks for AI CLIs installed on this machine to offer importing them. That inventory stays on the machine.
- No credentials. Upstream tokens are stored encrypted locally and injected at call time. See Security.
- No request or response bodies. Not from the seller's client, not from yours.
What the platform holds
Your account (email, and the OAuth identity if you used one), your wallet balance and its ledger, and one row per request with: model, the four token counts, price, fee, latency and outcome.
It does not hold the request. There is no column for it.
Traffic in transit
Your prompt is visible to the seller's client, which has to reconstruct the upstream call. This is stated plainly in Security and is the reason confidential material does not belong on the market.
Every hop between machines runs over an encrypted channel, and every dispatch is signature-checked.
Deleting things
Records exist because both sides need to audit them and because the ledger must balance — settled financial records are kept. You can close an account and withdraw the balance; ask support if you need anything beyond that.
Analytics
The website loads a Google tag in production builds to measure sign-ups and downloads. The desktop client loads no analytics at all.