[Analysis] Data Principal Rights Requests under the DPDP Act – The Six-Stage Workflow | Request Log | Ninety-Day Grievance Ceiling

  • Blog|Company Law|
  • 19 Min Read

Handling Data Principal rights requests under sections 11 to 15 and Rule 14: the six-stage fulfilment workflow, the request log, when erasure may be refused, deferred erasures, the ninety-day grievance ceiling and the exhaustion requirement under section 13(3).

  • By Taxmann
  • |
  • Last Updated on 16 November, 2026
Chapter III of the DPDP Act confers four rights: access under section 11, correction, completion, updating and erasure under section 12, grievance redressal under section 13, and nomination under section 14. The Act sets no deadline for responding to an individual rights request, and it sets a ninety-day ceiling under Rule 14(3) for responding to a grievance. The gap between those two facts is where enforcement risk accumulates. Taxmann’s Digital Personal Data Protection sets out a six-stage fulfilment workflow, from Intake to Closure, and a request log that captures each stage, on the premise that the Data Fiduciary may have to demonstrate in a Board proceeding exactly when a request arrived, how identity was verified, what was done and when the outcome was communicated.

Table of Contents

  1. Which rights can a request invoke?
  2. How does a Data Principal exercise a right?
  3. What does the right of access require the organisation to produce?
  4. When can an erasure request be refused?
  5. What is the six-stage rights fulfilment workflow?
  6. What should the rights request log capture?
  7. How should deferred erasures be handled?
  8. What is the grievance right, and why does ninety days matter?
  9. How does the nomination right work?
  10. What do the Data Principal’s duties change for the organisation?
  11. What does an auditor test, and what goes wrong?
  12. Quick answers

1. Which rights can a request invoke?

Four, under sections 11 to 14: access to information about personal data, correction, completion, updating and erasure, grievance redressal, and nomination. The DPDP Act does not include a right to data portability, a right to object, or a right to restriction of processing (para 9, opening). What each right covers, and the five duties that sit alongside them, is set out in rights of Data Principals under the DPDP Act. This article deals with what the organisation has to do when a request arrives.

For an organisation with an existing GDPR programme, the operational consequence is that a portability or objection workflow built for the GDPR has no DPDP equivalent to satisfy, while the access and erasure workflows carry more weight because there are fewer rights among which to distribute the demand.

2. How does a Data Principal exercise a right?

Through the means the Data Fiduciary publishes, which is itself an obligation.

Rule 14(1) requires the Data Fiduciary and, where applicable, the Consent Manager, to prominently publish on its website or application the details of the means using which a Data Principal may make a request for the exercise of rights, and the particulars such as username or other identifiers which may be required to identify the Data Principal under its terms of service. Rule 14(2) provides that the Data Principal may make a request using the means and furnishing the particulars required by the Data Fiduciary (paras 9.1 and 9.6).

Rule 14(5) defines “identifier” broadly: 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 (para 9.1).

Two constraints on that mechanism are easy to miss.

The publication must be prominent. The book’s gloss is specific: not buried in a footer link or a sub-page of the help centre, and accessible on both the website and the application if the Data Fiduciary operates both channels (para 9.6).

And the identification requirement must be proportionate. The Data Fiduciary may not impose identification requirements that are more onerous than those it applies in its ordinary terms of service. The book’s illustration makes the standard concrete: if a customer can access the Data Fiduciary’s services using an email address and a password, the Data Fiduciary may not require a notarised identity document for the exercise of a data access request. The identification requirement must be proportionate to the risk of responding to a fraudulent request, not a deterrent to the exercise of rights (para 9.6).

On form, the mechanism may be a dedicated web portal, an in-application submission form, a designated email address, or a combination of channels. Whatever its form, it must be prominently published as Rule 14(1) requires, and it must be capable of receiving, logging and routing requests for each category of right: access, correction, completion, updating, erasure and nomination (para 9.7.2). The mechanism must be built, tested and published before the substantive provisions of the Act come into force on 13 May 2027 (para 9.7.2). Rule 14 and sections 11 to 15 are on Taxmann.com | Research under Indian Acts and Rules.

