Data processing
How infere.dev processes personal data on behalf of its customers, which providers take part, and what we do to protect it. Last updated 19 November 2026.
1. Roles
For account data (your sign-in, keys, balance and usage) we act as controller. Where you send personal data of your own users through the API, you are the controller and we act as your processor, under our data processing terms, which are part of these terms.
2. Subprocessors
| Provider | Purpose | Data involved |
|---|---|---|
| Sign-in with your Google account | Name, email, profile picture and account identifier are received from Google. | |
| Turso | Database hosting (libSQL / SQLite) | Accounts, sessions, API key hashes, top-ups and usage records. |
| Vercel | Application hosting and request handling | Requests and responses pass through the hosting platform while being served. |
We will update this list before adding a provider that processes personal data.
3. What the API stores
- Prompts and responses are not stored. Only token counts, model, latency, time and charge are recorded.
- API keys are stored as a SHA-256 hash. The full secret is shown once, at creation.
4. Security measures
- All traffic uses HTTPS.
- Every query is scoped to the signed-in account. Keys belonging to other accounts cannot be read or revoked.
- Sessions are signed and expire.
- Access to production systems is limited to the people who operate the service.
5. Breach notification
We notify you without undue delay after becoming aware of a personal data breach affecting your data, and in any case within 72 hours.
6. Deletion and return
When the agreement ends you can export your usage records and delete your account from the console. We delete your data within 30 days, except where we must keep it by law.
7. Audits
We provide the information needed to show compliance with this page on reasonable request.