Privacy policy

Last updated 27 July 2026

What we collect, what we deliberately don’t, and why the difference is structural rather than a policy we promise to follow.

What we do not store

We do not store your prompts or the model’s completions. Not in a database, not in logs, not in a queue.

This is enforced by how the system is built, not by discipline:

Our usage table has no column a prompt could be written into. Storing one would require a schema migration, not a mistake.
Our logger reduces every object to an allowlist of permitted fields before formatting, so an engineer logging a whole request object during debugging gets an empty object rather than a leaked conversation — including for objects nested inside other objects.
The proxy streams responses through without assembling them, reading token counts from the byte stream rather than the text.

Prompt logging is available as a per-workspace opt-in for your own debugging. It is off unless you explicitly turn it on, and when on, content is retained for 30 days.

What we do store

Account data: name, email, password hash, OAuth identifiers.
Request metadata: which model, token counts, timings, cost, status. This is what your invoice and activity log are made of, and there is no way to bill accurately without it.
Billing records: transactions and payment references. Card details are handled by Stripe and never reach our servers.
Security data: IP address and user agent for console sessions.

Who we share with

We do not sell personal data. We use these processors:

Stripe — payment processing.
Render — application and database hosting.
GPU marketplace hosts — receive your request content transiently in order to generate a response. Our own endpoints are configured not to log or persist it.

Your rights

Request access to, correction of, or deletion of your personal data at privacy@infersia.com. We retain billing records for seven years as required by Australian tax law; everything else is deleted on request.

Cookies

A session cookie for authentication. No advertising or third-party analytics cookies, so there is no consent banner to dismiss.

These documents have not been reviewed by a lawyer. They describe accurately how the platform behaves, which is the part we can vouch for, but they are a starting point rather than finished legal terms. Have them reviewed before relying on them commercially.