Privacy Policy
Last updated: October 24, 2026
This policy explains what personal data TryAii, Inc. ("TryAii", "we", "us") collects when you use tryaii.com, the TryAii API at api.tryaii.com, and the tryaii command-line tool and software development kit (together, the "Services"), why we use it, how long we keep it, who we share it with, and what you can do about it. The data notice for the command-line tool and SDK is in the section Command-line tool and SDK (notice version 2026-10-24).
1. Who we are
The controller of your personal data is TryAii, Inc., a Delaware corporation. Contact us about anything in this policy at [email protected]. Where we process data on behalf of a business customer (for example the monitor records of a company's application), we act as that customer's processor under our Data Processing Addendum.
We are appointing a representative in the European Union under Article 27 of the GDPR. Until their details are listed here, write to [email protected] and we will answer from the EU-facing team.
2. What we collect on tryaii.com
Account
When you sign in with Google we receive your name, email address and profile picture from Google. We store them with an account identifier, your sign-in times and your plan or credit balance.
What you submit
The prompts and messages you send in chat and compare, the answers the models return, your comparison history, reports you generate and feedback you give. We store them with your account so you can see them again. We send each prompt to the model provider you chose to get the answer (see section 6).
Provider API keys you save
If you save your own API key for a model provider in your settings, we store it encrypted (AES-256) and use it only to send your prompts to that provider. Remove it in your settings at any time.
Payments
When you buy credits, PayPal processes the payment. We receive the order details (amount, currency, time, PayPal transaction id and the payer's name and email) and keep a transaction record. We never see or store your card or bank details.
Technical and usage data
Our servers record your IP address, browser and device type, the pages and API endpoints you call and the time, to run the Services, limit abuse and investigate errors. We use a sign-in cookie to keep you signed in; it is necessary for the site to work. Google Analytics loads only after you choose "Accept" in the cookie notice: until then no Google Analytics script runs and nothing is sent to Google. "Decline" is remembered in your browser. We do not use advertising cookies.
3. Command-line tool and SDK
This section applies when you use the tryaii command-line tool or SDK (Python or Node). The SDK runs on your own computers. Routing decisions are made on your computer; your prompts are never sent to TryAii to be routed. Signing in with tryaii login gives you the full model catalog; the catalog is downloaded to your computer and nothing about your calls is sent for it.
What the SDK sends to TryAii
Only when you set an application key (from tryaii apps create or your dashboard) in TRYAII_API_KEY, the tryaii monitor feature sends TryAii a record of each model call your application makes through it. A record contains:
- your account identifier, the name you gave the application and the part of it that made the call (for example "shop" and "purchase item");
- the file path inside your project (never an absolute path on your computer), the line and the function that made the call;
- the model you asked for, the model that was used, and the model TryAii would have recommended;
- the time of the call, how long it took, the number of tokens sent and received, and the estimated cost;
- the kind of error, if the call failed (for example "rate limit"), without the error message;
- a keyed hash of the prompt. The SDK computes it with a secret that stays on your computer, so TryAii cannot turn it back into the prompt or check a guess against it;
- a task profile: the public benchmark category the prompt is closest to (for example code, mathematics or knowledge questions) and how close. It does not contain the prompt.
The SDK never sends TryAii the text of your prompts, the text of the model's responses, prompt embeddings, your provider API keys, or the contents of your files. It refuses to send any record that carries such a field, and our server rejects one too. The first upload from a computer, and tryaii apps create, show a short notice in your terminal; tryaii monitor upload shows it at any time.
Prompt embeddings are stored only on your computer. If we offer to upload them in the future, it will be a separate choice you make, with its own notice.
Claude Code
If you connect Claude Code with tryaii claude-code connect, TryAii receives a record of each Claude Code API call in two ways: the command imports your past calls (the last 30 days by default) from Claude Code's logs on your computer, and, if you agree, Claude Code's own telemetry reports each new call as it happens. A record contains:
- the model, the token counts (input, output, cache read and cache write), the estimated cost and the time;
- whether the call came from the main conversation or a subagent, and the subagent type (for example "Explore");
- the name of the project folder (for example "my-app"), never its path on your computer;
- for calls reported by live telemetry, how long the call took and its effort level;
- whether the call had to write the prompt cache again after a pause (a "cold restart");
- for calls reported by live telemetry, a session reference (see below).
Claude Code's request id is used only to make an id that stops a call being counted twice; it is not stored. We never store your email address, your account or organization ids, Claude Code's session id itself, your prompts, your code, file contents, or tool inputs and outputs, and the import never reads them. Claude Code's telemetry attaches your email address, account and organization ids and session id to every record; our server drops them on arrival. The settings that connect adds keep Claude Code from sending the rest.
The session reference lets us show you how long the prompt cache stays warm in each Claude Code session (the cache timer). Our server makes it from Claude Code's session id with a keyed hash. The key is a secret that only TryAii holds and is different for each application, so the reference cannot be turned back into the session id or matched across applications or with other services. We use it only for the cache timer and remove it after 7 days. To leave it out, run tryaii claude-code connect --no-session or set OTEL_METRICS_INCLUDE_SESSION_ID=false in Claude Code; the cache timer then shows no sessions.
tryaii claude-code sync runs after each Claude Code session (through the TryAii plugin for Claude Code) or when you run it yourself. For each call reported by live telemetry it sends the project folder name, the subagent type, the task type and the model recommended for it. For the main conversation and each subagent type it sends a summary of advice: the share of each task type, which models are good enough, the recommended model and the estimated saving. It never sends text.
Task types and recommendations come from tryaii claude-code analyze. It reads the text of your messages on your computer only, and only after you agree; the text never leaves your computer. Calls imported after you run it also carry the task type and the recommended model.
Why we use this data
- To show you your own usage on your dashboard: which models your application uses, what they cost, and which models would have served the same calls at a lower cost.
- To apply the model choices you make on the dashboard to your application.
- To keep the Services secure and to detect abuse.
- To improve TryAii's model recommendations, using statistics we compute only from data that we first make anonymous on our servers: a separate table with no user, application, process, file, function or prompt-hash field, where every row combines calls from at least 3 different applications.
We rely on the performance of our contract with you (or with your employer, under the DPA) for the first two purposes and on our legitimate interest in a secure service for the third. The anonymous statistics are not personal data. We do not sell this data, we do not use it for advertising and we do not use it to train language models.
Where we store it
On Amazon Web Services in the European Union (Stockholm, eu-north-1).
How long we keep it
| Data | Kept |
|---|---|
| Individual call records | 90 days, then deleted automatically |
| Claude Code session references | 7 days, then removed automatically |
| Claude Code advice per process | 90 days |
| Daily totals per application (calls, tokens, cost) | While the application exists |
| Upload batch log and dashboard change log | 13 months |
| A deleted application | Restorable for 30 days, then every record of it is deleted. We keep only the application id, the owner and the dates, as the record that the deletion was done. |
| Database backups | 7 days |
| Anonymous statistics | Indefinitely (not personal data) |
Your controls
- See what is sent and whether sending is on:
tryaii monitor upload. Turn sending off on one computer withtryaii monitor upload off, in one process withTRYAII_TELEMETRY=0orDO_NOT_TRACK=1, or for your whole account in the monitor dashboard. Records then stay only on your computer. - Revoke an application key on the dashboard; the SDK stops sending with it immediately.
- Stop Claude Code's live telemetry with
tryaii claude-code disconnect. It removes exactly the settingsconnectadded. - Delete an application, or all your monitor data, on the dashboard. You can undo it for 30 days; after that it is gone, including from backups within 7 days.
- Ask for a copy of your records, or anything else about them, at [email protected].
4. The TryAii API
api.tryaii.com serves sign-in for the command-line tool, the model catalog and the monitor endpoints above. For sign-in it stores your session (an identifier, when it started and the client name and version the tool reported) so you can sign out everywhere. Request logs carry identifiers and counts, not the content of your records.
5. Purposes and legal bases
| Purpose | Data | Legal basis (GDPR Art. 6) |
|---|---|---|
| Provide your account, chat, compare and the dashboard | Account, content you submit, monitor records | Contract (6(1)(b)) |
| Take payments and keep accounting records | Payment and transaction data | Contract; legal obligation (6(1)(c)) |
| Security, abuse prevention, debugging | Technical data, logs | Legitimate interest (6(1)(f)) |
| Product analytics on the website | Google Analytics events | Consent (6(1)(a)), via the cookie notice |
| Service emails (sign-up, receipts) | Name, email | Contract |
| Improve recommendations | Anonymous statistics only | Not personal data |
6. Who we share data with
We share personal data only with the service providers that run the Services for us, listed with their purpose and location on our subprocessors page, and when the law requires it. When you send a prompt on tryaii.com to a model, we send that prompt and the conversation to the provider of that model: OpenAI, Anthropic, Google, xAI and Mistral AI, or DeepSeek, a company in China, if you choose a DeepSeek model. We do not sell or "share" (in the sense of California law) personal data, and we do not use it for targeted advertising.
7. International transfers
We store data in the European Union. Some providers are in the United States: we use providers certified under the EU-U.S. Data Privacy Framework or bound by the European Commission's Standard Contractual Clauses. A prompt you send on tryaii.com to a DeepSeek model goes to China, which has no adequacy decision; choose another model if you do not want that.
8. How long we keep website and account data
| Data | Kept |
|---|---|
| Account | While your account exists; deleted within 30 days of a deletion request |
| Chats, prompts, comparisons and their answers | Until you delete them or your account |
| Comparison and brains reports | 12 months (360 days) |
| Transaction records | As long as tax and accounting law requires (up to 7 years) |
| Server and security logs | Up to 13 months |
| Website database backups | Encrypted, up to 13 months; deleted data leaves them as they expire |
| Monitor data (command-line tool and SDK) | See section 3 |
9. Security
Data is encrypted in transit (TLS) and at rest. Access is limited to the people who run the Services. Application keys and API keys are stored only as hashes. Details: security overview.
10. Your rights
Depending on where you live, you have the right to:
- get a copy of your personal data, and receive it in a machine-readable format;
- have it corrected or deleted;
- restrict or object to how we use it, including to processing based on legitimate interest;
- withdraw a consent at any time (for analytics: clear this site's data in your browser, and the cookie notice asks again);
- if you live in a US state with a privacy law: know, delete and correct your data, and not be treated differently for using these rights. We do not sell or share personal data, so there is nothing to opt out of;
- complain to your data protection authority.
Write to [email protected] from the email address of your account. We answer within 30 days. For monitor data, the dashboard controls in section 3 work straight away.
11. Children
The Services are for professional use. They are not meant for anyone under 16 in the European Economic Area and the United Kingdom, or under 13 elsewhere. If we learn that we hold data of such a person, we delete it.
12. Changes to this policy
We tell you at least 30 days before a material change takes effect, by email or in the Services, and we update the "Last updated" date. A change to the command-line tool and SDK section gets a new notice version, and the tool shows the new notice again.
13. Contact
TryAii, Inc., [email protected].