Section 37: Power of Central Government to Issue Directions

Chapter: Miscellaneous

Direct Answer

Section 37 of India's DPDP Act 2023 (Power of Central Government to Issue Directions) government may issue directions including blocking access for repeated violations. It applies to online platforms and service providers. Organisations should document controls, maintain audit evidence, and review this obligation before full enforcement expected from May 2027.

Overview

Government may issue directions including blocking access for repeated violations.

Key Points of Section 37

• Government may issue directions to fiduciaries and intermediaries
• Blocking orders for repeated violations possible

Who This Applies To

Online platforms and service providers

Compliance Action Steps

1. Respond promptly to directions
2. Monitor blocking precedents

Practical Examples

1. New DPDP Rules 2025 define operational detail — Section 40 rule-making power requires monitoring Gazette notifications quarterly.
2. A social platform ignores repeated Board directions — Section 37 blocking powers create existential business risk in India.
3. Contracts still citing IT Act Section 43A — Section 44 requires updating agreements to the DPDP framework.

Statutory Text

Government directions. 37(1): On Board reference after repeated penalties, may block public access to Fiduciary's service-enabling information. 37(2): Intermediaries must comply with blocking directions.

Source: Digital Personal Data Protection Act, 2023 (No. 22 of 2023), Gazette of India, Extraordinary, Part II—Sec. 1, 11 Aug 2023. Operative excerpts for reference; official Gazette text prevails.

Legal Provisions and Compliance Guidance

Section 37 — Power of Central Government to Issue Directions (Chapter: Miscellaneous)

Statutory overview

Government may issue directions including blocking access for repeated violations.

Plain-English requirements

1. Government may issue directions to fiduciaries and intermediaries

2. Blocking orders for repeated violations possible

Operational implications for Indian organisations

Data fiduciaries and processors should translate Section 37 into concrete controls: update privacy notices, train staff, adjust product flows, and maintain evidence that demonstrates compliance during audits or Board inquiries. Map this section to your Record of Processing Activities (RoPA) and link each control to an owner, review date, and evidence repository. Product managers should embed privacy-by-design checkpoints in sprint reviews; security teams should align SOC monitoring with obligations that carry penalty exposure; and legal teams should track DPBI guidance that interprets ambiguous phrases in the statute.

Relationship to DPDP Rules 2025

The DPDP Rules 2025 notified in January 2025 provide operational detail for many Chapter obligations — including timelines, formats, and registration requirements. Monitor Central Government notifications and DPBI guidance for sector-specific interpretations that refine how Section 37 is enforced. Rule updates may introduce new forms, registration portals, or technical standards that supersede informal industry practice — subscribe to official Gazette notifications rather than relying solely on vendor marketing materials.

Sector-specific considerations

Rule-making (Section 40), blocking directions (Section 37), and IT Act amendments (Section 44) require ongoing legal monitoring through 2027.

Implementation playbook

1. Monitor Gazette for new rules.
2. Update contracts from IT Act 43A to DPDP.
3. Track blocking-order precedents if operating large platforms.

Related provisions

Section 37 should be read alongside Section 35, Section 36, Section 38, Section 39. Indian compliance programmes typically map these sections together in privacy impact assessments, vendor due diligence questionnaires, and board reporting packs. Cross-referencing prevents siloed fixes — for example, improving consent under Section 6 without updating notice under Section 5 leaves residual regulatory risk.

Documentation and evidence

Maintain version-controlled policies, system logs, consent records, training attendance, and DPIA outputs that reference Section 37. During a Data Protection Board inquiry, documented good-faith compliance efforts can influence remedial directions and penalty outcomes. Evidence should be tamper-evident where possible — immutable consent logs, WORM storage for audit trails, and timestamped policy approvals strengthen your position.

Audit and Board inquiry preparedness for Section 37

When the Data Protection Board opens an inquiry, investigators typically request: (a) your privacy notice and consent records tied to power of central government to issue directions; (b) RoPA entries referencing Section 37; (c) training records for staff handling relevant workflows; (d) technical evidence such as access logs, encryption configurations, or deletion confirmations; and (e) correspondence with Data Principals on related rights requests. Proactively assemble a section-specific evidence bundle quarterly. Government may issue directions to fiduciaries and intermediaries; Blocking orders for repeated violations possible. Platforms like Complynz automate control mapping and evidence collection so legal teams can respond to DPBI requests within days rather than weeks.

Enforcement timeline

The Act passed in August 2023. DPDP Rules were notified in November 2025. Consent Manager registration opens November 2026. Full operational enforcement is expected from May 2027 — organisations should complete gap remediation before that date. Early movers gain competitive advantage with enterprise buyers and government tenders that increasingly require demonstrable DPDP readiness.

Frequently Asked Questions

What does DPDP Act Section 37 require?

Section 37 (Power of Central Government to Issue Directions) requires that government may issue directions including blocking access for repeated violations. It applies to online platforms and service providers.

Who must comply with Section 37 of the DPDP Act?

Online platforms and service providers

What is the compliance deadline for DPDP Section 37?

DPDP Rules 2025 introduced a phased 18-month implementation window. While some provisions are being rolled out from 2025–2026, full enforcement with DPBI penalty powers is expected from May 2027. Organisations should implement Section 37 controls before that date.

How do I implement DPDP Section 37 in my organisation?

Start with a gap assessment mapping Section 37 requirements to your current privacy programme, product flows, and vendor contracts. Assign an internal owner, implement missing controls, document evidence in a central repository, and schedule quarterly reviews. Automated GRC platforms reduce manual effort and help maintain continuous compliance as rules evolve.

Does Section 37 apply to startups and small businesses in India?

Yes, unless a specific exemption notification applies to your organisation class. Section 37 (Power of Central Government to Issue Directions) applies to online platforms and service providers. Startups may receive targeted exemptions under Section 17, but core obligations around consent, security, and rights typically remain. Budget-constrained teams should prioritise high-penalty sections first.

How does Section 37 relate to GDPR or other global privacy laws?

Section 37 is India's standalone requirement under the DPDP Act 2023. Organisations already GDPR-compliant must still map DPDP-specific obligations — consent standards, DPBI enforcement, penalty caps, and Rules 2025 timelines differ from EU law. Apply the higher protection standard where laws overlap and maintain separate India-specific documentation.

Suggested Next Step

DPDP Platform — Track compliance status to avoid repeated violations.

Back to Complete DPDP Guide