Data Processing Agreement (DPA) for a WhatsApp API
If you send customer communication through a WhatsApp Business API, the provider of that API processes personal data on your behalf: phone numbers, message content, timestamps, sometimes attachments such as invoices or photos. Under the GDPR that makes the provider a processor and you the controller — and that relationship has to be laid down in a data processing agreement (DPA). This article is general information, not legal advice; if in doubt, always have a DPA reviewed by a lawyer.
Why you can't go without a DPA
Article 28 GDPR requires a written agreement as soon as a third party processes personal data on your instructions. Without a DPA, you as controller are not compliant, even if the technical failure lies with the provider. In an inspection by the data protection authority, "we had no agreement" is not a defensible position — it is itself an infringement.
This applies to every tool that processes customer data, not just WhatsApp APIs: your CRM, your mailing tool, your accounting software. But messaging via WhatsApp is sensitive enough (phone numbers are directly traceable to a person) that it is often the first thing overlooked, even though it holds a lot of data.
What a good DPA must cover
A complete data processing agreement covers at least:
- Subject matter and duration of the processing — which data, how long, for what purpose.
- Nature of the data: phone numbers, name, message content, media attachments, status data (sent/delivered/read).
- Security measures: encryption in transit and at rest, access control, logging.
- Sub-processors: which subcontractors (hosting, monitoring) the provider engages itself, and whether you are informed about them.
- Location of processing: inside or outside the EU. Processing outside the EU requires additional safeguards (SCCs).
- Assistance with data breaches: within what period the processor notifies you, so that you can inform the supervisory authority within the statutory 72 hours.
- Data subject rights: how the processor supports you with access, correction or deletion requests (see also our article on handling GDPR requests for WhatsApp data).
- Deletion/return of data at the end of the contract.
Practical checklist for SMBs
- Request the DPA before you go live, not afterwards. At textmeflow.eu the DPA is added automatically with a paid plan — you don't have to ask for it separately.
- Check where the servers are. textmeflow.eu hosts in the EU (Paris); that avoids discussions about transfers outside the EU for your message data.
- Check whether the provider publishes its sub-processors or shares them on request.
- Record internally who in your organization is responsible for handling GDPR requests that come in via WhatsApp.
- Link the DPA to your record of processing activities (Art. 30 GDPR) — one line per processor is enough, with a reference to the agreement.
- Review annually: new features (e.g. a new type of webhook or media storage) can extend the processing.
What this means for your WhatsApp integration
A DPA doesn't solve everything. You remain responsible for how you use the API: don't send messages without a legal basis, process STOP requests correctly, and don't keep data for unnecessarily long. See our overview of the basic GDPR rules for WhatsApp messages for that side of the story.
For the technical documentation on how webhooks and data events work exactly, see the webhooks documentation — handy for knowing which fields are in transit when you fill in your record of processing activities.
Getting started
A DPA shouldn't be an obstacle to getting started. Test the WhatsApp API from textmeflow.eu for free with the free plan (50 messages/month) — including EU hosting and a data processing agreement that is attached automatically as soon as you move to a paid 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