DPDP Rules 2025Updated 22 November 20268 min read

DPDP Rules 2025: What Changed From the January 2025 Draft

Four verified changes between the January 2025 draft and the final DPDP Rules: Consent Manager net worth, phased commencement, one-year retention and the 90-day grievance ceiling.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Draft
G.S.R. 02(E), 3 January 2025
Consultation
45 days from availability of the Gazette
Final
G.S.R. 846(E), 13 November 2025
Consent Manager net worth
₹12 crore (draft) → ₹2 crore (final)
Commencement
Phased: on publication, +12 months, +18 months
New retention floor
One year (Rule 8(3))
Grievance ceiling
90 days (Rule 14(3))

Quick answer

Four notable changes from the January 2025 draft (G.S.R. 02(E)) to the final DPDP Rules (G.S.R. 846(E), 13 November 2025): Consent Manager net worth fell from ₹12 crore to ₹2 crore; commencement became explicitly phased at 12 and 18 months; Rule 8(3) added mandatory one-year retention of personal data, traffic data and logs; and Rule 14(3) set a 90-day grievance ceiling. This list is not exhaustive.

  • The draft was published as G.S.R. 02(E) on 3 January 2025 with a 45-day window for objections and suggestions.
  • The Consent Manager net worth requirement dropped from ₹12 crore in the draft to ₹2 crore in the final First Schedule.
  • The final Rules stage commencement explicitly: some rules on publication, Rule 4 after 12 months, the rest after 18 months.
  • Rule 8(3) adds a one-year minimum retention of personal data, traffic data and processing logs, with e-book and cloud illustrations.
  • Rule 14(3) caps the published grievance response period at 90 days; these four changes are highlights, not a complete comparison.

Who this is for: Teams that built compliance plans on the draft, Prospective Consent Managers, Legal and policy teams, CTOs revisiting logging and retention design, Customer support and grievance teams

What changed between the draft and the final DPDP Rules?

MeitY published the draft DPDP Rules as G.S.R. 02(E) on 3 January 2025 and invited objections and suggestions for 45 days. The preamble to the final notification records that the comments received were considered before the Central Government notified the final Rules as G.S.R. 846(E) on 13 November 2025.

The four differences below are ones verified for this page. They are the changes most likely to alter a compliance plan built on the draft.

AreaDraft (Jan 2025)Final (Nov 2025)
Consent Manager net worth₹12 crore₹2 crore (First Schedule, Part A, item 4)
CommencementNo explicit 12/18-month stagingPhased under Rule 1(2)–(4)
Retention of data and logsNo mandatory one-year floorOne-year minimum under Rule 8(3), with illustrations
Grievance response periodNo 90-day ceilingPublished period not exceeding 90 days under Rule 14(3)

This list is not exhaustive. Wording, structure and other provisions may also differ between the two texts. If you are migrating a plan, gap analysis or contract template from the draft, compare it clause by clause against the final Gazette text rather than relying on any summary, including this one.

The draft required a Consent Manager applicant to have a net worth of ₹12 crore. Item 4 of Part A of the final First Schedule requires a net worth of not less than ₹2 crore.

The First Schedule note defines net worth as the aggregate value of total assets reduced by the value of liabilities, as appearing in the Consent Manager's books of accounts.

What the change means:

  • Lower entry barrier. A smaller, well-capitalised Indian company can now plausibly meet the financial threshold. The ₹12 crore figure set a considerably higher bar.
  • Net worth is not the only financial test. Part A also requires sufficient technical, operational and financial capacity (item 2), a sound financial condition and general character of management (item 3), and adequate business volume, capital structure and earning prospects (item 5). The Board can still refuse an applicant that clears ₹2 crore but looks fragile.
  • Independence and certification requirements remain demanding. Indian incorporation, conflict-of-interest provisions in the memorandum and articles, and independent certification of the interoperable platform against Board-published standards all still apply.

Since Rule 4 came into force on 13 November 2026, this is now a live criterion for applications. See registration conditions for all nine Part A items.

Explicit phased commencement

The final Rules set out a three-step commencement in Rule 1:

  1. Rule 1(2): Rules 1, 2 and 17 to 21 on publication, 13 November 2025.
  2. Rule 1(3): Rule 4 one year after publication, 13 November 2026.
  3. Rule 1(4): Rules 3, 5 to 16, 22 and 23 eighteen months after publication, 13 May 2027.

The draft did not set out this explicit 12- and 18-month structure. Under the final text, every company can now read its deadline directly from the Gazette.

Why it matters:

  • Certainty for budgets. Teams can schedule work against fixed calendar dates instead of waiting for further notifications.
  • Sequencing. The Board is constituted first, Consent Managers can register next, and the main fiduciary obligations follow. Each layer has time to settle before the next depends on it.
  • No company-specific grace periods. The dates are uniform. The only obligation with a company-specific clock is the Significant Data Fiduciary annual DPIA and audit, which runs from notification as an SDF.

MeitY issued a parallel commencement notification for the Act on the same date, aligned to the same three phases. The commencement timeline maps every rule and section to its date.

New: mandatory one-year retention under Rule 8(3)

