Data principal rights under the DPDP Act: handling access, correction and erasure requests.
What a user can ask for under Sections 11 to 14, what Rule 14 of the DPDP Rules, 2025 requires you to publish, and the setup that lets a business answer on time.
By Advocate Joginder Poswal · Updated November 2026
In short. A user can ask you for a summary of their data and a list of everyone you shared it with, ask you to correct or erase it, nominate someone to act after their death or incapacity, and raise a grievance. You must publish how to make these requests and who answers them. Grievances must be answered within the period you publish, which cannot exceed ninety days, and the user has to come to you before going to the Data Protection Board. These duties apply from 13 May 2027.
When this applies
The DPDP Rules, 2025 were published on 13 November 2025 and come into force in three steps. Rule 14, which sets out how rights are exercised, falls in the last group under Rule 1(4) and applies eighteen months after publication, which is 13 May 2027. Rule 9 on publishing a contact person and Rule 8 on retention start on the same day.
That leaves about six months. Most of the work described below is engineering and process work, not drafting, and it takes longer than a policy update.
The five rights at a glance
| Right | Provision | What the user gets |
|---|---|---|
| Access | Section 11 | A summary of their data and processing, and the identities of every Data Fiduciary and Data Processor it was shared with |
| Correction and erasure | Section 12 | Inaccurate data corrected, incomplete data completed, data updated, and data erased unless the law or the purpose requires it to be kept |
| Grievance redressal | Section 13, Rule 14(3) | A readily available complaint route, answered within a published period of no more than ninety days |
| Nomination | Section 14, Rule 14(4) | One or more people who can exercise these rights after the user's death or incapacity |
| Withdrawal of consent | Section 6(4) | Withdrawal at any time, as easily as consent was given |
Right to access
Under Section 11, a user can ask for two things: a summary of the personal data you are processing along with the processing activities, and the identities of all other Data Fiduciaries and Data Processors you shared it with, with a description of what was shared.
The second part is where most companies get stuck. A typical startup sends user data to a payment gateway, an email service, an analytics tool, a CRM, a cloud host and a support desk. Few can say, for a single user, which of these hold what. If that list does not exist today, building it is the first job.
Two limits are worth knowing. First, the right runs against a Data Fiduciary to whom the user gave consent, including the deemed consent in Section 7(a) where a person volunteers data for a specified purpose. Data processed only under another legitimate use, such as employment under Section 7(i), sits outside the text of Section 11. Second, Section 11(2) says you need not disclose sharing with an authority that asked for the data in writing to prevent, detect or investigate offences or cyber incidents.
Correction and erasure
Section 12(2) obliges you, on request, to correct inaccurate or misleading data, complete what is incomplete and update what is out of date. Section 12(3) obliges you to erase the data unless keeping it is necessary for the specified purpose or for compliance with any law.
The exception matters more than it first appears. A lender cannot erase loan records the moment a borrower asks, because other laws require them to be kept. The answer to that user is a partial erasure with a clear explanation of what is retained and under which law.
Rule 8(3) adds a floor that surprises people. Every Data Fiduciary must keep personal data, the associated traffic data and processing logs for at least one year from the date of processing, for the State and Board purposes listed in the Seventh Schedule. The Rules give the example of a user who deletes their account: the data still has to be held for that year, and the duty binds your processors too. So a compliant erasure workflow removes the data from live use at once and deletes it from the retained store once the one-year period runs out.
Erasure also has to reach your vendors. Section 8(7)(b) requires you to make your Data Processors erase data you gave them. A deletion that stops at your own database is incomplete.
Grievances and the ninety-day limit
Section 13 gives every user a right to readily available means of grievance redressal, and Section 13(3) requires them to use it before going to the Data Protection Board. Your grievance process is therefore the first forum for every dispute, and a careless answer there becomes the record the Board reads later.
Rule 14(3) requires you to publish, on your website or app, the period within which you will respond to grievances. That period cannot exceed ninety days. The government's explainer on the Rules, published through PIB in November 2025, reads the ninety days as applying to access, correction and erasure requests as well. The wording of the Rule ties it to grievances. A business that answers every rights request within ninety days is safe on either reading, and in practice most requests should take far less.
Nomination
Section 14 lets a user nominate another individual to exercise their rights after death or incapacity, which Section 14(2) defines as unsoundness of mind or infirmity of body. Rule 14(4) allows one or more nominees. You must offer a way to record the nomination and a way for a nominee to prove their status when the time comes. For a product with long-lived accounts, such as a bank, an insurer, a cloud storage service or a family records app, this flow deserves real design work.
For how nomination interacts with succession more broadly, the guide on probate and succession certificates explains why a nominee is not the same as an owner.
What you must publish
Three items have to appear prominently on your website or app, or both:
- The means of making a request, under Rule 14(1)(a). A web form, an in-app screen or a dedicated email address all work, provided a user can find it.
- The identifier a user must give, under Rule 14(1)(b). Rule 14(5) lists examples such as a username, customer number, application reference, email address or mobile number. Choose one you can actually match against your records.
- The contact of your Data Protection Officer or another person who can answer questions, under Section 8(9) and Rule 9. Rule 9 also requires this contact to be named in every response you send to a rights request.
The response period for grievances under Rule 14(3) belongs on the same page.
Duties on the user side
The Act is unusual in placing duties on the Data Principal. Section 15 requires users to follow the law when exercising rights, not to impersonate anyone, not to suppress material information when applying for identity documents, not to file false or frivolous grievances, and to give only verifiably authentic information when asking for correction or erasure. Item 5 of the Schedule sets a penalty of up to Rs. 10,000.
This does not let a business ignore requests it finds annoying. It does mean that identity checks before acting on a request are lawful and sensible, especially for erasure, where acting on a forged request destroys a real user's data.
A working setup
From the engineering side, a workable rights process has these parts:
- A data inventory keyed to the user. For any identifier, you should be able to pull every table, file store and vendor that holds that person's data.
- A vendor register. Each processor, what it receives, and how you instruct it to erase. This answers Section 11(1)(b) and Section 8(7)(b) at once.
- An intake channel with a ticket number. Every request gets logged with the date received, because the date is what the Board will ask about.
- Identity verification proportionate to the request. Matching a logged-in session is enough for an access summary. An erasure request by email needs more.
- A retention map showing which data must survive an erasure request, under which law, and for how long, including the one-year floor in Rule 8(3).
- Response templates that name the contact person, as Rule 9 requires, and explain any partial refusal with its legal basis.
Common mistakes
- Hiding the request route inside a long privacy policy instead of publishing it prominently.
- Deleting the user's row in the main database and forgetting backups, analytics exports and vendors.
- Deleting too much, including logs that Rule 8(3) requires to be kept for a year.
- Answering an access request with the raw database dump instead of a readable summary.
- Leaving out the list of processors because it is embarrassing or unknown.
- Having no way to record a nominee, or no way for a nominee to prove who they are.
- Treating grievance replies as customer service rather than as the first record of a possible Board complaint.
Frequently asked questions
Rule 14(3) requires you to publish a response period for grievances of no more than ninety days. The government's explainer applies the same limit to access, correction and erasure requests. Answering every rights request within ninety days satisfies both readings.
Not at first. Section 13(3) requires the user to exhaust your grievance process before approaching the Board.
No. Section 12(3) allows retention needed for the specified purpose or required by law, and Rule 8(3) requires data, traffic data and logs to be kept for at least one year from processing for the Seventh Schedule purposes, even after an account is deleted.
Section 11 runs against a Data Fiduciary to whom the person gave consent, including under Section 7(a). Data processed only for employment under Section 7(i) is not expressly covered, though the employer's other duties under the Act still apply.
Yes. Section 15 bars false or frivolous grievances and impersonation, and item 5 of the Schedule sets a penalty of up to Rs. 10,000.
Related reading
- DPDP Consent and Notice: what Rule 3 requires a notice to say and when consent is valid.
- DPDP Data Retention and Erasure: how long data may be kept and when it must go.
- DPDP Act Compliance for Indian Startups: the full set of obligations and the timeline to 13 May 2027.
- DPDP Data Breach Notification: who has to be told after a breach, and by when.
- DPDP Compliance: all guides on the Act in one place.
Enrolment: Bar Council of Punjab & Haryana | No.: PH/9616/2023
This page is informational and does not constitute legal advice. References are to the Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E), 13 November 2025). How these apply depends on the data and operations of each organisation.
