[Analysis] Data Protection Board of India – Composition | Powers | Inquiry Procedure | Penalties | Appeal

  • Blog|Company Law|
  • 22 Min Read

The Data Protection Board of India: how it is constituted, the five actions it may take under section 27, the six-month inquiry timeline, the penalty Schedule and the appeal to the Appellate Tribunal.

  • By Taxmann
  • |
  • Last Updated on 16 November, 2026
The Data Protection Board of India was established by Notification G.S.R. 844(E), dated 13 November 2025, with its head office in the National Capital Region. It is not a regulator in the conventional sense: it issues no regulations and sets no standards, and the only licence it grants is the registration of Consent Managers. Its function is adjudicatory. Taxmann’s Digital Personal Data Protection sets out the enforcement architecture in the sequence an actual enforcement action follows, from the five triggers under section 27, through the six-month inquiry under Rule 19(9), to the seven penalty categories in the Schedule and the sixty-day appeal to the Appellate Tribunal. The Board begins deciding cases when sections 27 and 28 commence on 13 May 2027.

Table of Contents

  1. What is the Data Protection Board of India?
  2. When was the Board established, and when does it start deciding cases?
  3. How is the Board constituted, and who can be appointed to it?
  4. What does it mean that the Board is a digital office?
  5. What can the Board do, and what sets it in motion?
  6. How does a Board inquiry run, and how long can it take?
  7. What powers does the Board have, and where do they stop?
  8. How is the amount of a penalty decided?
  9. Can a matter be closed without a penalty order?
  10. How is an appeal filed against a Board order?
  11. What powers does the Central Government retain?
  12. How should an organisation prepare for a Board inquiry?
  13. Quick answers

1. What is the Data Protection Board of India?

Section 18(1) provides that the Central Government shall establish, for the purposes of the Act, a Board to be called the Data Protection Board of India. Section 18(2) provides that the Board shall be a body corporate, having perpetual succession and a common seal, with power to acquire, hold and dispose of property, to contract, and to sue or be sued in its own name (para 14.1).

What the Board is not is as important as what it is. The book makes the point directly: the Board is not a regulatory body in the conventional sense of the term. It does not issue regulations, set standards or grant licences, other than the registration of Consent Managers. Its primary function is adjudicatory (para 1.5.1).

That distinction matters in practice. An organisation looking for the Board to publish codes of practice, sectoral guidance or certification schemes, as data protection authorities in other jurisdictions do, is looking for something the Act does not ask the Board to produce. What the Board will produce is decisions: orders closing proceedings, binding directions, interim orders, penalty orders and accepted voluntary undertakings.

The Board also sits at the centre of several obligations that have nothing to do with adjudication. It is the registering authority for Consent Managers under Rule 4. It is the recipient of breach intimations under Rule 7(2). It is the body to which Significant Data Fiduciaries must furnish Data Protection Impact Assessment and audit reports under Rule 13(2). And it is the body that may issue directions under section 27(2) and accept voluntary undertakings under section 32. In practice, the Board will be the primary institutional interface between Data Fiduciaries and the regulatory framework (para 1.8).

Above the Board sits a second tier and a third. The Act establishes a three-tier regulatory architecture: the Board as the primary adjudicatory and enforcement body, the Telecom Disputes Settlement and Appellate Tribunal as the appellate authority, and the Central Government as the rule-making and notification authority with certain residual powers (para 1.5).

2. When was the Board established, and when does it start deciding cases?

These are two different dates, and conflating them is a common source of confusion.

By Notification No. G.S.R. 844(E), dated 13 November 2025, the Central Government established the Data Protection Board of India under section 18(1) and (3), with effect from the date of publication. The head office of the Board is in the National Capital Region of India (para 1.8).

The Board exists. The rules governing its composition, appointment process, meeting procedure, salary structure and staffing are already in force under Rules 17 to 21 and the Fifth and Sixth Schedules. But the Board will begin adjudicatory functions only once the substantive provisions of sections 27 and 28 come into force on 13 May 2027 (para 1.8).

The reason is the phased commencement. Section 1(2) authorises the Central Government to appoint different dates for different provisions, and by Notification No. G.S.R. 843(E), dated 13 November 2025, it prescribed a three-phase schedule (para 1.6):

