Skip to main content
NewNMC’s advertising guidelines for doctors are in force from 6 Oct 2026. See what to change, and get a free compliance auditNew NMC advertising rules for doctors: what to change
Compliance

Consent Records for WhatsApp, SMS and Email Lists Under DPDP

What proof of consent to store for WhatsApp, SMS and email lists under the DPDP Act, a field-level record schema, evidence by capture method, and how to honour withdrawal across systems.

Consent Records for WhatsApp, SMS and Email Lists Under DPDP

This is an implementation checklist for hospital marketing, CRM and compliance teams in India that send WhatsApp, SMS and email to patient lists. It covers one thing: the evidence you should hold that a person agreed to receive marketing, and how to stop contacting them when they withdraw. It assumes you have read the basics of the Digital Personal Data Protection Act and want field-level detail you can hand to the person building your CRM.

We are a marketing team, not a law firm. Where the statute is clear we quote it. Where the Rules or your own systems need design choices, we say so and mark them as choices to confirm with counsel. This piece is about consent records for marketing channels. Our earlier article on the DPDP Act for healthcare marketing covers the wider obligations, and this one does not repeat them.

What the statute demands of a consent record

Section 6 of the DPDP Act, 2023 is the core. Reading it as a record-keeper:

  • Section 6(1): consent must be free, specific, informed, unconditional and unambiguous, with a clear affirmative action, for a specified purpose, and limited to the personal data necessary for that purpose. The Act's own illustration is a telemedicine app that asks for a phone contact list as well; consent is limited to what telemedicine needs.
  • Section 5(1): every request for consent must be accompanied or preceded by a notice that states the data and purpose, how the person can exercise their rights, and how to complain to the Board. Section 5(3) and Section 6(3) require the option to read the notice and the request in English or any Eighth Schedule language, in plain language, with contact details for a Data Protection Officer or other authorised person.
  • Section 6(4): the person may withdraw consent at any time, and the ease of withdrawing must be comparable to the ease of giving consent.
  • Section 6(6): after withdrawal, the data fiduciary must, within a reasonable time, cease processing and cause its processors to cease, unless law requires or authorises the processing.
  • Section 6(10): if a question arises in a proceeding, the data fiduciary must prove that notice was given and that consent was given in accordance with the Act and Rules.

The last point defines the exercise. You are not recording consent for your own comfort. You are building evidence that you may have to produce.

Timing: what applies when

The Rules were notified in November 2025. The Press Information Bureau's explainer on the DPDP Rules describes an eighteen-month period for phased compliance and says every data fiduciary must issue a separate, clear consent notice that explains the specific purpose of collection and use. It also says data fiduciaries must respond to rights requests within ninety days and display contact details for queries about personal data. Check the Rules themselves for the date on which each rule applies to you, because some provisions commence earlier than others. Do not wait for the final date to start: records you stop creating today cannot be reconstructed later.

The NMC's October 2026 advertising notice also ties the two regimes together. Paragraph 7.6 says advertisements involving processing, publication, storage or disclosure of digital personal data must comply with the IT Act and with the DPDP Act and Rules of 2025, to the extent applicable. A hospital list that is not properly consented is therefore both a privacy issue and a medical-advertising issue.

The record: a field schema

The schema below is a design proposal, not a statutory form. It is shaped to answer the five things Section 6(10) puts on you: what notice was shown, what was agreed, how, when, and what happened afterwards. Use one row per consent event, never overwrite, and add a new row for each change.

FieldPurposeNotes
consent_idUnique event identifierSystem-generated
person_refPseudonymous reference to the data principalKeep identity data in a separate table
channelwhatsapp, sms, email, voiceOne consent event per channel
purpose_codeSpecific purposeFor example appointmentreminders, healthtips, campaign_offers
notice_versionVersion identifier of the notice shownStore the full text of every version
notice_languageLanguage the notice was presented inSection 5(3)
captured_atTimestamp with time zoneServer time, not device time
capture_methodWeb form, paper form, WhatsApp reply, QR scan, front-desk tablet, IVREach needs different evidence
capture_evidence_refPointer to the stored evidenceForm snapshot, message ID, scanned page
affirmative_actionWhat the person actually didTicked an unticked box, sent "YES", signed
statusgranted, withdrawn, expiredAppend-only history
withdrawn_at, withdrawal_channelWithdrawal evidenceSection 6(4)
suppression_applied_atWhen all sends stoppedSection 6(6)
processors_notified_atWhen vendors were toldSection 6(6)
collectorStaff member or system that captured itFor audit

Three design rules follow from the Act.

One purpose, one consent. Consent for appointment reminders is not consent for campaign offers. Do not bundle. A single combined tick-box for "updates, offers and news" undermines the "specific" requirement.

No pre-ticked boxes, no consent by silence. The Act requires a clear affirmative action. A form that goes ahead when the box is left blank gives you no usable record.

Store the notice, not only the fact. A row that says "consented, 12 March" proves little. A row that points to notice version 3, in Hindi, captured through the front-desk tablet with a stored screenshot of the screen, proves a lot.

Evidence by capture method

MethodWhat to storeCommon failure
Web or landing-page formForm version, field values, timestamp, a rendered snapshot of the consent textConsent text edited later with no version history
Paper form at registrationScan of the signed page, form version, scanner dateForm with a general "I agree to be contacted" clause bundled with treatment consent
WhatsApp replyMessage ID, full text of the notice message sent, the reply, timestampsTreating a patient's first message to the hospital as consent to broadcast
QR code at the front deskQR landing page version, submission recordPage changed without keeping versions
Phone or IVRCall recording reference where lawful, script version, outcome codeAgent paraphrases the script

