5 minutes

Section 17(1)(b) Exemption For Regulatory And Judicial Bodies

A detailed review of the DPDP Act Section 17(1)(b) exemption for courts, tribunals, and regulatory bodies, explaining condition limits and the surviving Section 8(5) security obligations.

Written byVipul Abhishek· Former Advocate, Supreme Court of India

Last updated:

Section 17(1)(b) of the Digital Personal Data Protection Act 2023 removes obligations for specific bodies in India. The carve-out covers courts, tribunals, and entities entrusted by law with judicial, quasi-judicial, regulatory, or supervisory duties. They skip most general compliance rules when processing digital personal data necessary for those functions. The Act sets a precise boundary for this exemption. Private enterprises cannot unilaterally declare an internal team as a quasi-judicial entity, because an Indian statute must establish the legal mandate. Oversight and judicial actions proceed without standard Data Principal interventions. The exemption bypasses Section 6 consent frameworks entirely. Private organizations rely on Section 7 legitimate uses to conduct their own internal processing. Regulators invoke Section 17(1)(b) for core statutory tasks.

The exemption directly deactivates Chapter II, Chapter III, and Section 16 of the Act for qualifying processing. A regulatory body does not issue a Section 5 notice before collecting data for a supervisory audit. Individuals lose the rights granted under Chapter III. A person cannot invoke Section 11 to demand the erasure of their records from a court docket. Section 13 normally grants Data Principals the right to readily available grievance redressal mechanisms from a Data Fiduciary. Sub-section 13(2) allows the government to prescribe specific response periods, and the DPDP Rules, 2025 codify these exact timelines. The Act requires individuals to exhaust this channel before approaching the Data Protection Board. Under this carve-out, those Chapter III rights disappear. The regulatory body ignores the DPDP Rules, 2025 grievance timelines for data processed during a statutory investigation. The law also turns off Section 16. Since Section 16(1) permits the Central Government to restrict data transfers to notified countries, processing under this exemption skips that specific geographic block.

The Act retains two core duties for bodies processing data under this carve-out. Sub-sections (1) and (5) of Section 8 remain active. Section 8(1) assigns accountability directly to the entity. The regulatory or quasi-judicial body bears full responsibility for its processing and for any actions taken by a Data Processor on its behalf. Meanwhile, Section 8(5) mandates reasonable security safeguards. An exempted entity applies access controls and encryption to protect digital personal data from external threats. The entity actively prevents personal data breaches, as the Act does not forgive security failures. A tribunal handling financial records implements technical safeguards matching private sector requirements. If a breach occurs, the regulatory body follows the DPDP Rules, 2025 incident reporting procedures. The exemption shields the purpose of the data collection without lowering physical or technical security standards.

The statutory language imposes a strict necessity test. The exemption applies only where the processing is necessary for the performance of the entrusted function. A regulator cannot process personal data for unrelated commercial analysis, so the entity maps the data exactly to the supervisory action. If a regulatory body processes payroll data for its own staff, Section 17(1)(b) offers no protection. That administrative activity falls under standard employment processing or consent. The carve-out isolates the exact regulatory task. A tribunal gathers witness statements and financial logs to decide a case, pulling that specific data pool into the exemption. If the tribunal uses the same contact details to send unrelated material, the standard obligations of the DPDP Act attach immediately. The legal boundary depends entirely on the specific mandate. Processing that strays from the entrusted function loses the statutory shield.

Private companies sometimes misinterpret this provision by attempting to apply Section 17(1)(b) to internal disciplinary committees or audit boards. The statute requires the body in India to be entrusted by law with the function. A corporate human resources panel lacks this legal entrustment. Private organizations use Section 7 legitimate uses or explicit consent for corporate governance investigations. Section 17(1)(a) provides a separate exemption for processing necessary to enforce a legal right or claim, which enterprises apply when preparing for litigation. Section 17(1)(b) belongs strictly to statutorily authorized bodies. The legal team reviews the specific statute governing an industry to identify if any quasi-judicial power exists. A self-regulatory organization qualifies only if a direct statutory mandate authorizes its supervisory function over market participants.

Entities operating under this exemption maintain precise records to prove their processing qualifies for the carve-out. An auditor or the Data Protection Board expects a clear evidence trail. A compliance officer isolates the data streams.

1. Identify the statutory mandate. The legal department logs the specific Indian law granting the regulatory or quasi-judicial authority.

2. Segregate the exempted data. The IT control owner configures systems to separate regulatory investigation data from general administrative files.

3. Document the necessity threshold. The control owner records how the data collection directly serves the supervisory function.

4. Apply security safeguards. The security team engineers encryption and access logs to satisfy Section 8(5) and the DPDP Rules, 2025 standards.

5. Restrict data reuse. The entity prevents staff from transferring exempted data into non-exempt business units.

Proper implementation requires strict technical boundaries. The exemption provides legal cover for data acquisition, provided the entity applies tight data governance to maintain it.

Section 16 of the Act dictates cross-border transfer rules. The Central Government publishes notifications restricting transfers to specific countries. Processing under Section 17(1)(b) bypasses these Section 16 restrictions. A statutory body transfers data internationally if necessary for its regulatory function, without facing DPDP Act geographic blocks. Section 16(2) preserves any other Indian law providing a higher degree of protection or restriction on transfers. If a separate sectoral law forbids a regulatory body from transferring specific financial records abroad, that law remains valid. The DPDP Act does not override stricter sectoral data transfer bans. Organizations track both DPDP Act exemptions and sector-specific restrictions. The legal team monitors overlapping jurisdictions. Run a detailed gap check on processing activities today using https://www.complydp.com/audit-preview to confirm exemption mapping.

Sources

Frequently asked questions

Does Section 17(1)(b) apply to corporate disciplinary committees?

It applies only if a specific Indian law entrusts the committee with quasi-judicial or regulatory functions. Corporate disciplinary panels do not qualify. Private enterprises apply Section 7 legitimate uses or collect consent for internal investigations.

Do regulatory bodies skip the security requirements of the Act?

No. Section 17(1) specifically retains Section 8(5). The processing entity applies reasonable security safeguards to prevent personal data breaches. A tribunal or regulatory body implements encryption and access controls over its digital personal data pools. It also follows DPDP Rules, 2025 breach notification protocols.

How does the exemption affect Data Principal grievance redressal?

Chapter III does not apply to this specific processing. Section 13 grants Data Principals the right to a readily available grievance redressal mechanism. Under Section 17(1)(b), individuals cannot invoke Section 13 or the DPDP Rules, 2025 timelines to demand grievance redressal from the regulatory body regarding the exempted processing.

Can a regulatory body use exempted personal data for employee payroll?

No. The exemption covers only the processing necessary for the performance of the entrusted judicial, quasi-judicial, regulatory, or supervisory function. Employee payroll processing falls outside this scope. The body applies standard DPDP Act rules for its administrative functions.

Does this exemption bypass Section 16 cross-border transfer rules?

Yes. Processing under Section 17(1)(b) is exempt from Section 16 Central Government transfer restrictions. However, Section 16(2) specifies that sector-specific Indian laws providing stricter transfer restrictions remain active. The regulatory body follows those prevailing sectoral bans.