Phase Effective from What comes into force
Phase 1 13 November 2025 Section 1(2), section 2 (definitions), sections 18 to 26 (establishment, composition and governance of the Board), and sections 35, 38, 39, 40, 41, 42 and 43. On the Rules side, Rules 1, 2 and 17 to 21
Phase 2 13 November 2026 Consent Manager registration under section 6(9), the Board’s jurisdiction over breaches of Consent Manager registration conditions under section 27(1)(d), and Rule 4
Phase 3 13 May 2027 Sections 3 to 17, section 27 except clause (d) of sub-section (1), sections 28 to 34, sections 36 and 37, and section 44(2). On the Rules side, Rules 3, 5 to 16, 22 and 23

So the sequence is this. The Board was constituted in November 2025. Its jurisdiction over Consent Manager registration breaches arrived on 13 November 2026. Its general adjudicatory jurisdiction, the inquiry procedure and the penalty power arrive in May 2027.

The practical consequence the book draws out is a planning one. While the Board will not adjudicate complaints or impose penalties until May 2027, the establishment of the Board and the rule-making framework are already operative, and organisations that begin their compliance programmes only in 2027 will face a compressed and high-risk implementation window. The book’s illustration is pointed: an organisation that forms its DPDP steering committee only in January 2027 would have little more than four months to complete notice redesign, consent mechanism rebuild and security safeguard remediation before the enforcement date, work that better-prepared peers will have spread across the full eighteen-month window (para 1.9.2). The commencement notification and the Rules are on Taxmann.com | Research under Indian Acts and Rules.

3. How is the Board constituted, and who can be appointed to it?

Section 19(1) provides that the Board shall consist of a Chairperson and such number of other Members as the Central Government may notify. Section 19(3) specifies the qualifications: the Chairperson and other Members shall be persons of ability, integrity and standing who possess special knowledge or practical experience in the fields of data governance, administration or implementation of laws related to social or consumer protection, dispute resolution, information and communication technology, digital economy, law, regulation or techno-regulation, or in any other field which in the opinion of the Central Government may be useful to the Board. At least one among them shall be an expert in the field of law (para 14.1).

Rule 17 prescribes the appointment process through Search-cum-Selection Committees (para 14.1):

Appointment Committee chaired by Other members
Chairperson Cabinet Secretary Secretary, Department of Legal Affairs; Secretary, Ministry of Electronics and Information Technology; two experts of repute
Members other than the Chairperson Secretary, Ministry of Electronics and Information Technology Secretary, Department of Legal Affairs; two experts

The Chairperson and Members hold office for a term of two years under section 20(2) and are eligible for re-appointment. Rule 18 and the Fifth Schedule prescribe their salary and conditions of service: the Chairperson receives a consolidated salary of Rs. 4,50,000 per month, and each other Member receives Rs. 4,00,000 per month (para 14.1).

A two-year term with eligibility for re-appointment is short by the standards of Indian tribunals and regulatory bodies. It is a feature worth noting for anyone modelling how the Board’s interpretive approach may develop, because a body whose composition can turn over every two years builds precedent differently from one with longer tenures.

4. What does it mean that the Board is a digital office?

Section 28(1) requires the Board to function as a digital office, with the receipt of complaints and the allocation, hearing and pronouncement of decisions being digital by design. Rule 20 operationalises this requirement by providing that the Board may adopt techno-legal measures to conduct proceedings in a manner that does not require physical presence of any individual, without prejudice to its power to summon and enforce the attendance of any person and examine her on oath (para 14.1).

The term is also defined. Section 2(m) defines a digital office as an office that adopts an online mechanism wherein the proceedings, from receipt to disposal, are conducted in online or digital mode (Glossary).

The book is clear that this is not an administrative preference. The digital-by-design mandate is a structural feature of the Board’s operation that determines how evidence is submitted, how hearings are conducted and how orders are communicated (para 14.1).

That has concrete consequences for the organisation on the receiving end. Every interaction with the Board, from receiving an intimation of inquiry to submitting evidence, attending hearings and receiving orders, will be conducted through digital channels. The book’s guidance is that the organisation should designate a response team familiar with the Board’s digital platform, ensure that all evidence can be produced in digital format, including scanned documents, electronic records, log exports, system screenshots and policy documents in searchable format, and establish an internal protocol for the preparation, review and submission of responses within the timelines the Board specifies (para 14.8.3).

