> ## Documentation Index
> Fetch the complete documentation index at: https://aircaps.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Data & privacy

> What AirCaps keeps, for how long, and how to delete it.

**We don't use your audio or transcripts to train or improve models.** Your data is used only to process your requests.

## What we keep

| Data | Kept for |
| - | - |
| **Streaming audio and transcripts** (A5S Small V2 Streaming) | Not stored. Audio is processed in memory and the text is sent only to you. |
| **Uploaded files** (`POST /v1/files` or an upload URL) | Kept for 24 hours after upload, so you can reuse the `file_id`, then deleted within the following 24 hours (24 to 48 hours after upload). Deleting a transcript deletes its uploaded file right away. |
| **Audio from `audio_url`** | Kept only as the processing copy (next row). The URL itself is kept with the transcript (below). |
| **Processing copies** of the audio | Kept for 48 hours after the transcript is created, then deleted within the following 24 hours (48 to 72 hours). Deleting the transcript deletes them right away. |
| **Transcripts** (text, words, speakers) | 30 days after completion, or until you delete them with [`DELETE /v1/transcripts/{id}`](https://aircaps.ai/docs/api-reference/delete-transcript). |
| **Transcript details you send** (`metadata`, `audio_url`, webhook URL) | Removed when the transcript is deleted or expires. |
| **Speaker ID clips** (AirCaps Speaker ID-v1 enrollments and identifications) | Not kept. Each clip is used only to compute its speaker embedding and is discarded when the request finishes; clips are never saved to storage or to our database. |
| **Speaker profiles** (AirCaps Speaker ID-v1: each speaker's name, metadata and the speaker embeddings derived from its enrollment clips) | Until you delete the speaker or the enrollment. There is no automatic expiry: your application decides who stays enrolled. Embeddings are numbers derived from a voice, not audio, and they can't be played back, but they identify a person's voice: treat them as biometric data. |
| **Speaker identifications** (results) | Not stored. Only usage facts are kept (below). |
| **Webhook auth header** (`webhook_auth_header_value`) | Removed as soon as the webhook is delivered or delivery fails for good. |
| **Usage records** (duration, status, timestamps) | Kept for usage reporting and billing; they contain no audio, text or metadata. |
| **Account** (email, name, limits) | For the life of the account. API keys are stored only as SHA-256 hashes. |
| **Logs** | Requests (endpoint, status, timing and IDs). Logs don't contain audio or transcripts. |

## Deleting data

* **A transcript:** `DELETE /v1/transcripts/{id}` deletes it immediately. If it is still processing, it is canceled.
* **A speaker's voice data:** [`DELETE /v1/speakers/{id}`](https://aircaps.ai/docs/api-reference/delete-speaker) deletes the speaker and all its embeddings immediately; [`DELETE /v1/speakers/{id}/enrollments/{enrollment_id}`](https://aircaps.ai/docs/api-reference/delete-enrollment) deletes one enrollment. Both work even if your account no longer has access to the model.
* **Uploads:** deleted automatically 24 to 48 hours after upload, or right away when you delete a transcript that used them.
* **Processing copies:** deleted automatically 48 to 72 hours after the transcript is created, or right away when you delete it.
* **Your account and all its data:** [contact us](https://aircaps.ai/contact).

## Voice data and consent

AirCaps Speaker ID-v1 works by creating and storing a numerical representation of a person's voice. Laws such as the GDPR, the Illinois Biometric Information Privacy Act (BIPA) and other state privacy laws can treat this as biometric data. You are responsible for telling the people you enroll and identify, getting their consent where required, and deleting their speaker profiles when you no longer need them or when they ask. Delete with the endpoints above; deletion is immediate and permanent.

## Security

* **In transit:** every connection uses TLS: your client to the API, between our services, to storage and to our database (with certificate verification).
* **At rest:** stored data is encrypted with AES-256.
* **Isolation:** every request is scoped to your account; no account can read another's data.
* **Keys and webhooks:** API keys are stored as hashes and can be revoked at any time; webhooks are signed ([Standard Webhooks](https://aircaps.ai/docs/guides/webhooks.md)).

## Where data is processed

In the United States.

For a data processing agreement, custom retention or a dedicated deployment, [talk to sales](https://aircaps.ai/contact).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.