A four-page notice issued on July 4 by India's Ministry of Information and Broadcasting has ordered Telegram to build content-detection and removal systems targeting pirated films, web series, and OTT content - and to file an Action Taken Report within 15 days. The Internet Freedom Foundation, which obtained and published the notice, has challenged it on grounds that it exceeds the ministry's legal authority, conflicts with Supreme Court precedent, and was never made public. The demand is not merely aggressive; legal experts and digital rights advocates argue it is built on the wrong law, issued by the wrong ministry, and asks for something that cannot be built in a fortnight.
What the Law Actually Permits - and What It Does Not
The notice invokes Rule 3(1)(d) of the IT Rules, 2021, which requires an intermediary to act on content once it has "actual knowledge" through a court order or government notification. That is a reactive obligation: receive notice, then act. The MIB notice demands something categorically different - that Telegram proactively detect, report, disable, and remove infringing content before any rights holder complains, and prevent re-uploads across mirror channels, successor groups, and bots.
That distinction matters enormously. In its 2015 Shreya Singhal ruling, the Supreme Court held that a platform forfeits its safe harbour - the statutory immunity from liability for user-generated content under Section 79 of the IT Act - only when it ignores a court or government order to take down specific content. The Court's logic was deliberate: requiring platforms to proactively scan everything would make safe harbour meaningless. The government's counterargument, that the Rule 3(1)(b) duty to make "reasonable efforts" against unlawful content implies a proactive obligation, is currently being tested in X Corp v. Union of India before the Karnataka High Court. No court has yet endorsed that reading.
There is precisely one rule in India's IT framework that mandates proactive content hunting: Rule 4(4), which applies exclusively to child sexual abuse material. Parliament drew that line deliberately. No equivalent provision exists for pirated films. Copyright law, meanwhile, already provides a functioning enforcement route through site-blocking orders and John Doe injunctions obtainable from civil courts. Rights holders use these routinely. Routing enforcement through an unpublished ministerial letter instead trades legal due process for administrative speed - and, the IFF argues, for accountability.
The Wrong Ministry, an Unpublished Letter, and Questions of Jurisdiction
The jurisdictional objection may be the most straightforward problem with the notice. Telegram is a messaging intermediary. Messaging intermediaries are regulated by the Ministry of Electronics and Information Technology under the IT Act's intermediary framework. MIB's mandate covers news publishers, OTT content platforms, and digital news outlets - categories defined under Part III of the IT Rules. Telegram fits none of them. Legal experts quoted by Exchange4media have independently raised the same question the IFF poses: on what authority does MIB direct a messaging platform to rebuild its moderation architecture?
The IFF has also flagged that the notice was never published. Government directions that impose compliance obligations on platforms are ordinarily made public so that affected parties, the press, and civil society can scrutinize them. An unpublished letter demanding infrastructure changes within 15 days, the foundation argues, is precisely the kind of executive overreach the transparency provisions of the IT framework are meant to prevent. IFF asked MIB to authenticate the notice before it would formally respond to it - a reasonable request given that the ministry had already issued a March notice against more than 3,000 piracy channels using legitimate channels.
The Technical Reality Behind a 15-Day Deadline
Even setting aside the legal objections, the operational demand is difficult to take at face value. YouTube's Content ID - the most sophisticated rights-management fingerprinting system in commercial deployment - took its developer more than a hundred million dollars and close to two decades to build and refine. It detects content matches against a reference database; it cannot determine whether a given upload is licensed or whether it qualifies as fair dealing under Section 52 of the Copyright Act, 1957.
Telegram presents additional structural obstacles. The platform forwards, re-encodes, and renames files in transit, disrupting the consistent file signatures that fingerprinting systems rely on. Secret chats use end-to-end encryption, meaning no server-side scanning is possible without breaking that encryption entirely - a consequence that would affect every user on the platform, not only those sharing infringing content. What Telegram could plausibly construct in 15 days, the IFF concludes, is a blunt instrument that removes lawful speech to reduce compliance risk. Reaction videos, commentary, parody, and other content protected under Section 52's fair dealing exception would be the collateral damage.
A Pattern Wider Than One Notice
The IFF has situated this notice within a sequence of government actions against major messaging and social platforms over a compressed period. It follows a week-long Telegram service disruption that ended on June 22, and username-feature notices that MeitY sent to WhatsApp, Telegram, and Signal. Taken together, the foundation characterises these as evidence of accelerating pressure on digital intermediaries - pressure applied through administrative letters rather than legislation, and often without the publication and procedural safeguards that lawmaking requires.
The concern is structural, not merely tactical. When a ministry can direct a platform to build a private filtering infrastructure through an unpublished notice - without clear statutory authority, without judicial oversight, and on a timeline no engineer could meet responsibly - the legal framework governing digital intermediaries is being stretched well past its designed limits. The IFF's phrase "digital licence raj" is pointed: it invokes a historical analogy to a regulatory environment where arbitrary administrative discretion substituted for transparent rules. Whether or not that framing ultimately prevails in court, the underlying question it raises is genuine and unresolved. What India's government can actually require platforms to build, and on whose authority, remains a matter of active constitutional litigation - not settled law.
