TECH POLICY LAW

I. A Republication, Not a Reform

MeitY's 6 August press release announced nothing new. The three hour and two hour windows it describes were fixed by the February 2026 amendment to the IT Rules, in force since 20 February. What changed on 6 August was tone, not text. A ministry does not reissue a six month old rule through a press release unless it wants a particular audience, platforms, state police, or both, to treat enforcement as imminent rather than theoretical. Practitioners should read the reiteration as a signal of enforcement intent, and advise clients accordingly, rather than treat it as a fresh compliance event requiring a new gap analysis.

II. The Arithmetic Platforms Actually Face

A three hour window sounds administratively trivial until the underlying workflow is mapped. An intermediary must receive the order, route it to a legal or trust and safety desk, verify the order's authenticity and jurisdictional basis, assess whether the content in fact falls within the order's description, and execute removal, all within a period shorter than a typical internal escalation chain for a mid sized organisation. The prior 36 hour window, itself already compressed relative to global norms, at least permitted a same day human review cycle. Three hours effectively forces either round the clock legal staffing, which only the largest platforms can sustain, or automated compliance that removes first and evaluates the order's validity after the fact. The rule does not distinguish between the two paths. It simply penalises whichever platform picks wrong.

III. Grievance Redressal Cuts Both Ways

Less discussed is the parallel reduction in grievance redressal timelines, from 72 hours to 36. This change is not obviously adversarial to platforms; it also compresses the government's own patience for slow-walked user complaints. A grievance officer regime that must respond within 36 hours needs staffing depth that many mid tier intermediaries, particularly domestic ones without global trust and safety budgets, do not currently carry. The amendment therefore imposes a disproportionate compliance burden on Indian platforms relative to well resourced multinational ones, an outcome that sits uneasily with the government's simultaneous rhetoric about supporting domestic technology companies.

IV. The Litigation Backdrop MeitY Is Not Mentioning

The 6 August reiteration arrives while the Supreme Court has separately stayed multiple High Court challenges to the broader Section 79(3)(b) takedown framework and the Sahyog portal, brought by DigiPub News India Foundation, Kunal Kamra, and others. Those petitions argue that the underlying rule making exceeds what Shreya Singhal permits for court-ordered versus government-ordered takedowns. MeitY's decision to republicise the compressed timelines while that litigation is pending, rather than after resolution, suggests confidence that the Supreme Court will not disturb the operative timelines regardless of how it rules on procedural safeguards. Clients should treat the current three hour and two hour windows as durable compliance baselines and not defer implementation in anticipation of judicial relief.

V. Comparative Note

The compressed timeline invites comparison to the European Union's approach, which is instructive precisely because of how narrow the EU's one hour standard actually is. The EU mandates one hour removal only for terrorist content referred by a designated national authority under a dedicated regulation, a category defined with judicial precision and referred by a limited set of competent authorities. India's three hour rule applies to the entire universe of content a court or "appropriate government" official deems unlawful, a category with none of the narrow definitional discipline the EU regime relies on to make its faster clock workable. The comparison that flatters India's approach as merely matching global best practice does not survive contact with the actual scope of each rule. The Digital Services Act, notably, avoided fixing any general hourly deadline at all, requiring only that removal occur "in a timely manner" once a trusted flagger's notice is received, precisely because Brussels concluded during the DSA's drafting that a rigid clock applied broadly, rather than to a narrow, pre-defined category, forces platforms toward reflexive removal rather than considered assessment. India has effectively taken the DSA's narrowest emergency provision and applied it as the general rule.

VI. Practitioner Guidance

Clients operating intermediary services in India should treat this reiteration as confirmation that MeitY intends active enforcement, not as an isolated communications exercise. Compliance programmes should assume the three hour and two hour clocks start the moment an order is received by any employee, not merely the designated grievance officer, and should build a triage protocol that can make a preliminary removal decision within the first ninety minutes to preserve time for legal escalation on genuinely contestable orders. Firms without existing after hours legal coverage should treat that gap as the single highest priority remediation item arising from this update, ahead of any documentation or policy revision work. Documentation of the triage process itself, timestamped logs showing when an order was received, when it was assessed, and when action was taken, will matter more than the substantive correctness of any individual decision if the matter is later contested, since a demonstrable good-faith process is the strongest available defence against an allegation of deliberate delay.