On 13 November 2026, Rule 4 of India's Digital Personal Data Protection (DPDP) Rules, 2025 comes into force. It covers Consent Managers: registered platforms that let people give, review and withdraw consent across businesses. Many posts online are treating this date as the day every business must be fully DPDP-compliant. That is not what the rules say. Most obligations for ordinary businesses, such as notices, consent, security safeguards, breach reporting and user rights, start on 13 May 2027.

This guide explains what changes now, what can wait, and what clinics, coaching classes and D2C brands in Mumbai should do with their WhatsApp, website and CRM data. It is a practical guide, not legal advice; for your specific situation, speak to a lawyer.

The DPDP timeline

DateWhat comes into force
13 November 2025Rules notified (Gazette G.S.R. 846(E)). Rules 1, 2 and 17–21 apply: the Data Protection Board and its procedures.
13 November 2026Rule 4: registration and obligations of Consent Managers.
13 May 2027Rules 3, 5–16, 22 and 23: notices, consent, security, breach intimation, retention, children's data, user rights and the rest of the core duties.

Some sources give 14 November 2025 as the publication date because the Gazette was published a day after the notification. Either way, the core business obligations start in May 2027.

Timeline of DPDP Rules 2025 commencement dates in India
Most business duties start on 13 May 2027.

What 13 November 2026 means for a small business

Consent Managers are registered with the Data Protection Board and act as a single point for people to manage consent. A clinic or coaching class does not have to become a Consent Manager. But people may start using Consent Managers to give or withdraw consent, so your systems should be able to respect a withdrawal when it reaches you. For most small businesses this is a planning milestone, not a hard switch-over day.

What to do in the next six months

  1. Map your personal data. List where customer, patient or student data lives: WhatsApp, Google Sheets, CRM, Shopify, forms, email.
  2. Collect only what you need. A booking bot needs name, phone and slot, not date of birth and address.
  3. Write a clear notice. In plain English (and Hindi if your customers prefer it), say what you collect, why, and how to withdraw consent.
  4. Get proper WhatsApp opt-in. Ask before sending promotional messages, and keep a record of the opt-in.
  5. Lock down access. Remove old staff accounts, use two-factor login, and keep API keys on the server.
  6. Plan for deletion. Decide how long you keep leads and patient chats, and automate deletion or archiving.
  7. Check your vendors. Your WhatsApp provider, CRM and AI tools process data for you; read their data terms.

By industry

  • Clinics: patient details and health information need extra care. Keep clinical conversations with doctors, not in a bot, and limit who can read chats. See WhatsApp automation for clinics.
  • Coaching institutes: many students are under 18, and the rules have specific requirements for children's data from May 2027. Parents' consent flows matter.
  • D2C brands: marketing broadcasts and retargeting depend on clear consent; make unsubscribe easy.

How we help

When we build AI and WhatsApp automations, we include consent wording, minimal data collection, access controls and action logs by default. If you already run automations, we can review them against this checklist.