AudioClerk
Retention, deletion and acceptable use
Specific enough to publish and true enough to survive an audit. If any row here is wrong, the product is wrong — tell us and we will fix the product.
How your audio moves
The website is online — it has to be, to receive your file. The AI is not. Those are two different parts of the same machine, and the line between them is the whole promise.
- Your browser sends the file over an encrypted connection to our front server in Canada. It decrypts the connection and forwards the file, over a second encrypted link, to our own hardware. It streams the file straight through and never writes it to disk.
- On our hardware the file is stored on an encrypted disk, in a folder for that recording alone.
- Transcription — and the brief, if you ordered one — runs in a sealed compartment with no network connection. The audio is handed in as a file and the transcript is handed back out as a file. In between, there is nothing it could send your audio to. A fresh compartment is made for each recording and destroyed when it finishes.
- You fetch the transcript from the website through your private link. The audio is destroyed 24 hours after the job completes.
What we hold, and for how long
| What | Where it lives | Default life | You can change it |
|---|---|---|---|
| Upload in flight | Encrypted from your browser to our front server in Canada, then over a second encrypted link to our own hardware. Streamed through, never written to the front server’s disk | Seconds | No |
| Original audio | Encrypted disk on our own hardware, in a folder for that job alone | 24 h after the job completes | Yes — immediate, 7 d, 30 d, or keep |
| Decoded audio, alignment temp files | Memory inside the sealed compartment — never a disk | End of job | No — never configurable |
| Voice embeddings from diarization | Process memory only | End of job | No — never written to disk |
| Transcript and derived documents | Encrypted volume | 90 days | Yes — 30 d, 1 y, or until deleted |
| Job metadata: id, duration, cost | Our database | 7 years (tax) | No — contains no content |
| Logs | Our servers | 14 days, job ids only, never filenames | No |
| Deletion log | Append-only | 2 years | No — this is the evidence |
The thing that would make this a lie
Nightly backups are how a deletion promise usually turns out to be false. If audio sat in the backup set with a retention policy measured in weeks, “deleted after 24 hours” would be wrong by about thirty days — and wrong in a way nobody would notice until a subject-access request or a breach.
So the audio and transcript volumes are excluded from backup entirely. We back up the metadata database and nothing else. A lost disk means lost recordings. That is the correct trade for this product, and we would rather say it here than have you discover it.
What else is true
- Deleted means gone from the service.
We delete the file from an encrypted disk, and it was never in a backup to begin with. We do not claim a forensic wipe — on modern solid-state drives nobody honestly can — so we claim what is true instead: once deleted, nothing in the service can retrieve it.
- Nothing trains anything.
The models run locally and self-hosted weights do not learn. No recording has ever been used to train anything, and none will be.
- Sovereignty is not a tier.
Every recording, on every package, is processed on hardware we own by a container with no network interface. There is no upgrade that makes your audio more private, because there is no version of this service that sends it anywhere.
- Isolation is per job.
A fresh container per recording, destroyed at the end. Separate directories, no shared scratch, no network egress at all.
Acceptable use
Recording law is not uniform — one party's consent is enough in Canada and much of the United States, two parties are required in a dozen states, and the EU and UK need a lawful basis regardless. We do not do the recording and cannot police it, so you attest at upload that you had the right to record. We will not knowingly process covert recordings.
We cannot moderate content we delete within 24 hours, and we do not pretend to. There is a takedown contact and a right to terminate. Liability is capped at fees paid, and no output is warranted for decisions of consequence.
Subprocessors
No vendor transcribes or stores your audio, on any package. Every recording is transcribed on hardware we own, by an AI with no network connection. The only third party your audio passes through is the Canadian hosting company that runs our front server: it passes the upload on to our hardware, re-encrypted, and never stores it.
If we ever route a package to a hosted transcription vendor, that vendor will be named here before a single byte reaches it, it will be opt-in, and it will be on a zero-retention, no-training tier.
Questions, a DPA request, or a suspected breach: clerk@audioclerk.aitech.ca