Summary: India’s Digital Personal Data Protection Act, 2023 is being implemented in three phases under the Digital Personal Data Protection Rules, 2025. While the initial provisions commenced on 13 November 2025, the second phase relating to Consent Manager registration became effective on 13 November 2026. Most substantive compliance obligations for businesses are scheduled to commence on 13 May 2027. These include privacy notices, consent management, security safeguards, personal data breach reporting, retention and erasure, children’s data protection and Data Principal rights. Significant Data Fiduciaries will face additional requirements relating to Data Protection Officers, independent audits and impact assessments. The Act prescribes penalties of up to ₹250 crore for specified contraventions. Although the Data Protection Board’s operational readiness remains a concern, businesses should not delay preparations. The remaining six-month period provides an opportunity to map personal data, review lawful processing grounds, update privacy notices and vendor contracts, strengthen cybersecurity controls, establish grievance and breach-response mechanisms, and implement retention policies. Chartered Accountants and Company Secretaries can support organisations through governance reviews, compliance assessments, contractual safeguards and risk reporting. The key priority is to achieve operational readiness before the scheduled May 2027 commencement date.
- DPDP Act: Status & May 2027 Readiness
- Status at a glance
- Two caveats
- Who and what is covered
- Lawful basis: consent or a “legitimate use”
- Notice (Rule 3)
- Data Principal rights
- What Data Fiduciaries must do
- Consent Managers (Rule 4)
- Penalties
- How it interacts with other laws
- A six-month countdown to 13 May 2027
- Where CA and CS professionals fit
- Common mistakes
DPDP Act: Status & May 2027 Readiness
India’s Digital Personal Data Protection Act, 2023 is law, but most of it is not yet enforceable. The Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E), notified 13 November 2025) set a three-step commencement. This week the second step arrived. The third, which carries almost every business obligation, is about six months away.

