On 13 May 2027, India’s data protection law stops being a future problem and becomes an enforceable one. That is the date from which the main obligations of the Digital Personal Data Protection Act, 2023 (DPDP Act) and the DPDP Rules 2025 start to apply to businesses of every size. Get it wrong, and the Data Protection Board can impose a penalty of up to ₹250 crore for a single instance of non-compliance.
If you collect names, phone numbers, emails, addresses or payment details, this law is about you. A newsletter form, a CRM, a delivery app or a payroll file: all of it counts.
The good news is that DPDP Act compliance is very doable when you break it into clear steps. This guide explains the law in plain English: what it says, who it covers, what you must do, what happens if you don’t, and how to build a realistic plan before the deadline.
DPDP Act 2023 and DPDP Rules 2025: The Overview
The DPDP Act received Presidential assent on 11 August 2023. It is India’s first standalone, cross-sector law on personal data, and it applies to digital personal data: data collected online, or collected offline and later digitised.
The Act sets the principles. The DPDP Rules 2025, notified by MeitY on 13 November 2025, explain how to apply them. They cover what a privacy notice must contain, what security measures are expected, how breaches must be reported, how children’s data is handled and how the Data Protection Board works. You can read the official documents on the MeitY website, in the Gazette of India and on India Code.
Phased commencement
- 13 November 2025: Rules 1, 2 and 17 to 21 took effect. These set up the Data Protection Board.
- 13 November 2026: Rule 4, covering the registration of Consent Managers, takes effect.
- 13 May 2027: Rules 3, 5 to 16, 22 and 23 take effect. These contain the core obligations most businesses care about.
Until then, the existing rules under the IT Act continue to apply.
Important: timelines for Significant Data Fiduciaries may change
MeitY has consulted industry on shortening the compliance timeline for Significant Data Fiduciaries (large or high-risk organisations). Reports pointed to 13 November 2026 instead of 13 May 2027. We could not confirm a final notification at the time of writing [verify]. If your organisation may be classed as an SDF, check the latest notification before relying on the 2027 date. Official updates are posted on the MeitY website.
Petitions challenging the Act and Rules have also reached the Supreme Court, which issued notice to the Union Government in February 2026. Check the current status before publishing or acting on this point [verify].
Key Terms Explained Simply
The law uses its own vocabulary. Here is what each term means in everyday language.
Data Fiduciary
Any person or organisation that decides why and how personal data is processed. If you choose to collect customer emails, you are a Data Fiduciary. Most businesses reading this are one, and the data fiduciary obligations in this guide apply to you.
Data Principal
The individual the data is about: your customer, user, employee or job applicant. For a child or a person with a disability, the term also covers the parent or lawful guardian.
Data Processor
A vendor that handles data on your behalf, such as a cloud host, payroll provider or email marketing tool. You remain responsible for what they do with your data.
Significant Data Fiduciary (SDF)
A Data Fiduciary notified by the Central Government based on factors like the volume and sensitivity of data it handles and the risk to individuals. SDFs carry extra duties: appointing a Data Protection Officer based in India, engaging an independent data auditor and running periodic Data Protection Impact Assessments.
Consent Manager
A registered entity that lets individuals give, review, manage and withdraw consent through one interface. It is accountable to the individual. Using one is optional for businesses.
Data Protection Board of India (DPB)
The body that receives complaints and breach reports, runs inquiries and imposes penalties. It works as a digital office, and its orders can be appealed to the Telecom Disputes Settlement and Appellate Tribunal (TDSAT).
Who Must Comply with the DPDP Act?
The Act applies if you process digital personal data in India. It also applies outside India when the processing relates to offering goods or services to people in India. A foreign SaaS company with Indian customers is covered.
Size does not buy you an exemption. Startups, MSMEs, NGOs, clinics, schools and even a freelancer with a website sign-up form fall within scope. The Act lets the government notify certain classes of Data Fiduciaries, including startups, for relaxed obligations, but no blanket exemption exists today [verify].
Typical examples include:
- E-commerce and D2C brands
- Banks, NBFCs and fintech companies
- Hospitals, clinics and diagnostic labs
- EdTech platforms and schools
- SaaS and IT service companies
- HR teams handling employee and applicant data
The Act does not apply to data processed for purely personal or domestic purposes, or to data an individual has made publicly available themselves. Fully offline, non-digitised records are also outside its scope.
If you use vendors, the responsibility stays with you. [INTERNAL LINK: vendor and data processor agreement checklist]
Main Data Fiduciary Obligations
These data fiduciary obligations form the backbone of the law. Get these right and you have covered most of the risk.
1. Valid consent
Consent must be free, specific, informed, unconditional and unambiguous, given through a clear affirmative action. Pre-ticked boxes and bundled consent do not qualify. Withdrawing consent must be as easy as giving it.
Consent is not the only basis. The Act allows certain “legitimate uses”, such as compliance with a law, medical emergencies or some employment purposes. Do not assume this covers marketing.
2. Clear notice
When you ask for consent, give an itemised notice in plain language. It should describe what data you collect and why, explain how to exercise rights and withdraw consent, give contact details of your Data Protection Officer or designated contact, and say how to complain to the Board. It must be available in English or any language listed in the Eighth Schedule to the Constitution. [INTERNAL LINK: privacy notice template]
3. Purpose limitation and data minimisation
Collect only what you need for the stated purpose, and use it only for that purpose. If you need a phone number to deliver an order, do not also ask for a date of birth “just in case”.
4. Retention and erasure
Do not keep data longer than necessary. Once the purpose is served or consent is withdrawn, erase the data unless a law requires you to keep it. Set retention schedules and automate deletion wherever possible.
5. Reasonable security safeguards
The Rules expect measures such as encryption, masking or tokenisation, access controls, logging and monitoring, and data backups. Relevant logs and personal data must be retained for a minimum period, currently one year , so breaches can be detected and investigated. Your contracts with processors should demand the same standard.
This is the area with the highest penalty tier, so prioritise it.
6. Breach notification
If a personal data breach happens, you must inform the Data Protection Board and each affected individual without delay. A more detailed report to the Board is due within 72 hours of becoming aware of the breach, unless the Board allows more time. Have an incident response plan ready before you need it. [INTERNAL LINK: data breach response plan]
7. Accuracy and accountability
Keep data accurate if you use it to make decisions about a person or share it with another fiduciary. Publish contact details for rights requests and set up a working grievance mechanism.
Rights of Data Principals
The Act gives individuals several rights, and your systems must be able to honour each of them.
- Right to information: a summary of the personal data you process, what you do with it and who you share it with.
- Right to correction, completion, updating and erasure of their data.
- Right to grievance redressal: a way to complain to you first.
- Right to nominate another person to exercise rights in case of death or incapacity.
- Right to withdraw consent at any time.
The 90-day grievance window
You must publish how people can raise requests and complaints. Under the Rules, grievances must be responded to within a maximum of 90 days. Treat 90 days as the ceiling, not the target. Acknowledge requests quickly, verify the person’s identity and assign a named owner.
A Data Principal must use your grievance process before approaching the Board. Individuals also have duties, such as not filing false complaints or impersonating someone else.
Children’s Data and Parental Consent
Under the Act, a child is anyone below 18. Before processing a child’s personal data, you need verifiable consent from a parent or lawful guardian. The Rules expect you to take due diligence steps to confirm the adult’s identity and relationship, for example using reliable details you already hold or a government-backed digital token.
The Act also bars three practices when it comes to children:
- Processing that is likely to harm a child’s well-being
- Tracking or behavioural monitoring
- Targeted advertising directed at children
Limited exemptions exist for certain classes, such as healthcare professionals and educational institutions, for specific purposes. If you run an EdTech, gaming or social platform with under-18 users, treat this as a top priority.
DPDP Act Penalty: What Non-Compliance Can Cost
The DPDP Act penalty structure is among the steepest in Indian regulation. The Board imposes penalties after an inquiry and after giving you a chance to be heard. The maximum amounts are set in the Schedule to the Act:
| Violation | Maximum penalty |
|---|---|
| Failure to maintain reasonable security safeguards | ₹250 crore |
| Failure to notify the Board and affected individuals of a breach | ₹200 crore |
| Breach of obligations relating to children | ₹200 crore |
| Breach of additional duties of an SDF | ₹150 crore |
| Any other breach of the Act or Rules | ₹50 crore |
| Breach of duties by a Data Principal | ₹10,000 |
These are caps, not fixed fines. The Board considers the nature and seriousness of the breach, how long it lasted, the type of data involved, steps you took to reduce harm and whether you repeated the violation. The Act has no cure period for first-time breaches, so early preparation matters.
There is one useful tool: the Board can accept a voluntary undertaking from a Data Fiduciary, which can bring proceedings to an end. Beyond fines, expect reputational damage, lost enterprise deals and customer churn.
DPDP Compliance Checklist: 12 Steps
Use this DPDP compliance checklist as your working plan.
- Assign ownership. Appoint a privacy lead or Data Protection Officer. It is mandatory only for SDFs, but every business needs a named person.
- Map your data. List every place personal data enters, lives and leaves: forms, apps, CRM, HR files, analytics, backups and vendors.
- Define purposes. For each data type, write down why you collect it and on what basis.
- Rewrite privacy notices. Make them itemised, plain-language and available in English or Eighth Schedule languages.
- Rebuild consent flows. Use clear opt-ins, no pre-ticked boxes and an easy withdrawal option.
- Set retention and deletion rules. Define how long each dataset is kept and who deletes it.
- Harden security. Add encryption, role-based access, multi-factor authentication, logging and tested backups.
- Update vendor contracts. Add DPDP clauses on security, breach reporting and deletion.
- Create a rights and grievance process. Publish a contact point and track every request against the 90-day limit.
- Prepare a breach response plan. Define who investigates, who notifies the Board and individuals, and how the 72-hour report is filed.
- Handle children’s data. Add age checks and verifiable parental consent, and switch off tracking and targeted ads for minors.
- Train, test and document. Train staff, run a mock breach drill and keep records that prove what you did and when.
18-Month Compliance Roadmap in 3 Phases
The Rules gave businesses 18 months from November 2025. Here is how that window maps to a sensible plan.
Phase 1: Assess (Months 1 to 3, November 2025 to February 2026)
Map your data, identify gaps against the Rules and decide who owns what. Classify your risk, including whether you could be an SDF or process children’s data.
Phase 2: Implement (Months 4 to 12, February to November 2026)
Build the foundations: new notices, consent flows, retention rules, security upgrades, vendor contracts and the grievance process. This is the longest and most technical phase.
Phase 3: Test and validate (Months 13 to 18, November 2026 to May 2027)
Run breach drills, audit logs, test rights-request handling end to end and fix what breaks. Brief your leadership and keep evidence of compliance.
Starting late? Use a six-month sprint
If you are reading this close to the deadline, compress the plan:
- Month 1: Map data and fix the biggest risks first.
- Months 2 to 3: Ship new notices, consent flows and security fixes.
- Months 4 to 5: Launch rights and breach processes and update vendor contracts.
- Month 6: Test, train staff and document everything.
Common Mistakes to Avoid
- Treating it as a legal-only task. Compliance lives in product, engineering and HR too.
- Copying a generic privacy policy. Notices must match what you actually do.
- Bundling consent. Forcing one tick for several purposes is not valid consent.
- Ignoring vendors. A processor’s breach is still your problem.
- Keeping data forever. Without retention rules, old data becomes old liability.
- No breach plan. If you cannot report within 72 hours, you are exposed.
- Forgetting existing users. Customers who gave consent before the law took effect still need a compliant notice as soon as reasonably practicable.
- Waiting for the last month. Technical changes take longer than expected.
FAQs
1. Does the DPDP Act apply to small businesses and startups?
Yes. The Act applies by activity, not size. Small businesses that process digital personal data must comply, although the government may notify relaxations for some classes, including startups [verify].
2. Is a Data Protection Officer mandatory?
Only Significant Data Fiduciaries must appoint a DPO based in India. Other businesses must still publish contact details for a person who can answer questions about data processing.
3. Can I keep using my existing customer database?
Yes, but you need to give affected individuals a compliant notice as soon as reasonably practicable. You may continue processing until they withdraw consent.
4. Can I transfer personal data outside India?
Generally yes, except to countries the government restricts by notification. Sector laws, such as those for banking, may impose stricter localisation rules, and the Rules allow extra restrictions for SDFs [verify]. Check your sector regulator too.
5. What is the maximum DPDP Act penalty?
Up to ₹250 crore per instance, for failing to maintain reasonable security safeguards. Other violations carry lower caps, as shown in the penalty table above.
6. Is 13 May 2027 the final deadline?
It is the date set in the Rules for the core obligations. However, MeitY has proposed an earlier date for Significant Data Fiduciaries, so check the latest official notification on the MeitY website.
Conclusion: Start Your DPDP Act Compliance Now
DPDP Act compliance is not a one-time legal exercise. It is a set of habits: collect less, explain clearly, protect what you hold, respond quickly and be ready when something goes wrong. Businesses that start early will spend less, face fewer surprises and earn customer trust that competitors cannot easily copy.
Your next step is simple. Download our checklist, map your data this week and assign an owner. If you want expert help, book a DPDP readiness assessment with our team.
contact / compliance consultation page
This article is for information only and is not legal advice. Laws and timelines can change, so verify current requirements with official sources or a qualified professional.



