Technology & AI 20 November 2026 7 min read

India's DPDP Rules: What Businesses Must Change Before May 2027

Leadership team around a boardroom table with data dashboards on the wall screens

India's Digital Personal Data Protection Act was passed in 2023, but for two years it had no operating rules and could not bite. That changed when the Ministry of Electronics and Information Technology notified the Digital Personal Data Protection Rules, 2025 on 13 November 2025. The Rules switch the law on in three phases, and the second one passed a week ago: since 13 November 2026, consent managers can register with the Data Protection Board.

The phase that matters to most organisations is the third. Notice and consent, security safeguards, breach reporting, children's data, data principal rights and the Board's power to penalise all apply 18 months after notification, which commentators put at 13 May 2027. That is about six months away. For a company holding customer, employee or patient data in a dozen systems, that is not long, and much of the work sits where legal teams rarely look: sign-up flows, CRM fields, log retention settings and vendor contracts.

This is a practical list of what to change, written for Indian businesses and for foreign companies that process personal data of people in India. The Rules are new and some provisions are still being interpreted, so use it to organise the work and take advice from Indian counsel on the details.

The timeline, and what is still moving

Law firm analyses, including AZB & Partners', describe the phasing the same way.

  • 13 November 2025. The Data Protection Board and its procedures came into existence.
  • 13 November 2026. Consent manager registration under Rule 4. Applicants must be companies incorporated in India with net worth of at least Rs 2 crore. Individuals may use a consent manager to give and withdraw consent, but commentary we have read does not treat their use as mandatory for businesses.
  • May 2027. Everything substantive. The date is computed from the notification rather than printed in the Rules, and a few sources give 14 May instead; plan for the earlier one.

Two loose ends. In January 2026, Business Standard reported that the ministry was considering cutting the 18-month window to 12 months for some obligations, mainly affecting significant data fiduciaries. As of late October 2026 we found no notified amendment, but it is worth watching. And a Removal of Difficulties Order in October 2026 corrected wording in the sections on children's data and significant data fiduciary audits. Commentators read it as clarification, not new obligation.

Who is covered

The Act applies to digital personal data processed in India, and to processing outside India where it is connected with offering goods or services to people in India. A software company in Germany selling to Indian customers is in scope for that activity. In the Act's vocabulary, the business deciding why and how data is processed is the data fiduciary, and the vendor processing on its behalf is the data processor. Fiduciaries carry the obligations and may use processors only under a contract. They stay responsible for what those processors do.

What to change before May 2027

  • Rewrite your notices. Each notice must stand on its own, be given with or before the consent request, list the personal data being collected and the specific purposes, and explain how to withdraw consent, exercise rights and complain to the Board. A privacy policy linked from a footer will not do.
  • Rebuild consent flows. Consent has to be specific and informed for each purpose, and the Act requires withdrawal to be about as easy as giving it. If consent takes one tap and withdrawal takes an email to a shared inbox, that is a gap. Record when, how and for what each consent was given.
  • Set up breach reporting. On becoming aware of a breach, you must notify the Board without delay and follow up with a detailed report within 72 hours, extendable on request. Affected individuals must also be told without delay, in plain terms, what happened, the likely consequences and what they can do. That needs a runbook, a decision owner and templates, written before you need them.
  • Tighten security and logging. The Rules point to measures such as encryption, masking or tokenisation, access control, monitoring and backups, and require logs and related data to be kept for a year. Many companies keep application logs for weeks. Check.
  • Put retention on a clock. Personal data should go once its purpose is served. Large e-commerce, online gaming and social media platforms (the thresholds run from five million to 20 million registered users in India) must erase data after three years of user inactivity, with at least 48 hours' warning first.
  • Treat children's data as a separate design problem. Anyone under 18 is a child. You need verifiable consent from a parent or guardian, and you may not track, behaviourally monitor or target advertising at children. Some education, healthcare and childcare uses are exempt. Age assurance is product work, so start now.
  • Publish a rights process. Individuals can ask for access, correction and erasure. You must publish how, and respond within your own stated timelines, which cannot exceed 90 days.
  • Paper your processors. Contracts need security and deletion obligations, because the fiduciary carries the penalty if a vendor leaks the data.

All of this is easier if you know where personal data sits. If you do not, the inventory is the real first task, and it is the same work that makes data usable for AI. Our article on AI-ready data foundations covers that overlap.

Most DPDP work is not legal drafting. It is finding the data, fixing the flows that collect it and deciding, system by system, when it gets deleted.

If you are, or may be, a significant data fiduciary

The government can designate companies as significant data fiduciaries based on factors such as the volume and sensitivity of the data they process. Those designated must appoint a data protection officer based in India, carry out a data protection impact assessment and an independent audit every year, and check that their technical measures, including algorithmic software, do not put individuals' rights at risk. The government may also restrict transfer of specified personal data and related traffic data outside India for these companies. Large consumer platforms, lenders and health businesses in India should plan as if designation is possible.

That algorithmic check is where privacy compliance and AI governance meet. A scoring or recommendation model trained on customer data now needs documented testing and an owner, which is the same discipline described in our piece on an AI governance operating model built on ISO 42001.

The penalties, and why not to wait for the first case

The Schedule to the Act sets maximum penalties per breach: up to Rs 250 crore for failing to take reasonable security safeguards, up to Rs 200 crore each for failing to notify a breach or breaching the children's data obligations, up to Rs 150 crore for significant data fiduciary obligations and up to Rs 50 crore for other breaches. The Board decides the actual amount. There will be no enforcement record to learn from before May 2027, and it would be unwise to assume the first cases will be gentle.

For foreign groups, where data is hosted matters too. The cross-border rules allow transfer by default but let the government restrict it, and our view on where workloads should live sets out how to keep that option open.

Common questions

When do the DPDP Rules come into force?

In phases. Board provisions applied from 13 November 2025, consent manager registration from 13 November 2026, and the main obligations, including notice, consent, security, breach reporting and children's data, apply 18 months after notification, generally given as 13 May 2027.

Do the DPDP Rules apply to foreign companies?

Yes, where processing outside India is connected with offering goods or services to people in India. A foreign company selling into India should map which Indian personal data it holds and apply the same notice, consent, security and breach processes to it.

Do we have to use a consent manager?

Based on the analysis we have seen, no. Consent managers are registered intermediaries that individuals may choose to use. If a customer connects through one, you must be able to accept and honour consent and withdrawals arriving that way, so check whether your systems can.

Where Ganexa can help

Ganexa helps organisations turn the DPDP Rules into concrete changes: data mapping, consent and retention design, breach runbooks, and governance for the AI systems that use personal data. Our AI governance and compliance service covers the control framework, and AI data readiness covers the data inventory underneath it. To plan the next six months, book a free consultation.

DPDPData ProtectionIndiaPrivacyCompliance