Every Data Fiduciary processing personal data of Indian residents must give those individuals a way to raise concerns about how their data is handled. Section 13 of the Digital Personal Data Protection Act, 2023 creates this right, and Rule 12 of the DPDP Rules, 2025 prescribes how the mechanism must work. Getting it right matters: if a complaint goes unresolved within the prescribed period, the Data Principal can escalate directly to the Data Protection Board of India, and the Board has the power to impose significant penalties. This guide explains what the law requires and how to build a mechanism that meets it.
A grievance redressal mechanism under the DPDP Act is a formal, documented process through which a Data Principal — any individual whose personal data is processed — can raise a complaint with the Data Fiduciary. The complaint may concern any right under the Act: the right to information about processing, the right to correction or erasure, the right to withdraw consent, or the right to nominate another person to exercise their rights.
The mechanism must be accessible, operational, and backed by a named contact point whose details are publicly available. It is not optional, and a grievance form buried in a long privacy policy that no one can find does not meet the standard.
Every Data Fiduciary — whether a large enterprise, a mid-size company or a startup that processes personal data of individuals in India — must have a working grievance redressal mechanism. The requirement does not depend on whether you are a Significant Data Fiduciary (SDF). The difference is in the designated contact:
| Entity | Designated Contact | Requirement Source |
|---|---|---|
| Significant Data Fiduciary (SDF) | Data Protection Officer (DPO), based in India, reporting to the board | Section 10(2)(a) read with Rule 9 |
| All other Data Fiduciaries | A published contact person whose business details are prominently available | Section 8(9) read with Rule 9 |
In both cases, the contact details must be prominently published — on your website, in your app, and in any response to a Data Subject Access Request (DSAR).
Section 13 gives every Data Principal the right to file a grievance with the Data Fiduciary if they believe the Fiduciary has not discharged its duties. Rule 12 then prescribes how that grievance must be handled. The key obligations are:
| Obligation | Source | What it means in practice |
|---|---|---|
| Acknowledge the grievance | Rule 12 | Send a confirmation to the Data Principal that the complaint has been received, with a reference number or tracking identifier |
| Resolve within the prescribed period | Rule 12 | The complaint must be addressed and the outcome communicated to the Data Principal within the timeframe set by the Rules |
| Publish contact details prominently | Section 8(9), Rule 9 | The DPO's or contact person's business details must be easy to find — on the homepage, privacy notice, and in every DSAR response |
| Include contact details in rights responses | Rule 9 | Every reply to a Data Principal exercising a right must carry the contact details of the DPO or designated person |
| Enable escalation to the Board | Section 13(3) | If the grievance is not resolved within the prescribed period, or the Data Principal is dissatisfied, they may file a complaint with the Data Protection Board |
Confirm the exact prescribed resolution period against the final Gazette text of Rule 12 once the Board begins operations, as procedural timelines may be updated.
Building the mechanism from scratch takes four to eight weeks if you move steadily. Here is a practical sequence:
A well-run grievance process has five stages:
| Stage | What happens | Output |
|---|---|---|
| Receipt | Data Principal submits complaint via the published channel | Acknowledgement with reference number sent within 24 hours |
| Triage | Contact person or DPO categorises the complaint and routes it to the relevant team | Internal ticket opened with owner, priority and deadline |
| Investigation | Relevant team reviews the complaint, checks processing records and consent logs | Findings documented in the tracking log |
| Resolution | Action taken (correction made, data erased, consent withdrawn, or complaint not upheld with reasons) | Written response to the Data Principal, carrying DPO or contact details |
| Closure | Log updated; if unresolved within the prescribed period, the Data Principal is informed of their right to approach the Board | Closed record with full audit trail |
Rule 12 sets a prescribed period within which a Data Fiduciary must resolve a grievance. If the complaint is not resolved within that period, or if the Data Principal is not satisfied with the outcome, Section 13(3) allows them to file a complaint directly with the Data Protection Board of India.
The Board is not a first-resort body — it expects the Data Fiduciary's own mechanism to have been used first. A complaint to the Board that names your business will trigger an inquiry, and the Board may call for your records of how the complaint was handled internally. That is why the tracking log and the acknowledgement record are not optional extras.
If your mechanism also handles requests under IT Rules 2021 (the existing grievance officer requirement), check that the DPDP process meets both sets of obligations. One officer can hold both roles if they meet both sets of requirements, but the timelines and scope differ and should be documented separately.
Failing to establish and maintain a proper grievance redressal mechanism falls under the broader duty to comply with the Act's provisions. The Data Protection Board can impose penalties of up to ₹50 crore for failing to publish contact details as required, and higher penalties for broader non-compliance with the Act's obligations. More practically, a complaint filed with the Board triggers an inquiry that demands documented evidence of your internal process — and an absent or deficient process is difficult to defend after the fact.
The full penalty schedule is in our guide to DSAR and rights automation software and how it supports compliance.
Pixl is an AI-powered DPDP compliance platform with a Consent engine, Discover engine and operations layer, deployable on-premise or in the cloud. For grievance redressal, the platform contributes in three ways:
To see how the controls map to your systems, explore our DSAR and rights automation software or book a demo.
Ready to transform? Commence your Digital Transformation journey now!
Get Started