3. What does the right of access require the organisation to produce?

Section 11(1) confers on the Data Principal the right to obtain, from the Data Fiduciary to whom she has previously given consent, including consent as referred to in clause (a) of section 7, and upon making a request in such manner as may be prescribed, three categories of information (para 9.1):

Category What must be produced
Summary of processing A summary of personal data which is being processed by the Data Fiduciary and the processing activities undertaken with respect to such personal data
Recipients The identities of all other Data Fiduciaries and Data Processors with whom the personal data has been shared, along with a description of the personal data so shared
Prescribed information Any other information related to the personal data and its processing, as may be prescribed

The second category is the one that fails without preparation. The book sets out the implication: the Data Fiduciary must be in a position to produce, for each requesting Data Principal, a summary that identifies the categories of personal data being processed, the nature of the processing activities and the downstream recipients, whether those recipients are Data Fiduciaries or Data Processors. That requires the Data Fiduciary to maintain, at the backend, a register or mapping of data flows that permits it to trace, for any given Data Principal, where her data resides, who has received it and what is being done with it. An organisation that processes personal data across multiple systems and has shared it with multiple vendors but has not maintained a record of those flows will be unable to fulfil an access request accurately and completely (para 9.1).

There is one exception, and it is narrow. Section 11(2) carves out the disclosure of sharing information under clauses (b) and (c) of section 11(1) in respect of sharing by the Data Fiduciary with any other Data Fiduciary authorised by law to obtain such personal data, where such sharing is pursuant to a request made in writing by that other Data Fiduciary for the purpose of prevention or detection or investigation of offences or cyber incidents, or for prosecution or punishment of offences (para 9.1.1).

The practical effect is that if a law enforcement agency, an intelligence agency or CERT-In has requested the Data Fiduciary to share personal data for a law enforcement or cyber security purpose, the Data Fiduciary is not required to disclose the identity of that requesting agency or the fact of such sharing in response to an access request (para 9.1.1).

The book is careful about the boundary. The exception applies only to sharing pursuant to a written request, only for the specified law enforcement and cyber security purposes, and only with a Data Fiduciary that is authorised by law to obtain the data. Sharing with a commercial partner, a credit bureau or a marketing affiliate remains fully subject to the disclosure obligation under section 11(1)(b), regardless of any contractual confidentiality provisions. The operational conclusion is to maintain separate records of law-enforcement-related disclosures and commercial disclosures, so that accurate responses can be given to access requests while withholding only the information that falls within the section 11(2) exception (para 9.1.1).

4. When can an erasure request be refused?

Section 12 confers two related but distinct rights. Section 12(1) provides a right to correction, completion, updating and erasure of personal data for the processing of which the Data Principal has previously given consent, in accordance with any requirement or procedure under any law in force. Section 12(2) imposes the corresponding obligation: upon receiving a request, the Data Fiduciary shall correct the inaccurate or misleading personal data, complete the incomplete personal data, and update the personal data (para 9.2).

Erasure is addressed separately, and differently. Section 12(3) provides that a Data Principal shall make a request in such manner as may be prescribed for erasure of her personal data, and upon receipt of such a request the Data Fiduciary shall erase her personal data unless retention of the same is necessary for the specified purpose or for compliance with any law for the time being in force (para 9.2).

So the erasure right operates subject to two exceptions, and only two: purpose necessity, and legal retention requirements. The book’s illustration is the common case: a Data Principal who requests erasure of her personal data from a bank that is required by anti-money laundering law to retain her identity records for a prescribed period will receive a response explaining that the data cannot be erased during the retention period, and the bank must document the legal basis for the continued retention (para 9.2).

On what the response should say, the book goes further than the bare text. Where an erasure request is refused because retention remains necessary for a specified purpose or compliance with law, the response should identify the broad reason for continued retention, the categories of data retained, the applicable retention period or review point where known, and the available grievance route, even though the Act does not expressly require a reasoned refusal notice in those terms (para 9.2).

