Privacy Policy

• Google: your account id, email address (and whether Google verified it), name and profile picture.
• X: your account id, name and profile picture.
• A wallet: the address you sign in with. The signature proves it is yours and moves no funds.
• A passkey: its credential id, public key and the name you give it. Your fingerprint or face never leaves your device.

We use these to sign you in, to show who you are in the dashboard and to tell accounts apart. We also record when the account was created and last signed in.

A sign-in cookie keeps you signed in. Short-lived cookies protect the Google and X sign-in steps, and an invite cookie remembers the invite link you opened until you sign up. There are no advertising or tracking cookies and no analytics scripts.

Your account has its own USDC deposit address. We keep your balance and every change to it (deposits, hourly charges, refunds, vouchers and invite credit), and the deposits we saw arrive.

Blockchains are public and permanent: anyone can see the deposits sent to your address, and nobody can erase them.

Requests to your endpoint pass through our proxy and a secure tunnel to the GPU machine running your model, and the replies stream back the same way. We do not store the content of prompts, files or replies. For each request we record the time, the model and endpoint, the API key used, the status, the token counts and how long it took; these power your usage charts and billing.

Your instance runs on a machine owned by a third-party host on a GPU marketplace. The host controls that hardware. The machine is deleted when the instance stops, but do not send data you could not accept a host operator seeing.

We also keep what we need to run the instance: its model, GPU, price, status, timings and setup log.

Your playground conversations, your support assistant chat, your theme and a few display choices are kept in your browser's local storage on your device. We do not receive them, except a chat you choose to attach to a ticket. Clearing your browser data removes them.

• The assistant. To answer, your question and the last few messages of the conversation are sent to a third-party AI model provider, which processes them to produce the reply. We do not store the conversation; we count questions and tokens per day for limits and cost. Messages that look like an API key, private key or seed phrase are stopped on our server and never sent on.
• Tickets. Tickets, their replies and any chat you attach are stored so the team can answer and follow up.
• The contact form. Your name, email address and message are stored as a ticket so the team can answer by email. To limit abuse we keep a one-way hash of your network address for a day.

We keep your points and how you earned them, your lucky wheel spins with their proofs, and who invited whom. The rewards leaderboard, which signed-in accounts can see, shows a shortened name (for example "Rina S." or "ri•••"), never a full email address or wallet.

Running the service means passing data through other people's systems, each with its own privacy policy:

• our hosting provider, which runs our server, database and cache;
• a GPU marketplace and its hosts, which run your instances;
• Cloudflare, whose tunnels connect your endpoint to your instance;
• Hugging Face, from which model weights are downloaded (no data of yours is sent);
• Google and X, when you sign in with them;
• your wallet and the WalletConnect / Reown service, when you sign in with a wallet;
• blockchain RPC providers, which we use to watch deposits;
• a third-party AI model provider (currently Cerebras) for the support assistant;
• OpenRouter's public price list, which we read for the price comparison (no data of yours is sent).

Our server and hosting provider keep ordinary logs, which can include network addresses, for security and debugging. Network addresses are also used briefly to rate-limit sign-in attempts and the contact form.

We keep account, billing and usage records while your account exists. Tickets and contact messages are kept so the team can follow up. When an account is deleted we remove its profile and sign-in details; records needed to keep the books balanced, such as ledger entries and on-chain deposits, are kept without the profile they belonged to.

You can see your details, balance, usage and vouchers in the dashboard, remove sign-in methods and passkeys on Account, and delete API keys at any time. To get a copy of your data, correct it or delete your account, open a ticket.

Connections are encrypted, secrets such as worker credentials are stored encrypted, and API keys are stored only as one-way hashes. No system is perfectly secure; tell us through a ticket if you find a problem.

The service is for people aged 18 and over. We do not knowingly keep data about children.

We may update this policy. The date at the top shows the latest version, and important changes are announced in the dashboard. Questions go through a ticket on the Support page, or the contact form.