Privacy

What we collect, where your requests go, and who else is involved. This covers the website, the console, the API and the operator CLI.

Last updated 4 October 2026

Read this before sending a request Prompts and responses are processed on computers run by independent operators, not by us. Our gateway and the operator's machine both see the text. We don't store prompt or response text in our database, but we can't technically prevent an operator from capturing it. Don't send anything sensitive.

01Who's responsible

TezGrid is run by Ambitious Software. For anything about your data, email support@tezgrid.com or contact@ambitious.software.

02What we collect

Account: Email address, optional name, role (developer or operator) and sign-in sessions. Passwords are stored only as an Argon2 hash.
API keys: We keep a hash of each key and its first few characters so you can recognise it. The full key is shown once, when you create it.
Usage: For each request: time, model, prompt and completion token counts, charge, which node served it, and how long it took. Not the prompt or response text.
Wallet and ledger: Your balance, credits granted to you, and the charges and operator shares for each request.
Operator machines: A machine ID (a one-way hash built from hardware identifiers such as BIOS and board serial numbers; we don't store the serials themselves), hardware details (CPU, RAM, GPU, disk), installed models, approximate region, node address, and health and performance measurements.
Network: Your IP address, used for rate limiting, abuse prevention and estimating your rough location so requests go to nearby nodes.
Browser: The console keeps your session in your browser's local storage. We don't use analytics, advertising or tracking cookies.

03How a request travels

Your app sends the request to our gateway over HTTPS. The gateway picks a suitable operator node and forwards the request through an encrypted tunnel. The node decrypts it, runs the model and streams the answer back the same way.

The gateway handles the text in memory to route the request and count tokens. It keeps only the usage figures listed above. Operators agree in our terms not to read, log or keep request content. But they control their own hardware, so treat every request as something a stranger could see. "Confidential" routing isn't yet backed by verified hardware attestation.

04Why we use it

To run your account, route requests, and charge usage against your balance.
To record operator shares and show usage in the console.
To keep the network reliable and to prevent fraud and abuse.
To email you about your account, security or changes to the service. We don't send marketing email without asking.

We don't sell your data, and we don't use your prompts or responses to train models.

05Other services involved

Operators: Independent people and companies who run the nodes that process requests. See section 03.
ip-api.com: Receives IP addresses to estimate a country and region, for routing requests to nearby nodes.
ipapi.co: Receives your IP address when you open the earnings calculator on our home page, to pick a currency and electricity tariff. If it can't be reached, the page uses your browser's time zone instead.
Google Fonts: Serves the fonts used on the website and console, so your browser contacts Google when pages load.
jsDelivr and unpkg: Content delivery networks that serve some of the scripts and styles used by the site and console.
Hosting: The servers and network provider that run our gateway and database.

We don't take payments during the alpha, so no payment processor receives your data.

06How long we keep it

Account, key and machine data: while your account is open.
Usage and ledger records: as long as we need them for accounting, disputes and legal obligations, even after an account is closed.
Server logs: kept briefly for debugging and abuse prevention.

07Your choices

You can ask us to show you, correct, export or delete your data by emailing support@tezgrid.com. We'll respond within 30 days. Deleting your account removes your login, keys and machine records. We may keep usage and ledger entries where we need them for accounting, with your email removed where possible.

08Security

Passwords are hashed with Argon2 and API keys are stored as hashes. Traffic to the gateway uses HTTPS, and the hop to operator nodes is encrypted. Spend caps and rate limits limit damage from a leaked key. No system is perfectly secure: if you think something is wrong, tell us straight away.

09Children

TezGrid isn't for anyone under 18, and we don't knowingly collect data from children.

10Changes

We'll post changes on this page and update the date at the top. For significant changes we'll also tell you by email or in the console.