It is worth noting what the DPDP erasure right does not require. The book contrasts it with the Google Spain judgment of 2014, which required search engines to balance the individual’s privacy and data protection rights against the public’s interest in access to information, with a presumption in favour of delisting where information is inadequate, irrelevant or no longer relevant. Section 12(3) does not replicate that balancing-test approach. The Data Fiduciary is not required to conduct a public-interest balancing test, but must assess each erasure request against the two statutory exceptions and document the outcome (para 9.2).

The correction limb has a counterpart on the obligations side, which is useful for allocating ownership internally. The correction, completion and updating right under section 12(1) and (2) is a right of data quality that complements the Data Fiduciary’s obligation under section 8(3) to ensure the completeness, accuracy and consistency of personal data used for decision-making or disclosed to another Data Fiduciary. The right and the obligation operate from opposite directions towards the same objective, and where the organisation’s own data quality processes fail to detect an error, the Data Principal’s correction request serves as a corrective mechanism (para 9.2).

Taxmann.com | Research | Subscribe Now!

5. What is the six-stage rights fulfilment workflow?

The book designs the workflow as a structured process with defined stages, each producing a record (para 9.7.1):

Stage What happens
1. Intake Receiving the request through the published mechanism and logging it with a unique reference number
2. Verification Confirming the identity of the requesting Data Principal through the published identification requirements
3. Classification Determining which right is being exercised: access, correction, completion, updating, erasure, or a combination
4. Processing Retrieving the relevant personal data, executing the requested action, and documenting the steps taken
5. Response Communicating the outcome to the Data Principal, including the information requested or the action taken, and the contact details of the Data Protection Officer or designated person
6. Closure Recording the completion of the request, the date of closure, and any follow-up actions required

On timing, the Act creates an asymmetry that the workflow has to manage. It prescribes no specific deadline for responding to individual rights requests, as distinct from the ninety-day grievance response period under Rule 14(3). The book’s warning is that the absence of a deadline is not a licence: an organisation that takes sixty or seventy days to respond to a straightforward access request is creating conditions for a grievance under section 13, which then triggers the ninety-day grievance clock (para 9.7.1).

Its recommendation is to set internal service-level targets substantially shorter than the grievance ceiling, for example thirty days for access requests and fifteen days for correction requests, so that the organisation has a buffer of time before the matter escalates to the grievance tier and, potentially, to the Board (para 9.7.1).

The mechanism should also be designed to produce auditable records at every stage, because the Data Fiduciary may be required to demonstrate, in a Board proceeding, that it received a request on a specific date, verified the identity of the requestor, processed the request within a specific timeframe and communicated the outcome. The book is direct about what does not meet that standard: a mechanism that operates through an unstructured email inbox, where requests are handled ad hoc by whoever monitors the inbox, does not produce the level of documentation necessary for regulatory defensibility. A structured system with automated acknowledgements, assignment tracking and outcome recording provides both operational efficiency and evidentiary completeness (para 9.7.2).

Where that workflow and its documentation have to be designed and built rather than described, including compliance SOPs and automation of compliances, Taxmann Advisory provides implementation support.

6. What should the rights request log capture?

Figure 9.1 in the book sets out the fields (para 9.7.1):

Field Content
Request ID A unique reference, for example DSAR-2027-0042
Date received The date of receipt
Channel Web portal, email or in-app
Data Principal Name or user ID
Verified Yes or no, and the method: account login or ID match
Right exercised Access under section 11; correction under section 12(2); erasure under section 12(3); grievance under section 13; nomination under section 14
Description The Data Principal’s request in summary
Assigned to Handler name and date assigned
Systems queried For example CRM, billing, analytics, a named Data Processor
Action taken Summary of data retrieved, corrected or erased, or of the grievance investigated
If erasure declined Legal basis for retention: statute, section and retention period
Date responded The date, and the number of days elapsed
Response method Email, portal or post
DPO contact included Yes or no
Closure Date and outcome: fulfilled, partially fulfilled, or declined with reasons
Follow-up required For example a deferred erasure scheduled for a stated date, or none

Three fields in that log carry more weight than their size suggests. “Systems queried” is the field that proves the access response was complete rather than convenient. “If erasure declined” is the field that converts a refusal from a risk into a defence. And “Follow-up required” is the field that prevents the single most common rights failure, examined next.

