DPDP Rules 2025Updated 22 November 202610 min read

How 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.

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

Triggers
Intimation, complaint, reference or direction under section 27
Completion deadline
6 months from receipt (Rule 19(9))
Extension
Up to 3 months at a time, reasons in writing
Mode
Digital office, techno-legal measures (Rule 20)
Maximum penalty
₹250 crore per instance (security safeguards)
Appeal
TDSAT within 60 days (section 29)
Rules 19–20 in force
13 November 2025

Quick answer

A Data Protection Board inquiry starts with a breach intimation, a Data Principal complaint, a government reference or a court direction under section 27 of the DPDP Act. Rule 19(9) requires the Board to finish the inquiry within six months of receipt, extendable in writing by up to three months at a time, and Rule 20 lets it run proceedings digitally without physical presence.

  • Inquiries are triggered by a breach intimation, a complaint, a Central or State Government reference, or a court direction under section 27.
  • Rule 19(9) sets a six-month completion deadline, extendable for written reasons by up to three months at a time.
  • Rule 20 makes the Board a digital office that can hear matters without anyone being physically present, while keeping its summons powers.
  • Outcomes range from closure and voluntary undertakings to remedial directions and penalties of up to ₹250 crore per instance.
  • Orders can be appealed to TDSAT within 60 days under section 29 of the Act.

Who this is for: Data Fiduciaries and Significant Data Fiduciaries, Consent Managers, General counsel and litigation teams, CISOs and incident response leads, Data Protection Officers

What starts a Data Protection Board inquiry?

Rule 19(9) refers to four routes by which a matter reaches the Board under section 27 of the DPDP Act:

TriggerWho initiatesTypical scenario
IntimationThe Data Fiduciary itselfA personal data breach reported under section 8(6) and Rule 7
ComplaintA Data PrincipalConsent not honoured, rights request ignored, breach affecting her
ReferenceCentral Government or a State GovernmentA matter the government refers to the Board
DirectionA courtA court directs the Board to look into a matter

Two points matter most in practice.

Breach intimation is self-reporting. Because Rule 7 has no materiality threshold, every personal data breach goes to the Board. Each intimation is a potential inquiry, so the quality of your first report sets the tone. See breach notification.

Complaints come after your grievance process. Section 13 requires a Data Principal to exhaust the fiduciary's grievance redressal before approaching the Board. If your system responds well within the published period — capped at 90 days by Rule 14(3) — many disputes end there. See the 90-day grievance rule and how Data Principals file a complaint.

Consent Managers face an additional track: Rule 4(4) and 4(5) let the Board direct a non-adhering Consent Manager, and suspend or cancel its registration, after giving it an opportunity to be heard.

What are the stages of a Board inquiry?

The Act and Rules do not prescribe a detailed procedural code, but the structure of sections 27 to 33 and Rules 19 and 20 points to a predictable sequence.

  1. Receipt. The Board receives the intimation, complaint, reference or direction. The six-month clock in Rule 19(9) runs from this date.
  2. Initial assessment. The Board considers whether there are sufficient grounds to proceed. The Act allows it to close proceedings where grounds are insufficient.
  3. Urgent measures. In a breach, the Board may direct urgent remedial or mitigation steps. If a meeting is not feasible, the Chairperson can take emergent action under Rule 19(6), reporting to Members within seven days for ratification.
  4. Inquiry. The Board gathers information, may summon and examine persons on oath, and calls for documents. Hearings can be virtual under Rule 20.
  5. Alternative resolution. The Act also allows the Board to steer parties towards mediation where it considers that appropriate.
  6. Voluntary undertaking. The fiduciary may offer a voluntary undertaking under section 32 — for example, to take or refrain from specified actions. Once accepted, it bars proceedings on the matter covered, but breaching it attracts a penalty up to the amount for the underlying breach.
  7. Decision. The Board decides, by majority under Rule 19(4), whether a significant breach occurred and what penalty, if any, to impose under section 33.
  8. Authentication and communication. The order is authenticated under Rule 19(8).
  9. Appeal. Any aggrieved person may appeal to TDSAT within 60 days. See appealing to TDSAT.

The six-month deadline in Rule 19(9)

