Treasury, Risk & Business Consulting  ·  Not a SEBI-registered Investment Adviser
Home  /  Insights  /  DPDP Act field guide

India’s privacy law, drawn out step by step.

Who the Digital Personal Data Protection Act covers, when you need consent, what people can demand, what to do in a breach, and what it costs to get it wrong. Every point carries its section or rule number so you can check it against the official text.

Educational content only — not legal advice. This field guide is a general, simplified explanation of the Digital Personal Data Protection Act, 2023 and the DPDP Rules, 2025, prepared in October 2026 for education and awareness. It is not legal advice and is not a substitute for the official text, and it may not reflect later amendments, notifications, clarifications or orders of the Ministry of Electronics & IT (MeitY) or the Data Protection Board of India. Where this guide differs from the official text, the official text prevails. The interactive “Does it apply?” tool and the self-check are simplified learning aids and do not determine anyone’s legal obligations. CredNexa Advisory is not a law firm and is not affiliated with MeitY or the Data Protection Board. Please consult a qualified legal professional before acting on any matter covered here; CredNexa Advisory accepts no liability for any action taken in reliance on this guide.

DPDP Act and Rules — official texts

Always rely on the official text. These links open the Government of India sources:

  1. 1
    The Digital Personal Data Protection Act, 2023 (Act 22 of 2023)

    The principal legislation governing the processing of digital personal data in India.

    Read the Act (PDF) · meity.gov.in
  2. 2
    Digital Personal Data Protection Rules, 2025

    The notified Rules specify operational requirements, including provisions concerning notices, consent, security safeguards, breach notifications, children’s data and individual rights.

    Read the Rules · meity.gov.in
44sections in the Act
₹250 crhighest penalty per instance
18 monthsphased roll-out from Nov 2025
0criminal offences created
01

From Act to enforcement

The Act was passed in 2023 but switched on only when the final Rules were notified in November 2025. Obligations then arrive in three waves over 18 months.

11 Aug 2023

Act receives assent

Passed by Parliament; on the statute book but not yet in force.

3 Jan 2025

Draft Rules published

Released for public consultation. Not binding.

13–14 Nov 2025

Phase 1: Rules notified

Definitions, the Data Protection Board and its procedures come into force.

Nov 2026

Phase 2: Consent Managers

Registration and obligations of Consent Managers take effect.

May 2027

Phase 3: Full compliance

Notice, consent, rights, security, breach, children, SDF duties and penalties all apply.

02

Five players, one data flow

Almost every obligation in the Act sits with the Data Fiduciary. The diagram shows who hands data to whom and who answers to whom.

Data Principal the individual · §2(j) parent/guardian for a child Data Fiduciary decides why & how · §2(i) bears the liability Data Processor acts on instructions · §2(k) cloud, payroll, CRM vendor Consent Manager registered with Board · §6(7)–(9) Data Protection Board of India inquires, directs, penalises · §18–28 gives data + consent notice, rights, redress only under a valid contract §8(2) one dashboard to give, review and withdraw consents breach reports, inquiries complaint, after grievance route §13(3)

Fiduciary or Processor?

Ask who decides the purpose. A retailer collecting addresses to ship orders is the Fiduciary. The courier software firm storing those addresses for it is a Processor.

Processor liability

The Act places duties on the Fiduciary, which stays responsible even for what its Processor does (§8(1)). The Processor's exposure runs through its contract.

Consent Manager

A distinctly Indian feature, modelled on Account Aggregators. Must be an Indian company with net worth of at least ₹2 crore, and act in a fiduciary capacity for the individual.

03

Does the Act apply to this data?

Walk through the scope test in §3 and the exemptions in §17. Answer each question and the flowchart takes you to a verdict.

Your path
04

Two lawful routes: consent or legitimate use

Personal data may be processed only for a lawful purpose, and only on one of two grounds (§4). There is no general "legitimate interests" ground as in the GDPR.

You want to process someone's digital personal data§4(1)
Is the purpose lawful (not expressly forbidden by law)?If no, stop. No ground can cure an unlawful purpose.
Does the processing fit a listed legitimate use in §7?
YES → no consent needed
Legitimate use · §7
  • Person voluntarily gave data for a specific purpose and didn't object
  • State subsidies, benefits, licences, certificates
  • State functions under law; sovereignty and security
  • Legal obligation to disclose; court judgments
  • Medical emergency, epidemic, disaster, breakdown of public order
  • Employment purposes, incl. protecting the employer from loss
