DPDP Act 2023Updated 22 November 20268 min read

How to File a Complaint With the Data Protection Board

A step-by-step guide to complaining to the Data Protection Board of India: exhaust grievance redressal first, file digitally, and know the six-month inquiry timeline.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Pre-condition
Exhaust grievance redressal (s.13(3))
Fiduciary response ceiling
90 days (Rule 14(3))
Board format
Digital office (Rule 20)
Inquiry deadline
6 months + up to 3-month extensions (Rule 19(9))
Appeal
TDSAT within 60 days (s.29)
Frivolous complaint penalty
Up to ₹10,000

Quick answer

To file a complaint with the Data Protection Board of India, first raise a grievance with the Data Fiduciary or Consent Manager and wait for its response, as section 13(3) requires. If unresolved within its published period (at most 90 days under Rule 14(3)), file digitally with the Board. The inquiry should finish within six months, extendable by up to three months at a time.

  • You must exhaust the Data Fiduciary's grievance redressal before complaining to the Board (section 13(3)).
  • Fiduciaries must publish a grievance response period of no more than 90 days (Rule 14(3)).
  • The Board functions as a digital office; proceedings need not require physical presence (Rule 20).
  • Board inquiries must finish within six months, extendable by up to three months at a time (Rule 19(9)).
  • Penalties go to the Consolidated Fund of India; the DPDP Act does not award compensation to complainants.
  • False or frivolous complaints can attract a penalty of up to ₹10,000 under section 15.

Who this is for: Individuals and consumers, Parents of children using online services, Consumer advocates, Grievance and DPO teams preparing for complaints

How do you file a complaint with the Data Protection Board?

The Data Protection Board of India is the adjudicating body under the DPDP Act. It can inquire into personal data breaches and complaints by Data Principals, impose penalties and give directions. But it is not the first stop.

Section 13(3) requires a Data Principal to exhaust the grievance redressal opportunity with the Data Fiduciary or Consent Manager before approaching the Board. The process is:

  1. Raise a grievance with the Data Fiduciary or Consent Manager through the means it publishes (Rule 14(1)).
  2. Wait for the response within the period it publishes, which cannot exceed 90 days (Rule 14(3)).
  3. If unresolved, file a complaint with the Board digitally. Rule 20 makes the Board a digital office that may conduct proceedings without anyone's physical presence.
  4. Participate in the inquiry, which the Board must complete within six months of receiving the complaint, extendable for reasons in writing by up to three months at a time (Rule 19(9)).
  5. Appeal, if aggrieved by the Board's order, to the Appellate Tribunal (TDSAT) within 60 days (section 29), in digital form (Rule 22).

The fiduciary's notice must tell you how to complain to the Board (Rule 3(c)(iii)), and the Board's own website should set out the filing channel. Check MeitY's DPDP page for the current link.

What can you complain about?

The Board inquires into breaches of the Act and Rules by Data Fiduciaries, Consent Managers and others with obligations under the Act. Common complaint types will include:

IssueRelevant provision
Processing without valid consent or a legitimate useSections 4, 6, 7
Notice missing, unclear or not standaloneSection 5; Rule 3
Withdrawal of consent not honoured, or harder than giving itSection 6; Rule 3(c)(i)
Access, correction or erasure request ignoredSections 11, 12; Rule 14
No grievance response within the published periodSection 13; Rule 14(3)
No contact person publishedRule 9
Data breach not notified to youSection 8(6); Rule 7(1)
Children's data processed without verifiable parental consent, or targeted ads to a childSection 9; Rule 10
Consent Manager failing its obligationsRule 4; First Schedule Part B

Timing matters. Most of these obligations — including Rules 3, 6 to 16 and 22 — apply from 13 May 2027. The Board's own inquiry powers follow the same phasing: section 27(1)(d) came into force on 13 November 2026 with the Consent Manager rules, but the rest of section 27, and sections 28 onwards, apply from 13 May 2027. Before then, most fiduciary duties are not yet enforceable through the Board. Earlier issues may fall under section 43A of the IT Act, consumer law or sectoral regulators.

Prepare your evidence

Complaints succeed on clear facts. Before filing, gather:

  • Your identity and identifiers used with the fiduciary — username, registered email or mobile, customer ID (Rule 14(5) lists the kinds of identifiers).
  • The grievance you raised: date, channel, ticket or reference number, and a copy of what you sent.
  • The fiduciary's response, or evidence that none came within its published period.
  • The published grievance period, as a screenshot of its website or app.
  • The underlying facts: screenshots of notices, consent screens, marketing messages after withdrawal, breach emails, or account settings.
  • Dates for everything. A simple timeline table is easier for the Board to follow than a long narrative.
  • What you want: stop processing, erase data, correct records, or for the Board to direct compliance.

Keep it factual. Section 15(d) makes it a duty not to register a false or frivolous complaint, and section 15(e) requires verifiably authentic information in correction and erasure matters. Breach of a Data Principal duty can attract a penalty of up to ₹10,000.

Where a child is affected, the parent or lawful guardian files as the Data Principal on the child's behalf.