This is the change with the largest engineering impact. Rule 8(3) requires every Data Fiduciary to retain, for any processing it undertakes or that a Data Processor undertakes on its behalf, the personal data, associated traffic data and other logs of the processing for a minimum of one year from the date of processing, for the purposes in the Seventh Schedule. After that, the fiduciary must cause the data and logs to be erased, unless another law or a Government notification requires longer retention.

Two illustrations were included:

  • E-book platform. After an e-book purchase is delivered, the purpose is served, but the platform must keep order details, personal data and processing logs (order confirmation, payment and delivery events) for at least a year from the transaction, even if the buyer deletes her account.
  • Cloud provider. A company hosting customer records with a cloud provider must ensure the provider also keeps the data and associated logs for at least a year before erasure.

Rule 6(1)(e) separately requires keeping logs and personal data for one year to detect, investigate and remediate unauthorised access.

For teams that designed deletion pipelines against the draft, this is a redesign: immediate hard deletion on account closure is no longer compliant by default. See one-year log retention.

New: a 90-day ceiling for grievance responses

Rule 14(3) requires every Data Fiduciary and Consent Manager to prominently publish, on its website or app, the period within which it will respond to grievances under its grievance redressal system. That period must be reasonable and must not exceed ninety days. The fiduciary must also implement appropriate technical and organisational measures to make the system effective in meeting that period.

The draft did not contain this 90-day ceiling.

What to do with it:

  • Publish a number. A vague promise to respond "as soon as possible" does not satisfy a rule that requires a published period.
  • Pick a period shorter than 90 days if you can meet it. Ninety days is a ceiling. A shorter published period that you consistently meet is better evidence of an effective system.
  • Instrument the queue. Track received, acknowledged and resolved timestamps per grievance, with alerts well before the published deadline.
  • Remember the escalation path. Section 13 of the Act requires a Data Principal to exhaust the grievance mechanism before approaching the Board, so a missed deadline opens the door to a Board complaint.

See the 90-day grievance rule for workflow design.

How to migrate a draft-based compliance plan

Many organisations started DPDP work in early 2025 using the draft. A disciplined migration avoids carrying draft assumptions into production.

  1. Re-baseline every citation. Replace draft references with references to G.S.R. 846(E). Do not assume that numbering or wording carried over unchanged; check each cross-reference against the final text.
  2. Re-date every task. Map tasks to 13 November 2025, 13 November 2026 or 13 May 2027 using Rule 1.
  3. Redesign deletion around the one-year floor. Revisit account deletion, log rotation, data lake retention and processor contracts in light of Rules 6(1)(e) and 8(3).
  4. Set the grievance period. Choose and publish a period of 90 days or fewer, and build the tooling to meet it.
  5. Re-run Consent Manager decisions. If you ruled out becoming or partnering with a Consent Manager because of the ₹12 crore threshold, revisit that with the ₹2 crore figure.
  6. Do a full diff. Because the four changes above are not a complete list, have counsel or a reviewer compare the draft and final texts in full and record every difference that affects your plan.

The May 2027 roadmap gives a timeline to slot these tasks into.

Further reading on suhasbhairav.com

Key dates

  1. Draft Rules published as G.S.R. 02(E); 45-day consultation begins

  2. Final Rules notified as G.S.R. 846(E)

  3. Rule 4 in force with the ₹2 crore net worth condition

  4. Rule 8(3) one-year retention and Rule 14(3) 90-day ceiling apply

Answers

Frequently asked questions

What is the main difference between the draft and final DPDP Rules?

For most companies, the biggest operational change is Rule 8(3), which requires every Data Fiduciary to keep personal data, traffic data and processing logs for at least one year. Other verified changes include the lower ₹2 crore Consent Manager net worth, explicit phased commencement and the 90-day grievance ceiling. These are not the only differences.

When was the draft DPDP Rules published?

MeitY published the draft Digital Personal Data Protection Rules, 2025 as G.S.R. 02(E) on 3 January 2025 in the Gazette of India and invited objections and suggestions for 45 days. The final Rules were notified as G.S.R. 846(E) on 13 November 2025.

Did the Consent Manager net worth requirement change?

Yes. The draft required a net worth of ₹12 crore. The final First Schedule, Part A, item 4 requires a net worth of not less than ₹2 crore, defined as total assets minus liabilities in the books of accounts. Other capacity, management and certification conditions still apply.

Is the list of draft vs final changes complete?

No. This page lists four verified differences that most affect compliance plans. Wording, structure and other provisions may also differ. Anyone relying on draft-era analysis should compare it clause by clause against the final Gazette text of G.S.R. 846(E).

Did the draft DPDP Rules have a one-year log retention requirement?

No. The mandatory one-year retention of personal data, associated traffic data and processing logs in Rule 8(3), with its e-book and cloud provider illustrations, was added in the final Rules. It applies from 13 May 2027 and covers processing done by Data Processors too.

Should I redo my DPDP gap assessment if it was based on the draft?

Yes. At minimum, update citations to the final text, re-date tasks against the Rule 1 commencement dates, redesign deletion around the one-year floor, and publish a grievance period of 90 days or fewer. Then have a reviewer compare the full texts for any further differences.

Legal references and sources

  • Digital Personal Data Protection Rules, 2025 — Rule 1 (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 8(3) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 14(3) (official text)
  • Digital Personal Data Protection Rules, 2025 — First Schedule, Part A, item 4 (official text)

This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.

About the author

Suhas Bhairav

Suhas Bhairav

Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.