GDPR and WhatsApp Business: Is It Compliant? A 9-Point Checklist

, Co-Founder & CMO

· 9 min read

Is WhatsApp Business GDPR compliant? What changes between the Business App and the API, who is controller and processor, which legal basis your messages need, how data transfers and EU storage work, and a 9-point checklist to set it up.

TL;DR

WhatsApp Business is not GDPR compliant or non-compliant by itself; what counts is how you use it. You are the controller. You need a legal basis for every message, a privacy notice that names WhatsApp, a data processing agreement with your provider, a view on data transfers and deletion windows. The WhatsApp Business API makes these steps much easier to control than the app on a phone. The 9-point checklist below covers what to set up.

Is WhatsApp Business GDPR compliant?

WhatsApp Business can be used in line with the GDPR, but compliance depends on your setup. As the controller, you need a legal basis such as consent, a privacy notice, a data processing agreement with each provider and rules for transfers and deletion. The API makes this easier to control than the app.

Last checked: 14 November 2026. This guide sets out the legal position as we understand it on that date, to the best of our knowledge. It is not legal advice. For your specific case, talk to your data protection officer or a lawyer. Sources: the GDPR text, EDPB guidelines and the terms WhatsApp and Meta publish, linked where they are used.

A quick scene from a hair salon. The owner books appointments on WhatsApp from her own phone. Three stylists use the same phone when she is away, the address book holds customers and her family, and old chats go back four years. Nothing about this is unusual, and nearly every point on it is a data protection question: who has access, which contacts are shared, how long chats are kept and whether customers were told. The rest of this guide sorts those questions into a plan. For the wider topic across channels, see the glossary entry GDPR in messaging.

Business App vs. API: what changes for data protection

WhatsApp comes in two business versions. The free Business App runs on a phone; the WhatsApp Business API connects to a platform your team uses in the browser. For data protection, the difference is less about the law and more about control.

WhatsApp Business App and WhatsApp Business API compared on data protection points (terms checked 14 November 2026)
PointBusiness AppBusiness API via a provider
Where chats liveOn the phones and linked devices that use the accountIn the provider's platform; Meta keeps Cloud API messages for up to 30 days
Processing termsWhatsApp's Business Data Processing Terms, where the app terms say WhatsApp processes data for youMeta's Cloud API terms with Meta as processor, plus a data processing agreement with your provider
Team accessShared phone or linked devices, no rolesIndividual logins, roles and access rights
ContactsTaken from the phone's address bookImported or created from conversations, with consent stored per contact
DeletionManual, chat by chat and device by deviceDeletion windows you set in the platform
EU storageNo optionMeta's local storage option for Cloud API numbers

The app can be used lawfully by a one-person business that keeps the phone clean. Once a team shares the account, the API is the easier route to compliance. If you want to keep the app on your phone and still get the API's controls, WhatsApp Coexistence lets both share one number. The full comparison is in WhatsApp Business App vs. API.

Controller and processor: who is responsible for what

The GDPR splits responsibility between the controller, who decides why and how personal data is processed, and the processor, who processes it on the controller's behalf (Art. 4 and Art. 28 GDPR). The EDPB guidelines on controller and processor explain how to tell them apart. For WhatsApp Business that usually means:

  • You are the controller. You decide whom you message and why. The obligations to customers sit with you: legal basis, information, deletion, answering access requests.
  • Meta is a processor for the Cloud API. Meta describes its role for the Cloud API as a data processor or service provider for the business (Meta developer documentation) under the WhatsApp Business Platform Cloud API terms. For the app, WhatsApp's Business Data Processing Terms apply where the Business App terms say WhatsApp processes customer data for you. These are standard terms; Meta does not negotiate a separate agreement with each business.
  • Your provider is a processor too. The platform that connects you to the API processes your messages and needs a data processing agreement with you under Art. 28.

Every message needs a legal basis under Art. 6 GDPR. Two cover most cases:

  • Replying to a customer's request. When a customer writes to you about an order or appointment, your reply usually rests on the contract or the steps before it (Art. 6(1)(b)).
  • Marketing messages. Offers, newsletters and win-back campaigns need consent in practice (Art. 6(1)(a)), and national rules on electronic marketing in most EU countries ask for prior consent as well. Consent must be freely given, specific, informed and unambiguous, and you must be able to prove it (Art. 7, EDPB guidelines on consent).

How to collect that consent without losing half your list is the subject of our WhatsApp opt-in guide; the terms opt-in and double opt-in are explained in the glossary. If you collect consent inside a form on WhatsApp, read WhatsApp Flows and GDPR. Ads that open a chat are covered in Click-to-WhatsApp ads and GDPR.

Data transfers and EU storage

WhatsApp belongs to Meta, a US group, so transfers outside the EU are part of the picture (Chapter V, Art. 44 onwards). Three facts help you describe them correctly in your privacy notice:

  • WhatsApp is certified under the EU-U.S. Data Privacy Framework (WhatsApp DPF notice). For business data, WhatsApp's Business Data Transfer Addendum adds standard contractual clauses as a fallback.
  • Cloud API numbers can use local storage. With Meta's local storage option, message data at rest stays in the chosen region, such as the EU. Meta may still process messages outside that region while handling them, for up to about 60 minutes according to its documentation.
  • Meta keeps Cloud API messages for up to 30 days and then deletes them, according to its data privacy documentation.

