GDPR and WhatsApp — what every small business needs to know
Using WhatsApp to talk to customers means handling personal data: phone numbers, names and the content of conversations. This guide uses the GDPR (the EU General Data Protection Regulation) as its baseline: it applies to businesses established in any EU country — Portugal, Spain, Ireland, Germany and the rest — and to businesses elsewhere that offer services to people in the EU. Each country also has its own data protection authority and, in some cases, extra rules for marketing messages. On top of that, Meta has its own WhatsApp Business policies.
If your business is outside the EU, the same good practices apply, but check your local law (for example the UK GDPR, US rules on marketing messages, Brazil’s LGPD or Mexico’s data protection law).
The golden rule — outbound messages only with consent
To start a conversation with someone (a campaign, a template message, a promotional notice), you need clear, prior consent. Having their number is not enough. In the EU, the rules on electronic marketing (the ePrivacy rules, applied by each country’s national law) generally require prior consent for promotional messages; other countries have similar rules.
Valid consent:
- A checkbox ticked by the person themselves (never pre-ticked) on a form
- The customer messaged your business number (you can reply to them)
- Double opt-in ("reply YES to receive our messages")
- Documented verbal agreement (a call recorded with permission)
Invalid consent:
- A purchased list of numbers
- A pre-ticked checkbox
- Agreement buried in generic terms
- Contacts imported from a personal address book for campaigns
Which legal basis to use (GDPR)
The GDPR lists six legal bases. For business WhatsApp, the most common are:
- Consent — the most common; it must be as easy to withdraw as to give
- Performance of a contract — for existing customers: invoices, order updates, appointment reminders
- Legitimate interests — limited use, requires a documented balancing test
For most small businesses, consent is the simplest path to document.
What to record for each contact
To be able to prove compliance:
- When consent was given (date and time)
- Where (which form, page or channel)
- The IP address of the person who agreed, when available
- The exact text the person agreed to at that moment
- Authorized channels (WhatsApp? Email?)
Opt-out — how to respect it
Every outbound message should include a way to opt out. Suggested text:
To stop receiving these messages, reply STOP.
When you receive "STOP" (or variations: unsubscribe, cancel, quit):
- Mark the contact as unsubscribed automatically
- Block future outbound messages
- Confirm with a single message: "Done! You will no longer receive this type of message."
- Keep serving them if the customer contacts your business
The right to deletion
Under the GDPR (the "right to erasure"), people can ask you to delete their personal data, and you must reply within one month (extendable in some cases). Laws in many other countries give a similar right.
This includes:
- The record (name, email, phone)
- Conversations
- Internal notes that identify the person
- Backups (deleted or anonymized within a defined period)
Exceptions: data the law requires you to keep (tax records, active contracts, etc.).
How long to keep data
There is no single fixed period. The rule is: only for as long as needed for the purpose.
Reasonable references:
- Resolved support conversations — 12 to 24 months
- Leads who did not become customers — up to 24 months
- Active customers — during the contract and the tax retention period afterward
- Technical logs — 12 months
This policy must be described in your Privacy Policy.
What is at stake
GDPR fines can reach €20 million or 4% of global annual turnover, whichever is higher, and data protection authorities can order you to stop processing data — for example, banning campaigns for a period. Outside the EU, local laws also provide for fines and, in some countries, damages per message sent without consent. For a small business, the reputational damage also matters.
Quick checklist — are you compliant?
- [ ] You have a public Privacy Policy
- [ ] Consent is an unticked checkbox with clear text
- [ ] You record the date, time and source of consent
- [ ] Every outbound message says how to opt out
- [ ] You have a channel for deletion requests (e.g. a privacy email)
- [ ] You know who is responsible for data protection in your business (and whether you need a Data Protection Officer)
- [ ] You document the legal basis for each use
- [ ] You never buy lists
If you answered "no" to 2 or more items, fix them before your next campaign.
How Blocks2Work helps
- Consent recorded per contact (date, time and source)
- Automatic opt-out when a customer replies STOP
- A record of who did what in the account
- Export of all your data ("Download my data") and account deletion
- Message content, notes and attachments stored encrypted
- Media received through WhatsApp automatically deleted after 30 days
Next step
Create your free account — privacy features come built in.
This guide is informational and does not replace advice from a lawyer in your country.
See also: WhatsApp Business API, Conversational automation.
Put this into practice with Blocks2Work
Team WhatsApp, an AI customer-service bot, calendar and CRM in one place, for US$ 19.90/month (€19.90 in Europe). 14-day free trial, no card.
Start free →