Decoding DPDP Act compliance for enterprises
A General Counsel's plain-English guide to the Digital Personal Data Protection Act: key dates, obligations, breach rules, penalties and where to start.

Most DPDP Act compliance conversations with enterprise leadership teams start the same way. Someone has read about a Rs 250 crore penalty, IT has been told to "handle it", and legal has been asked for a policy by month-end. Many still don't know that such a law exists, let alone its implementation timeline.
The Digital Personal Data Protection Act, 2023 is short and, on paper, simple. The hard part is that it asks a business to know what personal data it holds, why, who touches it and when it is deleted. Not many enterprises can answer that without real digging.
DPDP Act compliance at a glance
Digital personal data processed in India, and processing outside India when it is tied to offering goods or services here.
Almost every enterprise is a Data Fiduciary for its staff and customer data, and remains answerable for how its vendors handle that data.
The Rules were notified on 13 November 2025, and the duties that matter to most businesses begin on 13 May 2027.
Penalties can reach Rs 250 crore where security safeguards are weak.
Draw up a data map covering what personal data the business holds, why, who handles it and when it is deleted.
Where the DPDP Act began and where things stand
In India, the journey of this new Privacy Law began with Justice K.S. Puttaswamy (Retd.) v. Union of India (2017), where the Supreme Court held the right to privacy to be a fundamental right under Article 21. The Act came in August 2023, and the DPDP Rules, 2025, notified on 13 November 2025, bring it into force in stages.
The Data Protection Board ("Board") was in place from the start, Consent Manager registration begins on 13 November 2026, and the obligations that matter to most businesses take effect on 13 May 2027. The SPDI Rules under the IT Act continue to apply until then.
The road to DPDP compliance
- 2017Puttaswamy judgmentSupreme Court holds privacy to be a fundamental right under Article 21
- August 2023DPDP Act enactedThe Digital Personal Data Protection Act, 2023 comes in
- 13 Nov 2025DPDP Rules notifiedThe Data Protection Board is in place from the start
- 13 Nov 2026Consent ManagersConsent Manager registration begins
- 13 May 2027Core obligations applyDuties that matter to most businesses take effect. SPDI Rules apply until then
The Board is responsible for enforcing the provisions of the Act (i.e. ensuring that Data Fiduciaries and other relevant entities comply with their obligations and that Data Principals' rights are protected) and for adjudicating instances of non-compliance.
The seven principles behind the DPDP Act
The Government of India identified seven principles in its explanation of the DPDP Bill. They do not appear as a separately enumerated list in the enacted DPDP Act. Their requirements are reflected across Sections 4-8, particularly the general obligations of Data Fiduciaries under Section 8.
Lawfulness, Fairness and Transparency
Personal data must be handled lawfully, for legitimate purposes and in a way that is fair to the Data Principal. Organisations should tell individuals openly what is collected, why, and how it will be used.
Purpose Limitation
Personal data should be collected and processed only for a specified purpose that has been communicated to the Data Principal or for another purpose permitted under the Act. Organisations should not use personal data for unrelated or undisclosed purposes.
Data Minimisation
Organisations should collect only such personal data as is necessary for the specified purpose. Excessive or irrelevant personal data should not be collected merely because it may be useful in the future.
Accuracy of Personal Data
Organisations should take reasonable steps to keep personal data accurate and complete, especially where it will be used to make decisions about the Data Principal or passed to another organisation.
Storage Limitation
Personal data should not be kept indefinitely. Once its purpose has been served it must be erased, unless the law requires it to be retained.
Integrity and Confidentiality (Data Security)
Organisations must implement reasonable security safeguards to protect personal data against data breaches, unauthorised access, disclosure, alteration or destruction. These safeguards should be proportionate to the nature and volume of personal data being processed.
Accountability
The Data Fiduciary is responsible for ensuring compliance with the DPDP Act, including the activities of its Data Processors. It must be able to demonstrate appropriate governance, controls, policies and processes to meet its statutory obligations.
Who the DPDP Act applies to
The Act applies to digital personal data processed in India, and to processing outside India that is connected with offering goods or services here. Paper records fall outside it until someone scans them.
A Data Principal is the individual whom the personal data relates to, such as an employee or a customer.
The key role is that of the Data Fiduciary, the person or organisation that decides why and how personal data is processed. In practice, almost every enterprise is a Data Fiduciary for its employees' and customers' personal data. Data Processors act on the Data Fiduciary's behalf, but the primary responsibility for protecting personal data stays with the Data Fiduciary: if a payroll vendor leaks salary data, it is the Data Fiduciary that answers for it. Significant Data Fiduciaries have additional duties, among them an India-based DPO and independent audits.
Data Fiduciary obligations under the DPDP Act
- To provide a clear, concise and comprehensible privacy notice to Data Principals
- To ensure that the data collected is accurate, complete and consistent
- To process personal data only on the basis of the Data Principal's consent or a recognised legitimate use
- To report personal data breaches to the Board and affected Data Principals
- To erase personal data when it has served its purpose, unless the law requires it to be kept
- To implement technical and organisational measures to ensure effective compliance with the law
- To set up a grievance redressal process
Notice and consent
Consent must be free, specific, informed and unambiguous. Pre-ticked boxes and bundled marketing consent are out. The notice has to stand on its own, say which data is collected and why, and let people withdraw consent as easily as they gave it.
A notice is only as accurate as the organisation's data map. If marketing uses CRM data for a purpose the notice never mentions, the notice is wrong, however well drafted.
Legitimate uses, and why HR can relax a little
The law allows some processing without consent, and the most significant one for enterprises is employment. This is not a blank cheque, though. Background checks, monitoring and family members' data deserve a closer look.
A good test is whether the processing would surprise a reasonable employee.
Vendors and contracts
A mid-sized company can have several vendors accessing personal data, most of them bound by little more than a confidentiality clause. Those contracts now need to limit processing to the Data Fiduciary's instructions, set checkable security standards, require prompt breach notification and provide for deletion at the end.
Breaches, retention and rights
Every personal data breach must be reported to the Board without delay, followed by a detailed report within 72 hours of the organisation becoming aware of it, and affected individuals must be told. There is no materiality threshold. Data must be deleted once its purpose is served, which sounds obvious until IT is asked how far back the backups go. Individuals can seek access, correction or erasure, and grievances must be answered within 90 days.
DPDP Act penalties
Maximum penalty for weak security safeguards
Maximum penalty for unreported breaches or lapses on children's data
To file a detailed breach report with the Board, after notifying it without delay
To answer grievances raised by individuals
Penalties are caps, not tariffs, but penalty orders are public, and clients and investors read them.
So, where does an organisation begin?
Think of it like moving house: before the packers arrive, every cupboard has to be opened. Let us just say the work falls into three phases.
From baseline to business as usual
Due diligence
The organisation engages with representatives from each function to understand what they do, how they manage personal data and where things stand. Once this baseline is established, a roadmap is prepared setting out the steps needed to align with the law.
Implementation
At this stage, the organisation sets up or fixes notices and consent flows, drops data it does not use, updates vendor contracts, tightens security, rehearses a breach playbook, sets up rights and grievance handling, agrees retention schedules and trains its people. In our experience, most challenges arise during this phase, and an experienced consultant can help organisations navigate it smoothly.
Ongoing improvement
This is a continuous process in which teams keep a close eye on changes in the law, evolving governance standards, industry practice and technology, and revisit existing processes as needed.
It also helps to align with any group-level privacy obligations, so that the group and Indian privacy frameworks remain consistent. We also recommend engaging a consultant who has set up such a programme before, preferably including abroad. That experience saves time and avoids the usual mistakes.
A closing thought
The law looks simple enough to make one ask, "what really is the big deal?" A closer look shows that it requires organisations to put robust, foolproof structures in place so that every obligation under the law is always met. Everyone, from those handling personal data to those managing privacy obligations and key stakeholders, should clearly understand their roles, responsibilities and obligations, not just when things are going well and equally when a breach or incident occurs. A robust privacy governance programme is therefore essential before stakeholders can be satisfied that everything is in order.
The potential penalty exposure under this law calls for serious consideration and an effective implementation strategy. The penalties are large enough to wipe out the balance sheets of most organisations. External support, however strong, will always have its limitations. The law demands a shift in organisational culture, where everyone is not only aware of their obligations but also confident enough to raise concerns and strengthen the process. It is a journey that needs everyone to help pull the cart.
Frequently asked questions about DPDP Act compliance
01What does the DPDP Act do?
India's Digital Personal Data Protection Act, 2023 regulates how digital personal data is handled. In practice it expects a business to know what personal data it holds, for what reason, who has access and when it will be deleted.
02When do the DPDP rules start to bind businesses?
The Rules were notified on 13 November 2025 and start in phases. The Board was in place from the start, Consent Manager registration begins on 13 November 2026, and the duties that matter to most businesses start on 13 May 2027. The SPDI Rules remain in place until then.
03Is my organisation a Data Fiduciary?
Very likely. A Data Fiduciary is whoever decides why and how personal data is processed, and nearly every enterprise does so for employee and customer data. Vendors that process data on its behalf are Data Processors, but responsibility stays with the Data Fiduciary.
04How large can DPDP penalties be?
Up to Rs 250 crore for weak security safeguards, and up to Rs 200 crore for unreported breaches or lapses on children's data. These are ceilings, not fixed charges.
05What must happen after a personal data breach?
The Board must be told without delay, with a detailed report to follow within 72 hours of the organisation becoming aware of the breach, and the affected individuals must also be informed. There is no materiality threshold.
06Where should DPDP compliance start?
With due diligence: speak to each function to learn what personal data it handles and where it stands, then build a roadmap. Implementation and continuous improvement follow.