Privacy and data use
The rule differs for paid and free traffic, and you can choose to change the paid rule for a discount. All three statements below are exact.
Paid credit: prompts are never trained on
When a request is paid for out of purchased credit, the prompt and the completion are processed in memory to answer it and are not written to durable storage by the serving stack. They are not used to train, fine-tune, distil or evaluate any model. There is no debug exception, no sampling for review and no human review queue.
The single exception is the switch below, which is off unless you turn it on yourself.
Optional: train on my prompts, 5% off every top-up
In your console under Settings → Training on your prompts you can agree that prompts and completions from your account may be retained and used to improve our models. While that is on, every credit purchase costs 5% less, and the discount is applied at checkout rather than claimed back later.
It is off by default, it is per account, and you can switch it off at any time — from that moment nothing further is used. What we cannot do is withdraw data from a training run that has already completed, and we will not pretend otherwise. Either way, we do not sell prompts and do not share them with another customer. Each change is recorded with its timestamp, so the posture that applied to any given request is auditable.
Trial credit: prompts may be trained on
When a request is paid for out of the free $10 sign-up grant, prompts and completions may be retained and used to improve our models and serving quality. That is the condition attached to the free credit.
If that is not acceptable for your data, buy the smallest credit pack instead of using the grant: the rule above then applies from your first request. No request to us is needed — the posture follows how the request was paid for.
What we keep either way
- Billing metadata
- Token counts, model, timestamps, key prefix, computed cost. Content-free. Kept up to 12 months because it is the record behind your invoice.
- Operational logs
- Status codes, latency, error classes, IP address of the calling client. No prompt or completion bodies. Kept up to 30 days.
- Account data
- Your email address, key prefixes, credit ledger, and the referral tag from the link you arrived on. Kept while the account exists.
- Payment data
- We never see your card. Paddle processes payments and returns a customer reference and the last four digits of the saved method so the console can show you what auto top-up will charge.
Cookies and tracking
One cookie: the session cookie that keeps you signed in to the console.
There are no advertising pixels and no cross-site tracking. Our platform
adds one cookieless page-view measurement script
(static.cloudflareinsights.com) which counts visits in
aggregate and sets nothing on your device; Cloudflare is already a
processor for this site. Everything else — fonts included — is served from
this origin.
Who processes what
- Cloudflare — site delivery, the console application, its database, and outbound email. Edge and storage in the EU where the platform allows it.
- Paddle.com Market Ltd (Paddle) — payments, tax, invoicing, and the saved payment method. They are the merchant of record.
- Compute providers — the infrastructure the model runs on. Inference is processed in the EU.
Your requests
Mail hello@tiyuvta.ai to get a copy of your account data, correct it, or delete the account. Deletion removes the account, its keys and its email address; the content-free billing records stay for the retention period above because tax law requires a record of a sale. Unused paid credit is refunded on deletion under the billing terms.
Children
The service is for people over 18 acting for themselves or for a business.
Changes
A change that widens what we do with your data is emailed to you before it takes effect. The date at the top moves with every change.