Privacy

What is not stored

• The prompt and response text of API requests (/v1/chat/completions, /v1/completions, /v1/embeddings) — not in logs, not in the database, not in any system alongside them.
• Headers that identify your client are not passed on to the model provider; the request reaches upstream under uttapen's own identity.
• An API key is stored as a SHA-256 hash. The key itself is shown once, at the moment you create it.

What is stored

• Metadata for each request: model, input and output token counts, cost, timestamp, status, client IP, key id. Used for billing, for limits, and to defend your account.
• Your mobile number (that is how you sign in), plus your email and invoicing details if you enter them yourself.
• Wallet transactions and the payment details the gateway returns (reference number, masked card).
• One exception — chat inside the dashboard: conversation history and attached files are your own data and are kept so the history can be shown back to you. You can delete any conversation, and deleting your account deletes all of them.

The route a request takes

The panel, the wallet and the keys sit on a server inside Iran. The model call travels through our own stateless infrastructure outside Iran to the model maker; that layer stores nothing. What the model makers retain is governed by their own policies; for sensitive data, use models whose policy is not to train on what you send.

Sites and plugins you connect to your account

If you connect a site to your uttapen wallet (for example through the WordPress plugin), that plugin sees only your name, your masked mobile number (the last four digits), your balance and the usage of that connection — not your full number and not the usage of your other keys. Disconnect it any time from Dashboard → Connected sites; the site loses access to your wallet at that moment.

Traffic figures for the public site

The public pages — not the dashboard, not the chat, not the API path — run a self-hosted page counter on our own server inside Iran, which sends nothing to any outside service. It sets no cookie and builds no identifier that follows you between visits; it records the page address, the referring page, a country and a coarse device class, so we can tell which pages are worth keeping. With Do Not Track on, or any tracker blocker, nothing is recorded and the site behaves exactly the same.

Error and page-speed reports

When a page of the site, the dashboard or the WordPress plugin hits an error or loads slowly, your browser sends a short technical report to our own server so we can find and fix it: the error text, the page (without its address parameters), the response code, load timings, the browser family and the plugin version. Anything that looks like a mobile number, an email, a key or text you wrote is removed before it is sent and again on the server, and the text of messages and answers is never sent. These reports are kept for 30 days. With Do Not Track on, only error reports are sent — no page speed and no usage steps.

Deleting your account

Ask support and the account, along with every conversation, is deleted. Financial records (invoices and transactions) are kept for as long as the law requires.