Quick answer
Under Rule 14(3) of the DPDP Rules, 2025, every Data Fiduciary and Consent Manager must prominently publish on its website or app a grievance response period not exceeding ninety days, and implement appropriate technical and organisational measures to respond within it. Data Principals must exhaust this mechanism before complaining to the Data Protection Board under section 13(3). The rule applies from 13 May 2027.
- Ninety days is a ceiling, not a target; a fiduciary may publish and meet a shorter period.
- The period must be prominently published on the website or app, or both.
- Rule 14(3) also requires technical and organisational measures that make the published period achievable.
- Data Principals must exhaust internal grievance redressal before approaching the Data Protection Board.
- The 90-day ceiling was added in the final Rules and applies from 13 May 2027.
Who this is for: Customer support and grievance officers, Data Protection Officers, Consent Managers, Product and CX leaders, Startup founders
What is the DPDP 90-day grievance rule?
Section 8(10) of the DPDP Act requires every Data Fiduciary to establish an effective mechanism to redress the grievances of Data Principals, and section 13 gives Data Principals the right to a readily available means of grievance redressal from the Data Fiduciary or Consent Manager. Section 13(2) leaves the response period to be prescribed.
Rule 14(3) of the DPDP Rules, 2025 prescribes it. Every Data Fiduciary and Consent Manager must:
- prominently publish on its website or app, or both, the period within which it will respond to grievances of Data Principals under its grievance redressal system;
- keep that period to "a reasonable period not exceeding ninety days"; and
- implement appropriate technical and organisational measures to ensure the system is effective in responding within that period.
So the rule has three parts: a ceiling, a publication duty and an effectiveness duty. Publishing "90 days" while routinely taking longer fails the effectiveness test. Publishing nothing fails the publication test.
The Rules do not define "grievance" narrowly. In practice, any complaint by a Data Principal about the processing of her personal data, including a failed or ignored rights request, should be treated as a grievance.
The explicit 90-day ceiling is one of the changes made in the final Rules notified on 13 November 2025. Rule 14 comes into force on 13 May 2027.
Why the grievance mechanism matters for Board complaints
Section 13(3) of the Act says a Data Principal shall exhaust the opportunity of redressing her grievance with the Data Fiduciary or Consent Manager before approaching the Data Protection Board. That makes your grievance system the gatekeeper for most individual complaints.
The practical consequences:
- A good system absorbs complaints. Most issues, such as an unprocessed erasure request or an unwanted marketing message, can be fixed internally within days.
- A slow or missing system escalates them. If no response arrives within the published period, the Data Principal can go to the Board, and the complaint arrives with a documented failure attached.
- The record becomes evidence. In a Board inquiry, which Rule 19(9) requires to be completed within six months (extendable by up to three months at a time), your grievance logs will show what happened and when.
| Stage | Who | Time limit |
|---|---|---|
| Grievance to fiduciary or Consent Manager | Data Principal | — |
| Response | Fiduciary or Consent Manager | Published period, max 90 days (Rule 14(3)) |
| Complaint to Board | Data Principal | After exhausting internal route (s.13(3)) |
| Board inquiry | Board | 6 months, extendable by up to 3 months at a time (Rule 19(9)) |
| Appeal | Aggrieved party | To TDSAT within 60 days (s.29) |
See how a Board inquiry works for the next stage.
How should you choose your published response period?
Ninety days is a legal ceiling, but it is rarely the right published number. Choosing the period is a business decision with compliance consequences.
Factors to consider
- Volume. Estimate monthly grievances from support data. Consumer apps with large user bases will see far more than B2B SaaS.
- Complexity. Grievances that require fan-out to many systems or processors take longer.
- Sector norms. Regulated sectors such as banking, insurance and telecom often have their own grievance timelines under sector regulations. Where those are shorter, align to them; check the latest circulars.
- Trust signal. A shorter, reliably met period is a competitive differentiator.
A tiered approach
Many organisations publish one maximum period but run internal targets:
| Grievance type | Internal target | Published maximum |
|---|---|---|
| Marketing or consent withdrawal not honoured | Short (days) | Within published period |
| Correction or erasure not done | Moderate | Within published period |
| Complex access or multi-system issues | Longer | Within published period |
Whatever you publish must be one clear number that a Data Principal can rely on. Avoid vague phrases such as "as soon as possible"; Rule 14(3) requires a period.
Record the reasoning behind your choice. If the Board ever asks why you published 60 days rather than 30, a capacity analysis is a far better answer than none.
Building a grievance system that meets the deadline
The effectiveness duty in Rule 14(3) is about "appropriate technical and organisational measures". In engineering terms, that means a ticketing workflow with deadlines enforced by software, not memory.
Technical measures
- Single intake. Route the privacy centre, web form, email and support chat into one queue tagged as DPDP grievances.
- Timestamps and SLA timers. Start the clock on receipt; set alerts at, for example, 50% and 80% of the published period.
- Identity verification using the identifiers published under Rule 14(1)(b).
- Fan-out automation to the systems and processors that must act.
- Audit trail. Keep the full history of each grievance, including internal notes and the final response. Rule 6(1)(e) and Rule 8(3) one-year retention give a floor.
Organisational measures
- A named grievance owner, often the DPO or the Rule 9 privacy contact.
- Escalation rules for breaches of internal targets.
- Training for support staff to recognise privacy grievances in ordinary tickets.
- Monthly reporting on volumes, ageing and root causes.
Response content
Each response should state the outcome, any action taken, and, under Rule 9, the business contact information of the DPO or privacy contact. If the grievance is rejected, explain why. A clear response reduces the chance of a Board complaint and shows good faith if one follows.
Consent Managers, processors and shared responsibility
Rule 14(3) applies to Consent Managers as well as Data Fiduciaries. Since Rule 4 came into force on 13 November 2026, any registered Consent Manager needs its own published grievance period and system, separate from the fiduciaries on its platform.
This creates routing questions:
- A Data Principal may complain to the Consent Manager about a fiduciary's processing. The Consent Manager should resolve what is within its control (for example, consent records) and route the rest.
- A fiduciary receiving a grievance about a consent recorded on a Consent Manager platform will need the Consent Manager's records to respond.
Agree these handoffs in onboarding agreements, with time allowances that still fit within each party's published period.
Data Processors have no direct grievance duty under the Rules, but section 8(1) keeps the fiduciary responsible for their processing. Contracts with processors should require prompt cooperation on grievances, such as locating records or confirming erasure, within a defined number of days.
Intermediaries regulated under the IT Rules already run grievance officer mechanisms with their own timelines. They can reuse that infrastructure, but DPDP grievances should be tagged and tracked against the published DPDP period, because the two regimes have separate deadlines and escalation routes.
Common mistakes and preparation before May 2027
Mistakes
- Publishing 90 days by default. It is legal, but it signals minimum effort and leaves no buffer if a complex case runs long.
- Not publishing anything. Rule 14(3) requires the period to be prominently published.
- Treating grievances as general tickets. Without tagging, privacy complaints get lost among delivery or billing issues.
- Closing without responding. A ticket marked resolved without a reply to the Data Principal is not a response.
- No Rule 9 contact. Responses must carry the DPO or privacy contact details.
Preparation
- Audit current support data to estimate grievance volumes.
- Decide and document your published period.
- Configure the ticketing tool with a DPDP grievance category and SLA timers.
- Publish the period on your website and app, near the rights request channel.
- Update your Rule 3 notice so it explains how to complain to the Board.
- Agree processor and Consent Manager cooperation terms.
- Run a mock grievance end-to-end before 13 May 2027.
For the wider rights framework, see Data Principal rights under Rule 14.
Further reading on suhasbhairav.com
- AI AgentsAI Agents for Complaint Resolution in Customer Service
- BlogVoice Agent Compliance: Consent, Audit Trails, Escalation
- BlogGDPR for AI Agents: Consent, Minimization, Auditability
- AI Use CasesAI Use Case: Website Complaints and Support Routing
- AI SkillsAGENTS.md Template for Privacy and Data Governance Agents
Before 13 May 2027
Compliance checklist
Set a response period of 90 days or less
Choose a period based on volume and complexity, and document why.
Rule 14(3)
Publish the period prominently
Display it on the website and app next to the rights request channel.
Rule 14(3)
Create a DPDP grievance queue
Tag privacy grievances separately from general support and start a timer on receipt.
Section 8(10)
Configure escalation alerts
Alert owners before the published deadline is breached and escalate ageing tickets.
Rule 14(3)
Include the privacy contact in responses
Add the DPO or privacy contact details to every response.
Rule 9
Bind processors to cooperate
Add contract clauses requiring timely help with grievance investigations.
Section 8(1)
Retain grievance records
Keep complete grievance histories for at least one year as evidence for any Board inquiry.
Rule 8(3)
Key dates
Final DPDP Rules published with the 90-day grievance ceiling
Consent Managers can register; they will also need grievance systems
Rule 14(3) grievance response obligation in force
Answers
Frequently asked questions
How long does a company have to resolve a DPDP grievance?
How long does a company have to resolve a DPDP grievance?
A Data Fiduciary or Consent Manager must respond within the period it publishes, which under Rule 14(3) of the DPDP Rules, 2025 cannot exceed 90 days. It must also implement technical and organisational measures to make sure it actually meets that period. The rule applies from 13 May 2027.
Can a company take the full 90 days?
Can a company take the full 90 days?
Yes, if it publishes 90 days as its period. The Rules set 90 days as the maximum. However, a company can publish a shorter period, and many will, because a faster response reduces escalations to the Data Protection Board and builds user trust.
What if the company does not respond within the published period?
What if the company does not respond within the published period?
The Data Principal can then approach the Data Protection Board, since the internal route has been exhausted under section 13(3). Failure to maintain an effective grievance mechanism can also lead to a Board inquiry and penalties under the Schedule to the DPDP Act.
Do Consent Managers need a grievance mechanism?
Do Consent Managers need a grievance mechanism?
Yes. Rule 14(3) applies to every Data Fiduciary and every Consent Manager. A registered Consent Manager must publish its own response period, not exceeding 90 days, and build systems to meet it, separate from the fiduciaries onboarded on its platform.
Where must the grievance response period be published?
Where must the grievance response period be published?
Prominently on the Data Fiduciary's or Consent Manager's website or app, or both. Placing it alongside the rights request channel and the Rule 9 privacy contact makes it easy to find and supports the 'prominently publish' requirement.
Was the 90-day limit in the draft DPDP Rules?
Was the 90-day limit in the draft DPDP Rules?
The explicit ceiling of 90 days was specified in the final DPDP Rules notified on 13 November 2025 as G.S.R. 846(E). Organisations that drafted processes against the January 2025 draft should update them to reflect the final Rule 14(3) text.
Legal references and sources
- Digital Personal Data Protection Rules, 2025 — Rule 14(3) (official text)
- Digital Personal Data Protection Act, 2023 — Sections 8(10) and 13 (official text)
- Digital Personal Data Protection Rules, 2025 — Rule 9 (official text)
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
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.
Related guides
- DPDP Rules 2025Data Principal Rights Under DPDP Rule 14The 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.
- DPDP Rules 2025How a Data Protection Board Inquiry Works (Rules 19–20)A step-by-step guide to Data Protection Board inquiries: what triggers them, the six-month deadline in Rule 19(9), digital hearings under Rule 20, outcomes and how to prepare.
- DPDP Rules 2025DPDP Rule 9: Publishing Your DPO or Privacy ContactRule 9 requires every Data Fiduciary to publish the business contact of its DPO, or of a person who can answer privacy questions, on its website or app and in every rights response.
- DPDP Rules 2025DPDP Consent Managers Explained: What Changed on 13 Nov 2026Rule 4 of the DPDP Rules came into force on 13 November 2026. Here is what a Consent Manager is, what is live now, and what still waits for 13 May 2027.
- DPDP Rules 2025Data Protection Board of India: Appointment, Pay and ProcedureHow the Data Protection Board of India is appointed, paid and run under Rules 17 to 21 of the DPDP Rules, 2025, which have been in force since 13 November 2025.
- DPDP Rules 2025Algorithmic Due Diligence for Significant Data FiduciariesRule 13(3) requires Significant Data Fiduciaries to verify that technical measures, including algorithmic software, are not likely to pose a risk to Data Principals' rights. Here is what that means in practice.