A personal data breach is not simply a technical incident. It may expose individuals to identity theft, financial fraud, impersonation and misuse of their personal information. The Digital Personal Data Protection Act, 2023 recognises the importance of this issue and provides for a regulatory mechanism through the Data Protection Board of India.
But what happens when a person suffers a data breach and the Board, although established, is not yet fully operational?
The question requires an examination of the statutory complaint mechanism, the commencement of the relevant provisions and the remedies that may remain available outside the Board.
The statutory role of the Board
The DPDP Act envisages the Board as the principal authority for examining matters arising under the legislation.
Section 27 sets out the Board’s powers and functions. These include examining complaints, inquiring into personal data breaches and performing other statutory functions.
Section 28 provides the procedure to be followed by the Board while exercising its powers.
The statutory framework therefore contemplates a process through which a Data Principal may bring a grievance before the regulator and seek appropriate action.
However, the existence of this mechanism in the enacted legislation does not automatically mean that every part of it became operational on the date the Act was notified.
The importance of commencement dates
The Central Government issued G.S.R. 843(E) on 13 November 2025, specifying different commencement dates for different provisions of the Act.
Under this notification:
- Sections 18–26 came into force on 13 November 2025.
- Section 27(1)(d) came into force on 13 November 2026.
- The remaining provisions of section 27 and section 28 are scheduled to commence on 13 May 2027.
This distinction is particularly important because the present date is 18 November 2026.
Although the Board has been established, the complete statutory framework governing its powers and procedure has not yet commenced.
A complaint mechanism should therefore not be represented as fully available merely because sections 18 and 19 have come into force.
Does a data breach go unaddressed?
No. The absence of a fully operational Data Protection Board does not mean that an organisation can treat a data breach as legally irrelevant.
There are several important considerations.
First, the commencement of the substantive obligations under the DPDP Act must be examined. Sections 3–17, which contain the principal obligations of Data Fiduciaries and rights of Data Principals, are scheduled to commence on 13 May 2027, subject to the specific commencement of section 6(9).
Accordingly, the statutory obligation under section 8(6) to intimate the Board and affected Data Principals in the event of a personal data breach should not be treated as having commenced in November 2026.
Second, other laws may continue to apply. Depending on the nature of the incident, an organisation may have obligations under the Information Technology Act, 2000, applicable rules, sector-specific regulations and other laws governing confidentiality, cybersecurity and disclosure.
For instance, regulated entities may have reporting obligations under applicable RBI, SEBI or IRDAI directions. The precise obligation depends on the entity, the incident and the relevant regulatory instrument.
Third, a person affected by a breach may consider other legally available remedies, including approaching the appropriate sectoral regulator, law enforcement authorities or a competent court, depending upon the facts.
The DPDP Act does not make the Board the exclusive forum for every legal issue arising from the misuse of personal information.
What does the Kerala High Court order tell us?
In C.R. Neelakandan v. Union of India, WP(PIL) No. 15 of 2026, the Kerala High Court recorded the Central Government’s submission that the Board had been constituted but was not yet functional.
The Court expressed the expectation that the Board would become functional within eight weeks from 7 October 2026.
The proceedings concerned concerns relating to passenger information and Digi Yatra. The order is relevant because it highlights the institutional gap between establishing the Board and making it capable of performing its functions.
However, the order does not create a new complaint procedure or extend the commencement date of section 27 or section 28.
What should businesses do in the meantime?
Businesses should not wait until the Board begins accepting and deciding complaints to establish their internal incident-response systems.
A sensible approach would include:
- Maintaining a documented data-breach response policy.
- Identifying the personal data held by the organisation and the systems in which it is stored.
- Maintaining records of security incidents and remedial action.
- Establishing an internal escalation mechanism involving legal, compliance and information-security teams.
- Reviewing contractual obligations with vendors and Data Processors.
- Identifying reporting obligations under existing sector-specific laws.
Businesses should also preserve evidence relating to the incident, including access logs, audit records, communications and remediation reports.
Such documentation will be important if the incident subsequently becomes the subject of regulatory scrutiny or litigation.
Conclusion
The absence of a fully operational Data Protection Board creates an institutional concern, but it does not create a legal vacuum in which every form of data protection obligation disappears.
The correct legal position requires three separate questions to be examined: whether the relevant DPDP provision has commenced, whether another applicable law imposes an independent obligation, and whether the appropriate regulatory or judicial remedy is presently available.
For businesses, the more prudent approach is to prepare for the regulatory framework before it becomes fully operational.
A data breach is fundamentally an issue of accountability. The absence of a functioning regulator should not become a reason for an organisation to remain unprepared.



