← All news and guides
Data protection

DPDP Marketing Consent: WhatsApp, SMS and Retargeting

How DPDP consent applies to marketing: what a valid opt-in is, how WhatsApp, SMS and retargeting differ, and how to make a withdrawal reach every tool.

Mono Team ·

A marketing team desk with a phone, a blank notepad and a coffee cup in warm office light, the background softly blurred.

Short answer: under the DPDP Act, marketing needs its own consent, and that consent has to be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, and as easy to withdraw as it was to give. Treat each marketing purpose (email, WhatsApp, SMS, calls, retargeting audiences) as a separate consent with its own record. Then add the channel rules. For SMS and calls, TRAI's TCCCPR applies. For WhatsApp, Meta's Business Messaging Policy applies. DPDP consent applies to both, and to retargeting. The engineering test is simple. When a person says stop, every tool that holds their data must stop, and you must be able to show when it did. The core DPDP duties start on 13 May 2027.

This is engineering guidance, not legal advice. Which legal ground fits a given message, and how to word your notice, are questions for counsel. Here we cover what to build, what to record and where the channel rules differ.

Which rules cover which marketing channel?

The Act and Rules govern the personal data. TRAI governs SMS and voice. Meta governs its own platform. A message can be caught by more than one.

ChannelRule set that appliesWhat it adds to DPDP consent
EmailRule set that applies: DPDP Act and RulesWhat it adds to DPDP consent: Nothing extra from TRAI or Meta. Your own consent record, notice and withdrawal path carry the load.
SMS and voice callsRule set that applies: DPDP Act and Rules, plus TRAI's TCCCPR 2018 as amendedWhat it adds to DPDP consent: Registered senders, message headers, a consent register, opt-out and consent-validity rules.
WhatsAppRule set that applies: DPDP Act and Rules, plus Meta's Business Messaging PolicyWhat it adds to DPDP consent: Opt-in permission, and respecting requests to block, stop or opt out, on or off WhatsApp.
Retargeting and custom audiencesRule set that applies: DPDP Act and Rules, plus each ad platform's termsWhat it adds to DPDP consent: Consent for the ad purpose, a lawful route to the platform, and suppression when consent ends.

In short: SMS and calls fall under TRAI's TCCCPR. WhatsApp falls under Meta's policy. DPDP consent applies to both. We found no provision in the TCCCPR that extends it to WhatsApp, although some stakeholders asked TRAI to do so in a 2026 consultation. Do not build your WhatsApp programme around that gap.

A shop counter in soft morning light with a small stack of blank paper slips and a brass bell beside an old rotary telephone, the shelves behind softly blurred.

Section 6(1) sets the test. Consent must be free, specific, informed, unconditional and unambiguous with a clear affirmative action. It must signify agreement to a specified purpose and be limited to the personal data necessary for that purpose. Turned into design rules:

  • A clear affirmative action. The person ticks an empty box, taps a button or sends an opt-in message. Pre-ticked boxes, silence and scrolling do not count as an action.
  • Specific. One purpose per consent. "Order updates" and "offers on WhatsApp" are two purposes. "Offers" and "sharing with partners" are two more.
  • Unconditional. Do not make marketing consent a condition of buying, signing up or getting support, unless the marketing is itself necessary for the service. The Act's own illustration says a telemedicine app cannot rely on consent to read a contact list that the service does not need.
  • Informed, with a standalone notice. Rule 3 requires the notice to be understandable on its own. It must itemise the personal data, state the specified purpose, and give links to withdraw consent, to exercise rights and to complain to the Data Protection Board.
  • Plain language, with choice of language. Section 6(3) requires a clear and plain request, available in English or any Eighth Schedule language, with the contact details of a Data Protection Officer or another person authorised to respond.
  • Provable. Section 6(10) puts the burden on you. If a question arises, you must prove that a notice was given and consent was given in line with the Act and Rules. A log is your proof.