7. How should deferred erasures be handled?

This is the edge case the book identifies as the most frequently encountered in rights fulfilment, and the mechanism it recommends is simple but almost always absent.

The situation: an erasure request conflicts with a legal retention obligation. Section 12(3) requires erasure unless retention is necessary for the specified purpose or for compliance with any law in force. The decision to decline must be documented with precision: the specific provision of law that requires retention, the categories of personal data subject to that provision, the retention period imposed, and the date on which the retention obligation expires. The response to the Data Principal should explain, in clear and plain language, that the erasure cannot be completed at present, the legal basis for the continued retention, and the date or conditions under which the data will be erased (para 9.7.3).

Then comes the part that fails. The book describes the gap exactly: an erasure request is declined on legitimate grounds at the time of receipt, but the underlying retention obligation subsequently expires and the data remains in the system indefinitely because no review mechanism exists to trigger the deferred erasure (para 9.7.3).

The fix is a follow-up stage in the workflow: a register of declined erasure requests with the corresponding legal justifications, reviewed periodically to ensure that data which has passed the end of its legal retention period is actually erased, and automatic or managed execution of the erasure once the retention obligation has expired (para 9.7.3).

The audit consequence is already recorded in the book’s findings: deferred erasures not tracked, with data retained beyond the expiry of the legal retention period (para 9.8).

8. What is the grievance right, and why does ninety days matter?

Section 13(1) confers on the Data Principal the right to have readily available means of grievance redressal provided by the Data Fiduciary or Consent Manager in respect of any act or omission regarding the performance of its obligations in relation to her personal data or the exercise of her rights under the Act and the rules (para 9.3).

The scope is broad. It encompasses any act or omission by the Data Fiduciary or Consent Manager relating either to the performance of obligations or to the exercise of rights. The book’s examples: a deficient notice, a withdrawal mechanism that is not of comparable ease, a failure to respond to an access request, an incomplete breach notification, or any other departure from the obligations in the Act (para 9.3).

Section 13(2) provides that the Data Fiduciary or Consent Manager shall respond to grievances within such period as may be prescribed, and Rule 14(3) prescribes it: the Data Fiduciary and Consent Manager shall prominently publish on their website or application a reasonable period not exceeding ninety days for responding to grievances, and shall implement appropriate technical and organisational measures for ensuring the effectiveness of the system in responding within that period. The ninety-day period is a ceiling, not a target, and the publication of the grievance response period is itself a mandatory compliance requirement (para 9.3).

Then comes the provision that shapes the whole enforcement architecture. Section 13(3) requires the Data Principal to exhaust the opportunity of redressing her grievance under section 13 before approaching the Board. The Board’s adjudicatory jurisdiction under section 27(1)(b), which empowers it to receive complaints from Data Principals about breaches of obligation or denial of rights, is therefore conditioned on the Data Principal having first sought redress from the Data Fiduciary. The grievance mechanism is not a voluntary customer service feature but a mandatory first-tier dispute resolution process (para 9.3).

The book’s reading of the practical consequence is the single most useful sentence in this area for anyone allocating budget. A grievance that is received, properly investigated and resolved within the prescribed period will ordinarily not reach the Board. A grievance that is ignored, inadequately investigated or responded to after the prescribed period provides the Data Principal with both the cause and the procedural standing to escalate, where the original complaint will be compounded by the failure of the grievance mechanism itself. Organisations that invest in an effective grievance mechanism are, in practical terms, investing in a buffer between themselves and the Board’s enforcement powers (para 9.3).

On design, the mechanism should be a structured workflow rather than an informal process, defining the channels through which grievances may be received, the classification criteria for routing them to the appropriate handler, the service-level targets for acknowledgement, investigation, resolution and communication of outcome, and the escalation path for grievances that cannot be resolved within the team’s authority (para 5.7.4).