For WhatsApp, the platform adds its own requirement on top of the law. The WhatsApp Business messaging policy says a business may only message people who have given their number and have given opt-in permission confirming they wish to receive subsequent messages. The business is responsible for choosing an opt-in method that complies with the communication laws that apply to it, the policy suggests separate opt-ins for each message category, and the business must honour requests to stop, whether made on or off WhatsApp. Our guide to WhatsApp marketing for healthcare covers setup and automation; here the point is evidence.

SMS and calls also fall under telecom rules on commercial communication, including sender and template registration. Those sit outside the DPDP Act, and this article does not cover them. Make sure your SMS vendor's records satisfy both.

Want this applied to your practice? Get a free compliance audit.

Book my free audit

Withdrawal: designing "as easy as giving"

Section 6(4) is a design standard. If a patient gave consent by sending "YES" on WhatsApp, withdrawal should be as simple as sending "STOP". If consent was a tick on a web form, the withdrawal route should not require a phone call during office hours. Practical rules:

  1. Offer a withdrawal route in every message. Email gets an unsubscribe link. WhatsApp templates carry a stop instruction. SMS carries a short keyword.
  2. Process it across systems. A "STOP" received in WhatsApp should suppress that purpose across the CRM, the email platform and any scheduled campaign, and should pass to every processor, as Section 6(6) expects.
  3. Set a service level. Choose an internal standard, for example suppression within one working day, and measure it. The Act says "within a reasonable time", so the number is your design choice. Document it.
  4. Keep a minimal suppression record. To make sure you never re-contact a person who withdrew, you need to retain something. Many teams keep a hashed identifier and the purpose code. Confirm this design with counsel against the Rules' provisions on erasure and retention.
  5. Do not penalise withdrawal. Section 6(5) puts the consequences on the person, but you may stop only what depended on the consent. A withdrawal from marketing must not affect their care.
  6. Log the outcome. Fill withdrawn_at, withdrawal_channel, suppression_applied_at and processors_notified_at, and keep the evidence.

Consent for care reminders and consent for marketing are different things. Section 7(a) separately permits processing for the specified purpose for which a person voluntarily provided their data, unless they have indicated they do not consent to that use. Whether a particular reminder qualifies depends on the facts and the purpose recorded, so take advice before relying on it for anything promotional.

Legacy lists

Many hospitals hold lists built over years from registration forms, camps and enquiries. Section 5(2) addresses consent given before the Act commenced: the data fiduciary must give notice as soon as reasonably practicable, and may continue processing until the person withdraws. That does not make an old, bundled "I agree to be contacted" clause equivalent to a fresh consent. Ask counsel how your historical records fit.

A method for assessing a legacy list, with no results assumed:

  1. Take a random sample of 100 records from each source system.
  2. For each, ask whether you can find the notice shown, the purpose, the date, the method and the evidence.
  3. Classify records as fully evidenced, partly evidenced or unevidenced.
  4. Report the split by source, and decide what to do with each class: keep, re-permission or retire.
  5. Run a re-permission campaign only to records you have a lawful basis to contact, and record the new consent in the schema above.

A hypothetical example: a 200-bed hospital in Pune finds that its camp-registration list has no stored notice at all, while its web-form list stores the form text and timestamp. The camp list becomes a re-permission candidate, handled at the front desk or through a service message you are lawfully allowed to send. The web-form list is kept, with its records mapped into the schema.

Tooling

You need a system of record for consent that your channels read from. If WhatsApp outreach runs in one tool, email in another and registration data in a hospital system, the consent table must be the shared source of truth. WaCRS can help plan WhatsApp outreach campaigns and manage business conversations, and in any tool, check how consent status is read before each send. Our healthcare marketing automation service covers the integration work.

Our wider reading on patient nurture sequences by email is a good companion when you rebuild sequences around purpose-specific consent.

Where to start

  1. Inventory every list: source, channel, volume, capture method and whether notice and evidence are stored.
  2. Fix the capture points first. New records should arrive with the full schema.
  3. Add withdrawal to every message template and test it end to end, including the suppression across vendors.
  4. Version your notices, in English and the languages your patients use.
  5. Audit a sample from each legacy source and decide what to keep, re-permission or retire.
  6. Brief your agencies in writing. If they send on your behalf, they must read from your consent table.
Filed underdpdp consent records marketingDPDP consent WhatsApp marketingDPDP consent withdrawalhospital consent management IndiaDPDP Rules 2025 consent notice

About the author

Founder & CEO · Gurugram, India

Nishu founded Branding Pioneers in 2016 with one rule that hasn't changed since: healthcare only. She'd run digital strategy at a top-10 Indian agency and watched generalist marketing underserve medical clients who needed something built for how patients actually search and decide. So she left to build the specialist instead. It's now an 80-person team working with healthcare brands worldwide.

Free guide · 15 pages

The Patient Acquisition Blueprint

A 90-day plan from first search to booked appointment.

The Pioneers Brief — one essay, three benchmarks, one teardown, every Thursday. Subscribe free →

Free compliance audit

Your next chapter starts with a conversation.

Three quick questions. We come prepared with a plan for your specialty and city.

  • A 30-minute call with a healthcare specialist
  • Your top three growth opportunities, in writing
  • Honest advice — even if that means not hiring us
  • No obligation and no hard sell
You’ll speak with a senior strategist
Consultations are hosted by Arush Thapar’s team.
Step 1 of 3Takes 30 seconds

What do you want to improve first?

Details stay privateNo obligationReply within 1 working day

Client portfolio · BTL & activations

Work relevant to consent records for whatsapp sms and email lists under dpdp.

Explore client work →