So the honest wording for your privacy notice is not "no data leaves the EU", but "stored in the EU, with transfers to the US covered by the Data Privacy Framework and standard contractual clauses".

The 9-point GDPR checklist for WhatsApp Business

  1. Choose the setup on purpose. App for a single person with a clean business phone, API for a team. Write the choice down.
  2. Sign a data processing agreement with your provider (Art. 28) and keep a copy of the WhatsApp or Meta terms you accepted.
  3. Add the processing to your record of processing activities (Art. 30): purpose, data categories, recipients, transfers, deletion windows.
  4. Update your privacy notice (Art. 13): name WhatsApp and Meta, your provider, the legal basis and the transfers.
  5. Collect consent before marketing messages, per channel and with proof of when and how it was given. Make opting out as easy as replying STOP.
  6. Keep the address book clean. On the app, the business phone should hold business contacts only, not private ones.
  7. Set deletion windows for messages and inactive contacts. Storage limitation (Art. 5(1)(e)) means data goes when you no longer need it.
  8. Control access (Art. 32): personal logins, roles, multi-factor sign-in, no shared phone passed around the team.
  9. Check whether you need a data protection impact assessment (Art. 35), for example for sensitive data, large volumes or AI that answers customers. Health data deserves extra care; ask your data protection officer before using any messaging channel for it.

What happens if you get it wrong

Two kinds of risk. Customers who suffer damage from a GDPR breach can claim compensation (Art. 82). Supervisory authorities can impose fines (Art. 83): up to €10 million or 2% of worldwide annual turnover for breaches such as missing processing agreements or poor security, and up to €20 million or 4% for breaches of the basic principles, the rules on consent or the rules on transfers, whichever amount is higher. For most SMBs the more likely trigger is a customer complaint about a message they never agreed to, which is why consent comes first on any to-do list.

How SendSeven handles the processor side

SendSeven is a processor for its customers. It cannot make your setup compliant on its own, because your legal basis and privacy notice stay your job, but it covers the parts a provider is responsible for:

  • EU hosting: the platform is hosted in the EU, on Google Cloud in Frankfurt. The ISO 27001 and SOC 2 certificates belong to Google Cloud, not to SendSeven itself.
  • Encryption: TLS 1.3 (1.2 minimum) in transit and AES-256 at rest.
  • Data processing agreement in every plan: the billing account owner can download it at any time under Settings > Legal & Compliance.
  • EU storage for WhatsApp: "Store message data in the EU" is ticked by default when you connect a number in an EU, EEA, Swiss or UK workspace. It is not available for Coexistence numbers.
  • Consent per channel: opt-in by keyword from the customer's own number, opt-out by STOP and double opt-in by email, with consent recorded per channel.
  • Deletion windows you set: under Settings > Data Retention for messages and inactive contacts; after that, deletion runs automatically every night.
  • Access control: roles for every team member, and multi-factor sign-in available per user.
  • AI under your control: AI features are on by default and can be switched off at any time. Your data is never used to train the underlying AI model.

If your chatbot answers customers, the EU AI Act adds a labelling duty; see EU AI Act chatbot labelling.

Frequently asked questions

Is the WhatsApp Business App GDPR compliant?

It can be used lawfully, but it is harder to control. Chats sit on phones, contacts come from the address book and there are no roles. For a single person with a clean business phone it can work; for teams, the API is the easier route.

Do I need consent to reply to a customer on WhatsApp?

Usually not for the reply itself. When a customer asks about an order or an appointment, your answer rests on the contract or the steps before it. For marketing messages you need consent that you can prove.

Do I need a data processing agreement with Meta?

Meta does not sign individual agreements. Its processing terms are part of the WhatsApp and Cloud API terms you accept. You do need a separate data processing agreement with the provider that connects you to the API.

Does WhatsApp data leave the EU?

It can. Cloud API numbers can keep message data at rest in the EU, but Meta may process messages outside the EU for up to about 60 minutes. Transfers to the US rely on the Data Privacy Framework, with standard contractual clauses as a fallback.

Do I need a data protection impact assessment for WhatsApp?

Not always. Check it when you process sensitive data, message large numbers of people or let AI answer customers (Art. 35). Your data protection officer can tell whether your case needs one.

How high are GDPR fines?

Up to €10 million or 2% of worldwide annual turnover for some breaches and up to €20 million or 4% for others, such as breaches of consent rules, whichever is higher. Customers can also claim compensation.

Conclusion

WhatsApp Business and the GDPR fit together when you treat it like any other system with customer data: know your role, choose a legal basis, tell customers, sign the right agreements, describe transfers honestly and delete what you no longer need.

The API makes most of that manageable, because access, consent and deletion live in one platform instead of on a phone. SendSeven adds EU hosting, a data processing agreement in every plan and deletion windows you set yourself. Start with the checklist above, and see the pricing page for plans.