Privacy

Account data. Your name and email address, and either a hashed password or the identifier returned by the identity provider you sign in with. We never store your password in a readable form.

API keys. Stored as a one-way hash. We can show a key only once, at the moment it is created, because we cannot recover it afterwards.

Audio you submit. Processed to produce the transcript you asked for.

Usage records. For each request we record a request identifier, timestamp, product, the duration of audio processed, and the credits charged. These are what your balance and usage history are built from, and we retain them for billing and accounting.

Your audio is used solely to generate your transcript. We do not use customer audio or transcripts to train, fine-tune, or evaluate any model, and we do not sell them or share them for advertising.

Synchronous requests — the ordinary transcribe call. Your upload is streamed to the worker without being written to our disks. The worker holds a temporary copy only while it decodes the audio and deletes it when the request ends. The transcript is returned to you and is not stored. What remains is the usage record: request id, timestamp, audio duration and credits charged.

Asynchronous jobs.The file you submit is stored until the job finishes and is then deleted. The resulting transcript is kept in our database so you can fetch it from the job's result endpoint. Be aware that transcripts from async jobs are retained indefinitely for now: a deletion endpoint and a defined retention window are planned but not yet available. If that matters for your data, prefer the synchronous route or contact us before you build on jobs.

Processing currently runs in Google Cloud region us-central1, in the United States. If you are submitting personal data from another country — including Brazil under the LGPD or the EEA under the GDPR — this involves an international transfer, and you should account for that in your own assessment.

Regional data residency is on our roadmap and is not available yet. If it is a requirement for your use case, contact us before you build on the API.

Google Cloud Platform hosts the API, the console, and the database. Payment processing, when enabled, is handled by Stripe, which receives the billing details you enter directly; we do not store card numbers.

You can revoke any API key from the console at any time, which takes effect immediately. To request access to, correction of, or deletion of your account data, email us at sales@inferentium.ai. Deleting your account does not remove usage records we are required to keep for accounting.

If we change this policy in a way that materially affects how we handle your data, we will update the date above and notify account holders by email.

Questions about this policy, or about a specific request, go to sales@inferentium.ai.