| Date | What starts | Status |
|---|---|---|
| 13 November 2025 | Definitions, the Data Protection Board provisions (ss. 18–26), Rules 1, 2 and 17–21, and a few miscellaneous provisions | In force |
| 13 November 2026 | Section 6(9) and Rule 4: registration of Consent Managers, with the Board’s related power in s. 27(1)(d) | Started this week |
| 13 May 2027 | Notice, consent, security safeguards, breach reporting, retention and erasure, children’s data, Data Principal rights, Significant Data Fiduciary duties, cross-border conditions (Rules 3, 5–16, 22, 23) | Six months away |
Status at a glance
If you are not applying to become a Consent Manager, nothing new is legally required of you on 13 November 2026. Your compliance cliff is 13 May 2027.
Two caveats
- The Board exists in law but is not staffed. MeitY invited applications for the Chairperson and four Members on 6 May 2026. In a Lok Sabha answer of 12 August 2026 the government said they “are to be appointed”. Reports through the autumn say no appointment had been announced, so registrations and complaints have no working forum yet.
- The 18-month runway could shrink. At a stakeholder meeting on 22 January 2026, MeitY floated cutting it to 12 months. I found no notification, but plan as if the date could move.
Who and what is covered
- Data:digital personal data, or non-digital data that is later digitised, processed in India. It also reaches processing outside India if it is connected with offering goods or services to people in India.
- Excluded:processing for personal or domestic purposes, and personal data a person has made public themselves or that is made public under a legal obligation.
- Roles
| Term | Meaning |
|---|---|
| Data Principal | The individual the data relates to (a parent or lawful guardian for a child or a person with a disability) |
| Data Fiduciary | The person who decides the purpose and means of processing |
| Significant Data Fiduciary (SDF) | A fiduciary notified by the government on volume and sensitivity of data and risk factors |
| Data Processor | Processes on behalf of a fiduciary |
| Consent Manager | A registered intermediary through whom a Data Principal gives, manages and withdraws consent |
Lawful basis: consent or a “legitimate use”
Personal data can be processed for a lawful purpose with consent, or for a listed legitimate use without it. The most relevant legitimate uses for businesses are:
- where the Data Principal voluntarily provided the data for a specified purpose and did not object
- compliance with a law
- medical emergencies and other specified protective uses
- employment, covering purposes related to employment or safeguarding the employer from loss or liability
Consent must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, and limited to the data necessary for the stated purpose. Withdrawing it must be as easy as giving it.
Notice (Rule 3)
Notice must come before or at the time of the consent request. It should be in clear and plain language, itemise the personal data and the specific purpose, say how to withdraw consent and exercise rights, and say how to complain to the Board. The Data Principal should be able to read it in English or any language in the Eighth Schedule.
Data Principal rights
- Information about the personal data processed and with whom it has been shared
- Correction, completion, updating and erasure
- Grievance redressal with the fiduciary first, and the Board afterwards
- The right to nominate a person to exercise rights in the event of death or incapacity
Data Principals also owe duties, such as not filing false or frivolous complaints. A breach is penalised at up to Rs. 10,000.
What Data Fiduciaries must do
| Duty | Substance |
|---|---|
| Accuracy | Reasonable efforts where the data is used to decide about the individual or shared with another fiduciary |
| Security safeguards (Rule 6) | Reasonable safeguards, which commentary reads as including encryption, access control and logs retained for at least a year |
| Breach (Rule 7) | Tell each affected Data Principal without delay, and report to the Board without delay, with a detailed report within 72 hours |
| Retention and erasure (Rule 8) | Erase data when the purpose is served or consent is withdrawn, unless the law requires retention. Commentary adds prior notice to the Data Principal, and a three-year clock for large e-commerce, gaming and social media platforms |
| Contact and grievance | Publish the contact details of someone who can answer questions, and run a grievance process |
| Processors | Use processors only under a valid contract, and stay responsible for them |
| Children (s. 9, Rules 10–12) | Verifiable parental consent for under-18s, no tracking, behavioural monitoring or targeted advertising directed at children, with prescribed exemptions |
Significant Data Fiduciaries carry more: a Data Protection Officer based in India, an independent data auditor, and periodic impact assessments and audits (Rule 13). The government can also restrict transfers of specified data to some countries (Rule 15).
Consent Managers (Rule 4)
From 13 November 2026 a company can apply to the Board for registration as a Consent Manager. As commentary summarises the eligibility, it must be an Indian company with net worth of at least Rs. 2 crore, must act in a fiduciary capacity towards the Data Principal, must not be able to read the data it routes, and must keep consent records for seven years. Data Principals’ right to use a Consent Manager starts on 13 May 2027. With no members on the Board, registration is not yet practical.
Penalties
The Schedule sets maximum penalties per breach, imposed by the Board after an inquiry:
| Breach | Up to |
|---|---|
| Failure to take reasonable security safeguards | Rs. 250 crore |
| Failure to notify a personal data breach | Rs. 200 crore |
| Breach of children’s data obligations | Rs. 200 crore |
| Breach of SDF obligations | Rs. 150 crore |
| Breach of any other provision | Rs. 50 crore |
| Data Principal’s breach of duties | Rs. 10,000 |
These are caps, not tariffs. The Board must weigh the nature, gravity and duration of the breach and mitigating steps taken.
How it interacts with other laws
- Sectoral regulators:SEBI, RBI and others keep their own data and security rules. The DPDP Act applies in addition, and where the two conflict the stricter requirement is safer to follow.
- IT Act:commentary reads the repeal of section 43A and the SPDI Rules as arriving with the main provisions, so they continue until then.
- RTI Act:the DPDP Act’s amendment of the personal-information exemption in section 8(1)(j) of the RTI Act commenced on 13 November 2025, per commentary.
- Employment data:employee records can generally be processed under the employment legitimate use, but notice and security duties still apply.
A six-month countdown to 13 May 2027
| When | Do | |
|---|---|---|
| November to December 2026 | Map personal data: where it is collected, stored, shared and deleted. Identify your role for each process | |
| January 2027 | Redraft notices and consent flows. Build the withdrawal and rights-request process | |
| February 2027 | Review every processor and vendor contract. Add DPDP clauses | |
| March 2027 | Test security controls and logging. Run a breach drill against the 72-hour reporting clock | |
| April 2027 | Fix retention and erasure. Train teams. Appoint the contact person (and a DPO if you are an SDF) | |
| May 2027 | Go live. Keep an evidence file | |
Where CA and CS professionals fit
- Governance:put DPDP on the board agenda, with a risk owner, a budget and quarterly progress reports.
- Contracts and policy:vendor agreements, privacy notices, retention schedules and breach protocols.
- Assurance:gap assessments now, and later the independent audits that SDFs will need.
- Reporting:consider how privacy risk is described in the Board’s Report and risk disclosures.
Common mistakes
- Waiting for the Board. Obligations do not depend on whether the Board has members.
- Treating the notice as a legal formality. Under Rule 3 it is an operative requirement.
- Forgetting processors, who are your responsibility.
- Over-relying on consent where a legitimate use fits, and the reverse.
- Keeping data forever with no erasure schedule.
- No breach playbook, so that the 72-hour report becomes a scramble.
- Ignoring children’s data in apps that collect a date of birth.
Bottom line: the law is on the statute book, the first phases are running, and the heavy obligations begin on 13 May 2027. The regulator is still unstaffed, which tempts businesses to wait. The six months left are about the right amount of time to map data, fix notices and contracts, and rehearse a breach, if you start now.






