Retention and Deletion
A recording is a continuing exposure as long as it exists. Keeping it forever is not safer than deleting it — it is just easier. A real retention plan answers two questions: how long, and what does delete actually mean.
The default for most recordings made on personal devices is to keep them until something runs out of storage. That is not a retention policy; it is the absence of one. The recording sits, the years accumulate, and the file becomes harder to find without becoming any less of a discoverable artifact.
How long is long enough
The honest answer is: long enough to do the thing you made the recording for. A customer-service recording made for dispute resolution can be deleted once the dispute is resolved — or, in commercial settings, once the statute of limitations on the underlying transaction has run, plus a buffer. A clinical recording follows state-law retention rules for the underlying medical record. A journalistic recording follows the newsroom’s retention policy, calibrated against the legal and source-protection considerations of the specific story. A personal recording follows whatever you actually want from it.
Most retention periods, set in advance, are too long. Six months is a common upper bound for general business recording; many recordings should be deleted within thirty days. The cost of keeping is not zero; the cost of deleting is approximately zero. The asymmetry favors deletion.
What “delete” actually means
Press “delete” on a phone’s Voice Memos and the file is moved to a “Recently Deleted” folder for thirty days. The cloud sync that backs up Voice Memos retains its own copy for as long as the cloud’s retention says it does. The local backup on the laptop that synced with the phone retains its copy until the next sync cycle, or longer. The backup-of-the-backup on the external drive that has not been plugged in for two years retains its copy indefinitely. None of these is reachable through the phone’s delete menu.
A real deletion is a list:
- Delete the local file.
- Empty the “recently deleted” folder.
- Sign in to the cloud account and confirm the cloud copy is gone.
- Check the backup system and confirm the backup copy is gone or scheduled for deletion on the backup’s rotation.
- If the recording was shared, follow up with recipients about their copies.
For organizational recording, the same logic produces an automated deletion pipeline rather than a manual list: the storage layer triggers deletion after the retention period; the backup retention is shorter than the original retention; the cloud platform’s policy is configured to mean what you want it to mean.
Automation
The cheap version of a retention policy is a calendar reminder. The right version is automation: an audio-file management tool that deletes files older than N days, a cloud platform configured to enforce retention, a transcript-storage system tied to the same lifecycle. Automation removes the temptation to keep “just in case,” which is the temptation that turns short-term recordings into long-term exposure.
When deletion is wrong
A recording subject to a litigation hold cannot be deleted; doing so is spoliation. A recording that documents harassment or abuse should not be deleted until a victim has decided whether to act on it. A recording that is the only remaining copy of an oral-history project should not be deleted lightly. The categorical preference for shorter retention has these real exceptions; the test is whether the recording is performing a continuing function or sitting passively.
A few concrete questions
- What was the purpose of this recording? Is the purpose still active?
- How many copies of this recording exist? Where?
- What would I lose if I deleted this today? What would I gain?
- If a court asked for this file, what would I do?
- Is there an automated retention policy I could set up so I do not have to make this decision again?