Rule 19(9) reads: "The inquiry by the Board shall be completed within a period of six months from the date of receipt of the intimation, complaint, reference or direction under section 27 of the Act, unless such period is extended by it, for reasons to be recorded in writing, for a further period not exceeding three months at a time."

What this means:

  • The clock starts on receipt, not when the Board decides to open a formal inquiry. A breach intimation filed on day one starts it.
  • Extensions are open-ended in number but each is capped at three months and must be justified in writing. There is no stated overall maximum.
  • Reasons are on record. If you later appeal, the written reasons for any extension form part of the record.

For a Data Fiduciary, the deadline cuts both ways. It brings certainty that a matter will not sit open for years, but it also means the Board will move quickly and will expect you to respond promptly to requests. A team that needs weeks to pull access logs, processor contracts or consent records will struggle.

Engineering implications:

  • Keep logs searchable for at least the one-year minimum required by Rule 6(1)(e) and Rule 8(3). See one-year log retention.
  • Maintain an incident timeline with UTC timestamps from detection onward.
  • Version your privacy notices and consent text so you can show what a user saw on a given date.

How digital hearings work under Rule 20

Rule 20 says the Board "shall function as a digital office" and, without prejudice to its power to summon and enforce attendance and examine on oath, "may adopt techno-legal measures to conduct proceedings in a manner that does not require physical presence of any individual."

Practical expectations:

  • Electronic filing. Submissions, evidence and replies will be exchanged digitally. Prepare documents as searchable PDFs with consistent naming, page numbers and an index.
  • Virtual hearings. Witnesses — your CISO, DPO or engineering lead — may be examined over video. Brief them to speak precisely about controls, dates and logs.
  • Authenticity. Digital proceedings make provenance important. Export logs with hashes, keep chain-of-custody notes for forensic images, and avoid screenshots as primary evidence.
  • Summons still exist. Digital-first does not mean optional. The Board can summon and examine on oath, and failing to attend or produce documents will count against you.

Techno-legal measures are defined in Rule 2(1)(b) by reference to Rules 20 and 22, so the Appellate Tribunal operates on the same digital footing. Evidence you prepare for the Board should be reusable on appeal without reformatting.

Tip: designate a single "regulatory evidence store" — an access-controlled repository holding incident reports, notices, contracts, DPIAs and audit reports — so that the same material can be produced quickly to the Board, the Appellate Tribunal or an auditor.

What can the Board decide at the end of an inquiry?

Outcomes range from closure to a significant penalty.

OutcomeBasis
Close proceedings for insufficient groundsAct, Board procedure
Accept a voluntary undertakingSection 32
Direct remedial or mitigation measuresSection 27
Impose a monetary penaltySection 33 and Schedule
Refer for blocking after repeat penaltiesSection 37

When imposing a penalty, the Board must consider factors including the nature, gravity and duration of the breach; the type and nature of the personal data affected; repetitive nature; whether the person realised a gain or avoided a loss; mitigation measures taken and their timeliness and effectiveness; whether the penalty is proportionate and effective; and the likely impact on the person.

Maximum penalties per instance under the Schedule:

  • Failure to take reasonable security safeguards — up to ₹250 crore.
  • Failure to notify a breach to the Board or affected Data Principals — up to ₹200 crore.
  • Breach of children's data obligations — up to ₹200 crore.
  • Breach of Significant Data Fiduciary obligations — up to ₹150 crore.
  • Breach of any other provision — up to ₹50 crore.

Penalties are paid into the Consolidated Fund of India. The Board's enforcement of fiduciary obligations becomes relevant once they commence on 13 May 2027. For the full schedule, see DPDP penalties explained.

How to prepare your organisation for a Board inquiry

Most of the work happens before any inquiry starts. The factors in section 33 reward timely and effective mitigation, so your preparation directly influences outcomes.

Before an incident

  • Map personal data and processors so you can say quickly what was affected. See data mapping.
  • Implement the Rule 6 minimum safeguards and document them. See security safeguards.
  • Write a breach runbook covering the "without delay" intimation and the 72-hour report. See breach response playbook.