The warning that accompanies this is worth quoting in substance. The Board’s proceedings, while conducted digitally, carry the same legal consequences as proceedings before any other adjudicatory body, and the response team should include or have access to legal counsel with experience in regulatory proceedings (para 14.8.3). A digital office is not an informal one.

5. What can the Board do, and what sets it in motion?

Section 27(1) enumerates five categories of action that the Board may take. Each has a different trigger, and the trigger determines who can start the process (para 14.2):

Clause Trigger What the Board may do
27(1)(a) Receipt of an intimation of personal data breach under section 8(6) Direct urgent remedial or mitigation measures, inquire into the breach, and impose penalty
27(1)(b) Complaint by a Data Principal in respect of a personal data breach, a breach by a Data Fiduciary in observance of its obligations, or the exercise of her rights; or a reference by the Central Government or a State Government; or compliance with court directions Inquire and impose penalty
27(1)(c) Complaint by a Data Principal regarding breach of Consent Manager obligations Inquire and impose penalty
27(1)(d) Receipt of an intimation of breach of Consent Manager registration conditions Inquire and impose penalty
27(1)(e) Reference by the Central Government regarding breach by an intermediary of compliance obligations under section 37(2) Inquire and impose penalty

Two of these five are worth separating out. Clause (a) is self-reporting: the organisation’s own breach intimation under section 8(6) is itself a trigger for Board action, which means the breach notification obligation and the enforcement process are directly connected. Clause (b) is the one most organisations will encounter, and it is conditioned on something that happens before the Board is involved at all, examined in section 12 below.

Beyond the five triggers, section 27(2) confers a general power to issue binding directions: the Board may, after giving the person concerned an opportunity of being heard and after recording reasons in writing, issue such directions as it may consider necessary, and the person shall be bound to comply. Section 27(3) permits the Board to modify, suspend, withdraw or cancel any direction, on representation from the affected person or on a reference from the Central Government, subject to conditions it deems fit (para 14.2).

6. How does a Board inquiry run, and how long can it take?

Section 28 prescribes the procedure, with a series of procedural safeguards drawn from the principles of natural justice (para 14.3).

The Board shall first determine whether there are sufficient grounds to proceed with an inquiry under section 28(3). Where it determines that there are insufficient grounds, it may close the proceedings for recorded reasons under section 28(4). Where it determines that there are sufficient grounds, it may inquire into the affairs of any person for ascertaining compliance, again for recorded reasons, under section 28(5). Section 28(6) requires the Board to conduct the inquiry following the principles of natural justice and to record reasons for its actions during the course of the inquiry.

On timing, Rule 19(9) prescribes that the inquiry shall be completed within a period of six months from the date of receipt of the intimation, complaint, reference or direction under section 27, unless the period is extended by the Board for reasons to be recorded in writing, for a further period not exceeding three months at a time. The book reads this as creating a defined outer boundary for the duration of the inquiry, giving the person under inquiry a degree of procedural certainty about the timeline (para 14.3).

Within that window, section 28(10) permits the Board to issue interim orders after giving the person concerned an opportunity of being heard, for reasons to be recorded in writing. Section 28(11) provides that on completion of the inquiry and after giving the person an opportunity of being heard, the Board may either close the proceedings or proceed to impose penalty under section 33. Section 28(12) provides that if the Board is of the opinion that a complaint is false or frivolous, it may issue a warning or impose costs on the complainant (para 14.3).

The book’s note on natural justice sets the floor the Board cannot go below. The requirement that the Board conduct inquiries following the principles of natural justice, and give the person concerned an opportunity of being heard before issuing directions under section 27(2), interim orders under section 28(10) or final orders under section 28(11), establishes a procedural floor. Natural justice, in the administrative law context, encompasses at a minimum the right to notice of the proceedings, the right to be heard before an adverse order is passed, the right to access the material on which the decision is based, and the obligation of the decision-maker to act without bias and to record reasons. A Board order that fails to observe these requirements is liable to be set aside on appeal (para 14.3).

7. What powers does the Board have, and where do they stop?

The Board possesses the same powers as a civil court under the Code of Civil Procedure, 1908 in respect of four matters (para 14.3):

Provision Power
Section 28(7)(a) Summoning and enforcing the attendance of any person and examining them on oath
Section 28(7)(b) Receiving evidence of affidavit requiring the discovery and production of documents
Section 28(7)(c) Inspecting any data, book, document, register, books of account, or any other document
Section 28(7)(d) Such other matters as may be prescribed

