Privacy policy
Triody runs an inference API and a console at triody.ink. This page says what we collect when you use them, what we do with it, and how to get it removed. We collect the minimum the service needs to run and bill, and we do not sell any of it.
Who we are
Triody is operated from Singapore. Questions about this policy go to kyriecai.me@gmail.com.
What we collect
Depending on how you use Triody, we hold:
- Account details: your email address, and the name and avatar your sign-in provider (GitHub or Google) shares with us. Signing in with an email code gives us only the address.
- API keys: we store a hash of each key, its prefix, its name, and when it was last used. The key itself is shown once and is not recoverable by us.
- Request metadata: for every API request, the time, model, token counts, latency, status code, cost, and a request id. This is what the Usage page shows you and what your balance is settled against.
- Billing records: your prepaid balance, credit purchases, and the Stripe customer and payment identifiers that link to them. Card numbers never reach our servers; Stripe holds them.
- Server logs: IP addresses and request lines are kept briefly for abuse prevention and debugging.
What we do not keep
We do not store the content of your prompts or of the model's replies. Request bodies pass through our gateway and the GPU worker only for as long as it takes to produce the response. Usage records contain counts, never text.
How we use it
To run the service: authenticate you, route requests, meter and bill them, and show you your usage. To keep it safe: enforce rate limits and spending caps, investigate abuse, and respond to security incidents. To reach you: sign-in codes, receipts, and notices about your account. We do not use your data for advertising, and we do not train models on it.
Who else touches it
We rely on a small number of providers, each of which only receives what its job needs:
- Render hosts the API and the console, and the database, in the United States (Oregon).
- RunPod provides the GPUs that run the models; request content is processed there transiently.
- Stripe processes payments and holds your card details and invoices.
- Resend delivers sign-in codes and receipts by email.
- GitHub and Google act as sign-in providers when you choose them.
Cookies
The console sets one cookie, a signed session token, so you stay signed in. It carries no tracking. Neither the site nor the console uses advertising or third-party analytics cookies. Your theme preference is kept in your browser's local storage.
How long we keep it
Account details, keys, and billing records stay for as long as your account exists, and billing records for as long afterwards as tax and accounting rules require. Request metadata is kept while your account exists so your usage history and disputes can be checked. Server logs are rotated within weeks.
Your choices
You can revoke API keys, sign out of every device, and change your details from the console at any time. To export or delete your account, email kyriecai.me@gmail.com from the address on the account and quote your account id from Settings; we confirm from that address and remove what we are not required to keep.
Changes
When this policy changes we update the date at the top. Material changes are announced in the console before they take effect.