DPDP Rules 2025Updated 22 November 202610 min read

Data Principal Rights Under DPDP Rule 14

The DPDP Act grants access, correction, erasure, grievance and nomination rights. Rule 14 sets how fiduciaries publish request channels, identifiers and a grievance period of up to 90 days.

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

Rights in the Act
Sections 11 (access), 12 (correction/erasure), 13 (grievance), 14 (nomination)
Procedural rule
Rule 14, DPDP Rules, 2025
Grievance response ceiling
Not exceeding 90 days (Rule 14(3))
Who must publish
Data Fiduciaries and, where applicable, Consent Managers
Contact in every response
DPO or privacy contact details (Rule 9)
In force from
13 May 2027

Quick answer

Data Principals under the DPDP Act have four rights: access to information (section 11), correction and erasure (section 12), grievance redressal (section 13) and nomination (section 14). Rule 14 of the DPDP Rules, 2025 requires Data Fiduciaries and Consent Managers to publish how to make requests, the identifiers needed, and a grievance response period not exceeding 90 days. Rule 14 applies from 13 May 2027.

  • The DPDP Act grants access, correction and erasure, grievance redressal and nomination rights, in sections 11 to 14.
  • Rule 14(1) requires the request channel and required identifiers to be prominently published on the website or app.
  • Rule 14(3) caps the published grievance response period at 90 days and requires technical and organisational measures to meet it.
  • Rights requests go to the Data Fiduciary to whom the Data Principal previously gave consent, using its published means.
  • Rule 14 comes into force on 13 May 2027, with Consent Managers also covered.

Who this is for: Product and platform engineering teams, Customer support and trust teams, Data Protection Officers and privacy contacts, Consent Managers, SaaS and consumer app founders

What rights do Data Principals have under the DPDP Act?

The DPDP Act gives every Data Principal, meaning the individual to whom personal data relates (and, for a child, the parent or lawful guardian), four core rights.

RightSectionWhat the Data Principal gets
Access to informations.11A summary of personal data processed and the processing activities; identities of other Data Fiduciaries and Data Processors with whom data was shared, with a description of the data shared
Correction and erasures.12Correction, completion and updating of data, and erasure, subject to retention required by law
Grievance redressals.13A readily available means of grievance redressal; must be exhausted before approaching the Board
Nominations.14Nominate one or more individuals to exercise rights in the event of death or incapacity

These rights sit alongside consent-linked controls that are not labelled as rights but work like them, especially the ability to withdraw consent with the same ease as giving it (section 6(4) and Rule 3(c)(i)).

The access right applies to data processed on the basis of consent or the voluntary-provision legitimate use. It is narrower than GDPR's Article 15: there is no standalone right to data portability or to object to automated decisions in the Act.

Data Principals also carry duties under section 15, such as not filing false or frivolous complaints and furnishing only verifiably authentic information when seeking correction. Breach of those duties can attract a penalty of up to ₹10,000.

What does Rule 14 require from Data Fiduciaries?

Rule 14 turns the Act's rights into operational obligations. It has five sub-rules.

  • Rule 14(1) — publish the means. The Data Fiduciary and, where applicable, the Consent Manager must prominently publish on its website or app, or both: (a) the details of the means by which a Data Principal may make a rights request; and (b) the particulars, such as username or other identifier, that may be required to identify her under its terms of service.
  • Rule 14(2) — request to the right fiduciary. A Data Principal exercises her rights by making a request to the Data Fiduciary to whom she previously gave consent, using the published means and furnishing the required particulars.
  • Rule 14(3) — grievance response period. Every Data Fiduciary and Consent Manager must prominently publish the period, not exceeding ninety days, within which it will respond to grievances, and must implement appropriate technical and organisational measures to make the system effective within that period.
  • Rule 14(4) — nomination. A Data Principal may nominate one or more individuals in accordance with the fiduciary's terms of service and applicable law, using its published means.
  • Rule 14(5) — identifier. "Identifier" means any sequence of characters issued by the Data Fiduciary to identify the Data Principal, including a customer identification file number, customer acquisition form number, application reference number, enrolment ID, email address, mobile number or licence number.