The ninety-day ceiling should be translated into internal targets that allow for investigation complexity, with graduated timelines by grievance type and the ceiling serving as the absolute outer boundary rather than the default. The book’s contrast: a straightforward access request may be acknowledged and answered the same day where the information is readily retrievable, while a grievance alleging that data was used for an undisclosed purpose may require a multi-week review of notices, consent records, system logs and processor activity. The difference in handling time may be reasonable, but the organisation should acknowledge the grievance promptly, explain the review process, identify the responsible contact and communicate the outcome within its published period (para 5.7.4).

Organisations in banking, insurance and telecommunications, which already operate customer complaint management systems under sectoral requirements, should assess whether those systems can be extended to accommodate DPDP grievances or whether a separate mechanism is required. The advantage of extension is operational efficiency; the risk is that DPDP grievances, which may involve rights and obligations unfamiliar to customer service teams, may be inadequately handled unless the team is specifically trained on the Act’s requirements and the categories of grievance it contemplates (para 5.7.4). Role-specific training of that kind for customer service teams on rights fulfilment and grievance handling is one of the two tiers the book recommends under section 8(4) and Rule 6(1)(g), and sessions of this kind, live or recorded, run on Taxmann.com | Learning.

9. How does the nomination right work?

Section 14(1) provides that a Data Principal shall have the right to nominate, in such manner as may be prescribed, any other individual who shall, in the event of her death or incapacity, exercise her rights in accordance with the Act and the rules. Section 14(2) defines incapacity as inability to exercise the rights of the Data Principal due to unsoundness of mind or infirmity of body. Rule 14(4) operationalises the mechanism: the Data Principal may, in accordance with the terms of service of the Data Fiduciary and such law as may be applicable, nominate one or more individuals, using the means and furnishing the particulars required by the Data Fiduciary (para 9.4).

The gap the right fills becomes clear when one considers the lifecycle of personal data. A Data Principal who dies or becomes incapacitated loses the ability to exercise access, correction, erasure and grievance rights. Without a nomination mechanism, the personal data remains with the Data Fiduciary indefinitely, subject to whatever retention policies it applies, but without any individual having the standing to exercise the Data Principal’s rights in respect of that data (para 9.4).

The book notes the right has no direct GDPR equivalent, although several Member States have addressed the question through national legislation, and France’s Loi Informatique et Libertes, as amended, permits individuals to issue advance directives regarding the conservation, erasure and communication of their personal data after death. The DPDP Act’s approach is more structured: it provides a nomination mechanism integrated into the Data Fiduciary’s platform, creates a clear record of the nominee’s identity and the scope of the nomination, and requires the Data Fiduciary to facilitate the process through its terms of service (para 9.4).

On design, the mechanism should be integrated into the account management interface, enabling the Data Principal to designate one or more nominees through the same platform she uses to access the service. It should capture the identity of each nominee, the scope of the nomination, whether it covers all rights under the Act or specific rights, and the conditions under which it takes effect. The Data Fiduciary should confirm the nomination to the Data Principal and maintain the records in a manner that permits retrieval when a nominee seeks to exercise rights (para 9.7.4).

Verification of a nominee’s standing requires a separate procedure, and the Data Fiduciary should define the evidence it will accept for each trigger event: a death certificate or legal declaration for death, and a medical certificate or court declaration for incapacity. The book adds a note on how that procedure should feel to use: it should balance the need for verification against the need for reasonable responsiveness, recognising that the nominee may be exercising rights in circumstances of personal distress and should not be subjected to an unnecessarily burdensome or prolonged verification process (para 9.7.4).

One interaction is worth anticipating. Where a Data Principal who has nominated an individual subsequently dies and the nominee requests erasure of the deceased Data Principal’s personal data, the Data Fiduciary must process the request in accordance with section 12(3), erasing the data unless retention is necessary for the specified purpose or for compliance with law. If the Data Fiduciary is a bank and banking law requires retention of the deceased customer’s records for a prescribed period, the erasure request must be declined with documented justification. The nominee’s rights are co-extensive with the Data Principal’s rights, not broader (para 9.4).

10. What do the Data Principal’s duties change for the organisation?

