How long to keep a conversation, and how to actually delete one
Keeping everything forever is a decision too, and usually the wrong one: it is a growing liability, a growing bill and a growing thing to protect. Set a period, and make sure delete actually reaches media, backups, search indexes and exports.
Deciding the period
Work from your obligations rather than from a round number. Three questions:
- How long could a dispute about this arrive? Warranty length, chargeback windows, your own returns policy.
- What are you required to keep? Tax and sector rules may require records for years - though usually the transaction rather than the chat about it.
- What is useful? Support history helps for a while and then stops. Nobody has ever needed a four year old "are you open".
These usually give different answers for different things, and that is fine: the order record and the conversation about it do not need the same lifetime. Deleting the chat and keeping the invoice is normal and defensible.
The four places a deletion misses
| Place | Why it survives |
|---|---|
| Object storage | Rows deleted, files orphaned. The most sensitive part. |
| Search index | A separate store with its own copy of the text |
| Backups | By design. Document the rolling window rather than pretending |
| Exports | A CSV somebody downloaded is now outside your system entirely |
The first is the one to fix in code. Media is stored by reference, so a deletion routine that clears rows and leaves object storage full of photographs has deleted the index and kept the data.
Backups, honestly
You cannot surgically remove one person from last week's backup, and regulators broadly accept that. What is expected is that you say so: a documented rolling window, after which the backup expires and the deletion becomes complete. "Deleted immediately, and from backups within 35 days" is an honest and defensible answer.
Build it as a job, not a promise
A retention policy in a document and not in a cron job is not a retention policy. Write the job, log what it deleted, and record the run in the audit trail - both because it is evidence and because the day it silently stops running is the day the policy becomes untrue.
Questions people actually ask
How long should customer messages be kept?
Long enough for your disputes, warranties and tax obligations, and no longer. There is no universal number - the point is that somebody decided it rather than defaulting to forever.
Does deleting a conversation delete the media?
Only if you built it that way. Rows in a database are easy to delete and object storage is easy to forget, and photographs are the most sensitive thing in most conversations.
Njiwa
One inbox for WhatsApp, Facebook and Instagram, and an API that sends over either WhatsApp rail. 7 days free, no card.