How Long Can You Keep WhatsApp Messages Under GDPR?
"How long are we allowed to keep those WhatsApp conversations?" is a question that, for many SMEs, only comes up after the data has been sitting there for years — in a CRM, a support tool, or simply in webhook logs nobody ever cleans up. The GDPR gives no fixed number, but it does give a clear principle: you may not keep data longer than necessary for the purpose you collected it for. This article translates that principle into concrete retention periods for WhatsApp communication.
Note: this is general information, not legal advice. For your specific situation, consult a lawyer or your DPO.
The principle: storage limitation, not a fixed number
Article 5(1)(e) GDPR calls it "storage limitation": personal data may not be kept longer than necessary for the purpose of the processing. There is no legal table saying "WhatsApp messages: 2 years". Instead, you have to justify per data source why you keep it as long as you do — and record that in your record of processing activities. The longer the period, the heavier the justification has to be.
Not all WhatsApp data is equal
The biggest misconception is that "WhatsApp data" is one block with one retention period. In practice, a simple reminder runs through four different data sources, each with its own logic:
- Message content (the text of the message itself, stored in your system or your provider's): keep it as long as needed for the purpose — usually the duration of the customer relationship or transaction, plus a reasonable buffer for complaints.
- Sending and status metadata (when it was sent, delivered, read): useful for debugging and support, but rarely relevant for longer than 12–24 months.
- Opt-in/opt-out evidence: this is the exception — you keep proof of consent as long as possible, because it's your defence if someone files a complaint later. See also our article on keeping an opt-in log.
- Invoicing and accounting data: if a WhatsApp confirmation is attached to an invoice, the GDPR storage limitation doesn't apply but the statutory accounting retention period does (in Belgium and the Netherlands usually 7 years) — that period wins.
A practical checklist
- Take stock of where WhatsApp data ends up. Not only your own database, but also your CRM, helpdesk tool, and the webhook logs of your API provider.
- Link each source to a purpose and a period. "We keep support history for 12 months after last contact" is a justification; "forever, to be safe" is not.
- Automate deletion. A manual clean-up that has to happen "someday" never happens in practice. Build a cron job or use the retention settings of your tools.
- Treat opt-outs separately. A STOP request must block sending, but you keep the proof that someone unsubscribed longer, not shorter. Our pipeline handles this automatically — see processing STOP messages automatically.
- Document it in your record of processing activities. A supervisory authority doesn't ask "is 18 months fine", but "why 18 months" — make sure you have an answer to that.
- Don't forget access and erasure requests. Even within your retention period, you must be able to respond to a request from an individual. What that looks like is covered in GDPR access or erasure requests about WhatsApp data.
What TextMeFlow already handles for you
Part of this storage limitation is already built into the infrastructure rather than sitting on your to-do list:
- EU hosting in Paris: your data doesn't leave the EU, which simplifies the legal basis for transfers.
- Automatic DPA on paid plans: the data processing agreement is signed along with your switch to a paid plan, without a separate process. More on this in our guide to the data processing agreement for a WhatsApp API.
- Anti-spam pipeline with opt-out enforcement: rate limits, risk score, STOP handling and quiet hours run at API level — see the full anti-spam policy.
What TextMeFlow can't decide for you is how long you keep message content in your own CRM or ticketing system — that remains your responsibility as the controller of that data.
Start small
You don't have to write a complete retention policy in one go. Start with the data source holding the most personal data — usually your CRM or helpdesk — and set an automatic deletion rule there. The rest follows.
Want to experience how the anti-spam and opt-out handling works before writing your own retention policy? Start for free with 50 messages per month, forever — no credit card needed.
Want to send WhatsApp messages via API yourself?
Free forever up to 50 messages/month. Scan a QR and send your first message within 5 minutes.
Free forever