Then comes the limitation, and the book flags it as unusual in regulatory proceedings. Section 28(8) provides that the Board or its officers shall not prevent access to any premises or take into custody any equipment or any item that may adversely affect the day-to-day functioning of a person. This limitation protects the operational continuity of the entity under inquiry and distinguishes the Board’s powers from the search-and-seizure powers available to other regulatory bodies (para 14.3).

For a Data Fiduciary, the practical reading is that an inquiry will be conducted on documents and on sworn testimony, not through a dawn raid. Which in turn means the quality of the documents decides the outcome.

8. How is the amount of a penalty decided?

Section 33(1) provides that if the Board determines, on conclusion of an inquiry, that breach of the provisions of the Act or the Rules by a person is significant, it may, after giving the person an opportunity of being heard, impose such monetary penalty as specified in the Schedule (para 14.4).

The word “significant” introduces a threshold, and the book is careful about it: not every breach results in a penalty, and the Board must determine that the breach is significant before the penalty-imposing power is engaged. This threshold is not defined in the Act and will be interpreted by the Board and the Appellate Tribunal on a case-by-case basis, informed by factors such as the number of Data Principals affected, the severity of the harm, the duration of the breach, and whether the breach was isolated or systemic (para 14.4).

The Schedule specifies seven categories of breach and their corresponding maximum penalties (para 14.4):

Breach Maximum penalty
Breach of the obligation to take reasonable security safeguards under section 8(5) Up to Rs. 250 crore
Breach of the obligation to give the Board or affected Data Principal notice of a personal data breach under section 8(6) Up to Rs. 200 crore
Breach of additional obligations in relation to children under section 9 Up to Rs. 200 crore
Breach of additional obligations of a Significant Data Fiduciary under section 10 Up to Rs. 150 crore
Breach of duties by a Data Principal under section 15 Up to Rs. 10,000
Breach of any term of a voluntary undertaking accepted by the Board under section 32 Up to the extent applicable for the breach in respect of which the original proceedings were instituted
Breach of any other provision of the Act or the Rules Up to Rs. 50 crore

These are ceilings, not tariffs. Section 33(2) prescribes seven factors that the Board shall have regard to when determining the amount (para 14.4):

Factor What it turns on
Nature, gravity and duration of the breach How serious it was and how long it ran
Type and nature of the personal data affected What categories of data were compromised
Repetitive nature of the breach Whether this has happened before
Gain realised or loss avoided Whether the person benefited as a result
Mitigation action, and its timeliness and effectiveness What was done after the breach, and how fast
Proportionality and effectiveness Whether the penalty secures observance and deters breach
Likely impact of the penalty on the person The financial capacity and circumstances of the entity

The book reads these factors as a calibrated framework that permits the Board to impose penalties ranging from modest amounts for minor, first-time breaches by small entities, to amounts approaching the statutory maximum for serious, repeated or systemic breaches by large organisations that have failed to take corrective action (para 14.4).

Three of the seven factors are within the organisation’s control before anything goes wrong, and the book treats them as a guide to where the compliance budget should go (para 14.8.1). The mitigation factor under section 33(2)(e) means an organisation that can demonstrate prompt, effective and documented remedial action presents a materially different risk profile from one that delayed or failed to act. The proportionality factor under section 33(2)(f) means the Board will assess the penalty in light of both the need to secure future compliance and the need to deter similar breaches across the sector. The impact factor under section 33(2)(g) means the Board will consider the financial capacity and circumstances of the entity, which provides some protection for smaller entities that face the same statutory maximums as large corporations.

One design feature closes this section. Section 34 provides that all sums realised by way of penalties shall be credited to the Consolidated Fund of India. Penalty revenue accrues to the public exchequer rather than to the Board, removing any financial incentive for the Board to impose penalties for revenue-generation purposes (para 14.4).

Taxmann.com | Research | Subscribe Now!

9. Can a matter be closed without a penalty order?

Yes, by two separate routes.

