AMLEGALS
Back to Documents
Procedure

Data Subject Request Procedures

Operationalizing the rights of Data Principals to access, correct, and erase their personal data

Section 11Section 12Section 13Section 14Rule 14

Data Principals have rights. The right to access their data. The right to correct inaccuracies. The right to erasure. The right to nominate someone to exercise these rights after death. Your procedures must enable these rights to be exercised effectively within statutory timelines.

The Rights Framework

Section 11 grants Data Principals the right to access a summary of their personal data and processing activities. Section 12 provides the right to correction and erasure. Section 11 concerns access, Section 12 correction and erasure, Section 13 grievance redressal, and Section 14 nomination. Rule 14(3) requires a published reasonable grievance-response period not exceeding 90 days; it is not a universal deadline for every rights request.

Request Intake

You need a clear channel through which Data Principals can submit requests. This could be a web form, email address, or other mechanism. But it must be accessible and monitored. Requests buried in general inboxes or requiring physical mail create compliance risk.

Key Points
  • Dedicated request intake channel
  • Identity verification procedure
  • Request logging and tracking
  • Acknowledgment within reasonable timeframe

Identity Verification

Before fulfilling a request, you must verify the requester is the Data Principal or authorized representative. This prevents unauthorized disclosure. But verification should not be so burdensome that it effectively denies the right. Balance security with accessibility.

Published Grievance-Response Period

Section 11 concerns access, Section 12 correction and erasure, Section 13 grievance redressal, and Section 14 nomination. Rule 14(3) requires a published reasonable grievance-response period not exceeding 90 days; it is not a universal deadline for every rights request. This is the outer limit, not the target. Faster response demonstrates respect for rights and reduces complaints. Build processes that can respond in days, not months.

Handling Complex Requests

Some requests are straightforward. Others involve data scattered across systems, requiring coordination across departments. Your procedures must account for this complexity while still meeting deadlines. Internal SLAs should be tighter than the statutory window to provide buffer for complications.

Essential Clauses

Request Submission Methods

Rule 14

How Data Principals can submit requests

Identity Verification Process

Rule 14

Proportionate verification without undue burden

Response Timeline Commitments

Rule 14

Published reasonable grievance-response period, not exceeding 90 days; separate operational targets for other requests

Access Request Fulfillment

Section 11

What information is provided and in what format

Correction Procedure

Section 12(2)

How inaccuracies are investigated and corrected

Erasure Procedure

Section 12(3)

How deletion requests are processed subject to lawful retention

Nomination Registration

Section 14; Rule 14(4)

Nomination for death or incapacity

Exception Handling

Rule 14

Grounds for declining requests and communication process

Implementation Steps

1

Establish dedicated DSR intake channel with monitoring

2

Develop identity verification protocol balancing security and accessibility

3

Create internal workflow routing requests to relevant data custodians

4

Build tracking system with deadline alerts

5

Draft response templates for common request types

6

Train customer-facing teams on DSR handling

7

Establish escalation path for complex or disputed requests

8

Implement quality review before response dispatch

Frequently Asked Questions

Need This Document Drafted?

Understanding the requirement is the first step. Having it implemented correctly is what protects your organization. Our team drafts DPDPA-compliant documents tailored to your specific operations.

Get in Touch
DPDPA Dsr Procedures: legal reference

What must a DPDPA privacy notice contain?

Section 5 read with Rule 3 requires a notice, understandable independently of other information, that itemises the personal data and the specified purpose, and explains how the Data Principal may withdraw consent, exercise rights and complain to the Board. A Data Principal has the right to access the notice in English or any language specified in the Eighth Schedule to the Constitution. The design of translation operations is an implementation matter.

What makes consent valid under DPDPA?

Section 6 requires consent to be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action and limited to personal data necessary for the specified purpose. Withdrawal must be as easy as giving consent.

Is a Data Fiduciary responsible for its vendors under DPDPA?

Yes. Section 8(1) makes the Data Fiduciary responsible for compliance in respect of processing undertaken by it or on its behalf by a Data Processor. Section 8(2) requires a Data Fiduciary to engage a Data Processor under a valid contract. Detailed contractual clause architecture is an implementation best practice guided by Section 8(2).

Which provisions of the DPDPA and the DPDP Rules, 2025 are relevant to DPDPA Dsr Procedures?

Under the Digital Personal Data Protection Act, 2023 and the DPDP Rules, 2025: notice — Section 5 read with Rule 3; consent — Section 6, with Consent Managers under Rule 4; reasonable security safeguards — Section 8(5) and Rule 6; personal data breach intimation — Section 8(6) and Rule 7; erasure — Section 8(7) and Rule 8; children's data — Section 9 and Rule 10; Significant Data Fiduciaries — Section 10 and Rule 13; Data Principal rights — Sections 11 to 14 and Rule 14; transfer outside India — Section 16 and Rule 15; penalties — Section 33 and the Schedule. Published by AMLEGALS (Anandaday Misshra, Founder & Managing Partner).