Less than might be expected. Section 15 places five duties on the Data Principal, among them the duty not to impersonate another person and the duty to furnish only verifiably authentic information when seeking correction or erasure, and breach carries a penalty of up to Rs. 10,000 imposed by the Board, not by the Data Fiduciary (para 9.5). The full list is in rights of Data Principals under the DPDP Act.

What the duties do not do is relieve the Data Fiduciary. Section 8(1) provides that the Data Fiduciary’s obligations are not relieved by the Data Principal’s failure to discharge her duties. The book works the example through: a Data Principal who provides false identity information in breach of section 15(b) is subject to a penalty of up to Rs. 10,000; the Data Fiduciary that processes the false information remains subject to its obligations under section 8(3) on data quality, section 8(5) on security safeguards and every other applicable provision, and cannot invoke the Data Principal’s breach as a defence to its own non-compliance (para 9.5).

For frivolous complaints there is a separate procedural consequence. Section 28(12) provides that at any stage after receipt of a complaint, if the Board is of the opinion that the complaint is false or frivolous, it may issue a warning or impose costs on the complainant. Read with section 15(d), a Data Principal who files a complaint the Board determines to be false or frivolous may face both costs under section 28(12) and a penalty of up to Rs. 10,000 (para 9.5).

11. What does an auditor test, and what goes wrong?

The test programme for this obligation area (para 9.8): whether the rights request mechanism is prominently published on the website or application per Rule 14(1); whether identification requirements are proportionate to terms-of-service requirements and not more burdensome; whether the rights fulfilment log captures all stages from intake to closure; whether response times fall within internal service-level targets and do not exceed the ninety-day grievance ceiling; whether declined erasure requests are documented with the specific legal retention basis; whether deferred erasures are tracked for follow-up when the retention period expires; whether the nomination mechanism is integrated into the account management interface; and whether the grievance response period is published and compliance demonstrated through grievance records.

The evidence to have ready: website and application screenshots showing the published rights request mechanism and grievance response period; the rights request log with complete entries; a response time analysis giving average, median and maximum; sample responses to access, correction and erasure requests; the register of declined erasure requests with legal retention references; nomination mechanism documentation; the grievance log with receipt and resolution dates; and sample grievance responses (para 9.8).

The five findings the book reports as recurring (para 9.8):

Finding What it looks like
Mechanism not prominently published The rights mechanism exists but is buried in a sub-page
No structured log Requests handled through ad hoc email exchanges without tracking
Erasure declined without a documented basis No record of the specific legal provision requiring retention
Deferred erasures not tracked Data retained beyond the expiry of the legal retention period
Grievance mechanism published but no grievances recorded Suggests the mechanism is either inaccessible or non-functional

The last of those five is the most instructive, because it is the only finding on the list that is triggered by an absence of activity rather than by a defect in it. A published grievance channel with an empty log invites the inference that nobody can find it or that it does not work.

12. Quick answers

How does a Data Principal make a rights request?

Through the means the Data Fiduciary publishes. Rule 14(1) requires the Data Fiduciary, and where applicable the Consent Manager, to prominently publish on its website or application the details of the means for making a request and the particulars required to identify the Data Principal. Rule 14(2) provides that the Data Principal may make the request using those means. Rule 14(5) defines identifier broadly, covering a customer identification file number, application reference number, enrolment ID, email address, mobile number or licence number.

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

The Act prescribes no deadline for an individual rights request. Rule 14(3) prescribes a ceiling of ninety days for responding to a grievance under section 13, which the Data Fiduciary must publish. Taxmann’s Digital Personal Data Protection recommends internal service-level targets substantially shorter than that ceiling, for example thirty days for access requests and fifteen days for correction requests, because a slow rights response creates the conditions for a grievance, which then starts the ninety-day clock.

Can a company refuse to erase personal data?

Only on two grounds. Section 12(3) requires the Data Fiduciary to erase personal data on request unless retention is necessary for the specified purpose or for compliance with any law for the time being in force. The refusal should identify the broad reason for continued retention, the categories of data retained, the applicable retention period or review point where known, and the available grievance route, and the specific legal provision should be recorded in a register of declined erasure requests.

