· 5 min · TextMeFlow Team

WhatsApp API Data Breach: GDPR Notification Duty

A leaked API token, a lost device with an active WhatsApp connection, logs that accidentally contain phone numbers and message content — these aren't hypothetical risks, they're the most common ways a WhatsApp integration leaks. This article is general information, not legal advice; for a concrete incident, always consult a lawyer or your data protection officer (DPO).

What counts as a data breach under the GDPR

A personal data breach (Art. 4(12) GDPR) is any security incident that leads to the destruction, loss, alteration, unauthorised disclosure of, or unauthorised access to personal data. That's broader than "someone stole our database": a wrongly addressed export, an employee logging in with a shared password that wasn't revoked after they left, or an API token that ends up in a public GitHub repo all qualify. Phone numbers and message content are personal data — often directly traceable to one person — so a leak through your messaging stack is just as much a data breach as a leak through your CRM.

When you have to report, and to whom

Two separate obligations, often confused:

  • Notifying the supervisory authority (in Belgium the Data Protection Authority, in the Netherlands the Autoriteit Persoonsgegevens) within 72 hours of becoming aware of the breach — unless the breach is unlikely to result in a risk to the rights and freedoms of the individuals concerned. An internally logged error message that nobody outside could access is generally not a reportable breach; a leaked API token that allowed customer messages and phone numbers to be read usually is.
  • Notifying the data subjects themselves (Art. 34 GDPR) is only mandatory in case of a high risk — for example when message content containing sensitive information (health, financial data) was exposed, or when the breach enables identity fraud.

You make both assessments yourself, as the data controller — not your WhatsApp API provider. Always document your reasoning, even when you decide not to report: Art. 33(5) GDPR requires you to record every breach internally, reported or not.

Typical breach scenarios in a WhatsApp integration

  • Leaked API token. Whoever has your token can send and receive messages on behalf of your number, and gets access to your conversation history. This is generally a reportable breach as soon as the token circulated outside your own infrastructure (a public repo, a shared log file, a compromised server).
  • Lost or stolen device with an active connection. A paired session gives access to ongoing conversations until it is unlinked. See our explanation of the QR pairing flow and re-pairing for how to terminate a session yourself.
  • Misconfigured webhook endpoint. If you send inbound messages to a test URL that accidentally stayed public, customer data flows through an endpoint without the security your production environment has.
  • Insufficiently protected logs. Application logs that write raw webhook payloads (phone number, message text, media links) become a leak as soon as those logs are accessible more widely than necessary — for example in a shared logging dashboard without access control.

First steps when you suspect a breach

  1. Stop the exposure first, document afterwards. Immediately unlink a compromised device via the dashboard or the disconnect call from the pairing flow; for a leaked token or webhook secret, ask support right away for a replacement so the old value stops working.
  2. Record the time of discovery. The 72-hour clock starts when you — not your provider — became aware of the breach. Note that moment as soon as possible, because it determines your deadline.
  3. Ask your processor what happened. Under your data processing agreement, a WhatsApp API provider is obliged to assist you and to inform you "without undue delay" as soon as it detects an incident itself. See our overview of what a good DPA should cover for what you can contractually expect.
  4. Assess the risk, not how alarmed you feel. A token that was visible for one day in a private CI log that nobody else saw has a different risk profile than a token that sat publicly on the internet for weeks. Document that assessment.
  5. Report, or document why not. When in doubt, report — an unnecessary notification costs far less than a missed mandatory one.

What this is not

A send refused by the rate limiter, a message that is ignored because the recipient sent STOP, or a temporary API timeout are not data breaches — they are exactly the safeguards meant to prevent a breach elsewhere. Don't confuse an outage with an incident; that saves you unnecessary notifications and keeps your register reliable for the cases that do matter.

How TextMeFlow limits this

EU hosting (Paris) keeps processing within the EU, which avoids international transfer discussions in the event of an incident. Every WhatsApp connection can be unlinked and set up again by you without involving support, so if you suspect a compromise you don't have to wait for a ticket to stop the exposure. For the full technical background on what travels over a webhook connection, see the webhooks documentation.

Want to check how your integration reacts to an unlink or a token rotation before it goes live? Test it at your own pace on the free plan.

Start free on TextMeFlow →

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