TECH POLICY LAW

I. The Provision That Deserves the Most Attention Is Getting the Least

Of every item in this update cycle, Rule 3(4) carries the greatest structural significance and the least public scrutiny relative to that significance. Takedown timelines generate headlines because they are numerically dramatic. Rule 3(4) generates comparatively little coverage because its mechanism, tying safe harbour to compliance with ministry advisories, is procedurally abstract. Abstraction is not a measure of importance. This provision, if notified, would change the fundamental character of intermediary liability in India more than any timeline compression could.

II. From Judicial Notice to Administrative Preference

Section 79(3)(b), as read down in Shreya Singhal, conditions the loss of safe harbour on an intermediary's failure to act on actual knowledge, defined as a court order or a notification from the appropriate government following the procedures the Constitution permits. Rule 3(4) would fold MeitY's own clarifications, advisories, SOPs, and codes of practice into that due-diligence calculus, instruments that carry no comparable procedural formality, no requirement of judicial or quasi-judicial process, and no fixed content. An intermediary's safe harbour would depend not on compliance with a legal order but on staying current with, and correctly interpreting, an evolving stream of ministry communications that can be issued and revised without notice-and-comment rulemaking.

III. Separate Notification as a Deliberate Choice

MeitY's reported preference to notify Rule 3(4) separately from the broader package of draft amendments, rather than folding it into the ordinary consultation and notification process those amendments are undergoing, is itself a signal worth reading carefully. A government official's stated rationale, that separate notification "could ensure compliance begins at the earliest," is an admission that the ordinary process would delay the provision's effect. Procedural expedience of this kind is generally deployed when a provision is expected to face resistance during a fuller consultation process, not when it commands broad stakeholder agreement. Civil society submissions on the broader draft amendments, including the Internet Freedom Foundation's formal comments urging complete withdrawal of Rule 3(4), have already signalled exactly the resistance a separate, expedited notification would be designed to bypass.

IV. The Written-Basis Safeguard Is Thinner Than It Looks

Rule 3(4)(b)'s requirement that any advisory be issued in writing, identify its legal basis, and remain consistent with the parent Act and Rules is frequently cited as a meaningful constraint. It is a weaker safeguard than its drafting suggests. "Consistent with the parent legislation" is precisely the standard that will be contested case by case, likely only after an intermediary has already lost safe harbour and faces liability, since there is no ex ante mechanism for challenging an advisory's legal basis before compliance is required. The safeguard operates as a defence available in subsequent litigation, not as a gate that prevents an overbroad advisory from taking effect in the first place.

V. Comparative Note

The comparison to Section 230 of the US Communications Decency Act is instructive precisely because Section 230 immunity is unconditional on any executive instruction whatsoever; a platform's protection from liability for third-party content does not turn on whether it heeded a federal agency's non-binding guidance. Rule 3(4) moves the Indian framework in the opposite direction, making safe harbour conditional on ongoing deference to an executive body's evolving preferences rather than on a fixed statutory standard. This is not merely a difference of degree between two intermediary liability regimes; it is a difference in what safe harbour means as a legal concept, a stable entitlement in one system, a continuously renewable licence in the other. Critics who invoke Shreya Singhal against Rule 3(4) are making precisely this point in doctrinal terms: that judgment fixed the boundary of due diligence at judicial and formally notified government orders specifically because a broader standard would let executive preference substitute for judicial process, and Rule 3(4) reopens exactly that boundary the Court closed.

VI. Practitioner Guidance

Clients should track MeitY's rule-making activity on this specific provision as a standalone monitoring item, separate from the broader IT Rules amendment package, given the indicated intent to notify it independently and potentially with limited advance notice. Intermediaries should begin building an internal process for tracking, logging, and assessing legal basis for every MeitY advisory and SOP received, regardless of whether Rule 3(4) is ultimately notified, since the compliance infrastructure required either way is the same and is better built ahead of a binding deadline than in response to one. Where an advisory's stated legal basis appears doubtful under Rule 3(4)(b)'s own written-basis requirement, clients should document that assessment contemporaneously rather than waiting until a safe harbour dispute makes the question urgent, since a real-time record of reasoned non-compliance is a materially stronger position than an after-the-fact justification constructed once liability is already in issue.