Section 42: Power to Amend Schedule

Chapter: Miscellaneous

Direct Answer

Section 42 of India's DPDP Act 2023 (Power to Amend Schedule) government may amend the penalty Schedule by notification. It applies to penalty exposure monitoring. Organisations should document controls, maintain audit evidence, and review this obligation before full enforcement expected from May 2027.

Overview

Government may amend the penalty Schedule by notification.

Key Points of Section 42

• Government may amend penalty Schedule by notification
• Schedule linked to Section 33 penalties

Who This Applies To

Penalty exposure monitoring

Compliance Action Steps

1. Track Schedule amendments

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

Amend Schedule. 42(1): Government may amend Schedule; penalties not more than doubled. 42(2): Amendment effective on notification as if enacted.

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 42 — Power to Amend Schedule (Chapter: Miscellaneous)

Statutory overview

Government may amend the penalty Schedule by notification.

Plain-English requirements

1. Government may amend penalty Schedule by notification

2. Schedule linked to Section 33 penalties

Operational implications for Indian organisations

Data fiduciaries and processors should translate Section 42 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 42 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 42 should be read alongside Section 40, Section 41, Section 43, Section 44. 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 42. 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 42

When the Data Protection Board opens an inquiry, investigators typically request: (a) your privacy notice and consent records tied to power to amend schedule; (b) RoPA entries referencing Section 42; (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 amend penalty Schedule by notification; Schedule linked to Section 33 penalties. 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.

Related DPDP Rules 2025

• Rule 23: Miscellaneous — Residual operational provisions and forms.

Frequently Asked Questions

What does DPDP Act Section 42 require?

Section 42 (Power to Amend Schedule) requires that government may amend the penalty Schedule by notification. It applies to penalty exposure monitoring.

Who must comply with Section 42 of the DPDP Act?

Penalty exposure monitoring

What is the compliance deadline for DPDP Section 42?

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 42 controls before that date.

How do I implement DPDP Section 42 in my organisation?

Start with a gap assessment mapping Section 42 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 42 apply to startups and small businesses in India?

Yes, unless a specific exemption notification applies to your organisation class. Section 42 (Power to Amend Schedule) applies to penalty exposure monitoring. 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 42 relate to GDPR or other global privacy laws?

Section 42 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

Penalty Schedule — Full Schedule with current penalty caps.

Back to Complete DPDP Guide