Two cautions. First, do not bundle. One "I agree to the terms and to receive offers" checkbox is hard to defend as specific or unconditional. Second, do not confuse service messages with marketing. An order confirmation or a delivery OTP may rest on a different ground, such as the section 7(a) legitimate use for data a person voluntarily gave for a stated purpose. The moment a message includes an offer or a cross-sell, treat it as marketing. Which ground fits is for counsel.

One consent log serves every channel. Our consent log guide covers the design. For marketing, make sure each event stores at least these fields.

FieldWhy it matters
Person identifier (internal ID, not just a phone number)Why it matters: Phone numbers get reassigned. Tie consent to a person and a verified identifier.
Purpose and channelWhy it matters: One row per purpose and channel, for example `promo_offers` on `whatsapp`.
Action: granted, denied or withdrawnWhy it matters: Record denials and withdrawals as events. Never overwrite a grant.
Notice version and language shownWhy it matters: Proves what the person was told, as section 6(10) expects.
Timestamp and sourceWhy it matters: Where the action happened: form, checkout, app, inbound WhatsApp message, store counter, import.
Evidence referenceWhy it matters: A form snapshot, message ID or session reference that lets you replay the screen or chat.

Keep the log append-only, and make every sending system check it before it sends. A tool with its own private opt-in list is a second source of truth, and it will drift.

Meta's Business Messaging Policy, updated 23 September 2026, sets a baseline. You may contact people only if they have given you their mobile phone number and you have received opt-in permission. You must respect all requests, on or off WhatsApp, to block, discontinue or otherwise opt out. Build to that, and to DPDP, at once.

  • Collect the opt-in in a way you can prove. A web form checkbox with the notice beside it, or an inbound message from the customer that clearly asks for offers. Store the evidence reference in your log.
  • Name WhatsApp and the purpose. "Send me offers on WhatsApp" is specific. A general "contact me" is not. Keep order updates and offers on separate opt-ins.
  • Make stopping easy inside the chat. Honour a STOP or "unsubscribe" reply, and also a block or a request made by email, call or support ticket. Meta's policy covers requests made off WhatsApp as well.
  • Treat your messaging provider as a processor. The provider or BSP sends on your behalf. Section 8(2) of the Act needs a valid contract, and section 8(1) leaves you responsible. Our processor guide shows what to put in that contract.

What do the TRAI rules add for SMS and voice calls?

A row of old desk telephone handsets resting in their cradles on a long wooden table in a quiet office, late light from a side window, the far end out of focus.

TRAI's Telecom Commercial Communications Customer Preference Regulations (TCCCPR), 2018 are amended. TRAI published the 2025 amendment on 12 February 2025, and further amendments dated 18 September 2026 and 4 November 2026 appear on its regulations page. The 2026 documents are scanned PDFs, so treat our summary of them as a pointer and read the text before you act.

From TRAI's release on the 2025 amendment, the points that matter for engineering are:

  • Promotional messages must carry a mandatory way to opt out.
  • Message headers carry a standard suffix that tells the reader whether the message is promotional, service, transactional or government. Check the exact suffix letters in the regulation text before you configure headers.
  • A sender must not ask for consent again from someone who opted out, for 90 days from the opt-out. The customer can still opt in at any time.
  • Consent given to complete an ongoing transaction is valid for only 7 days.
  • Implied consent for transactional and service messages lasts only for the duration of the contract. After that, a service call needs explicit consent.
  • Promotional calls use the 140 series. Service and transactional calls use the 1600 series.

The September 2026 amendment changes the definition of Explicit Consent. As we read it, consent can now also be one that a sender obtained by any verifiable means before or outside the consent registration framework, provided it is then registered in the Consent Register under the procedure TRAI specifies. Commencement is staged, so confirm the dates that apply to you.

What this means for your build:

  • Keep the 90-day cool-off as a rule in your consent service.
  • Store the TRAI consent reference next to your own DPDP record, so one withdrawal updates both.
  • Never send an offer through a transactional route.
  • Send suppression lists to your SMS gateway or telemarketer, and check that it applies them.