The first is the voluntary undertaking under section 32. A person may offer a voluntary undertaking to the Board at any stage of a proceeding under section 28. The undertaking may include a commitment to take specified action within a specified time, or to refrain from specified action, and the Board may require the person to publicise the undertaking. The Board may, with the consent of the person, vary the terms after acceptance. Acceptance of the voluntary undertaking constitutes a bar on further proceedings under the Act as regards the contents of the undertaking, except where the person fails to adhere to any term, in which case the breach is deemed to be a breach of the Act and the Board may proceed to impose penalty under section 33 (para 14.5).

The book describes this as an off-ramp from formal enforcement that benefits both sides. The Board avoids the time and resource cost of completing the inquiry and adjudicating the penalty. The person avoids the reputational consequence and legal cost of a formal penalty order, while committing to remedial action that addresses the underlying compliance deficiency. Because the mechanism is available at any stage of the proceedings, even after an inquiry has commenced the person may offer an undertaking that resolves the matter without a formal determination (para 14.5).

There is a caution attached. The decision to offer a voluntary undertaking should be made with legal counsel’s advice, and the terms should be carefully drafted to ensure that the commitments are achievable within the specified timelines, that the scope of the undertaking is clearly defined, and that the bar on further proceedings under section 32(4) extends to all aspects of the matter the organisation intends to resolve. A failure to adhere to the terms is treated as a breach of the Act under section 32(5), which means the consequences of non-compliance with an undertaking are at least as severe as the consequences of the original breach (para 14.8.4).

The second route is mediation. Section 31 provides that if the Board is of the opinion that any complaint may be resolved by mediation, it may direct the parties to attempt resolution through a mediator mutually agreed upon or as provided for under any law for the time being in force in India. The book reads this mechanism as directed at complaints under section 27(1)(b), that is, complaints by Data Principals about breaches of obligation or denial of rights, rather than at breach intimations or references from the Central Government, which involve public interest considerations that may not be suitable for mediation (para 14.5).

10. How is an appeal filed against a Board order?

Section 29(1) provides that any person aggrieved by an order or direction made by the Board may prefer an appeal before the Appellate Tribunal. The Appellate Tribunal is the Telecom Disputes Settlement and Appellate Tribunal established under section 14 of the Telecom Regulatory Authority of India Act, 1997, designated as the Appellate Tribunal under section 2(a). It already exercises appellate jurisdiction under the TRAI Act and the Information Technology Act, 2000, and now does so under the DPDP Act as well (para 14.6).

The procedure is as follows (paras 14.6 and 1.5.2):

Provision Requirement
Section 29(2) Sixty-day limitation period from the date of receipt of the order or direction
Section 29(3) Appellate Tribunal may entertain a late appeal where sufficient cause is shown
Rule 22(1) The appeal shall be filed in digital form
Rule 22(2) Fee of like amount as applicable for appeals under the TRAI Act, unless reduced or waived by the Chairperson of the Appellate Tribunal, payable digitally through the Unified Payments Interface or other authorised payment system
Rule 22(3) The Appellate Tribunal shall not be bound by the Code of Civil Procedure but shall be guided by the principles of natural justice, and shall function as a digital office
Section 29(4) After giving the parties an opportunity of being heard, the Tribunal may confirm, modify or set aside the order appealed against
Section 29(6) and (7) The Tribunal shall endeavour to dispose of the appeal within six months, and shall record reasons where this timeline is not met
Section 29(9) Where an appeal is filed against the orders of the Appellate Tribunal, section 18 of the TRAI Act applies, permitting further appeal to the Supreme Court of India

That produces a three-tier enforcement architecture, which the book sets out plainly. The first tier is the Data Protection Board, which receives breach intimations and Data Principal complaints, conducts inquiries and imposes penalties. The second tier is the Appellate Tribunal, which hears appeals against Board orders within a sixty-day limitation period and endeavours to dispose of appeals within six months. The third tier is the Supreme Court of India, which hears appeals against Appellate Tribunal orders under section 18 of the TRAI Act. The structure provides both the specialised adjudication that data protection matters require at first instance and the constitutional oversight that the gravity of the penalties and the fundamental rights at stake demand (para 14.6).

The sixty-day limitation is the item most likely to be missed, and the book lists exactly that among its common audit findings: the appeal timeline is not tracked, creating a risk of missing the limitation period (para 14.9).

11. What powers does the Central Government retain?

Two, and they operate outside the Board’s adjudicatory process.

