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.
| Field | Purpose | Notes |
|---|---|---|
consent_id | Unique event identifier | System-generated |
person_ref | Pseudonymous reference to the data principal | Keep identity data in a separate table |
channel | whatsapp, sms, email, voice | One consent event per channel |
purpose_code | Specific purpose | For example appointmentreminders, healthtips, campaign_offers |
notice_version | Version identifier of the notice shown | Store the full text of every version |
notice_language | Language the notice was presented in | Section 5(3) |
captured_at | Timestamp with time zone | Server time, not device time |
capture_method | Web form, paper form, WhatsApp reply, QR scan, front-desk tablet, IVR | Each needs different evidence |
capture_evidence_ref | Pointer to the stored evidence | Form snapshot, message ID, scanned page |
affirmative_action | What the person actually did | Ticked an unticked box, sent "YES", signed |
status | granted, withdrawn, expired | Append-only history |
withdrawn_at, withdrawal_channel | Withdrawal evidence | Section 6(4) |
suppression_applied_at | When all sends stopped | Section 6(6) |
processors_notified_at | When vendors were told | Section 6(6) |
collector | Staff member or system that captured it | For 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
| Method | What to store | Common failure |
|---|---|---|
| Web or landing-page form | Form version, field values, timestamp, a rendered snapshot of the consent text | Consent text edited later with no version history |
| Paper form at registration | Scan of the signed page, form version, scanner date | Form with a general "I agree to be contacted" clause bundled with treatment consent |
| WhatsApp reply | Message ID, full text of the notice message sent, the reply, timestamps | Treating a patient's first message to the hospital as consent to broadcast |
| QR code at the front desk | QR landing page version, submission record | Page changed without keeping versions |
| Phone or IVR | Call recording reference where lawful, script version, outcome code | Agent 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.