Passing the TRAI check does not pass the DPDP check. A message can go out on a registered header and still lack a section 6 consent record for the purpose.

How does retargeting fit under DPDP?

Retargeting means showing ads to people who visited your site, used your app or sit on your customer list. It runs on three mechanisms: tags and SDKs that report browsing events to an ad platform, uploads of customer identifiers (emails, phone numbers) to build audiences, and server-to-server events that send purchases back to the platform. All three move personal data to another company.

  • Consent for the ad purpose. If you rely on consent, ask for it for advertising and name the platforms or categories in the notice. Do not hide it inside a cookie banner line about "improving your experience". The Act does not mention cookies. The test is whether personal data is collected and shared for a specified purpose.
  • Load tags after the choice. A tag manager should fire ad tags only after the person has said yes, and must stop when they say no.
  • Hashed identifiers are still personal. A hashed email can be matched back to a person by the platform that receives it. Treat uploaded audiences as personal data and keep them in your data map. Confirm the legal position with counsel.
  • Suppress on withdrawal. When someone withdraws, remove them from every audience, stop server events about them, and block re-import from stale exports.
  • Children. Section 9(3) bars tracking or behavioural monitoring of children and targeted advertising directed at children. There are exemptions for classes the Rules prescribe. If under-18s use your product, you need an age signal, and you need to switch ad tags off for them. Our parental consent guide covers the design.

Run a tag audit first: list every pixel, SDK and server-side event, what each sends and where it goes. Our mobile SDK data audit guide shows how.

How do you build withdrawal that reaches every tool?

Section 6(4) says withdrawal must be as easy as giving consent. Section 6(6) says that on withdrawal the fiduciary must, within a reasonable time, cease processing and cause its processors to cease. The Act does not define a reasonable time. Pick an internal service level and write it down.

A withdrawal has to reach each place that holds marketing data.

SystemWhat withdrawal must doHow to test it
Email service providerWhat withdrawal must do: Move the address to a suppression list for that purposeHow to test it: Withdraw a test user, send a campaign, confirm no delivery
WhatsApp providerWhat withdrawal must do: Block marketing templates for that numberHow to test it: Send a test template and confirm it is refused by your own check
SMS gateway and diallerWhat withdrawal must do: Add to do-not-send and do-not-call listsHow to test it: Compare the gateway list with the consent log
Ad platformsWhat withdrawal must do: Delete the person from custom audiences and stop eventsHow to test it: Check audience exports after the next sync
CRM and data warehouseWhat withdrawal must do: Flip the consent flag and exclude from segmentsHow to test it: Run the segment query and look for the test user
Offline lists and agency filesWhat withdrawal must do: Request removal, and keep the confirmationHow to test it: Ask for a written confirmation from the agency

Withdraw by purpose, not all or nothing. Someone who stops WhatsApp offers may still want order updates. And a withdrawal does not undo earlier lawful processing (section 6(5)). It stops what comes next.

Our consent management service builds this chain: the log, the preference centre, the notices and the propagation to each tool.

What about existing marketing lists?

Section 5(2) deals with consent given before the Act started. The fiduciary must, as soon as reasonably practicable, send a notice that describes the personal data and purpose, explains how to withdraw and exercise rights, and how to complain to the Board. It may continue to process until the person withdraws.

A practical clean-up for an old list:

  • Export the list with the source and date for each contact. Drop anyone you cannot trace to a real opt-in, and split the rest by purpose.
  • Send the notice and a clear way to opt out. Log each reply.
  • For SMS and calls, check the legacy consent against TRAI's rules as well. The September 2026 amendment points to registering legacy consents in the Consent Register.
  • Retire anything with no consent evidence and no valid ground.

How does this apply to marketplaces and consumer apps?

A marketplace connects buyers, sellers and often delivery partners. Each group gives data for a different purpose, and marketing mixes them easily. The risk is not one big failure. It is many small flows that nobody mapped.