Rule 9 adds that every response to a rights request must mention the business contact information of the DPO, if applicable, or a person who can answer questions about processing.

How to design a compliant rights request channel

Rule 14 does not mandate a specific channel, but it does require the channel to be prominently published and usable with identifiers the fiduciary itself issued. That shapes the engineering design.

Channel options

  • An in-app or account-settings privacy centre for logged-in users (the strongest option, because identity is already established).
  • A web form for users who have lost access, accepting the identifiers listed in your terms of service.
  • An email address or support channel as a fallback, routed into the same ticketing queue.

Identity verification

Use identifiers you already hold, such as registered mobile number with OTP, registered email, customer ID or application number, consistent with Rule 14(5). Do not demand new documents you would not otherwise collect; that creates fresh personal data and friction.

Workflow

  1. Capture request type: access, correction, completion, updating, erasure, nomination, consent withdrawal, or grievance.
  2. Verify identity against the identifier.
  3. Create a ticket with a timestamp and the published response deadline.
  4. Fan the request out to every system and processor holding the data.
  5. Respond with the outcome and the Rule 9 contact details.
  6. Log the request, response and evidence.

Consent Managers

Where a Data Principal manages consent through a registered Consent Manager, Rule 14 applies to the Consent Manager as well, so request routing between platforms must be designed explicitly.

How to fulfil each right in real systems

Access (s.11)

Build an export that assembles a summary of personal data and processing activities, plus a list of other Data Fiduciaries and Data Processors with whom data was shared. Generating it from the data catalogue and processor register is far more reliable than manual collation.

Correction, completion and updating (s.12)

Route corrections to the system of record and propagate them downstream. Where data is used for decisions or disclosed to another fiduciary, section 8(3) requires completeness, accuracy and consistency, so stale copies are a real risk.

Erasure (s.12)

Erase unless retention is necessary for the specified purpose or required by law. Remember the Rule 8(3) minimum one-year retention of personal data, traffic data and processing logs for Seventh Schedule purposes, which survives account deletion. Tell the user what has been erased and what is retained and why. Instruct processors to erase too (s.8(7)).

Grievance (s.13)

Treat any complaint about processing as a grievance with a tracked deadline, not as a generic support ticket.

Nomination (s.14)

Store nominee details securely and define how a nominee proves death or incapacity under your terms of service. See right to nominate.

Consent withdrawal

Withdrawal must be as easy as giving consent. After withdrawal, stop processing within a reasonable time and cause processors to stop.

Common mistakes with Data Principal rights

  • Hiding the channel. Rule 14(1) says "prominently publish". A privacy email buried in the footer of a terms page will be hard to defend.
  • Asking for unrelated ID. Requiring Aadhaar or passport scans when you identify users by mobile number creates new data and friction. Use the identifiers you issued.
  • Treating erasure as absolute. Erasure is subject to legal retention and Rule 8(3) one-year retention. Over-deleting logs can itself breach the Rules.
  • Forgetting processors. Requests must reach analytics tools, CRM, data warehouses and LLM vendors, with backups handled under a documented expiry policy, that hold personal data.
  • No deadline tracking. Without a published period and timers, the 90-day ceiling in Rule 14(3) becomes impossible to evidence.
  • Missing the Rule 9 contact. Every response to a rights request must carry the DPO or privacy contact details.
  • Publishing an unrealistic period. A short published period looks good, but missing it is worse than publishing a longer period, up to 90 days, that you reliably meet.

The Board generally hears complaints only after the grievance route is exhausted (s.13(3)), so an effective internal process is the first line of defence against inquiries and penalties of up to ₹50 crore for failures in provisions not otherwise specified in the Schedule.

What to do before 13 May 2027