Section 36 provides that the Central Government may, for the purposes of the Act, require the Board and any Data Fiduciary or intermediary to furnish such information as it may call for. Rule 23 operationalises this power by specifying, through the Seventh Schedule, the purposes for which information may be called and the authorised persons who may exercise the power. The book notes that this information-gathering power is broad and is not conditioned on the existence of proceedings or the suspicion of a breach; it is an executive power available to the Central Government for the general purposes of the Act (para 14.7). Among the purposes listed is the carrying out of assessments for notifying Significant Data Fiduciaries (para 1.5.3).

Section 37 provides a more consequential power. The Central Government may, upon receipt of a reference from the Board that intimates the imposition of monetary penalty on a Data Fiduciary in two or more instances and advises blocking for access by the public in the interests of the general public, after giving the Data Fiduciary an opportunity of being heard and on being satisfied that blocking is necessary or expedient in the interests of the general public, direct any agency of the Central Government or any intermediary to block for access by the public any information that enables the Data Fiduciary to carry on any activity relating to offering of goods or services to Data Principals within India. Section 37(2) requires every intermediary receiving a blocking direction to comply with it (para 14.7).

The book calls this the most severe enforcement measure in the Act, because it permits the Central Government to effectively shut down a Data Fiduciary’s digital operations in India. It is subject to multiple procedural safeguards: two or more prior penalty impositions by the Board, a written reference from the Board, an opportunity of being heard for the Data Fiduciary, satisfaction by the Central Government that blocking is necessary or expedient in the general public interest, and recorded reasons. The practical consequence of a blocking direction would be the removal of the Data Fiduciary’s application from application stores, the blocking of its website by internet service providers, and the denial of access to its digital services by Indian users (para 14.7).

Two penalty orders are therefore not merely two penalties. They are the precondition for a measure that ends the business in India.

12. How should an organisation prepare for a Board inquiry?

Start with the one procedural fact that shapes everything else. Section 13(3) establishes that the Data Principal shall exhaust the opportunity of redressing her grievance under section 13 before approaching the Board. The Board’s jurisdiction under section 27(1)(b) is therefore conditioned on the Data Principal having first sought redress from the Data Fiduciary (para 9.3).

The book draws the operational conclusion: the grievance mechanism functions as the organisation’s primary point of regulatory exposure. A grievance that is received, properly investigated and resolved within the prescribed period will ordinarily not reach the Board. A grievance that is ignored, inadequately investigated or responded to after the prescribed period provides the Data Principal with both the cause and the procedural standing to escalate, where the original complaint will be compounded by the failure of the grievance mechanism itself. Organisations that invest in an effective grievance mechanism are, in practical terms, investing in a buffer between themselves and the Board’s enforcement powers (para 9.3).

Behind the grievance mechanism sits the evidence. The book’s position is that preparation for a Board inquiry should begin not when the inquiry is received, but when the compliance programme is established, so that the production of evidence in response to a Board direction is a retrieval exercise rather than a creation exercise (para 12.2.5). The same point is made from the enforcement side: the evidence generated during breach detection, investigation and notification will be the same evidence the Board examines during its inquiry, and the organisation’s consent records, notice versions, security safeguard documentation, grievance logs and rights fulfilment records should be maintained in a state of constant readiness, because an inquiry may be initiated at any time and the six-month timeline under Rule 19(9) means evidence must be produced promptly once it commences (para 14.8.1).

For the inquiry itself, the book supplies a response protocol. Figure 14.1 sets out six steps against a timeline (para 14.8.2):

Step Timing Core actions
Trigger Event-triggered Receipt of intimation, complaint, reference or direction under section 27
Receipt and logging Day 0 Response coordinator logs the communication; classifies it as a breach intimation, a Data Principal complaint, a Central Government reference or a Consent Manager matter; notifies the programme sponsor, legal counsel and the relevant workstream lead
Initial assessment Days 1 to 7 Review the allegations; identify the provisions cited or implicated; determine whether a section 17 exemption applies; assemble relevant evidence; engage external counsel if severity warrants
Evidence preparation Days 7 to 21 Compile documentary evidence; prepare a chronological narrative; cross-reference evidence against the Appendix A requirements register; identify gaps and prepare explanations
Response submission Per Board timeline Prepare the response in digital format per Rule 20, covering factual narrative, documentary evidence, legal submissions and remedial actions taken; review and approval by the DPO, legal counsel and programme sponsor; submit through the Board’s digital platform
Hearing preparation If a hearing is scheduled Prepare oral submissions; designate an authorised representative; anticipate Board questions based on the evidence submitted
Post-order actions After the Board order If a penalty is imposed, assess appeal options under section 29 within the sixty-day limitation; if a voluntary undertaking has been accepted, implement its terms; if directions have been issued, implement within the specified period; document lessons learned and update the compliance programme

