Your data. Plain answers.

Where your messages go

Qwen runs on a remote server rented through Vast. The web backend forwards your messages and conversation context to that inference server. The model does not run in your browser.

The browser keeps conversation context in memory. Resetting it does not delete server records. Temporary beta debugging records requests, model answers, reasoning, tool calls and the API key used in private VPS logs. These logs have no automatic expiry and remain until the operator deletes them. Conversations are not stored in the account database.

Your selected interface language is saved in localStorage on this browser. No analytics, advertising trackers or remote fonts are loaded. A necessary HttpOnly, SameSite=Strict session cookie keeps you signed in for up to seven days; production also sets Secure. Hosting infrastructure may process IP addresses, requested URLs and browser information.

What the account stores

Support tickets and replies are stored with your Ethereum account. They are accessible to you and authorized support operators, and included in database backups. Opening a ticket does not create a read receipt. Do not submit API keys or wallet secrets.

SQLite stores your public wallet address, session and API-key hashes, token counts, balances, request statuses and payment references. Sign-in challenges expire after five minutes and are single-use. Wallet signatures are verified but not stored. No seed phrase or private key is requested or retained. Conversations are not stored in this database.

Account records remain until operator intervention. Public retention periods and deletion procedures are not yet defined. Transport encryption does not hide data from the server processing it. We do not claim end-to-end encryption into a confidential enclave or zero access by the inference host.

New accounts use wallet signatures without email or passwords. Historical email-account records remain in the database, but those accounts cannot sign in or use old API keys. They are not automatically linked to a wallet. A public wallet address can identify activity across services; wallet sign-in does not provide anonymity.

Credits and blockchain records

Development credits are simulated. Ethereum USDC is the selected launch network, but automatic Ethereum payment crediting is not yet implemented. The separate Solana adapter uses RPC providers to verify addresses, references and transactions. Payment verification does not send your conversation to the RPC provider.

Blockchain transactions are public and may link a wallet to an order. Payment records associate orders and verified transfers with an account. The web server does not hold the receiving wallet private key. Test networks and development balances are separate from real payments.

Before commercial launch

Operator identity, contact details, hosting providers, retention periods, terms of sale, account recovery and refund procedures must be completed before payments open. This preview offers no contractual availability or retention guarantee.