Rule 14 — DPDP Rules, 2025
(1) A Data Principal may exercise her rights under Chapter III by submitting a request to the Data Fiduciary through a published channel. (2) Every Data Fiduciary shall— (a) publish the contact information specified under Rule 9; (b) acknowledge receipt of a request from a Data Principal within such period as may be specified; (c) respond to the request within such period as may be specified; (d) accept and process requests made on behalf of the Data Principal by an authorised representative. (3) A Data Fiduciary may verify the identity of the Data Principal before processing a request.
Source: Digital Personal Data Protection Rules, 2025. Official text available at truconsent.io/resources/dpdp-rules.pdf.
Rule 14 makes Chapter III rights operational by prescribing four requirements: a published channel (linked to Rule 9), acknowledgement within a specified period, resolution within a specified period, and a mechanism to accept requests from authorised representatives (including nominees under Section 14). The Board will specify the exact timelines — but Data Fiduciaries should design systems capable of acknowledging within 24 hours and resolving within 30 days (common benchmarks from comparable frameworks). Rule 14(3)'s identity verification is permitted, not optional — use it to prevent Section 15(b) impersonation.
When a Data Principal submits an erasure request, the Data Fiduciary must acknowledge receipt within the prescribed period. Acknowledgement means more than an auto-reply — it should confirm that the request has been received, will be processed, and give a reference number the Data Principal can use if they need to follow up. Silence on receipt is a Rule 14 violation.
A Data Principal's lawyer submits an access request on their behalf. Under Rule 14(2)(d), the Data Fiduciary must have a mechanism to accept and process this request. This requires verifying that the representative is authorised — by checking a power of attorney or a nomination registration from Section 14. A blanket refusal to deal with representatives is non-compliant.
Rule 14(3) allows identity verification before processing a request — this is the Section 15(b) impersonation protection. However, the verification process cannot be so burdensome that it effectively prevents the exercise of rights. A verification step that takes three weeks or requires notarised documents will be treated by the Board as an effective denial of rights.
One Licence, No Middlemen: Why India Does Not Need CMPs Beside Consent Managers
The industry has settled on a neat split: the Consent Manager serves the Data Principal, and a CMP serves the Data Fiduciary. I think it is wrong. India built one consent intermediary on purpose. Here is why the unlicensed CMP layer adds risk without adding value.
19 Oct 2026
What DPDPA Rule 6 Actually Requires in Every Data Processor Contract
Rule 6's security safeguards obligation doesn't stop at your organisation's boundary, it flows downstream to every vendor who touches personal data on your behalf. Most processor contracts in use today don't reflect this, and the liability gap lands squarely with the Data Fiduciary.
11 Jul 2026
Outsourcing Data Processing Doesn't Outsource Liability Under DPDPA
Under India's DPDPA, engaging a KYC provider, cloud vendor, or email platform doesn't transfer your legal accountability, it multiplies it. Here's what Data Fiduciaries must contractually lock down before handing personal data to any processor.
11 Jul 2026