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 conversation stays in page memory, without localStorage persistence. “New conversation” clears this local context; it does not delete information that an inference host may have retained. Our application database and application logs do not store prompts or responses. The inference server and hosting logs still need an infrastructure-wide review.

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

SQLite stores your email, salted password hash, session and API-key hashes, token counts, balances, request statuses and payment references. Full API keys and plaintext passwords are not 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.

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 email or 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.