A Look at Upcoming Innovations in Electric and Autonomous Vehicles India's MIB Demands Telegram Build Piracy Filters. The Law May Not Allow It.

India's MIB Demands Telegram Build Piracy Filters. The Law May Not Allow It.

A four-page notice from India's Ministry of Information and Broadcasting, issued on July 4 and brought to public attention by the Internet Freedom Foundation, has directed Telegram to build, deploy, and report on proactive content-detection systems within 15 days - targeting pirated films, web series, and OTT content circulating through the platform's channels, groups, and bots. The demand is sweeping. According to digital rights advocates and independent legal experts, it may also exceed the ministry's authority by a considerable margin.

What the Notice Actually Demands

The MIB notice, issued under Rule 3(1)(d) of the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021, accuses Telegram of enabling the spread of pirated content through mirror channels, successor groups, and automated bots designed to redistribute infringing material after earlier copies are taken down. It directs the platform to detect, report, disable, and remove such content; to act against repeat infringers including administrators and "associated entities"; to share its grievance-redressal mechanisms with rights holders, OTT platforms, and law enforcement; and to file an Action Taken Report within a fortnight. This is not MIB's first move against Telegram on piracy grounds - a March notice had identified over three thousand piracy channels - but the July notice goes significantly further by demanding that Telegram construct proactive filtering infrastructure rather than respond to individual takedown requests.

Where the Legal Argument Breaks Down

The rule cited in the notice does not say what MIB appears to believe it says. Rule 3(1)(d), read alongside Section 79(3)(b) of the IT Act, requires a platform to remove content once it has "actual knowledge" of a violation through a court order or government notification. Crucially, neither provision creates any obligation to scan proactively for content before it is flagged. The Supreme Court of India made this boundary explicit in its 2015 Shreya Singhal judgment, holding that an intermediary loses safe harbour - its statutory immunity from liability for user content - only when it fails to act on a court or government order. Mandating that platforms surveil their own infrastructure in anticipation of unlawful content was, the Court indicated, precisely the kind of obligation that safe harbour is designed to prevent from arising.

There is exactly one rule in the IT Rules framework that requires platforms to proactively search for and remove a category of content without waiting for a complaint: Rule 4(4), which applies exclusively to child sexual abuse material. No equivalent provision exists for pirated entertainment. The government's broader argument - that a platform's duty to make "reasonable efforts" against unlawful content under Rule 3(1)(b) implicitly requires proactive prevention - is itself the subject of a live constitutional challenge in the Karnataka High Court, in the case of X Corp v. Union of India.

The jurisdictional question compounds the legal uncertainty. Telegram is a messaging intermediary regulated by the Ministry of Electronics and Information Technology under the IT Rules. MIB's mandate covers news publishers and OTT platforms; Telegram is neither. IFF has raised this objection formally, noting that the notice was not published - a procedural irregularity that itself raises accountability concerns - and asking the ministry to confirm its legal basis before any compliance response is expected. Legal experts cited by Exchange4media have independently reached the same conclusion about the jurisdictional mismatch.

Why 15 Days Is Not an Engineering Timeline

Even setting aside the legal objections, the operational demand is difficult to take at face value. Building a functional content-fingerprinting system is not a fortnight's work. YouTube's Content ID - the most widely recognised automated rights-management system in operation - required years of development and expenditure in excess of a hundred million dollars to build, and it remains limited to detecting matches against a pre-registered content library. It cannot determine whether a user holds a licence for the content or whether a given use qualifies as fair dealing under copyright law.

Telegram's architecture presents additional obstacles. The platform forwards, re-encodes, and renames files as a routine function, which degrades the reliability of fingerprinting techniques that depend on consistent file characteristics. More fundamentally, Telegram's secret chats are end-to-end encrypted; scanning them for infringing content would require breaking that encryption. What a rushed compliance effort could realistically produce, IFF argues, is a blunt filtering mechanism that suppresses lawful speech - reaction videos, parodies, commentary - to avoid enforcement risk. India's Copyright Act already protects such uses under Section 52's fair dealing provisions, but an automated filter has no mechanism for making that legal determination.

A Pattern, Not an Isolated Notice

IFF has framed the July notice as the third significant government action against messaging platforms within a two-week period, following a week-long Telegram block that ended on June 22 and separate MeitY notices to WhatsApp, Telegram, and Signal concerning username features. Taken together, these actions suggest a shift in regulatory posture - one that moves from responding to specific violations toward demanding that platforms redesign their moderation architectures to the executive's specification, without clear statutory authority and outside the normal process of published rulemaking or court supervision.

Copyright enforcement in India is not without lawful mechanisms. Rights holders have long obtained site-blocking orders and John Doe injunctions - court orders against unnamed infringers - through civil proceedings. Those routes involve judicial oversight, published orders, and avenues for affected parties to contest the action. Routing enforcement through an unpublished ministerial notice accelerates the process but strips it of accountability. The IFF has called on MIB to publish the notice, specify the legal provision that authorises its demands, and explain why it - rather than MeitY - has the standing to direct a messaging intermediary. Until those questions receive clear answers, the notice sits in contested legal territory, regardless of the legitimacy of the underlying concern about piracy.