The DPDP Rules, 2025 are dated 13 November 2025 in the Gazette and were announced by the government on 14 November 2025. The Data Protection Board provisions applied at once, consent manager registration starts one year later, and the main duties for apps and websites (notices, consent, security, breach reporting, retention, children's data and user rights) start eighteen months after notification, in May 2027.
This is not legal advice. We are software developers. We build apps and websites, and we have read the Act and the Rules closely because our clients ask us to build compliant products. This guide explains what the law says and how it translates into product and engineering work. For decisions about your own business, especially whether you could be a Significant Data Fiduciary or whether an exemption applies, speak to a lawyer who practises data protection law in India.
Last checked: 23 October 2026. We read the Act and the Rules on the Ministry of Electronics and Information Technology (MeitY) website and the government's own summary on PIB. Links are in the sources section at the end.
What are the DPDP Act and the DPDP Rules?
The Digital Personal Data Protection Act, 2023 is India's data protection law, and the DPDP Rules, 2025 are the detailed rules that make it work. Parliament enacted the Act on 11 August 2023, according to the government's explainer (PIB backgrounder, 17 November 2025). The Act sets out the duties and rights. The Rules fill in the how: what a notice must contain, how fast a breach must be reported, how long logs must be kept, and how parental consent works.
The law uses a few terms you will see everywhere:
- Data Principal: the person the data is about. For a child, this includes the parent or lawful guardian.
- Data Fiduciary: the business that decides why and how personal data is processed. If you own the app or website, this is almost certainly you.
- Data Processor: anyone who processes personal data on your behalf, such as your hosting provider, your email service, your CRM, or a development company that runs your servers.
- Consent Manager: a registered company that offers people a single place to give, review and withdraw consent across services.
- Data Protection Board of India: the regulator that handles complaints, inquiries and penalties.
Does the DPDP Act apply to my app or website?
If your app or website collects personal data in digital form from people in India, assume yes. The Act covers digital personal data processed in India, and also processing outside India if it is connected with offering goods or services to people in India. That means an overseas company with Indian users is also covered.
There are exclusions. The Act does not apply to personal data processed by an individual for any personal or domestic purpose, or to personal data that the person has made public themselves. The Act's own illustration is someone blogging their views on social media. But almost every business app, ecommerce store, booking site, SaaS product and lead form falls inside the law.
What is the DPDP Rules timeline?
The Rules say exactly when each part starts. Rule 1 of the notification reads (DPDP Rules, 2025, as published by MeitY):
(2) Rules 1, 2 and 17 to 21 shall come into force on the date of their publication in the Official Gazette. (3) Rule 4 shall come into force one year after the date of publication of this Gazette. (4) Rules 3, 5 to 16, 22 and 23 shall come into force eighteen months after the date of publication of this Gazette.
| Phase | When | What starts |
|---|---|---|
| Immediately | 13 and 14 November 2025 | Rules 1, 2 and 17 to 21: definitions and the setting up of the Data Protection Board (appointments, meetings, a digital office, staff) |
| After one year | November 2026 | Rule 4: registration and obligations of Consent Managers |
| After eighteen months | May 2027 | Rules 3 and 5 to 16, 22 and 23: notices, security safeguards, breach reporting, retention and erasure, contact details, children's and guardians' consent, Significant Data Fiduciary duties, user rights, cross-border transfers, appeals and calls for information |
Is it 13 or 14 November?
You will see both dates. The Gazette copy published by MeitY carries the heading "New Delhi, the 13th November, 2025" and the notification number G.S.R. 846(E). The government's own explainer says the Rules were "notified on 14 November 2025". Depending on which date is treated as the publication date, the one-year date falls on 13 or 14 November 2026 and the eighteen-month date on 13 or 14 May 2027.
Our advice is simple: plan to be ready before 13 May 2027, and treat the earlier date as your deadline. A day of difference matters to lawyers. It should not matter to your release plan, because you do not want to ship compliance changes the night before.
Has the deadline been brought forward?
Not as of 23 October 2026, as far as we can find. In February 2026, law firm S.S. Rana & Co. reported that MeitY had discussed with industry a proposal to shorten the eighteen-month window to twelve months, which would have moved the final date to 13 November 2026, and had asked for feedback by 4 February 2026 (S.S. Rana & Co. via Chambers, 23 February 2026). We have not found a gazetted amendment that changes the dates. Check MeitY's website before you rely on May 2027, and if you can be ready earlier, be ready earlier. Nothing in the law penalises you for complying ahead of time.
What does the DPDP Act require from an app or website?
Here are the duties that change how your product works, with the section of the Act or the rule they come from. Most of them start in May 2027 under the Rules, but a few product changes take months to design and test, so the work should start now.
A clear notice before you ask for consent
Section 5 of the Act says every request for consent must be "accompanied or preceded by a notice" telling the person what personal data you will process and why, how they can withdraw consent and exercise their rights, and how they can complain to the Board.
Rule 3 adds detail. The notice must:
- be understandable on its own, without relying on other documents;
- give, in clear and plain language, an itemised description of the personal data and the specific purposes, with a specific description of the goods, services or uses the processing enables;
- give a link to your website or app, and describe how the person can withdraw consent (as easily as they gave it), exercise their rights and complain to the Board.
Section 5(3) and section 6(3) of the Act also require you to offer the notice and the consent request in English or any language in the Eighth Schedule to the Constitution. If your users read Hindi, Tamil or Marathi, your notice should be available in those languages.
What this means in your product: your privacy policy is no longer enough on its own. You need short, specific notices at the point where you collect data, such as sign-up, checkout, a lead form, or a permission request, with a link to the full policy. "We may use your data to improve our services" will not pass the itemised and specific test.
Consent that is real
Section 6(1) says consent must be "free, specific, informed, unconditional and unambiguous with a clear affirmative action", and limited to the data necessary for the purpose.
The Act's own illustration is useful. A telemedicine app asks for consent to process personal data for telemedicine and to access the phone's contact list. Because the contact list is not necessary for telemedicine, the consent is limited to the telemedicine data. In other words, you cannot bundle unnecessary permissions into one "I agree".
Section 6(4) gives people the right to withdraw consent "at any time, with the ease of doing so being comparable to the ease with which such consent was given". Section 6(10) puts the burden of proof on you: if there is a dispute, you have to prove that notice was given and consent was obtained properly.
What this means in your product:
- No pre-ticked boxes. The person must take an action, such as ticking a box or tapping a button.
- Separate consent for separate purposes. Marketing messages, analytics and sharing with partners should each have their own choice.
- A withdrawal option in the account settings, not only by email.
- A consent log in your database: who consented, to which notice version, for which purpose, when, and how. Without it, you cannot meet section 6(10).
Legitimate uses where consent is not needed
Section 7 lists "certain legitimate uses" where you can process personal data without asking for consent. The most relevant one for businesses is section 7(a): when someone voluntarily gives you their data for a specified purpose and has not said they object. The Act's example is a pharmacy customer who gives her phone number to receive a payment receipt.
This is narrower than it sounds. It covers using the data for the purpose the person gave it for. It does not cover reusing a delivery address for marketing. Section 7 also covers employment purposes, legal obligations, court orders and medical emergencies. Ask your lawyer which basis applies to each purpose, and write it down.
Reasonable security safeguards
Section 8(5) of the Act requires "reasonable security safeguards to prevent personal data breach". Rule 6 lists the minimum:
- Encryption, obfuscation, masking or tokenisation of personal data.
- Access controls on the systems that hold it.
- Logs, monitoring and review, so unauthorised access can be detected and investigated.
- Backups and measures to keep processing going after an incident.
- Keeping those logs and the relevant personal data for one year to support detection and investigation, unless another law requires otherwise.
- Security clauses in your contracts with Data Processors.
- Appropriate technical and organisational measures to make all of this work.
This is the section with the highest penalty. The government's explainer says failure to maintain reasonable security safeguards can attract a penalty of up to ₹250 crore (PIB backgrounder).
What this means in your product: encryption at rest and in transit, role-based access for staff, audit logs of who viewed or changed personal data, backups you have actually restored from, and contracts with your hosting, email and analytics providers. In our own VisaVisa platform, uploaded documents are encrypted at rest and the expert console limits who can see what, because a visa file is about as sensitive as personal data gets.
Breach reporting within 72 hours
Section 8(6) requires you to tell the Board and each affected person about a personal data breach. Rule 7 sets out how:
- To each affected person: without delay, through their user account or registered contact details, in plain language. You must describe the breach, its likely consequences for them, what you are doing about it, what they can do to protect themselves, and who they can contact.
- To the Board: a description of the breach "without delay", and then, within seventy-two hours of becoming aware of it (or longer if the Board allows on written request), a detailed report covering the facts, the cause, mitigation, any findings about who caused it, steps to prevent it happening again, and a report on the notifications sent to affected people.
The penalty for failing to notify can go up to ₹200 crore, according to the government's explainer.
What this means in your product: you need to know who is affected, which means your logs must tie data access to user records. You need a way to message every affected user quickly, which is easy if you have an email or in-app message system and very hard if you do not. And you need a written incident plan with names, so the 72 hours are not spent working out who is in charge.
Erasing data when the purpose is over
Section 8(7) says you must erase personal data when the person withdraws consent or "as soon as it is reasonable to assume that the specified purpose is no longer being served", unless another law requires you to keep it. You must also make your Data Processors erase it.
Rule 8 and the Third Schedule set fixed periods for three classes of large platforms:
| Class | Threshold | Erase after |
|---|---|---|
| Ecommerce entity | at least 2 crore registered users in India | 3 years since the user last engaged |
| Online gaming intermediary | at least 50 lakh registered users in India | 3 years since the user last engaged |
| Social media intermediary | at least 2 crore registered users in India | 3 years since the user last engaged |
These platforms must warn the user at least forty-eight hours before erasure, so they can log in to keep their account.
Rule 8(3) applies to everyone, and it pulls in the other direction: you must keep personal data, traffic data and processing logs for at least one year from the processing, for the purposes in the Seventh Schedule, and then erase them unless another law requires longer. The Rules' own example: an e-book platform must keep the order, payment and delivery records for at least a year even if the buyer deletes her account.
What this means in your product: you need a retention schedule, written down, with a period for each kind of data. Then you need code that enforces it: scheduled jobs that delete or anonymise records when their time is up, including in backups and at your processors. In our VisaVisa platform, personal data is purged on a schedule set by the privacy policy. That job runs automatically, which is the only way retention reliably happens.
Contact details and a grievance system
Rule 9 requires you to publish prominently on your website or app the business contact details of your Data Protection Officer, if you have one, or of a person who can answer questions about how you process personal data. You must also include those details in every reply to a rights request.
Rule 14(3) requires you to publish the period for responding to grievances, which must not exceed ninety days, and to have the technical and organisational measures to meet it.
Rights: access, correction, erasure and nomination
People have the right to get a summary of their data and how it is processed, to correct, complete, update and erase it, to have their grievances addressed, and to nominate someone to act for them if they die or become incapacitated. Rule 14(1) says you must publish how people can make these requests and what identifier they need to give, such as a username, customer ID, email or mobile number.
What this means in your product: a "Your data" or "Privacy" section in the account settings, with a way to download or view data, edit it, delete the account, and add a nominee. For apps without accounts, a simple request form tied to a phone number or email with a one-time code works well.
Children's data
Under the Act, a child is anyone under eighteen. Section 9 requires you to obtain verifiable consent from a parent or lawful guardian before processing a child's personal data, and forbids processing likely to cause a detrimental effect on a child's well-being, as well as tracking, behavioural monitoring and targeted advertising directed at children. The government's explainer puts the penalty for breaching the children's obligations at up to ₹200 crore.
Rule 10 explains verifiable consent. You must check that the person claiming to be the parent is an identifiable adult, either using identity and age details you already hold reliably, or details provided voluntarily by the person or through a virtual token from an authorised entity, which the Rule says includes details verified through a DigiLocker service provider.
The Fourth Schedule lists exemptions. Part A exempts certain classes, such as clinical establishments and healthcare professionals for health services, educational institutions for educational activities and safety, crèches and childcare centres for safety, and transport providers for school transport location tracking. Part B exempts certain purposes, including creating an email-only user account, tracking real-time location for a child's safety, and keeping harmful content away from children.
What this means in your product: if children could use your app, add an age question early in sign-up, a parent verification flow when the answer is under eighteen, and a version of the product without behavioural ads or tracking for those accounts. If your app is clearly for adults, say so in the terms and design the sign-up for adults.
Significant Data Fiduciaries
The government can notify a business or class of businesses as a Significant Data Fiduciary based on the volume and sensitivity of data, risk to people, and other factors in section 10(1). These businesses must appoint a Data Protection Officer based in India, appoint an independent data auditor, and carry out periodic Data Protection Impact Assessments. Rule 13 makes the assessment and audit annual, requires due diligence on algorithmic software, and allows the government to require certain personal data to stay in India.
Most small and mid-sized businesses will not be notified as Significant Data Fiduciaries. If you run a large consumer platform, a health service or a financial service with millions of users, ask your lawyer now.
Sending data outside India
Rule 15 allows personal data to be transferred outside India, subject to any requirements the government sets by order for making data available to a foreign state or entities it controls. Section 16 of the Act lets the government restrict transfers to specific countries by notification. Today, most businesses can continue to use overseas cloud and software providers, but you should keep a list of where your data goes, so you can react if a restriction is notified.
Data Processors and your development company
Section 8(1) makes you responsible for compliance "irrespective of any agreement to the contrary", including for processing done by your Data Processors. Section 8(2) says you may engage a processor "only under a valid contract". Rule 6 adds that the contract must include reasonable security safeguards.
If an agency builds and hosts your app, or has access to your production database for support, they are probably your Data Processor. You need a written contract covering security, confidentiality, breach notification to you, deletion at the end of the engagement, and their own sub-processors. We cover the full list of contract terms in our guide to hiring a software development company in India.
What are the DPDP penalties?
The Schedule to the Act sets the maximum penalties. The government's explainer summarises them:
| Breach | Maximum penalty |
|---|---|
| Failing to take reasonable security safeguards | up to ₹250 crore |
| Failing to notify the Board or affected people of a breach | up to ₹200 crore |
| Breaching the obligations for children's data | up to ₹200 crore |
| Any other breach of the Act or Rules by a Data Fiduciary | up to ₹50 crore |
These are maximums, not fixed fines. The Board decides the amount in each case. But the scale tells you what the law cares about most: security, breach notification and children.
The Rules also set out how the Board works. It operates as a digital office, complaints can be filed online, and Rule 19(9) says an inquiry must be completed within six months, extendable by three months at a time. Appeals go to the Telecom Disputes Settlement and Appellate Tribunal (TDSAT).
See your price before you call anyone
Pick your features and get an itemised estimate in two minutes.
Build my estimateA practical DPDP checklist for apps and websites
This is the checklist we work through with clients. It is organised by where the work happens, so you can hand each part to the right person. It is not a substitute for legal review, but it covers the product and engineering side of the Act and the Rules as we read them.
Map your data first
- List every place you collect personal data: sign-up, login, checkout, contact forms, chat, support tickets, file uploads, analytics, ads pixels, call recordings, WhatsApp and SMS.
- For each one, write down: what data, why, the legal basis (consent or a legitimate use), how long you keep it, where it is stored, and who else receives it.
- List your Data Processors: hosting, database, email, SMS, payment gateway, analytics, CRM, support desk, AI APIs, and your development agency.
- Find old data. Section 5(2) of the Act says that for consent given before the Act came into force, you must give people a notice "as soon as it is reasonably practicable". Plan a notice to existing users.
Notices and consent
- Write short, itemised notices for each collection point, in plain language, and offer them in English and the languages your users read.
- Replace "by using this site you agree" with an affirmative action, such as a checkbox or button, and separate optional purposes from essential ones.
- Build a consent log: user, notice version, purpose, timestamp, channel, and withdrawals.
- Add a withdraw option in settings that is as easy as the original consent.
- Review every app permission request (contacts, location, camera, microphone) and remove anything not needed for the feature.
Security
- Encrypt personal data in transit (HTTPS everywhere) and at rest, with extra protection for identity documents, health and financial data.
- Use role-based access for staff and admins. Remove shared logins.
- Log access to personal data and keep logs for at least a year, as Rule 6 requires.
- Back up, and test a restore at least once.
- Review third-party scripts on your website. Each one is a potential leak.
Breach readiness
- Write a one-page incident plan: who decides, who investigates, who writes to users, who reports to the Board.
- Make sure you can identify affected users from your logs and message them quickly.
- Prepare templates for the user notice and the Board report, using the headings in Rule 7.
Retention and erasure
- Set a retention period for each type of data, with the one-year minimum for processing logs in mind.
- Build scheduled jobs that erase or anonymise data when its time is up, and confirm your processors do the same.
- If you are a large platform under the Third Schedule, build the forty-eight-hour warning before erasure.
Rights and contact
- Publish a contact for data questions (a DPO if you have one) on the website and in the app.
- Add self-service access, correction, deletion and nomination, or a request form with identity verification.
- Publish your grievance response period, no longer than ninety days, and track requests to meet it.
Children
- Decide whether children can use your product. If yes, add age checks, a parent verification flow, and turn off tracking and targeted ads for under-eighteen accounts.
- Check whether a Fourth Schedule exemption applies to you, with your lawyer.
Contracts
- Sign data processing terms with every processor, including your development agency, covering security, breach notice, deletion and sub-processors.
- Keep a record of where data is transferred outside India.
How much does DPDP compliance cost for an app?
It depends on how far your product is from the checklist. For a well-built app, the changes are mostly notices, a consent log, a settings screen and a retention job. For an older app with shared admin logins, no audit logs and personal data scattered across spreadsheets, it is a bigger project.
We price compliance work the same way as any other feature: line by line, in a fixed proposal. If you are starting a new product, it costs far less to build these into the first version than to retrofit them. For reference, a custom web app costs ₹3.5 lakh to ₹12 lakh with us, and a mobile app for iOS and Android costs ₹4.5 lakh to ₹14 lakh. User accounts, admin dashboards and notifications are priced as separate lines on our pricing page, and most compliance features reuse them.
Where we can help:
- A DPDP readiness review of your app or website. We go through the checklist above against your actual code, database and infrastructure, and give you a written list of changes with a price for each one. Your lawyer handles the legal questions. We handle the build.
- Building the changes. Notices, consent logs, rights screens, audit logs, retention jobs and breach messaging, built into your existing stack.
- New products built compliant from day one. Our custom software development, mobile app development and web development projects include this by default.
What we learned building for privacy
A few lessons from building and running our own products, which we think apply to most apps:
Collect less. The cheapest data to protect is data you never collected. When we built Niyyara, a free worship app, we calculated prayer times on the device. It works offline, and we never needed to store anyone's location on a server. Ask, for every field in every form, what breaks if you remove it.
Make retention automatic. A retention policy that depends on someone remembering to delete old data will not be followed. A scheduled job will.
Use one-time codes instead of passwords where it fits. VisaVisa signs people in with a one-time code. There is no password database to leak, and the phone number or email doubles as the identifier for rights requests.
Keep the AI provider away from the phone. In SPAIKING, our server relays the realtime voice session, so the AI provider's key never sits on the device. The same pattern lets you control which personal data reaches an AI API and log it.
Questions about DPDP compliance
When do the DPDP Rules come into force?
In three phases. Rules on the Data Protection Board applied from notification in November 2025. Consent Manager registration applies from November 2026. Notices, consent, security, breach reporting, retention, children's data and user rights apply eighteen months after notification, in May 2027. Plan to be ready before 13 May 2027.
Does the DPDP Act apply to small businesses and startups?
Yes. The duties apply to any Data Fiduciary processing digital personal data, whatever its size. The heavier duties, such as annual audits and impact assessments, apply only to businesses notified as Significant Data Fiduciaries.
Do I need a Data Protection Officer?
Only Significant Data Fiduciaries must appoint a Data Protection Officer based in India. Everyone else must publish the contact details of a person who can answer questions about personal data, under Rule 9.
How quickly must a data breach be reported under the DPDP Rules?
Affected people must be told without delay. The Board must be told without delay, and then sent a detailed report within seventy-two hours of becoming aware of the breach, unless the Board allows longer on a written request.
Is a cookie banner enough for DPDP compliance?
No. A cookie banner covers one kind of data collection. The Act requires itemised notices and consent for each purpose, a way to withdraw, security safeguards, breach reporting, retention limits, rights handling and, for children, parental consent.
Who is responsible if my development agency causes a breach?
You are. Section 8(1) makes the Data Fiduciary responsible for processing done on its behalf by a Data Processor, whatever the contract says. That is why you need a written contract with security and breach notice terms, as section 8(2) and Rule 6 require.
What is the maximum DPDP penalty?
Up to ₹250 crore for failing to take reasonable security safeguards. Up to ₹200 crore for failing to report a breach or for breaching the children's data obligations, and up to ₹50 crore for other breaches.
Sources
All checked on 23 October 2026.
- Ministry of Electronics and Information Technology, Digital Personal Data Protection Rules, 2025, G.S.R. 846(E), Gazette of India, 13 November 2025. PDF on meity.gov.in.
- The Digital Personal Data Protection Act, 2023 (22 of 2023). PDF on meity.gov.in.
- Press Information Bureau, DPDP Rules, 2025 Notified, backgrounder, 17 November 2025. PDF.
- PIB press release on the notification of the DPDP Rules. pib.gov.in.
- S.S. Rana & Co., MeitY plans to cut short DPDP compliance timeline, 23 February 2026, via Chambers and Partners. Reports a proposal; we found no gazetted amendment.
This guide is general information about the law as published, written by software developers. It is not legal advice, and it does not create a lawyer and client relationship. Rules and dates can change; check the sources above.
Get an estimate for your compliance work
If you are building a new product, choose its type and features below to see an itemised range. If you need a readiness review of an existing app or website, contact us with a link and we will reply within one business day.