The response coordinator should be the Data Protection Officer for Significant Data Fiduciaries, or the designated contact person under Rule 9 for other Data Fiduciaries, responsible for receiving Board communications, coordinating the collection of evidence across the organisation, ensuring responses are submitted within the Board’s timelines, and engaging external legal counsel where complexity or severity warrants (para 12.2.5).

The book then sets out what an auditor will test on enforcement readiness: whether a Board inquiry response protocol exists and has been communicated to the response team; whether the evidence framework is maintained in a state of readiness rather than requiring creation upon receipt of an inquiry; whether the organisation has conducted at least one simulation exercise for a Board inquiry scenario; whether the section 33(2) penalty calibration factors have been assessed for the organisation’s specific risk profile; and whether the voluntary undertaking mechanism under section 32 is understood by legal counsel and the programme sponsor as a strategic option (para 14.9).

Against that, the five findings the book reports as recurring (para 14.9):

Finding What it looks like in practice
No documented response protocol The organisation would improvise its response on receiving a Board inquiry
Partial evidence framework Consent records exist but grievance logs or deletion logs are incomplete
No simulation exercise The response team has never practised the workflow
Voluntary undertaking not understood Legal counsel is unaware of the mechanism or of the procedural consequences of acceptance and non-compliance
Appeal timeline not tracked Risk of missing the sixty-day limitation period under section 29(2)

Where the response protocol, the evidence framework and the simulation exercise have to be built rather than described, Taxmann Advisory provides implementation support, including compliance SOPs and automation of compliances.

13. Quick answers

What is the Data Protection Board of India?

The Data Protection Board of India is the adjudicatory body established under section 18 of the Digital Personal Data Protection Act, 2023, and constituted by Notification G.S.R. 844(E), dated 13 November 2025, with its head office in the National Capital Region. It is a body corporate under section 18(2). Taxmann’s Digital Personal Data Protection notes that it is not a regulator in the conventional sense: it does not issue regulations, set standards or grant licences other than the registration of Consent Managers, and its primary function is adjudicatory.

When will the Data Protection Board start hearing cases?

The Board was established on 13 November 2025, but it begins adjudicatory functions only when sections 27 and 28 of the DPDP Act come into force on 13 May 2027 under the Timelines Notification G.S.R. 843(E). Its jurisdiction over breaches of Consent Manager registration conditions under section 27(1)(d) commenced earlier, on 13 November 2026.

Who are the members of the Data Protection Board?

Section 19(1) provides for a Chairperson and such number of other Members as the Central Government may notify. Section 19(3) requires persons of ability, integrity and standing with special knowledge or practical experience in data governance, administration or implementation of laws related to social or consumer protection, dispute resolution, information and communication technology, digital economy, law, regulation or techno-regulation, and at least one must be an expert in the field of law. Appointments are made through Search-cum-Selection Committees under Rule 17, for a term of two years under section 20(2), with eligibility for re-appointment.

How long can a Data Protection Board inquiry take?

Rule 19(9) requires the inquiry to be completed within six months from the date of receipt of the intimation, complaint, reference or direction under section 27. The Board may extend that period for reasons recorded in writing, for a further period not exceeding three months at a time.

What is the maximum penalty under the DPDP Act?

Rs. 250 crore, for breach of the obligation to take reasonable security safeguards under section 8(5). The Schedule sets six further ceilings: Rs. 200 crore for failure to give notice of a personal data breach under section 8(6), Rs. 200 crore for breach of the children’s data obligations under section 9, Rs. 150 crore for breach of Significant Data Fiduciary obligations under section 10, Rs. 10,000 for breach of Data Principal duties under section 15, the amount applicable to the original breach for breach of a voluntary undertaking under section 32, and Rs. 50 crore for any other provision. Section 33(1) applies only where the Board determines the breach to be significant, and section 33(2) sets seven factors for calibrating the amount.

Can a Data Fiduciary avoid a penalty by settling with the Board?