Rule 14 commences on 13 May 2027. Building rights handling takes longer than drafting a notice, so start now.

  1. Map data stores and processors that hold personal data, including logs and backups.
  2. Choose identifiers you will accept and list them in your terms of service, consistent with Rule 14(5).
  3. Build the privacy centre or request form, with request types and identity verification.
  4. Decide your published response period for grievances, no longer than 90 days, and staff for it. See the 90-day grievance rule.
  5. Automate fan-out to downstream systems and processors for correction and erasure.
  6. Template responses that include the Rule 9 contact.
  7. Update notices: Rule 3(c) requires the notice to describe how to withdraw consent, exercise rights and complain to the Board.
  8. Test end-to-end with synthetic users before launch and keep evidence.

This work also serves Rule 7 breach handling, because the same contact and communication channels are used to notify affected Data Principals.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Publish the rights request channel

    Show the means of making requests prominently on the website and app, not just in a policy PDF.

    Rule 14(1)(a)

  2. Publish required identifiers

    State which username, customer ID, mobile number or other identifier is needed to verify a requester.

    Rule 14(1)(b); Rule 14(5)

  3. Publish a grievance response period

    Choose and display a response period of no more than 90 days, and build timers to meet it.

    Rule 14(3)

  4. Build an access export

    Produce a summary of personal data, processing activities and recipient fiduciaries and processors.

    Section 11

  5. Propagate corrections and erasure

    Push changes to downstream systems and processors while honouring legal and Rule 8(3) retention.

    Section 12; Rule 8(3)

  6. Enable nomination

    Let users nominate one or more individuals and define the proof a nominee must provide.

    Section 14; Rule 14(4)

  7. Include the Rule 9 contact in responses

    Add DPO or privacy contact details to every response to a rights request.

    Rule 9

  8. Log every request

    Keep timestamps, decisions and evidence so the Board can see the process works.

    Rule 14(3)

Key dates

  1. DPDP Rules, 2025 published

  2. Consent Manager registration (Rule 4) in force

  3. Rule 14 rights procedures and sections 11–14 of the Act apply

Answers

Frequently asked questions

What rights do I have under the DPDP Act?

You have the right to access a summary of your personal data and who it was shared with (section 11), to correct, complete, update or erase it (section 12), to grievance redressal (section 13) and to nominate someone to act for you on death or incapacity (section 14). You can also withdraw consent as easily as you gave it.

How long does a company have to respond to a DPDP rights request?

Rule 14(3) requires every Data Fiduciary and Consent Manager to publish a grievance response period that does not exceed 90 days, and to put measures in place to meet it. Companies can choose a shorter period. The Act and Rules do not set a separate fixed deadline for access or correction requests.

Is there a right to data portability under DPDP?

No. The DPDP Act does not include a GDPR-style data portability right. The access right in section 11 gives a summary of data and processing activities. Separately, a registered Consent Manager must give a Data Principal a machine-readable copy of its consent records on request.

Can a company refuse to erase my data?

Yes, in some cases. Erasure under section 12 is subject to retention needed for the specified purpose or required by law. Rule 8(3) also requires every Data Fiduciary to retain personal data, traffic data and processing logs for at least one year from processing for Seventh Schedule purposes, even after account deletion.

What identifiers can a company ask for to verify a request?

Rule 14(5) defines an identifier as any sequence of characters the Data Fiduciary issued to identify you, such as a customer ID, application reference number, enrolment ID, email address, mobile number or licence number. The fiduciary must publish which identifiers it needs under Rule 14(1)(b).

Can I go straight to the Data Protection Board with a complaint?

Generally no. Section 13(3) of the DPDP Act requires a Data Principal to exhaust the Data Fiduciary's or Consent Manager's grievance redressal mechanism before approaching the Board. If the response is unsatisfactory or does not arrive within the published period, a complaint to the Board can follow.

When do Data Principal rights start applying?

Sections 11 to 14 of the DPDP Act and Rule 14 of the DPDP Rules come into force on 13 May 2027, eighteen months after the Rules were published on 13 November 2025. Until then, the IT Act and SPDI Rules continue to apply to many organisations.

Legal references and sources

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.