Data Principal Rights Under DPDP

Four rights, one correlative set of duties, and the operational reality of actually answering a request within your own stated timeline.

9 min readLast updated: Last updated: September 2026
Key Takeaway
  • Data Principals have four core rights under Sections 11–14: access, correction and erasure, grievance redressal, and nomination — plus their own duties under Section 15.
  • A grievance-redressal mechanism has to exist and actually work before a complaint can lawfully be escalated to the Data Protection Board.
  • Erasure rights connect directly to your retention schedule (Chapter 08) — you can't honour a deletion request for data you don't know you're holding.
  • Building a working rights-request intake — identity verification, a way to locate data across systems, a real SLA — is more operationally demanding than the legal text suggests.

Right to Access Information

LawSection 11 gives a Data Principal the right to obtain a summary of the personal data being processed about them and the processing activities undertaken on it, along with the identities of any other Data Fiduciaries or Processors that data has been shared with, and any other information prescribed by the Rules. In practice, this means being able to answer "what do you hold on me, and who have you given it to" in a way that's actually accurate — which depends entirely on having a working data inventory (Chapter 07).

Right to Correction and Erasure

LawSection 12 lets a Data Principal request correction of inaccurate or misleading data, completion of incomplete data, updating of data, and erasure of data that's no longer necessary for the purpose it was collected for — unless retention is otherwise required by law. This right is where Chapter 08 and this chapter meet directly: an erasure request is only straightforward to honour if you already know which systems hold the data in question and whether any of them have an independent legal reason to keep it.

Right of Grievance Redressal

LawSection 13 gives a Data Principal the right to have their grievance addressed by the Fiduciary, which is required under Section 8(10) to maintain an effective mechanism for this. Only once a grievance has gone through that mechanism (or gone unaddressed within a reasonable time) does escalation to the Data Protection Board become the next step — the internal mechanism isn't optional window-dressing, it's a genuine first line that most complaints should never need to go past.

Right to Nominate

LawSection 14 lets a Data Principal nominate another individual to exercise their rights in the event of death or incapacity — a provision with no close GDPR equivalent, reflecting a genuinely India-specific design choice. Few organisations have built a working process for this yet, since it's rarely tested in practice, but it's worth having a plan for at least how such a request would be verified and actioned once one arrives.

Withdrawal is technically a consent mechanism under Section 6 rather than one of the four rights listed above, but it functions as a right in practice — a Data Principal exercising control over their own data. It's covered in full in Chapter 04.2, Consent Withdrawal, since it's substantial enough to warrant its own chapter.

Duties of Data Principal

LawRights come with correlative duties under Section 15: not impersonating another person when providing data, not suppressing material information when providing documents, not registering a false or frivolous grievance or complaint, and furnishing only verifiably authentic information when exercising a right. This is a genuine two-way structure — a Fiduciary that suspects a rights request is fraudulent or made in bad faith isn't left without any recourse.

Exercising Rights in Practice

StepWhat it requires
Identity verificationConfirming the requester is who they claim to be, proportionate to the sensitivity of the data involved
Locating the dataSearching across every system the data inventory (Chapter 07) says might hold it
Applying the rightCorrecting, erasing, or compiling a summary, as requested
Responding within SLAA published, consistently honoured timeframe — not an open-ended "we'll get to it"
Common mistake

Routing every rights request to a general support inbox with no defined process, identity-verification step, or SLA. This tends to work fine for the first handful of requests and then quietly breaks down — inconsistent handling, missed deadlines, and no record of what was actually done — exactly when volume starts to matter.

Organisation's Responsibilities

PracticeBeyond the specific rights above, an organisation needs a published way for a Data Principal to actually reach it (the business contact information required under Section 8(9)), a documented internal process for handling each right consistently, and a record of requests received and how they were resolved — partly for the Data Principal's benefit, and partly as your own evidence of a functioning programme if a complaint is ever escalated to the Board.

Related Topics

Frequently Asked Questions

How does a Data Principal actually exercise these rights?

By contacting the Data Fiduciary through its published contact information (typically a Data Protection Officer or designated contact under Section 8(9)) and making the specific request — access, correction, erasure, grievance, or nomination.

What happens if a Fiduciary ignores a rights request?

The Data Principal can escalate through the Fiduciary's own grievance-redressal mechanism first, and from there to the Data Protection Board once its enforcement powers are fully active.

Are there duties on the Data Principal too, not just rights?

Yes — Section 15 requires Data Principals not to impersonate others, suppress material information, or file false or frivolous grievances when exercising their rights.

Sources