Privacy notice

What we keep, and what we can’t see.

Last updated 27 October 2026

Your account

You sign in by signing a one-time message with a crypto wallet or with an access key created in your browser. We receive your public address and the signature, never your private key. For access keys, the key itself never leaves your device; if you lose it, we cannot recover your account.

The terminal app

yuask Code is a command-line client for the same account. It signs in with a short code instead of a signature: the CLI asks for a code, you enter it on /device while signed in, and the terminal receives its own token. We store only a hash of that token and of the code, plus the device name and system you see in Settings. The token spends the same plan and credits, lasts a year, and you can revoke any terminal in Settings, which signs that machine out at once.

The CLI works on your files locally. Only what it sends to the model leaves your machine: the task, the files it reads, and the output of commands it runs. Your project is not uploaded as a whole and is not stored by us.

Your chats

When you save a chat, your browser encrypts it with AES-256-GCM before sending it to us. The encryption key is derived on your device from your access key or from a signature made by your wallet, and is not sent to us. We store the encrypted result so you can open your chats on other devices. Our staff and our admin tools have no way to decrypt it.

Temporary chats are never saved anywhere.

How replies are generated

To answer you, the text of your conversation has to be sent to the servers that run the model. It travels encrypted over TLS to our server, which forwards it to the GPU infrastructure that runs the model, and streams the reply back. This step is not end-to-end encrypted: the machines running the model must see the text to answer it.

• Our server does not write message content to disk or to logs.
• Our inference infrastructure does not use your data to train models. It may keep short-lived operational logs under its own retention policy.
• Your messages are not linked to a name or email, because we don’t have one.

Don’t share secrets you could not afford to have exposed, as with any online service.

What we store

• Account: your public address or key, when it was created and last used, your plan, balance and settings needed to run the service.
• Usage: per account and per day, the number of replies, the number of tokens used, and what they cost. Not the content.
• Payments: the amount, network, token and transaction id. Payments on public blockchains are visible to anyone.
• Session: one cookie that keeps you signed in. It holds a random token, nothing else.
• Terminals: for each connected CLI, a hash of its token, the device name and system, and when it was last used.
• On your device: your encryption key (as a non-exportable browser key) and small preferences, such as your thinking level.

Your IP address is used briefly in memory to limit abuse and is not stored in our database. Our network provider may process it to protect the site from attacks.

Deleting your data

In the app, under Settings, you can delete all your chats or your whole account at any time. Deleting your account removes your account record, sessions, connected terminals, encrypted chats and remaining balance. Records of past payments are kept for accounting, without your account id. If the account had used its trial, we keep a one-way hash of the account id, so the trial is not offered to it again; the hash reveals nothing on its own.

Changes

If we change how we handle data, we will update this page and the date above before the change takes effect.