Section 32 allows a person to offer a voluntary undertaking at any stage of a proceeding under section 28, committing to take or refrain from specified action within a specified time. Acceptance bars further proceedings as regards the contents of the undertaking. If any term is not adhered to, the breach is deemed a breach of the Act under section 32(5) and the Board may impose penalty under section 33. Section 31 separately allows the Board to direct mediation where it is of the opinion that a complaint may be resolved that way.

Where does an appeal against a Data Protection Board order go?

To the Telecom Disputes Settlement and Appellate Tribunal, designated as the Appellate Tribunal under section 2(a). Section 29(2) sets a sixty-day limitation period from receipt of the order, Rule 22(1) requires the appeal to be filed in digital form, and section 29(6) requires the Tribunal to endeavour to dispose of the appeal within six months. A further appeal lies to the Supreme Court of India under section 18 of the TRAI Act, read with section 29(9).

Must a Data Principal complain to the company before going to the Board?

Yes. Section 13(3) requires the Data Principal to exhaust the opportunity of redressing her grievance under section 13 before approaching the Board. Rule 14(3) requires the Data Fiduciary and Consent Manager to publish a reasonable period not exceeding ninety days for responding to grievances. This makes the grievance mechanism the first tier of dispute resolution and, as Taxmann’s Digital Personal Data Protection puts it, a buffer between the organisation and the Board’s enforcement powers.


This article draws on Chapter 14 of Taxmann’s Digital Personal Data Protection – An Essential Guide to India’s DPDP Law by CA Narasimhan Elangovan (2026 Edition), which examines the enforcement architecture in the sequence a typical enforcement action would follow, with the Board inquiry response protocol in Figure 14.1 and audit considerations on enforcement readiness. It also draws on Chapter 1, which maps the three-tier regulatory architecture and the three-phase commencement schedule, on Chapter 9 on the grievance framework, and on Chapter 12 on the evidence framework and preparing for a Board inquiry. Law stated as updated till 15 September 2026.

The DPDP Act, 2023, the DPDP Rules, 2025 and the notifications of 13 November 2025 are available on Taxmann.com | Research under Indian Acts and Rules.

Related reading: data privacy breach, enforcement and penalties under the DPDP Act · commencement dates for the DPDP Act · the notification of the DPDP Rules, 2025 · an analysis of the Act read with the Rules.

More in this series: how a DPDP compliance audit is conducted · Significant Data Fiduciary obligations · Consent Managers under the DPDP framework · personal data breach intimation under Rule 7 · handling Data Principal rights requests · Data Fiduciary, Data Processor or both · children’s data and verifiable parental consent · the SPDI Rules and the DPDP Act · the Record of Processing Activities (ROPA) · the incident response plan · data retention and erasure · the privacy notice under Rule 3 · the data processing agreement · data localisation and cross-border transfers · employee data and workplace monitoring · exemptions under the DPDP Act · legitimate uses under section 7.

Disclaimer: The content/information published on the website is only for general information of the user and shall not be construed as legal advice. While the Taxmann has exercised reasonable efforts to ensure the veracity of information/content published, Taxmann shall be under no liability in any manner whatsoever for incorrect information, if any.

Leave a Reply

Your email address will not be published. Required fields are marked *

Everything on Tax and Corporate Laws of India

To subscribe to our weekly newsletter please log in/register on Taxmann.com

Author: Taxmann

Taxmann Publications has a dedicated in-house Research & Editorial Team. This team consists of a team of Chartered Accountants, Company Secretaries, and Lawyers. This team works under the guidance and supervision of editor-in-chief Mr Rakesh Bhargava.

The Research and Editorial Team is responsible for developing reliable and accurate content for the readers. The team follows the six-sigma approach to achieve the benchmark of zero error in its publications and research platforms. The team ensures that the following publication guidelines are thoroughly followed while developing the content:

  • The statutory material is obtained only from the authorized and reliable sources
  • All the latest developments in the judicial and legislative fields are covered
  • Prepare the analytical write-ups on current, controversial, and important issues to help the readers to understand the concept and its implications
  • Every content published by Taxmann is complete, accurate and lucid
  • All evidence-based statements are supported with proper reference to Section, Circular No., Notification No. or citations
  • The golden rules of grammar, style and consistency are thoroughly followed
  • Font and size that's easy to read and remain consistent across all imprint and digital publications are applied