What is the six-stage rights fulfilment workflow?

Intake, logging the request with a unique reference number; Verification of the requester’s identity through the published requirements; Classification of which right is being exercised; Processing, retrieving the data and executing the action; Response, communicating the outcome with the contact details of the Data Protection Officer or designated person; and Closure, recording completion and any follow-up required. The structure is set out in Taxmann’s Digital Personal Data Protection.

Must a Data Principal complain to the company before the Data Protection Board?

Yes. Section 13(3) requires the Data Principal to exhaust the opportunity of redressing her grievance under section 13 before approaching the Board, which conditions the Board’s jurisdiction under section 27(1)(b) on the Data Principal having first sought redress from the Data Fiduciary. The grievance mechanism is therefore a mandatory first-tier dispute resolution process rather than a customer service feature.

What is the ninety-day period under the DPDP Rules?

Rule 14(3) requires the Data Fiduciary and the Consent Manager to prominently publish on their website or application a reasonable period not exceeding ninety days for responding to grievances, and to implement appropriate technical and organisational measures to ensure the effectiveness of the system in responding within that period. It is a ceiling rather than a target, and publishing the period is itself a compliance requirement.


This article draws on Chapter 9 of Taxmann’s Digital Personal Data Protection – An Essential Guide to India’s DPDP Law by CA Narasimhan Elangovan (2026 Edition), which examines each of the four rights and five duties, the manner of exercising rights under Rule 14, the six-stage rights fulfilment workflow, the rights request log in Figure 9.1, the handling of competing legal retention obligations and deferred erasures, the nomination mechanism, and the audit considerations for this chapter. It also draws on Chapter 5 on designing the grievance redressal mechanism under section 8(10) and Rule 14(3). Law stated as updated till 15 September 2026.

The DPDP Act, 2023, the DPDP Rules, 2025 and the notifications of 13 November 2025 are available on Taxmann.com | Research under Indian Acts and Rules.

Related reading: rights of Data Principals under the DPDP Act · obligations of Data Fiduciaries · lawful processing and consent · the DPDP Act compliance checklist for businesses.

More in this series: the Data Protection Board of India · how a DPDP compliance audit is conducted · Significant Data Fiduciary obligations · Consent Managers under the DPDP framework · personal data breach intimation under Rule 7 · Data Fiduciary, Data Processor or both · children’s data and verifiable parental consent · the SPDI Rules and the DPDP Act · the Record of Processing Activities (ROPA) · the incident response plan · data retention and erasure · the privacy notice under Rule 3 · the data processing agreement · data localisation and cross-border transfers · employee data and workplace monitoring · exemptions under the DPDP Act · legitimate uses under section 7.

Disclaimer: The content/information published on the website is only for general information of the user and shall not be construed as legal advice. While the Taxmann has exercised reasonable efforts to ensure the veracity of information/content published, Taxmann shall be under no liability in any manner whatsoever for incorrect information, if any.

Leave a Reply

Your email address will not be published. Required fields are marked *

Everything on Tax and Corporate Laws of India

To subscribe to our weekly newsletter please log in/register on Taxmann.com

Author: Taxmann

Taxmann Publications has a dedicated in-house Research & Editorial Team. This team consists of a team of Chartered Accountants, Company Secretaries, and Lawyers. This team works under the guidance and supervision of editor-in-chief Mr Rakesh Bhargava.

The Research and Editorial Team is responsible for developing reliable and accurate content for the readers. The team follows the six-sigma approach to achieve the benchmark of zero error in its publications and research platforms. The team ensures that the following publication guidelines are thoroughly followed while developing the content:

  • The statutory material is obtained only from the authorized and reliable sources
  • All the latest developments in the judicial and legislative fields are covered
  • Prepare the analytical write-ups on current, controversial, and important issues to help the readers to understand the concept and its implications
  • Every content published by Taxmann is complete, accurate and lucid
  • All evidence-based statements are supported with proper reference to Section, Circular No., Notification No. or citations
  • The golden rules of grammar, style and consistency are thoroughly followed
  • Font and size that's easy to read and remain consistent across all imprint and digital publications are applied