Examine whether judicially ordered takedowns of online content are consistent with the safeguards laid down in *Shreya Singhal v. Union of India*.
New · District CollectorCan you hold the district for 72 hours?Floods, a heatwave, an outbreak, a grievance queue. Take the decisions, see the consequences.Play →In this answer
In Shreya Singhal v. Union of India (2015), the Supreme Court struck down Section 66A of the IT Act. It upheld Section 69A blocking because that power is narrowly drawn and has procedural safeguards [1]. Court-ordered takedowns fit within this framework in principle, but many individual orders fall short of its standards.
Safeguards laid down in Shreya Singhal
- Grounds limited to Article 19(2): sovereignty, security of the State, public order and friendly relations with foreign States [2]. Causing offence or annoyance is not a valid ground [1].
- Due process: written reasons, review by a committee, and notice to the originator or platform, which the 2009 Blocking Rules set at no less than 48 hours [3].
- Section 79(3)(b) read down: platforms must remove content only on a court order or government notification [1].
Where judicial takedowns are consistent
- The judgment itself names a court order as a valid trigger for removal [1]. The IT Rules, 2021 build platforms' takedown duties on the same basis [4].
- Transparency and hearing: court orders are public, reasoned, open to appeal and made after hearing both sides. Section 69A orders stay confidential under Rule 16 [3].
Where they fall short
- Ex parte interim orders: urgent mentioning can lead to removal before the originator is heard. This skips the hearing the Rules require [3].
- Drift in grounds: some pleas rest only on offence. The 2026 plea against Giacomo Filibeck's "Vote Chor, Gaddi Chhod" slogan calls it "derogatory" and "prejudicial" [5]. Neither label is an Article 19(2) ground [1].
- Blanket scope: orders covering "all videos" or future re-uploads are not narrowly tailored.
- Bypassing the statute: direct petitions by people who were not harmed skip the Section 69A process [2]. This risks a chilling effect and makes courts the first-stage censors.
- Viewers' rights: a foreign speaker may lack Article 19 rights, but a takedown still limits Indian citizens' right to receive information.
Way forward
- Orders should name specific URLs, give reasons and cite a precise Article 19(2) ground.
- The originator and platform should get notice. Interim orders should be time-bound, with a quick hearing after removal.
- Petitioners should first be sent to the Section 69A route unless they show urgent harm.
Judicial takedowns are consistent with Shreya Singhal in principle but not always in practice. Courts should apply to their own orders the narrowness, reasons and hearing they demand of the executive. Takedowns can then prevent real harm while keeping Article 19(1)(a) intact, which is the balance the Court struck in 2015.
Sources
- 1Shreya Singhal v. Union of India, W.P. (Crl.) No. 167 of 2012, Supreme Court judgment (24 March 2015)Section 69A upheld as narrowly drawn; offence or annoyance not a ground; Section 79(3)(b) read down to court or government orders
- 2Information Technology Act, 2000, Section 69A, India Codegrounds for blocking; the statutory blocking route
- 3IT (Procedure and Safeguards for Blocking for Access of Information by Public) Rules, 2009, Gazette notification, India Codecommittee review, 48-hour notice and hearing, Rule 16 confidentiality
- 4The IT (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021, PRS Legislative Researchplatforms' duty to remove content on court or government orders
- 5Italian politician's remark: Supreme Court agrees to hear plea to take down videos of Giacomo Filibeck's comments at Bharat Summit, The Hindu (November 2026)the plea's "derogatory" and "prejudicial" description of the slogan (the search tool cannot reach thehindu.com, so this links the site's home page; the article's exact URL is in the study note but I couldn't check it)