Effective date: September 17, 2026. This replaces the policy of March 20, 2025.
Inference APIs ("we", "us") runs the website inferenceapis.com and the API at api.inferenceapis.com. This policy says what we collect, why, who else handles it, and what we do not keep. It is written to be read; if anything is unclear, write to support@inferenceapis.com.
The short version
- We do not store the prompts, audio or images you send to the API, or the text and audio it returns. Neither do the providers that run the models: zero data retention is switched on with them. Section 3 has the detail.
- For each API request we store metering data only: your account, the model, the number of tokens, characters or audio minutes, the cost and the time.
- We do not sell personal data and we do not run advertising.
- Card payments are handled by Stripe. We never see or store card numbers.
1. What we collect
Account data
When you register we store your name, email address and a salted hash of your password. If you sign in with Google we receive your name, email address, profile picture URL and Google account identifier from Google, and no password. We also store your API key and your prepaid balance.
API request data
Requests to the API are forwarded to the inference backend and the response is returned to you. The content of the request and of the response is held in memory for the duration of the request and is not written to our database or logs. What we record for each request is: your account and API key, the model id, prompt and completion token counts or character or audio-minute counts, the cost charged, and a timestamp. This is what your usage history and balance are built from.
Audio you upload is written to a temporary file so its duration can be measured, and the file is deleted when the request ends.
Playground
The browser playgrounds call the same API through your signed-in session. Conversations live in your browser tab; they are not saved to your account.
Website and server logs
Our web server logs IP address, time, requested URL, status code, referrer and user agent, as web servers do. Logs are used for security and debugging and are rotated automatically.
Cookies and analytics
We set one first-party session cookie so you stay signed in. We use Google Analytics to count visits and see which pages are read; it sets its own cookies and receives your IP address and page URLs. We do not use advertising or retargeting cookies. You can block analytics with your browser settings or an extension without losing any site function.
2. Why we use it
- To run your account, authenticate API requests, meter usage and maintain your balance.
- To answer support requests and send service messages about your account, such as receipts, security notices and changes to models you use.
- To keep the service secure and to investigate abuse.
- To understand which pages and features are used.
- To comply with legal and tax obligations.
We do not use the content of your API requests for any purpose, including training models, because we do not keep it.
3. Who else handles your data
| Provider | What for | What they receive |
|---|---|---|
| Together AI (United States) | Runs most chat models, speech and transcription | The content of your API requests, sent under our account and not linked to your identity. Use of that content for training other models is switched off. Zero data retention is switched on for our organisation, so Together does not keep prompts or responses after the request. |
| DeepInfra (United States) | Runs Kimi K2.7 Code, embeddings and rerank | The content of those API requests, sent under our account. DeepInfra states that it does not store inputs or outputs and does not train on them. |
| Stripe | Card payments for prepaid credits | Your email address and payment details, entered on Stripe's own checkout page |
| Optional sign-in; website analytics | Sign-in: that you authenticated with us. Analytics: IP address, pages viewed, device information | |
| Akamai (Linode) | Hosting for the website, the API gateway and the database | Everything we store, on servers in the United States |
We disclose personal data to authorities only when the law requires it. If the business is sold or merged, account data would transfer to the successor under this policy.
4. How long we keep it
- Account data: until you delete your account.
- Per-request metering records and payment records: for as long as tax and accounting rules require, then deleted or anonymised.
- Request and response content: not kept.
- Server logs: a rolling window of a few weeks.
5. Your choices and rights
You can see and change your account details in Settings, create and delete API keys on the API Keys page, and ask us to export or delete your account by email. Depending on where you live you may have legal rights to access, correct, delete or restrict the use of your personal data, and to complain to a data-protection authority. We honour such requests from anyone, wherever they live.
6. Security
Traffic to the website and API is encrypted with TLS. Passwords are stored as salted hashes. API keys grant access to your balance; keep them out of client-side code and source control, and delete a key and create a new one if it leaks. No system is perfectly secure; if we learn of a breach affecting your data we will tell you.
7. Children
The service is for developers and businesses and is not directed at children under 16. We do not knowingly collect their data.
8. Changes
When this policy changes we will update the date above and note it in the changelog. Material changes will also be emailed to account holders.
9. Contact
Inference APIs · support@inferenceapis.com · contact page