· 5 min · TextMeFlow Team

WhatsApp Messages in Your GDPR Record of Processing (Art. 30)

Every small business that processes personal data must keep a record of processing activities under Article 30 GDPR — an overview of which processing takes place, for what purpose, and with which safeguards. WhatsApp traffic through an API provider such as TextMeFlow is exactly such a processing activity, and yet in practice it often isn't in the record (or isn't recorded correctly), simply because nobody is sure which fields belong there.

This article is a concrete fill-in guide: not legal advice (see the disclaimer at the bottom), but a practical checklist of the fields a supervisory authority expects, plus example wording you can reuse.

Why WhatsApp messages deserve their own line

Many companies cram "customer communication" into one broad line of their record, together with email, SMS and phone calls. That works until there's a complaint or a data breach — then the supervisory authority asks specifically about the WhatsApp channel, and a vague line saying "communication with customers" won't hold up. WhatsApp messages travel through a third party (your API provider), they often contain phone numbers plus content (appointment details, order status, documents), and the retention period usually differs from email. Those are three reasons to give it its own, specific line.

The fields Article 30 GDPR requires

For every processing activity, your record must contain at least these fields:

  1. Name and contact details of the controller — your company, with a contact point for privacy questions.
  2. Purpose of the processing — be specific: "sending appointment confirmations and reminders via WhatsApp", not "customer service".
  3. Categories of data subjects — customers, prospects, employees (if you also use WhatsApp internally for scheduling).
  4. Categories of personal data — phone number (mandatory field), name, message content, possibly attachments (photos, invoices, documents) if you send media.
  5. Categories of recipients — this is where your API provider comes in: the processor's name, and whether there are sub-processors (e.g. a hosting partner).
  6. Transfers to third countries — within the EU (see below) or not.
  7. Retention period — a concrete number, with justification. See also our article on retention periods for WhatsApp messages if you still need to set this period.
  8. Description of the technical and organisational measures — encryption, access restriction, HMAC signatures on webhooks, and so on.

An example entry to reuse

A concrete entry in your record could look like this:

Processing activity: WhatsApp messaging (transactional + reminders)
Purpose: appointment confirmations, status updates and reminders to customers
Data subjects: customers
Data categories: phone number, name, message content, attachments (optional)
Recipients/processors: TextMeFlow (Fades Management EOOD, Bansko, Bulgaria) — EU hosting (Paris)
Transfers to third countries: none, processing stays within the EU
Retention period: [your justified period]
Legal basis: performance of a contract (transactional) / consent (marketing)
Security measures: TLS, HMAC-signed webhooks, access control on the API key

Adjust the legal basis to the type of message: an order confirmation is generally based on performance of a contract, while a marketing message requires valid consent (opt-in). Don't mix the two in the same line if your legal basis differs per message type.

The processor itself: what to check

Your record refers to your API provider as a processor, but that isn't enough without an underlying data processing agreement (DPA). If you haven't signed one yet or linked it to your record, first read our article on the data processing agreement for a WhatsApp API — it also explains how to link the DPA to the same record entry. Also check where your provider's servers are located: data that stays within the EU is a lot easier to justify than data that goes to a third country.

Common mistakes

  • One line for all channels. Email, SMS and WhatsApp often have different processors, retention periods and risks — split them.
  • No link to the DPA. The record points to a processor, but nobody can find the agreement when it's needed.
  • Forgetting to list attachments. Do you send invoices, photos or documents via WhatsApp? Those are separate data categories that must be listed separately.
  • Never updating the record. A new integration (for example a new webhook to your CRM) means a new or amended entry, not just a technical change.

How this relates to your technical setup

The record isn't a standalone administrative document — it has to match what actually happens technically. If you want to know exactly which fields pass through your webhooks (and therefore which data categories you need to list), check the webhooks documentation. That way you fill in the record based on what is really being sent, not on a hunch.


This article provides general information and is not legal advice. For a watertight record of processing that fits your specific situation, we recommend consulting a lawyer or DPO.

Want to start with a WhatsApp API that combines EU hosting and an automatic DPA on paid plans? Create a free account and test your first 50 messages at no cost.

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