Proving WhatsApp Marketing Consent: Build an Opt-In Log
You send WhatsApp messages to customers and they're happy with them, until a regulator or a customer asks: "what did I sign up for?" Without a provable opt-in log you're left empty-handed, even if the consent was perfectly legitimate at the time. This article shows how to record consent for WhatsApp marketing in a way that holds up.
This is general information, not legal advice. For your specific situation, consult a lawyer or DPO.
Why "they said yes" isn't enough
Under the GDPR, the burden of proof for consent is on you, not the customer. Article 7(1) GDPR is explicit about it: the controller must be able to demonstrate that the data subject has given consent. "I'm sure he said yes at the counter" isn't proof; a timestamped record is.
For transactional messages (order confirmation, appointment reminder) you usually rely on a different legal basis than consent, such as performance of a contract. But as soon as you use WhatsApp for marketing, offers or newsletters, in practice you need consent, and therefore also the proof of it.
What an opt-in record contains at a minimum
A usable consent record is not a tick in a spreadsheet. It contains at least:
- Who: the phone number (and name/customer ID if known).
- When: the exact timestamp of the moment of consent.
- For what: the precise text or description used to ask for consent (e.g. "Receive WhatsApp offers from Bakery X").
- How: the channel: web form, in-store QR code, checkbox at checkout, verbally at the counter followed by a confirmation message.
- Source/version: which version of your privacy statement or opt-in text applied at that moment.
- Withdrawal: the date and manner in which someone later unsubscribes, if that happens.
Keep this separate from your message log. It's a legal piece of evidence, not operational data.
Practical setup: tie opt-in to an event, not a tick
The most robust approach: consent is only registered after the user has confirmed an action themselves, and that confirmation automatically generates the proof.
- Double opt-in via WhatsApp itself. Have people send "START" or "YES" to your number after a web form. The incoming message with its time and sender number is your proof right away, with nothing extra to keep track of.
- Webhook events as source data. Every incoming message that arrives through your webhook already carries a timestamp and the sender's number. Store that specific confirmation message separately in your opt-in table as soon as it contains the trigger text, rather than relying on your general chat history. See the webhooks documentation for the exact payload fields you can use for this.
- Log form opt-ins with metadata. For a web form or checkout checkbox, log not only "consent = true" but also the IP address, the user agent and the exact form text at that moment (keep a version of your form copy in git or a CMS with history).
- STOP always keeps working, alongside opt-in. Regardless of how someone signed up, a "STOP" message must always be processed as an opt-out. TextMeFlow's anti-spam pipeline processes STOP messages automatically as part of its standard handling. That's your safety net if your own opt-in administration has a gap.
Retention: keep the opt-in proof, clean up the rest
A common mistake is companies keeping full chat histories for years "just in case", when the opt-in record (small, structured, easy to store) is the only thing you really need for a long time. Set a retention period for ordinary message content (often a few months to a year is enough) and keep the consent record separately, typically for as long as the customer relationship lasts plus a reasonable limitation period. For a more thorough approach to retention periods in general, see our article on WhatsApp data retention under the GDPR.
What if someone asks to see their consent proof
An access request can also be specifically about your opt-in administration: "when and for what did I give consent?" Because you keep this record separate from your regular chat data, it's a matter of looking up one row by phone number rather than searching a full chat export. Our approach to handling that kind of request is worked out in GDPR access and deletion requests about WhatsApp data.
Checklist to start today
- One separate table or sheet for opt-in records, apart from your chat logs.
- Each record contains: number, timestamp, exact opt-in text, channel, form version.
- Double opt-in via a WhatsApp confirmation message where possible.
- STOP handling is on and tested.
- Retention period set and documented, separately for opt-in proof versus message content.
- Withdrawal (unsubscribe) is added with a date to the same record, never deleted.
With that log in order, you answer a GDPR question in minutes instead of falling into audit panic.
Want to see how TextMeFlow's webhook events and STOP handling support this in practice? Try it for free with the free plan (50 messages/month, for life), with EU hosting in Paris and an automatic data processing agreement once 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