NO → consent required
Consent route · §5 + §6
  • Give a notice first (or with the request)
  • Obtain consent that meets all five tests below
  • Process only data necessary for that purpose
  • Let them withdraw as easily as they gave it
  • On withdrawal, stop and erase (and make processors erase) within a reasonable time

What makes consent valid? §6(1)

Tap each test to see what passes and what fails. All five must hold, and consent must come by a clear affirmative action.

The notice

§5 · Rule 3
  • Stand-alone and understandable on its own, not buried in terms of service
  • Itemised list of the personal data and the specific purpose for each
  • How to withdraw consent, exercise rights, and complain to the Board
  • Reader can choose English or any of the 22 Eighth Schedule languages
  • For data collected before the Act started: a notice as soon as reasonably practicable

Withdrawal

§6(4)–(6)
  • Available at any time, and as easy as giving consent
  • Processing done before withdrawal stays lawful
  • The person bears the consequences (e.g. a service that needs the data stops)
  • Fiduciary must cease processing and have its Processors do the same
05

What individuals can demand, and what they owe

Four rights and a short list of duties. The rights apply where the person gave consent or volunteered data under §7(a).

§11

Access

A summary of their data and the processing done; the identities of other fiduciaries and processors it was shared with.

§12

Correction & erasure

Correct, complete or update data; erase it unless retention is needed for the purpose or required by law.

§13

Grievance redressal

A readily available complaint channel. Must be used before approaching the Board. Rules set a 90-day outer limit for a response.

§14

Nomination

Nominate someone to exercise these rights on death or incapacity.

Not in the Act

No right to data portability, and no standalone right to object to automated decisions. Both exist under the GDPR.

Duties of the individual

§15

Follow the law, don't impersonate anyone, don't suppress material facts when submitting documents, don't file false or frivolous complaints, give only verifiably authentic information when seeking correction. Breach: penalty up to ₹10,000.

06

The Data Fiduciary's checklist

General obligations under §8, made concrete by the Rules. These apply to every fiduciary, large or small, unless an exemption says otherwise.

Security safeguards

§8(5) · R6

Encryption, masking or tokenisation; access controls; logs and monitoring; backups for continuity; matching clauses in processor contracts. Logs kept at least one year.

Accuracy

§8(3)

Ensure data is complete, accurate and consistent where it drives a decision about the person or is shared with another fiduciary.

Erasure

§8(7) · R8

Erase once the purpose is served or consent is withdrawn, unless law requires retention. Large e-commerce, gaming and social media platforms: erase after 3 years of user inactivity, with 48 hours' warning.

Contact point

§8(9)

Publish the business contact of a DPO (for SDFs) or a person who can answer questions about processing.

Processors under contract

§8(2)

Engage a processor only through a valid contract. The fiduciary remains answerable for its processors.

Breach reporting

§8(6) · R7

Report every personal data breach to the Board and to each affected person. See the breach chapter below.

07

Children's data: a stricter regime

A child is anyone under 18, with no lower age for digital consent as in the GDPR. Penalty for breach of these duties: up to ₹200 crore.

User may be under 18§2(f)
Is the fiduciary or purpose in the Fourth Schedule exemption list?e.g. clinical establishments, educational institutions, crèches and childcare, school transport tracking for safety
YES
Relaxed, only for that purpose

Parental consent and/or tracking restrictions lifted to the extent the Schedule allows, and only within the stated purpose.