What the Board does with your complaint

After receiving a complaint, the Board considers whether there are sufficient grounds for inquiry. It can close a complaint where grounds are insufficient, and record reasons. If it proceeds, the inquiry follows principles of natural justice and is conducted largely digitally.

Possible outcomes include:

  • Directions to the fiduciary — for example, to correct a process or take urgent measures.
  • Mediation, where the Board considers that the complaint may be resolved by mediation and the parties agree.
  • Voluntary undertaking by the fiduciary under section 32, which the Board may accept; it bars proceedings on the same matter unless the undertaking is breached.
  • Penalties under the Schedule, up to ₹250 crore per instance for security failures, after considering factors such as nature, gravity, duration, type of data, repetition, gains made or losses avoided, mitigation and proportionality.

Penalties go to the Consolidated Fund of India, not to the complainant. The DPDP Act does not provide compensation for individuals; claims for damages, if any, lie under other laws.

Rule 19(9) gives the Board six months from receipt to complete the inquiry, extendable by up to three months at a time with written reasons. See the Board inquiry process.

For companies: avoid complaints reaching the Board

Every complaint the Board receives is one your grievance system did not resolve. Engineering and operations teams can reduce escalations:

  1. Publish one obvious channel for rights and grievances, plus your contact person's business details (Rules 9 and 14(1)).
  2. Publish a realistic period well under 90 days, and meet it with SLA tracking and escalation alerts.
  3. Acknowledge immediately with a ticket number and the expected response date.
  4. Answer the actual request — access summaries, completed erasure confirmations — not boilerplate.
  5. Include the contact person's details in every response, as Rule 9 requires.
  6. Log the lifecycle: received, verified, decided, responded. Keep it as evidence; Rule 8(3) already requires processing logs for a minimum of one year.
  7. Tell users how to escalate. Rule 3(c)(iii) requires your notice to describe how to complain to the Board. Hiding it only shifts the complaint elsewhere.
  8. Review complaint trends monthly and fix root causes in product, not just in support macros.

See grievance redressal within 90 days for system design.

If you disagree with the Board's decision

Any person aggrieved by an order or direction of the Board may appeal to the Appellate Tribunal, which is TDSAT, within 60 days of receiving the order (section 29). Rule 22 sets the procedure:

  • The appeal is filed in digital form, as the Tribunal decides.
  • The fee is the same as for appeals under the TRAI Act, 1997, unless the Tribunal's Chairperson reduces or waives it.
  • Payment is digital, through UPI or another RBI-authorised payment system.
  • The Tribunal is not bound by the Code of Civil Procedure, is guided by natural justice, and functions as a digital office.

This applies equally to individuals and companies. Details of TDSAT's filing process are on its website. See appeal to TDSAT.

Further reading on suhasbhairav.com

Key dates

  1. Board provisions (Rules 17–21) in force

  2. Consent Manager registration (Rule 4) in force

  3. Fiduciary obligations, Rule 14 grievance period and Rule 22 appeals in force

Answers

Frequently asked questions

How do I complain to the Data Protection Board of India?

First raise a grievance with the company through its published channel and wait for its response, which must come within its published period of at most 90 days. If unresolved, file a complaint with the Board digitally, attaching your grievance, the response and supporting evidence. The Board then decides whether to inquire.

Do I have to complain to the company first?

Yes. Section 13(3) of the DPDP Act requires a Data Principal to exhaust the grievance redressal opportunity with the Data Fiduciary or Consent Manager before approaching the Board. Keep the ticket number, dates and any response as evidence for your complaint.

How long does the Data Protection Board take to decide?

Rule 19(9) requires the Board to complete an inquiry within six months from receiving the complaint. It may extend that period for reasons recorded in writing, by up to three months at a time. Appeals to TDSAT must be filed within 60 days of the Board's order.

Can I get compensation from the Data Protection Board?

No. The DPDP Act empowers the Board to impose penalties and issue directions, and penalties go to the Consolidated Fund of India. It does not award compensation to individuals. Remedies such as damages may be available under other laws; consult a lawyer for those.

Is there a fee to complain to the Data Protection Board?

The DPDP Rules do not set a fee for complaints to the Board; Rule 22 sets a fee only for appeals to TDSAT, matching TRAI Act appeals unless reduced or waived. Check the Board's website for its current filing requirements before you submit.

Can I complain about a data breach that affected me?

Yes. If a company fails to notify you of a personal data breach as Rule 7(1) requires, or failed to protect your data, you can raise it, first through the company's grievance process and then with the Board. Breach notices to individuals apply from 13 May 2027.

What happens if my complaint is found frivolous?

Section 15(d) makes it a duty not to register false or frivolous complaints, and breach can attract a penalty of up to ₹10,000 imposed by the Board after inquiry. Genuine complaints carry no such risk, even if the Board ultimately finds no breach.

Legal references and sources

  • Digital Personal Data Protection Act, 2023 — Sections 13, 27, 28, 29 (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 14(3) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rules 19(9) and 20 (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 22 (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

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.