Section 69A “Any Information” Includes Software Platforms: Temporary Platform-Wide Blocking Can Be Proportionate in an Emergency

1. Introduction

This writ petition challenged the Union Government’s emergency blocking directions issued by the Ministry of Electronics and Information Technology (MeitY) under Section 69A of the Information Technology Act, 2000 (IT Act) read with the Information Technology (Procedure and Safeguards for Blocking for Access of Information by Public) Rules, 2009 (2009 Rules).

The trigger was alleged repeated misuse of the Telegram messaging platform in connection with NEET UG, 2026, including circulation of purported leaked papers, misleading information, bots/channels facilitating fraud, and related public-order concerns. The petitioners (Telegram entity and its India nodal officer) asserted sustained cooperation and compliance with takedown requests, and argued that a platform-wide block was ultra vires and disproportionate.

Key Issues Framed by the Court

• Non-application of mind: Whether the interim blocking order was vitiated for lack of reasons/independent satisfaction.
• Proportionality: Whether temporarily blocking access to the entire Telegram platform (and disabling message-editing) satisfied constitutional proportionality.

Timeline (Condensed)

2. Summary of the Judgment

The High Court dismissed the petition and upheld both the interim emergency blocking order (16.06.2026) and the final confirming order (18.06.2026).

• The Court held the interim order contained sufficient reasons given the emergency context; it was not vitiated by non-application of mind.
• The Court held that Section 69A empowers blocking not only of specific posts/messages but can extend to blocking an entire application/platform, because “information” in the IT Act includes codes, computer programmes, software and databases.
• Applying Anuradha Bhasin v. Union Of India, (2020) 3 SCC 637, the Court held the measures were proportionate, being time-bound, event-linked (NEET re-exam), and adopted after narrower options were found ineffective due to platform architecture (mirror channels, bots, audience migration, and message-editing risks).

3. Analysis

3.1 Precedents Cited

(a) Anuradha Bhasin v. Union Of India, (2020) 3 SCC 637

This was the central proportionality authority. The petitioners relied on it to argue: (i) restrictions on fundamental rights must be proportionate and least restrictive; and (ii) wholesale blocking measures (by analogy to broad internet restrictions) are constitutionally suspect when targeted takedowns could suffice.

The Court expressly extracted and applied the proportionality framework from Anuradha Bhasin—legitimate aim, rational nexus, necessity, least restrictive means, and tailoring in duration/extent—and concluded the Government satisfied these requirements because the blocking was temporary, linked to a critical exam window, and narrower measures were found ineffective in practice.

(b) Bishamber Dayal Chandra Mohan v. State of U.P., (1982) 1 SCC 39

Cited by the petitioners for the proposition that restrictions on fundamental rights must be reasonable, proportionate, and not excessive or arbitrary. The High Court’s proportionality discussion implicitly addresses this concern by emphasizing the limited temporal scope and the failure of entity-by-entity takedowns in the immediate pre-exam period.

(c) Assistant General Manager, State Bank of India & Anr. v. Tanya Energy Enterprises through its Managing Partner Shri Alluri Lakshmi Narsimha Varma, Neutral Citation: 2025 INSC 1119

Relied upon by the respondents to contend that a court may, in appropriate cases, uphold an administrative order on an alternative ground traceable to the factual narrative, subject to fair notice and opportunity. While the High Court primarily upheld the orders on the reasons recorded within them and the statutory process under Section 69A/2009 Rules, the citation supported the respondents’ broader defence that the orders should be assessed substantively and not set aside for hyper-technical reasoning objections, particularly in an emergency framework with post-decisional hearing.

(d) Akshay N. Patel v. Reserve Bank Of India & Anr., (2022) 3 SCC 694

Relied upon by the respondents to argue that constitutional rights should not be used by private commercial entities to defeat lawful public-interest regulation. The High Court’s reasoning aligns with this theme when it treats public-order and examination-integrity concerns affecting ~2.2 million candidates as weighty interests justifying calibrated restrictions, notwithstanding the platform’s private interests and lawful user base.

3.2 Legal Reasoning

A. Non-application of mind and adequacy of reasons in an emergency interim order

• The Court held that administrative/statutory decisions must carry reasons showing nexus between material and conclusion, but the emergency nature of the interim order informs what is “sufficient” at that stage.
• The interim order recorded: alleged exam-fraud ecosystem, repeated re-emergence despite takedowns, public unrest/public order apprehension, and the need for platform-level intervention for the exam window. The Court found this adequate to defeat the “non-application of mind” attack.
• The Court emphasized the statutory architecture: Rule 9 emergency power allows interim blocking subject to post-decisional process, including placement before the Rule 7 Committee and a hearing soon after.
• On the argument that the final order impermissibly “supplied reasons”, the Court rejected it as inconsistent with the Section 69A + 2009 Rules design, where a fuller final decision follows a post-decisional hearing.

B. Statutory power under Section 69A to block an entire platform/application

The petitioners argued Section 69A only permits blocking of specific “information”, not a blanket platform block. The Court rejected this by construing the statutory definitions:

