Mobile Messaging and GDPR: SMS, WhatsApp and Push Consent
Under GDPR, you can send marketing by SMS, WhatsApp or push notification only if you have a lawful basis and also meet the ePrivacy rules for electronic marketing. In practice that usually means clear, opt-in consent, with a narrow exception for existing customers, plus an easy opt-out in every message.
This guide is for marketers, CRM owners and IT teams in organizations that message people in the EU or UK and want a working compliance setup, not just a policy.
This article is general information, not legal advice.
Key takeaways
- GDPR asks why you may process a phone number at all (lawful basis), while ePrivacy rules decide whether you may send electronic marketing to it.
- In the UK, the ICO says you must not send marketing texts to individuals without specific consent, unless the "soft opt-in" for existing customers applies.
- Valid consent is freely given, specific, informed and unambiguous, and the EDPB says pre-ticked boxes are invalid.
- Apple's App Store rules require explicit opt-in through in-app consent language before you send promotional push notifications.
- GDPR fines can reach up to 20 million euros or 4% of a company's global annual turnover, according to the EDPB.
How do GDPR and ePrivacy rules fit together for mobile messaging?
Two layers apply at once. GDPR governs your use of personal data, such as a phone number or app user ID. The ePrivacy rules, set by the EU ePrivacy Directive (2002/58/EC) and national laws that implement it, govern electronic marketing and access to people's devices.
The European Commission makes the connection explicit: if you use electronic communication tools for direct marketing, you must also comply with the ePrivacy Directive, particularly Article 13, on top of GDPR (European Commission guidance on marketing data). The UK runs the same structure through UK GDPR and the Privacy and Electronic Communications Regulations, known as PECR.
The ICO explains the practical effect. PECR has no lawful bases of its own, but where it requires consent for a channel, consent is the likely lawful basis under data protection law too. Where PECR allows the soft opt-in, legitimate interests can work (ICO, choosing your lawful basis).
Two definitions worth fixing in your head:
- Lawful basis: one of the six legal grounds GDPR allows for processing personal data: consent, contract, legal obligation, public interest, vital interests and legitimate interests (EDPB SME guide).
- Direct marketing: promotional messages aimed at a particular person. A delivery update isn't marketing; a discount code is.
If you also process employee phone numbers for internal alerts, the employee side has its own rules, which we cover in GDPR and HRMS employee data privacy.
Do you need consent to send marketing SMS?
Usually yes. For texts to individuals, consent is the default, and the only common exception is the soft opt-in for your own existing customers.
The ICO's electronic mail marketing guidance treats texts, picture and video messages and social media direct messages as "electronic mail." You must not send marketing to individuals by these channels without specific consent, such as an opt-in box they've ticked. The soft opt-in lets you skip fresh consent only when all of these are true:
- The person bought, or negotiated to buy, a product or service from you.
- You're marketing your own similar products or services.
- You gave a simple way to opt out when you collected the number, and you give one in every message.
It doesn't cover prospects, bought-in lists or charity and political campaigns. The ICO notes this guidance is under review after the Data (Use and Access) Act, so check for updates. EU member states have their own national versions of these rules, and they don't all read the soft opt-in the same way.
Messages also need to identify you, give a valid contact address and offer an opt-out by reply or link that you honor promptly.
If you text job applicants in the US, the rules differ again; see our guide to SMS consent for text-to-apply hiring.
What makes consent valid under GDPR?
Valid consent is freely given, specific, informed and unambiguous, and you must be able to prove it. If any one of those is missing, the consent doesn't count.
The EDPB's Guidelines 05/2020 on consent spell out what that means for sign-up flows:
- No pre-ticked boxes. The EDPB says the use of pre-ticked opt-in boxes is invalid under GDPR.
- No bundling. Consent tucked into general terms and conditions is presumed not to be freely given.
- Separate purposes. If you want to text offers and also share numbers with group companies, ask for each separately.
- Easy withdrawal. Withdrawing must be as easy as giving consent. The guidelines cite a festival that only accepted withdrawals by phone during business hours as non-compliant.
- Don't make it a condition. Tying a service to consent for processing it doesn't need is presumed not to be freely given.
Right to object matters too. The European Commission says people can object to direct marketing at any time, after which you may no longer process their data for that purpose, and you must tell them about this right, free of charge, at the latest at your first communication (European Commission on objections).
How do the rules apply to WhatsApp and push notifications?
The same consent logic applies, with platform rules layered on top. WhatsApp and the app stores add their own opt-in requirements, and breaking them can get your account limited even if a regulator never looks.
| Channel | Legal layer | Platform layer | Practical default |
|---|---|---|---|
| SMS / MMS | Electronic mail rules: consent or soft opt-in for individuals | Carrier and sender ID rules vary by country | Opt-in checkbox, STOP keyword in every message |
| WhatsApp Business | GDPR lawful basis; messaging is likely treated like electronic mail where it's sent to individuals | Meta requires opt-in naming your business before you message | Separate opt-ins for service updates and promotions |
| App push | GDPR lawful basis; ePrivacy device access rules for identifiers and SDKs | Apple requires explicit in-app consent for promotional pushes and an in-app opt-out | OS permission plus a separate marketing toggle |
| Social media DMs | Treated as electronic mail by the ICO | Each platform's messaging policy | Don't send unsolicited promotional DMs |
Meta's WhatsApp opt-in documentation says businesses must get opt-in before messaging people. The person must be told they're agreeing to receive messages and which business will send them, and you must follow applicable law. Meta recommends separate opt-ins by category, such as order updates versus promotions, and warns that low quality ratings from blocks and reports can lead to rate limits.
Push notifications
A push permission from the operating system isn't marketing consent. Apple's App Review Guidelines (4.5.4) say push notifications shouldn't be used for promotions or direct marketing unless customers have explicitly opted in through consent language in your app's UI, and you provide an in-app way to opt out.
Push also touches device access. The EDPB's Guidelines 2/2023 on Article 5(3) of the ePrivacy Directive say storing or reading information on a user's device needs consent unless an exemption applies, and that this covers device identifiers and SDKs that send stored data off the device, and tracking pixels in messages. Your analytics SDKs need the same scrutiny as your marketing copy. Our explainer on how mobile apps track users shows what that looks like from the user's side.
What is a practical GDPR checklist for mobile messaging?
A workable program comes down to collecting consent properly, storing proof, honoring opt-outs everywhere, and auditing what your tools do. Work through these steps in order:
- Map every channel and message type. List SMS, WhatsApp, push, in-app and DMs, and tag each message as service or marketing.
- Pick a lawful basis per message type. Service messages often rest on contract; marketing to individuals usually needs consent or a valid soft opt-in.
- Redesign the opt-in. Unticked boxes, one per channel and purpose, with your business name and what people will receive.
- Record proof. Store who consented, when, where, to what wording and on which channel. Your CRM's consent and audit features should hold this, not a spreadsheet.
- Sync opt-outs across systems. A STOP reply on SMS should suppress WhatsApp promotions too if that's what the person expects.
- Vet vendors. Sign data processing agreements with SMS gateways and messaging providers and check where they store data.
- Audit SDKs and tracking. Confirm which identifiers your app and links collect and whether consent covers them.
- Write the privacy notice for mobile. Short, layered, and including the right to object to direct marketing.
- Review quarterly. Check opt-out handling times, complaint rates and platform quality ratings.
Common mistakes with SMS, WhatsApp and push consent
- Treating a checkout number as marketing consent. A number given for delivery updates isn't permission for promotions, unless the soft opt-in conditions were met at collection.
- Buying or renting lists. The Commission says you must be able to show third-party data was collected lawfully and may be used for advertising. Most purchased mobile lists fail that test.
- Sneaking promotions into service messages. A shipping text with a discount code is a marketing message.
- Relying on the OS push prompt. Accepting notifications isn't agreeing to marketing.
- Forgetting B2B nuance. The ICO says corporate subscribers aren't covered by the same consent rule, but sole traders are treated as individuals, and GDPR still applies to named employees.
Good consent practice also helps engagement. People who chose a channel complain less and churn less, which ties into reducing churn by listening to customers.
FAQ
Can I use legitimate interests for marketing texts?
Only in narrow cases. The ICO says legitimate interests can work for texts to individuals where the soft opt-in applies, meaning existing customers, similar products and an opt-out offered at collection and in every message. For prospects or bought-in numbers, PECR requires consent, so consent becomes your lawful basis under data protection law as well.
Does GDPR apply to transactional messages like delivery updates?
Yes. GDPR covers any processing of a phone number or app ID, so you still need a lawful basis, often contract, and a privacy notice. The extra ePrivacy consent rules target marketing, though, so a pure service message doesn't need marketing consent. Once you add promotional content, it becomes marketing and the stricter rules apply.
Is a WhatsApp opt-in collected on my website valid?
It can be. Meta lets businesses collect opt-in through a website, SMS, phone flow or paper form, as long as the person is told they're agreeing to messages and from which business. For GDPR, the same form must meet the consent standard: unticked, specific to the purpose, and easy to withdraw.
How big are the fines for getting messaging consent wrong?
Under GDPR, the EDPB says fines can reach up to 20 million euros or 4% of a company's global annual turnover. ePrivacy breaches are enforced under national laws with their own penalty regimes. Regulators also order companies to stop processing, which can halt a campaign channel entirely.
What to do next
- Pull a sample of 20 recent mobile messages and label each as service or marketing, with the lawful basis you rely on.
- Screenshot every opt-in point in your app, site and checkout and compare it with the EDPB consent criteria above.
- Test a STOP reply and an in-app opt-out end to end and time how long suppression takes.
- If you use generative AI to draft or personalize messages, review the privacy points in our guide to generative AI and data privacy under GDPR and CCPA.
Sources
- EDPB: Guidelines 05/2020 on Consent
- ICO: Electronic Mail Marketing under PECR
- European Commission: Can Data Received From a Third Party Be Used for Marketing?
- EDPB: Guidelines 2/2023 on the Technical Scope of Article 5(3) ePrivacy Directive
- EDPB: Fines
- Meta: Get Opt-in for WhatsApp
Last reviewed: October 2026.

Comments
Post a Comment