Section 22: Resignation by Members and Filling of Vacancy

Chapter: Data Protection Board of India

Direct Answer

Section 22 of India's DPDP Act 2023 (Resignation by Members and Filling of Vacancy) procedures for resignation and vacancy filling on the Board. It applies to board operations. Organisations should document controls, maintain audit evidence, and review this obligation before full enforcement expected from May 2027.

Overview

Procedures for resignation and vacancy filling on the Board.

Key Points of Section 22

• Members may resign with notice to Government
• Vacancies filled per prescribed procedure

Who This Applies To

Board operations

Compliance Action Steps

1. Track vacancies affecting proceedings

Practical Examples

1. The Data Protection Board receives a complaint about opaque consent banners — Section 27 inquiry powers follow establishment under Section 18.
2. A Data Fiduciary participates in a digital Board hearing — Section 23 virtual proceedings require e-filing and authenticated submissions.
3. Board staffing grows through Section 24 — enforcement intensity in regulated sectors rises through 2026–2027.

Statutory Text

Resignation and vacancy. 22(1): Resignation effective on permission, 3 months, successor, or term end — earliest. 22(2): Vacancy filled by fresh appointment. 22(3): One-year cooling-off before employment with Fiduciaries subject to member's proceedings.

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 22 — Resignation by Members and Filling of Vacancy (Chapter: Data Protection Board of India)

Statutory overview

Procedures for resignation and vacancy filling on the Board.

Plain-English requirements

1. Members may resign with notice to Government

2. Vacancies filled per prescribed procedure

Operational implications for Indian organisations

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

Every Data Fiduciary should treat DPBI as the primary regulator. Sections 18–26 establish Board governance; monitor appointments and digital proceeding requirements.

Implementation playbook

1. Subscribe to DPBI notifications.
2. Designate inquiry response team.
3. Maintain immutable audit logs.
4. Run mock complaint-handling drills.

Related provisions

Section 22 should be read alongside Section 20, Section 21, Section 23, Section 24. 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 22. 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 22

When the Data Protection Board opens an inquiry, investigators typically request: (a) your privacy notice and consent records tied to resignation by members and filling of vacancy; (b) RoPA entries referencing Section 22; (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. Members may resign with notice to Government; Vacancies filled per prescribed procedure. 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 22 require?

Section 22 (Resignation by Members and Filling of Vacancy) requires that procedures for resignation and vacancy filling on the Board. It applies to board operations.

Who must comply with Section 22 of the DPDP Act?

Board operations

What is the compliance deadline for DPDP Section 22?

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

How do I implement DPDP Section 22 in my organisation?

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

Yes, unless a specific exemption notification applies to your organisation class. Section 22 (Resignation by Members and Filling of Vacancy) applies to board operations. 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 22 relate to GDPR or other global privacy laws?

Section 22 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 Guide — Monitor Board composition changes.

Back to Complete DPDP Guide