NO
Full §9 duties apply
  • Verifiable consent of a parent or lawful guardian (Rule 10: verify the adult's identity and age via existing records or a token such as DigiLocker)
  • No processing likely to harm the child's well-being
  • No tracking, behavioural monitoring or targeted advertising aimed at children

For a person with a disability who has a lawful guardian, consent comes from that guardian, after the fiduciary checks the guardianship (Rule 11).

08

Significant Data Fiduciaries

The Government can notify any fiduciary, or a class of them, as an SDF. Designation brings a second layer of duties. Penalty for breaching them: up to ₹150 crore.

What triggers designation

§10(1)
  • Volume and sensitivity of data processed
  • Risk to the rights of Data Principals
  • Potential impact on sovereignty and integrity of India
  • Risk to electoral democracy
  • Security of the State and public order

Extra obligations

§10(2) · R13
  • DPO based in India, answerable to the board of directors
  • Independent data auditor
  • Data Protection Impact Assessment and audit every 12 months, findings reported to the Board
  • Due diligence that algorithmic software doesn't harm Data Principals' rights
  • Possible restriction on transferring specified data outside India
09

When a breach happens

There is no materiality threshold: every personal data breach is reportable. Two clocks run. The first says "without delay"; the second gives 72 hours for the detailed report.

T + 0

Breach discovered

  • Unauthorised processing, accidental disclosure, loss of access or integrity
  • Contain and preserve logs
Without delay

Tell each affected person

  • What happened, extent, timing
  • Likely consequences
  • Steps taken and safety measures they can take
  • Contact who can answer
Without delay

Initial intimation to the Board

  • Description: nature, extent, timing, location
  • Likely impact
Within 72 hours

Detailed report to the Board

  • Facts and probable cause
  • Mitigation and remediation
  • Who caused it, if known
  • Proof the individuals were informed

The Board can allow more than 72 hours on a written request. Failure to notify: up to ₹200 crore. Failure of security that led to the breach: up to ₹250 crore, assessed separately. §8(6) · Rule 7

10

Cross-border transfers

India uses a negative list. Data can go anywhere unless the Government blocks a country.

Transfer personal data outside India§16
Is the destination country notified as restricted?
NO
Transfer allowed

Subject to any conditions the Government sets on making data available to foreign States (Rule 15), and to all other DPDPA duties.

YES
Transfer prohibited

No adequacy decisions or standard contractual clauses route around it.

Sector rules still win if stricter§16(2): RBI payment-data localisation, SEBI, IRDAI and similar rules continue to apply
11

Exemptions

Outside the Act entirely (§3), or inside it with most obligations switched off (§17). Security safeguards under §8(5) continue to apply under §17(1).

Out of scope

§3(c)
  • Personal or domestic use by an individual
  • Data made public by the person themselves
  • Data made public under a legal obligation
  • Non-digital data that is never digitised

Partial exemption

§17(1)
  • Enforcing legal rights or claims
  • Courts, tribunals and regulators performing their functions
  • Prevention and investigation of offences
  • Indian firms processing foreigners' data under contract (outsourcing)
  • Court-approved mergers, demergers and amalgamations
  • Finding the assets and liabilities of a loan defaulter

Notified exemptions

§17(2)–(3)
  • Notified State instrumentalities (security, public order)
  • Research, archiving or statistics, if no decision is taken about the individual
  • Notified classes, including startups, can be relieved of notice, accuracy, erasure, SDF and access duties
12

Complaint to final appeal

The Board is a digital-first body with no civil-court route around it (§39). A complaint follows this path.

§13Grievance to fiduciarymust be exhausted first
§27–28Board inquirymay be closed if no ground; mediation possible (§31)
§32–33Orderdirections, penalty, or accept a voluntary undertaking
§29Appeal to TDSATwithin 60 days; tribunal aims to decide in 6 months
§29Supreme Courtfurther appeal from TDSAT, under the TRAI Act route

Blocking as a last resort

§37

If a fiduciary has been penalised in two or more instances, the Board can recommend that the Government block public access to its platform in India.

13

Penalties under the Schedule

Maximum amounts per instance, drawn to scale (the voluntary-undertaking item has no fixed figure: its cap follows the breach that started the proceedings). These are civil penalties paid into the Consolidated Fund of India; they are not compensation to the affected person.

What the Board weighs in setting the amount · §33(2)
Nature, gravity, durationType and nature of dataRepetitive nature Gain made or loss avoidedMitigation steps and timelinessProportionality and deterrenceLikely impact on the business
14

Common misreadings, corrected

These errors show up often in summaries and FAQs, including widely shared ones. Each correction cites the text.

15

Self-check

Eight questions. If you get all of them, you have the key features down.

About this guide. Prepared October 2026 from the Digital Personal Data Protection Act, 2023 and the DPDP Rules, 2025 as notified in November 2025. Phase dates are cited as 13 or 14 November by different commentators depending on gazette versus publication date. This is an educational explainer, not legal advice — check the notified text and any later MeitY or Board notifications before acting.

Let’s talk about your business.

Start with a confidential, no-obligation discovery conversation. We’ll understand the problem, agree a scope and tell you plainly whether we are the right fit.

Book a Consultation