· 4 min · TextMeFlow Team

GDPR Access and Deletion Requests for WhatsApp Data

Disclaimer: this article is general information, not legal advice for your specific situation.

You've been sending WhatsApp reminders or order updates for months, and then the email arrives: a customer wants to know what data you hold about them, or asks you to delete everything. The GDPR gives that customer the right to do so, and you have just one month to respond. For email or a CRM, most companies by now know what to do. For WhatsApp conversations, it's often still uncharted territory.

Which rights are involved

Two articles of the GDPR come together here:

  • Article 15 — right of access. The customer may find out which personal data you process, for what purpose, how long you keep it and to whom you pass it on.
  • Article 17 — right to erasure. The customer may ask for that data to be deleted, unless you have a valid ground to keep it anyway (for example a statutory retention obligation for invoices).

You must answer both types of request within one month, with a possible extension of two months for complex cases — but you have to notify the person of that within the first month.

Three types of data, three answers

As we wrote earlier in our retention checklist, "WhatsApp data" is not one indivisible whole. When a request comes in, you need to tell three things apart:

  1. Message content — the text, photos or PDFs you sent or received.
  2. Sending metadata — timestamps, sent/delivered status, phone number, message IDs.
  3. Consent data — when and how someone signed up, and any STOP requests.

The answer is different for each of the three. Message content may sit in your own CRM or helpdesk system — you have to search and delete there yourself. Sending metadata at your WhatsApp provider has its own retention period, independent of what you work with yourself. Consent data, on the other hand, you keep slightly longer than the rest, as proof that an opt-out was processed — that doesn't contradict the deletion request; it's the reason you may keep one specific item (the fact of the opt-out) while erasing everything else.

You are the controller, your provider is the processor

This is the core point that often gets overlooked: an access or deletion request from your customer is addressed to you, not to your WhatsApp API provider. You are the data controller; the provider processes the data on your behalf under the data processing agreement (DPA). That means you are responsible for the complete answer — including the part of the data held by your provider.

In practice: know in advance which data your provider keeps about your customers and for how long, so that when a request arrives you don't have to figure out what sits in a system you don't manage. A provider without a clear answer to that question is a risk you only feel at the moment a customer explicitly asks about it.

The steps for an access request

  1. Verify the identity of the requester — you don't want to leak data to the wrong person.
  2. Search your own systems (CRM, helpdesk, chatbot logs) for message content linked to that phone number.
  3. Ask your WhatsApp provider which metadata and consent data are stored for that number.
  4. Combine this into a readable overview and send it within the deadline.

The steps for a deletion request

  1. Make sure future messages stop — a correctly processed STOP request should already enforce this automatically (see our anti-spam documentation).
  2. Delete message content from your own systems, as far as you have no statutory retention obligation (invoices often fall under a different, longer period).
  3. Ask your provider to confirm what happens to the metadata — a good provider already runs an automatic anonymisation process for this, rather than you having to ask for something to be deleted manually per request.
  4. Keep only the proof of the deletion request itself, not the content the request was about.

What TextMeFlow already handles for you

TextMeFlow doesn't log message content — so there is nothing to delete at provider level. Sending metadata is kept for 90 days for debugging and billing, and then automatically anonymised. Every paid plan automatically gets a data processing agreement, and all processing takes place on EU infrastructure (Paris). That means an access or deletion request about the provider's share of your WhatsApp data usually comes down to: "the metadata exists for 90 days at most and is then automatically anonymised" — an answer you can have ready in advance, rather than something you have to research per request.

Try TextMeFlow for free — EU hosting, automatic DPA on paid plans, 50 messages per month forever on the free plan.

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