Skip to main content
DPDP-AID Readiness Checkby

The DPDP Rules 2025 and what they add

The Act says what must happen. The DPDP Rules 2025, notified on 13 November 2025, say how, and in several places how fast. If you have already read the Act, the Rules are where the operational detail sits: notice wording, the safeguards you are expected to have, breach reporting timelines, erasure after long inactivity and the duties of a consent manager.

Reviewed 16 September 2026Educational self-assessment content, not legal advice

When the obligations bite

The Rules commence in phases. Some provisions, including those that let the Data Protection Board be constituted, took effect on notification. Consent manager provisions commence on 13 November 2026. The remaining obligations, which is most of what a business has to build, commence on 13 May 2027.

That staged start is a planning window, not a holiday. Discovery, vendor contracts and retention changes are the slowest items in practice, and they are the ones other work depends on.

  1. In force

    11 August 2023

    DPDP Act receives assent

  2. In force

    13 November 2025

    DPDP Rules notified; Board provisions in force

  3. In force

    13 November 2026

    Consent Manager provisions commence

  4. Upcoming

    13 May 2027

    Remaining obligations commence

    175 days to go

Notice, in the Rules' words

A notice must be understandable on its own, without reading anything else, and written in clear and plain language. It has to give an itemised description of the personal data being collected and the specified purpose, with the goods, services or uses that purpose enables.

It also has to tell people how to act: how to withdraw consent, how to exercise their rights and how to complain to the Board. In practice that means a real link or route, not a sentence saying rights exist.

Reasonable security safeguards

The Rules turn "reasonable security safeguards" into a list you can audit yourself against. The expectation is that a fiduciary can show these are in place for personal data, and can show them for the processors it uses too.

  • Encryption, obfuscation, masking or the use of virtual tokens for personal data.
  • Access control for the computer resources that hold personal data.
  • Logs, monitoring and review to detect unauthorised access, retained for a set period.
  • Backups and measures that let processing continue after a compromise.
  • Contractual terms that carry the same safeguards through to processors.
  • The means to detect, investigate and reconstruct a breach after it happens.

Breach reporting, and the clock

On becoming aware of a personal data breach, a fiduciary must tell the affected people without delay, in concise, clear and plain language, covering what happened, the likely consequences, what is being done about it, what they can do to protect themselves and who to contact.

The Board gets two communications: an immediate one describing the breach's nature, extent, timing and likely impact, and a fuller one within 72 hours, extendable only on a written request, covering remedial measures, the circumstances and who appears to have caused it, and confirmation that affected people were told.

Seventy two hours is short. It is a detection and drill problem, not a paperwork problem, which is why breach handling is one of the two areas that caps your readiness band in this assessment.

Erasure after long inactivity

The Rules require certain larger platforms, including e-commerce, online gaming and social media services above specified user thresholds, to erase a user's personal data after a long period with no contact and no exercise of rights, unless it is needed for a legal reason. Users must be told in advance before that erasure happens.

Below those thresholds the general rule still applies: keep personal data only while the purpose needs it, then erase it, including at your processors.

Children, guardians and verification

Where a child's personal data is processed, the Rules expect due diligence to check that the adult giving consent is identifiable as the parent or lawful guardian, using reliable identity details or a virtual token mapped to them. The same approach applies to the lawful guardian of a person with a disability.

Certain classes of provider, such as some healthcare, educational and childcare settings, get narrower exemptions from parts of the children's obligations for specified purposes.

Extra duties for significant data fiduciaries

A significant data fiduciary must carry out a data protection impact assessment and an audit at a set frequency and report significant findings to the Board. It must also exercise due diligence to check that algorithmic software it deploys does not risk data principals' rights, and observe any restriction the government notifies on transferring specified personal data outside India.

DPDP Rules 2025 requirements, in numbers

Most of the framework is written in words. A handful of it is written in numbers, and those are the parts an auditor can check and a team can plan against. These are the figures worth putting in front of your board.

  • 72 hours: the deadline for the fuller breach report to the Data Protection Board after you become aware, extendable only on a written request the Board allows.
  • Three years: the period of user inactivity after which certain larger platforms must erase personal data, counted from the last login or transaction.
  • 48 hours: the notice a user gets before that erasure happens, so they can act if they want the account kept.
  • 2 crore registered users for e-commerce and social media, and 50 lakh for online gaming: the thresholds above which that erasure duty applies.
  • ₹2 crore: the minimum net worth for an entity registering as a consent manager, which must be a company incorporated in India.

What changed between the draft and the final Rules

The draft Rules circulated for consultation before the final version was notified, and several things moved. The numbering changed, which matters more than it sounds: guidance written against the draft cites provisions that now cover something else entirely, and a good deal of published commentary still has not caught up.

The practical advice is to check the date on anything you read about the Rules, including ours. If a page does not say when it was last reviewed, treat its provision numbers with suspicion. Everything on this site is generated from one configuration file with a review date shown on the page.

What the security safeguards actually require

"Reasonable security safeguards" sounds like a standard you cannot fail until someone tells you that you have. The Rules make it more concrete than that, and the list is short enough to audit yourself against this quarter.

  • Encryption, obfuscation, masking or virtual tokens applied to personal data, in storage and in transit.
  • Access control over the computer resources that hold personal data.
  • Logs of access and processing, monitored and reviewed, and retained long enough to investigate.
  • Backups and continuity measures so processing can resume after a compromise.
  • Contractual terms that carry the same safeguards through to every processor.
  • The means to detect a breach, investigate it and reconstruct what happened.

Frequently asked questions

When were the DPDP Rules notified?

The DPDP Rules 2025 were notified on 13 November 2025. Consent manager provisions commence on 13 November 2026 and the remaining obligations commence on 13 May 2027.

How long do I have to report a personal data breach under the DPDP Rules?

Affected people must be told without delay. The Data Protection Board must be told without delay with initial details, and a fuller report follows within 72 hours of becoming aware, extendable only on a written request to the Board.

What counts as reasonable security safeguards?

The Rules list measures including encryption, masking or tokenisation, access control, logging and monitoring with retention of logs, backups, contractual safeguards with processors, and the ability to detect and investigate a breach.

Do the DPDP Rules require data localisation?

The Rules do not impose general localisation. Transfers outside India are allowed subject to terms the government may specify, and a significant data fiduciary may face restrictions on transferring specified categories of personal data. Sector regulators can still impose stricter localisation.

How many rules are in the DPDP Rules 2025?

The final Rules run to a little over twenty, with several Schedules carrying the detail on consent managers, exempt classes and the platform thresholds for erasure. The numbering changed between the draft and the final version, so check the date on any commentary you read.

Do the DPDP Rules 2025 apply to small companies?

Most of them do. A few duties are tied to thresholds, such as the erasure duty for platforms above 2 crore registered users, or the extra duties of a notified significant data fiduciary. Everything else applies whatever your size.

What is a consent manager under the DPDP Rules 2025?

A registered intermediary through which people can give, manage, review and withdraw consent, accountable to the data principal. It must be a company incorporated in India with a minimum net worth of ₹2 crore. Most businesses need consent management, not registration as a consent manager.

See your readiness in five minutes.

Start with the quick check. You can move to the full assessment at any time without losing your answers.

The DPDP-AID Readiness Check is a free self-assessment tool for educational and self-learning purposes. It is not legal advice. Disclaimer

A free self-assessment tool for educational use. Not legal advice.