Data retention
Audio and transcripts are deleted automatically on a schedule you control, per project. Deleting sooner is one API call.
The schedule
Each project has two settings, under Settings → Project in the console:
| Setting | Meaning | Default | Range |
|---|---|---|---|
| Keep audio | How long uploaded audio is kept after its last transcription finishes. Audio that is never transcribed is kept this long after upload. | 24 hours | 1 hour – 30 days |
| Keep transcripts | How long results are kept after a transcription finishes. | 30 days | 1 – 90 days |
Deletion runs automatically. Audio is never deleted while a transcription that uses it is still running. When a transcript is deleted, the transcription record stays with content_deleted_at, and fetching the result returns 410 content_deleted.
Deleting now
curl -X DELETE "$TWENTYSIX_BASE_URL/v1/transcriptions/$ID" -H "Authorization: Bearer $TWENTYSIX_API_KEY"This deletes the transcript and, if no other transcription uses it, the audio — immediately. Deleted audio stays deleted: an upload link issued before the deletion stays valid for up to two hours, and anything uploaded through it afterwards is removed as well. A deleted upload cannot be used for a new transcription.
What we keep, and for how long
| Record | Contains | Kept for |
|---|---|---|
| Usage records | Duration, options, amount — for billing | As long as accounting law requires |
| Request logs | Method, route, status, timing | 90 days |
| Audit log | Administrative changes, who made them and from which IP address | 1 year |
None of these contain audio or transcript text. Backups follow a short, automatic expiry.
Where it lives
Uploads and transcripts are stored in the region of the project they belong to. Customer audio and transcripts are not used to train models without a separate written agreement.