When a matter reaches the Board

  • Open a privileged matter file and appoint a single coordinator.
  • Preserve evidence immediately: freeze log rotation for relevant systems and snapshot affected stores.
  • Build a factual chronology before drafting legal arguments.
  • Consider early whether a voluntary undertaking is appropriate; it can end proceedings on the matter covered.

After the decision

  • Diary the 60-day appeal window under section 29 from the date you receive the order.
  • Track any remedial directions to completion and keep evidence of compliance.

Involve external counsel early for any inquiry that could lead to a penalty; procedural choices made in the first weeks are hard to undo.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Appoint an inquiry coordinator

    Name one person who receives Board communications, tracks deadlines and coordinates legal and engineering responses.

    Rule 19(9)

  2. Create a regulatory evidence store

    Keep notices, consent records, processor contracts, DPIAs and incident reports in one access-controlled, exportable repository.

    Rule 20

  3. Retain and index logs

    Keep access and processing logs for at least one year and make them searchable by user, system and time.

    Rule 6(1)(e), Rule 8(3)

  4. Rehearse breach intimation

    Practise the immediate description and the 72-hour detailed report so the Board's first view of you is accurate and timely.

    Rule 7(2)

  5. Prepare witnesses for virtual hearings

    Brief engineering and security leads to explain controls, timelines and logs clearly over video.

    Rule 20

  6. Evaluate a voluntary undertaking early

    Assess with counsel whether offering an undertaking could resolve the matter and what commitments are realistic.

    Section 32

  7. Diary the appeal window

    Record the date of receipt of any Board order and calendar the 60-day deadline to appeal to TDSAT.

    Section 29

Key dates

  1. Rules 19 and 20 on Board procedure and digital office come into force

  2. Core fiduciary obligations, breach intimation and appeal Rule 22 come into force

Answers

Frequently asked questions

How long does a Data Protection Board inquiry take?

Rule 19(9) requires the Board to complete an inquiry within six months from receipt of the intimation, complaint, reference or direction. It may extend that period, for reasons recorded in writing, by up to three months at a time. There is no stated cap on the number of extensions, so complex matters could run longer.

Does every data breach lead to a Board inquiry?

Every personal data breach must be intimated to the Board under Rule 7, because there is no materiality threshold. An intimation is one of the triggers for an inquiry, but the Board can assess whether there are sufficient grounds to proceed. A complete, prompt report with clear mitigation improves the chance of a quick resolution.

Can a Data Principal go straight to the Board with a complaint?

No. Section 13 of the DPDP Act requires a Data Principal to exhaust the Data Fiduciary's or Consent Manager's grievance redressal mechanism before approaching the Board. The fiduciary must respond within its published period, which Rule 14(3) caps at 90 days, after which she can take the complaint to the Board.

Will Board hearings be held online?

Very likely. Rule 20 requires the Board to function as a digital office and allows techno-legal measures so proceedings need not require anyone's physical presence. The Board keeps its power to summon and enforce attendance and to examine a person on oath, so in-person appearance can still be ordered when needed.

What is a voluntary undertaking under the DPDP Act?

Under section 32, a person may offer the Board a voluntary undertaking to take, or refrain from, specified actions during proceedings. If the Board accepts it, proceedings on the matter covered are barred. Breaching an accepted undertaking can attract a penalty up to the amount applicable for the underlying breach.

Can I appeal a Data Protection Board decision?

Yes. Any person aggrieved by a Board order or direction can appeal to the Appellate Tribunal, which is TDSAT, within 60 days under section 29 of the Act. Rule 22 requires the appeal to be filed in digital form with a fee equal to that for TRAI Act appeals, payable digitally.

What factors decide the size of a DPDP penalty?

The Board must consider the nature, gravity and duration of the breach, the type of personal data affected, whether it is repetitive, any gain made or loss avoided, the timeliness and effectiveness of mitigation, proportionality and effectiveness of the penalty, and its likely impact on the person. Maximums are set per instance in the Schedule.

Legal references and sources

  • Digital Personal Data Protection Rules, 2025 — Rule 19(9) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 20 (official text)
  • Digital Personal Data Protection Act, 2023 — Sections 27, 32, 33 and 29 (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.