GroupData flows to mapMarketing consent point
BuyersData flows to map: Profile, address, orders, browsing, payment eventsMarketing consent point: Marketplace offers need the buyer's own consent. A seller's offers are a different purpose and a different recipient.
SellersData flows to map: Business and contact details, catalogue, bank details, performance dataMarketing consent point: Seller contact for promotions needs consent from the individual. Sellers' staff data is personal data too.
Delivery partnersData flows to map: Identity, phone, live location, trip historyMarketing consent point: Do not reuse location or contact data for marketing. Whether a partner counts under the employment ground is for counsel.
  • Buyer data given to sellers. Pass sellers only what they need to fulfil the order. If a seller wants to market to that buyer, the buyer must consent to that seller for that purpose.
  • Delivery data. Keep rider locations and numbers out of marketing systems.
  • Roles. Work out whether the platform and each seller are separate fiduciaries or one is the other's processor. Write it into the seller agreement.
  • Erasure for large platforms. The Third Schedule to the Rules sets a 3-year inactivity period, with 48 hours' notice, for e-commerce entities with 2 crore or more users. Marketing data that you no longer need before then should go earlier. Our erasure automation guide shows how.

What should you build before 13 May 2027?

  • Map every marketing system, tag and vendor that holds personal data.
  • Build the append-only consent log and make every sender check it before it sends.
  • Add working opt-out in each channel and propagate withdrawals to every tool, with a written service level.
  • Align SMS and voice handling with TRAI's rules, and WhatsApp handling with Meta's policy.
  • Test everything with a dummy user, and keep the test evidence.

Not sure where your marketing data sits? Start with a gap assessment.

Sources: Digital Personal Data Protection Act, 2023, sections 5, 6, 7, 8 and 9 and the Gazette text. Digital Personal Data Protection Rules, 2025, Rule 3 and the Third Schedule. TRAI, Telecom Commercial Communications Customer Preference Regulations, 2018 and amendments, https://www.trai.gov.in/release-publication/regulations; TRAI Press Release No. 11/2025, 12 February 2025. Meta, WhatsApp Business Messaging Policy, updated 23 September 2026, https://whatsappbusiness.com/policy/. Last reviewed 20 November 2026.

FAQ

Do I need DPDP consent to send marketing messages?

In most cases yes, in our reading. Marketing is not an obvious fit for the legitimate uses in section 7, so consent under section 6 is the usual basis. It must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, with a standalone notice. Which ground fits a particular message is a question for counsel. The core duties start on 13 May 2027.

Does the DPDP Act cover WhatsApp marketing?

Yes, where you process personal data such as a phone number to send it. DPDP consent applies to the purpose. Meta's Business Messaging Policy adds its own rules: you may contact people only if they have given you their number and you have received opt-in permission, and you must respect requests to block or opt out, on or off WhatsApp.

Do TRAI rules apply to WhatsApp messages?

TRAI's TCCCPR covers SMS and voice calls. We found no provision in it that extends to WhatsApp, although stakeholders asked TRAI to consider this in a 2026 consultation. Check the current regulation text. Even so, DPDP consent and Meta's policy still apply to WhatsApp marketing.

How quickly must I stop marketing after someone withdraws consent?

Section 6(6) of the DPDP Act says within a reasonable time, and the fiduciary must make its processors stop too. The Act does not set a number of hours or days, so set and document an internal service level. For SMS, TRAI's rules add that you cannot ask an opted-out person for consent again for 90 days.

Is retargeting allowed under the DPDP Act?

It can be, if you have a lawful ground and handle it properly. Collect consent for the advertising purpose, fire ad tags only after the person says yes, treat uploaded customer lists as personal data, and remove people from audiences when they withdraw. Section 9(3) bars tracking of children and targeted advertising directed at children.

Are marketplaces treated differently from other apps under DPDP?

The same duties apply, but the data flows are more complex. Buyers, sellers and delivery partners each give data for different purposes, and a seller who wants to market to a buyer needs the buyer's own consent. Large e-commerce entities with 2 crore or more users also fall under the Third Schedule erasure period of 3 years.

Build marketing consent that stands up to an audit.