Section 29: Appeal to Appellate Tribunal

Chapter: Appeal and Alternate Dispute Resolution

Direct Answer

Section 29 of India's DPDP Act 2023 (Appeal to Appellate Tribunal) appeals from Board orders lie to the Telecom Disputes Settlement and Appellate Tribunal. It applies to parties aggrieved by board orders. Organisations should document controls, maintain audit evidence, and review this obligation before full enforcement expected from May 2027.

Overview

Appeals from Board orders lie to the Telecom Disputes Settlement and Appellate Tribunal.

Key Points of Section 29

• Appeal from Board order to TDSAT
• Appeal within prescribed period
• TDSAT may confirm, modify, or set aside order

Who This Applies To

Parties aggrieved by Board orders

Compliance Action Steps

1. Preserve complete inquiry records
2. Engage appellate counsel

Practical Examples

1. A fintech disputes a penalty order — Section 29 TDSAT appeal must be filed within the prescribed period with complete inquiry records.
2. Two parties in a data-sharing dispute agree to mediation — Section 31 ADR can produce a Board-confirmed settlement faster than litigation.
3. A retailer offers a voluntary undertaking after a consent audit failure — Section 32 can reduce penalty exposure if fulfilled on schedule.

Statutory Text

Appeal to Appellate Tribunal. 29(1): Appeal Board orders to TDSAT. 29(2): Within 60 days in prescribed form and fee. 29(6): Dispose within six months where practicable.

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 29 — Appeal to Appellate Tribunal (Chapter: Appeal and Alternate Dispute Resolution)

Statutory overview

Appeals from Board orders lie to the Telecom Disputes Settlement and Appellate Tribunal.

Plain-English requirements

1. Appeal from Board order to TDSAT

2. Appeal within prescribed period

3. TDSAT may confirm, modify, or set aside order

Operational implications for Indian organisations

Data fiduciaries and processors should translate Section 29 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 29 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

Appeals to TDSAT (Section 29), ADR (Section 31), and voluntary undertakings (Section 32) offer alternative resolution paths after Board orders.

Implementation playbook

1. Preserve complete Board proceeding records.
2. Evaluate TDSAT appeal or ADR options.
3. Consider voluntary undertaking for identified gaps.

Related provisions

Section 29 should be read alongside Section 28, Section 30, Section 31. 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 29. 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 29

When the Data Protection Board opens an inquiry, investigators typically request: (a) your privacy notice and consent records tied to appeal to appellate tribunal; (b) RoPA entries referencing Section 29; (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. Appeal from Board order to TDSAT; Appeal within prescribed period. 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 21: Appeal to Appellate Tribunal — Procedure for appeals from Board orders to TDSAT.

Frequently Asked Questions

What does DPDP Act Section 29 require?

Section 29 (Appeal to Appellate Tribunal) requires that appeals from Board orders lie to the Telecom Disputes Settlement and Appellate Tribunal. It applies to parties aggrieved by board orders.

Who must comply with Section 29 of the DPDP Act?

Parties aggrieved by Board orders

What is the compliance deadline for DPDP Section 29?

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

How do I implement DPDP Section 29 in my organisation?

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

Yes, unless a specific exemption notification applies to your organisation class. Section 29 (Appeal to Appellate Tribunal) applies to parties aggrieved by board orders. 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 29 relate to GDPR or other global privacy laws?

Section 29 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 Consulting — Connect with advisors experienced in TDSAT data appeals.

Back to Complete DPDP Guide