How WhisperAPI Handles Privacy and File Retention

Updated

WhisperAPI's stated privacy policy is short and specific: uploaded files auto-delete after 24 hours. That single retention rule is the main privacy guarantee the site makes, and it's the detail to check against your own requirements before you send sensitive audio or video. If your content can't tolerate being stored on a third-party server for up to a day, this policy won't be enough on its own — you'd need to confirm the details with the provider directly.

What the retention policy actually says

The site lists "Privacy First" as a feature with one supporting line: files auto-delete after 24 hours. There is no separate privacy page, data-processing agreement, or encryption detail referenced in the available page content, so the 24-hour auto-deletion is the only retention commitment you can rely on from the public materials.

What that means in practice:

  • Uploaded files are not kept permanently. The deletion is automatic, not something you have to request.
  • The window is up to 24 hours. A file may be removed sooner, but the stated maximum is one day.
  • Transcripts are a separate question. The policy describes file deletion; it doesn't state how long generated transcripts persist in your account or dashboard. Treat transcript retention as unconfirmed unless the provider says otherwise.

Why the 24-hour window matters for sensitive content

A short, automatic retention period is the practical difference between a service you can use for confidential material and one you can't. For example, if you're transcribing an internal team meeting, a customer call, or a research interview, the exposure is bounded: the file exists on the provider's systems for at most a day, then it's gone without any action from you.

That said, "auto-deletes after 24 hours" is a retention statement, not a full security statement. The available materials don't describe encryption at rest or in transit, access controls, or where files are stored. If your use case requires those guarantees, ask the provider before uploading.

How to decide whether it fits your use case

Your situation Does the stated policy cover it?
General business audio, low sensitivity Yes — 24-hour auto-deletion is a reasonable baseline
Content you'd rather not store long-term anywhere Likely yes, but confirm transcript retention too
Regulated data (health, legal, financial) with strict rules Not confirmed — the public materials don't address compliance
Content that must never leave your infrastructure No — this is a hosted API, so files are uploaded to the provider

Practical steps before you upload

  1. Check what you're sending. If the file contains anything you wouldn't want stored for a day on someone else's server, resolve that first.
  2. Confirm the retention terms in writing if the 24-hour rule is load-bearing for your decision — the site states it as a feature, but a direct confirmation is stronger.
  3. Ask about transcripts, not just files. The stated policy covers uploaded files; clarify how long the resulting transcripts are kept.
  4. Use the free credits to test with non-sensitive material first, so you can see how the dashboard handles your files before committing real content.

The bottom line: WhisperAPI's public privacy position rests entirely on automatic 24-hour file deletion. That's a clear, useful commitment for everyday transcription, but it isn't a substitute for a full data-handling agreement if your content is regulated or highly confidential.