Docs/Trust

Privacy: what we keep

What askr stores about me, and what it does not.

Checked against the code on

Short version: we keep what we need to run your account and bill it, and nothing you say to a model.

ThingKept?Detail
Messages and repliesNoA conversation exists in the browser tab you typed it in. The API forwards your messages to the model and keeps none of them.
Images and clips you makeYesIn your library, with the prompt, the model and the cost, served to you only. A temporary copy also exists on the model gateway for up to 24 hours. Ask and it is deleted.
Your email addressYesIt is the account.
Sign-in codes and sessionsAs hashesSHA-256 only. A copy of the database contains nothing usable.
API keysAs hashesThe plain key exists only in your copy. Name, prefix and cap are kept so the wallet can list it.
LedgerYesEvery deposit and every charge: model, tokens, credits, time, and which key made it. This is your activity.
Deposit recordsYesAddress, asset, amounts, status, and the processor's payment id. Not the wallet you sent from. NOWPayments, the processor, issues the address and sees the payment; it does not learn who you are.
Where it runsA rented virtual server at OVH in the United Kingdom. Standard request logs (IP address, user agent, URL, time, status) rotate like any web server's.
IP addressIn flightUsed for rate limiting and in server logs, which rotate. Not tied to your account's ledger.
Anything for trainingNoNothing you type trains a model, ours or anyone's.

Who else sees a request

The model's provider does, because it answers it. Today requests reach providers through a model gateway, PPQ; the roadmap replaces that with direct routing. Your account identity does not travel with the request. Because there is no table of chat text on askr's side, a past conversation cannot be sent to you or deleted for you: it was never held. Copies that reached the gateway and the provider follow their retention rules.

The full policy is at /privacy.