• Section 2(1)(v) defines “information” to include “codes, computer programmes, software and data bases”.
• An application/platform is, in ordinary terms, software/code plus databases and related programmatic components; hence it can fall within “information”.
• The Court reasoned that limiting “information” to individual posts/messages would unduly narrow Section 69A and risk rendering it ineffective against systemic, architecture-enabled harms.

On this basis, the Court concluded MeitY had the legal competence under Section 69A to direct blocking of public access to Telegram as a whole (temporarily, in this case).

C. Proportionality of a temporary platform-wide block + disabling message-editing

The Court’s proportionality conclusion rests on a fact-specific assessment captured in the orders and accepted by the Court:

• Legitimate aim: protect integrity of NEET UG, 2026 re-examination; prevent fraud; avert public-order disruption.
• Rational nexus: blocking the platform and disabling message-editing were linked to curbing rapid, large-scale dissemination and alleged “backdating”/misleading artifacts.
• Necessity / least restrictive measure (in context): the Government’s case (accepted by the Court) was that channel-by-channel takedowns were repeatedly defeated by mirror/backup channels, bots, auto-rotated handles, and audience migration mechanisms.
• Tailoring: the block was time-limited till 22.06.2026 (immediately around the 21.06.2026 exam), while message-editing disablement was limited till 30.06.2026; the Court treated this temporal limitation as strong evidence of narrow tailoring.

Critically, the Court treated Telegram’s platform characteristics (cloud-based architecture, large broadcast channels, bot ecosystem, username-based concealment, rapid reconstitution of networks, and message-editing risks) as the differentiating factual foundation for why narrower measures were inadequate in the immediate timeframe.

3.3 Impact

1) Doctrinal impact: platform-wide blocking is within Section 69A (subject to safeguards)

A key legal takeaway is the Court’s explicit endorsement that Section 69A’s “any information” can encompass an entire software application/platform. This interpretation potentially widens the operational scope of Section 69A beyond content-item or URL-level blocking, especially where authorities present an “architecture-driven” systemic risk narrative.

2) Process impact: emergency interim orders can be leaner, final orders can be fuller

The judgment signals that in Rule 9 emergencies, an interim order need not resemble a fully reasoned final order so long as it records sufficient satisfaction and is followed by prompt post-decisional hearing and a reasoned final determination under the 2009 Rules.

3) Future litigation impact: proportionality will turn on evidentiary demonstration of “ineffectiveness of narrower measures”

The judgment places practical emphasis on whether targeted takedowns are shown (with material) to be ineffective due to re-emergence mechanisms, scale, and time sensitivity. Future challenges to platform-level measures will likely pivot on the quality of the record demonstrating: (a) attempted narrower measures, (b) measurable re-emergence, and (c) time-linked urgency.

4) Regulatory impact: “feature-level” restrictions as a proportionality tool

The directions included not only blocking access but also disabling a specific feature (message editing). The judgment treats feature disablement as a potentially “narrowly tailored” intervention when the feature is linked to the identified harm (here, alleged backdating/misleading artifacts).

4. Complex Concepts Simplified

• Section 69A blocking: A statutory power allowing the Government to direct intermediaries/ISPs to block public access to “any information” through a computer resource, on specified grounds (including public order), with reasons recorded and procedural safeguards under the 2009 Rules.
• Rule 9 (Emergency) under the 2009 Rules: A mechanism for interim blocking when delay would harm the objective. It is typically followed by rapid review through the Rule 7 Committee and a post-decisional hearing leading to confirmation or revocation.
• Non-application of mind: A ground to invalidate administrative action where the authority appears to mechanically reproduce statutory language without engaging with facts/material. Here, the Court found adequate factual linkage in the interim order, supplemented (as contemplated by the scheme) by a detailed final order after hearing.
• Proportionality (from Anuradha Bhasin v. Union Of India, (2020) 3 SCC 637): A structured test asking whether (i) the aim is legitimate, (ii) the measure is connected to that aim, (iii) it is necessary (no equally effective but less restrictive option), and (iv) it is narrowly tailored in scope and duration.
• “Information” includes software: Because the IT Act defines information to include “codes, computer programmes, software and data bases”, the Court treated an app/platform as falling within the definition—enabling platform-wide blocking under Section 69A in appropriate cases.

5. Conclusion

The Delhi High Court’s decision in TELEGRAM FZ LLC & ANR. v. UNION OF INDIA & ORS. upholds emergency, time-bound platform-wide blocking under Section 69A where authorities demonstrate (and record) a public-order-linked threat, the ineffectiveness of narrower measures, and tight tailoring to an event-specific window. The judgment’s most consequential legal proposition is its expansive construction of “information” under the IT Act to include an entire software application/platform—thereby confirming that Section 69A can extend beyond item-level content blocking to platform-level access restrictions, subject to the statutory safeguards and constitutional proportionality review anchored in Anuradha Bhasin v. Union Of India, (2020) 3 SCC 637.