IT Act Section 79: How It Forces Platforms to Remove Content Within 36 Hours

What Section 79 of the IT Act Actually Does

Those conditions are not unconditional, and that is where the power lies for content removal. Section 79(3) of the IT Act states that a platform loses its safe harbour the moment it receives "actual knowledge" of unlawful content and fails to expeditiously remove or disable access to it. The IT (Intermediary Guidelines and Digital Media Ethics Code) Rules 2021 — the subordinate legislation under Section 79 — define precisely what constitutes "actual knowledge" for this purpose.

Under Rule 3(1)(d) of the 2021 Rules, actual knowledge is deemed to arise when a platform receives a complaint from a user in the prescribed format, or when a government authority or court issues a direction to remove specific content. A properly formatted legal notice sent by a practising advocate identifying unlawful content by specific URL and ground of complaint constitutes the triggering event for actual knowledge — and the 36-hour removal obligation attaches from that point.

The implication is significant and frequently misunderstood: platforms do not need to be told to remove content under a court order for this mechanism to apply. A pre-litigation legal notice — if properly drafted, correctly addressed, and sent by a qualified practising advocate — is sufficient to create the platform's legal removal obligation. Court orders are the escalation path when platforms refuse to comply with the notice, not the prerequisite for sending the notice.

The 36-Hour Rule: Where It Comes From and What It Covers

Rule 3(1)(d)(i) of the IT (Intermediary Guidelines and Digital Media Ethics Code) Rules 2021 specifies that where a complaint relates to content falling under specified categories — including sexually explicit material involving minors, content affecting sovereignty and integrity of India, and content violating privacy — the platform must acknowledge the complaint within 24 hours and act on it within 36 hours.

For defamation-related content, the specific timeline is different. Rule 3(2) requires platforms to acknowledge complaints within 24 hours and resolve them within 15 days as a standard. However, for categories specified under Rule 3(1)(d) — which includes content that threatens public order, promotes enmity, or constitutes gross defamation — the 36-hour removal obligation applies.

In practice, a formal IT Act notice sent by a practising advocate identifying content as grossly defamatory and demanding removal creates significant pressure for expedited action regardless of the precise regulatory timeline. The consequence of non-compliance — loss of safe harbour and potential liability as a defamation publisher — incentivises platforms to process advocate-sent notices more rapidly than user-submitted reports.

The distinction between a user's complaint and an advocate's formal legal notice is critical in practice. User reports go through automated systems and are routinely rejected when they cannot establish a clear platform policy violation without external legal analysis. Legal notices from practising advocates are escalated to a platform's in-house legal team, which assesses them under the actual legal framework rather than the automated content policy checklist. This creates a fundamentally faster and more effective process.

What a Valid Section 79 Notice Must Contain

A notice that validly invokes Section 79 and creates the platform's compliance obligation must: (1) be sent by a practising advocate registered with the Bar Council of India, (2) identify the specific URL or URLs containing the unlawful content, (3) quote the specific defamatory passage or identify the content with sufficient specificity, (4) state the legal ground — defamation under IPC Sections 499 and 500 or BNS Section 356, privacy violation under Section 66E, obscenity under Section 67, or other applicable provision, (5) be addressed to the platform's Grievance Officer or legal department at the correct address, and (6) demand specific action — removal of the content, de-indexing from search results, or both — within a defined timeline.

The notice must be sent in a manner that creates a verifiable delivery record. A WhatsApp message, standard email to a general support address, or verbal communication does not constitute effective service of an IT Act notice. Registered post with acknowledgement due, email to the designated legal or grievance address with read receipt, or courier with delivery confirmation are the appropriate service methods.

A deficiency in any of these elements weakens the notice's legal effect. A notice that correctly identifies the content but fails to invoke the specific statutory provision gives the platform's legal team an argument for treating it as a general user complaint rather than a formal legal demand. A notice that invokes the IT Act but is sent to a general customer service address — rather than the designated Grievance Officer — may be legitimately routed to the content moderation team rather than the legal team, resulting in automated rejection.

RepuLex's legal notices are drafted by practising advocates who prepare dozens of IT Act notices annually. The notice is structured to maximise the legal pressure on the platform, anticipate its standard responses, and create the strongest possible record for subsequent court proceedings if voluntary compliance is refused.

What Happens After the Notice Is Sent

After a valid Section 79 notice is received by the platform, three outcomes are possible. First: the platform removes the content within the notice period. This is the most common outcome for properly served notices addressed to responsive platforms like Instagram, Facebook, and Indian news portals with active legal departments. The content is deleted at source, the URL becomes inaccessible, and Google's recrawl eventually removes the search result. RepuLex files a concurrent de-indexing request directly with Google to accelerate this final step.

Second: the platform removes the content but challenges the legal basis of the removal — this is uncommon but occurs occasionally with platforms that have strong editorial positions. In these cases, RepuLex secures the removal as a fact and documents it, which serves the client's immediate practical need even if the legal argument continues separately.

Third: the platform refuses to comply or does not respond within the notice period. This is the escalation trigger. RepuLex prepares and files an application before the competent High Court for an interim injunction directing the platform to remove the content. The application is made on the strength of the IT Act notice (which establishes actual knowledge and the platform's failure to act), the evidence of harm from the content, and the prima facie case for defamation. Indian High Courts — particularly Delhi, Bombay, and Karnataka — have a consistent and established practice of granting urgent injunctions in digital defamation matters.

The combination of notice and escalation paths creates a system where voluntary compliance is incentivised by the prospect of court proceedings, and court proceedings are made more efficient by the prior notice establishing actual knowledge. Running both paths simultaneously — notice sent and injunction application prepared but not yet filed — is the approach RepuLex uses in cases where the content harm is severe and the platform's response is uncertain.

Which Platforms Does Section 79 Apply To?

Section 79 applies to all "intermediaries" as defined in Section 2(1)(w) of the IT Act. The definition is broad: any person who on behalf of another person receives, stores, or transmits a record or provides any service with respect to that record. This covers search engines (Google, Bing), social media platforms (Facebook, Instagram, LinkedIn, Twitter/X), video platforms (YouTube), news aggregators, review sites (Glassdoor, JustDial, Sulekha), e-commerce platforms, hosting providers, and essentially any service that stores or transmits third-party content.

The key question for Indian jurisdiction is whether the platform can be reached with an Indian legal notice. Under the IT (Intermediary Guidelines and Digital Media Ethics Code) Rules 2021, intermediaries serving more than 50 lakh (5 million) users in India are classified as "significant social media intermediaries" and are required to appoint a Resident Grievance Officer based in India. Google, Facebook, Instagram, LinkedIn, Twitter/X, and YouTube all meet this threshold and have India-based Grievance Officers. A notice addressed to the India Grievance Officer of a significant social media intermediary triggers the same legal obligations as a notice to a domestic platform.

For platforms outside the significant social media intermediary category — smaller international platforms or regional portals without a dedicated India legal presence — the appropriate path is an IT Act notice to whatever address is publicly available for legal correspondence, followed by High Court application if the notice is ignored. Courts have granted John Doe orders against platforms that do not have an India presence, directing Google to de-index the content when the source platform is unreachable through standard notice.

Google and Section 79: De-indexing Without Source Removal

Google presents a specific challenge under Section 79 that is distinct from the source platform question. Google is an intermediary under Section 79 — it indexes and surfaces third-party content in its search results. A valid IT Act notice served on Google India (the Grievance Officer) can require Google to de-index specific URLs from its search results, even if the source platform has not removed the content.

This creates a two-track strategy for complete removal: notice to the source platform to delete the content, and concurrent notice to Google to de-index the URL. In cases where the source platform is non-responsive or located outside effective Indian jurisdiction, de-indexing the URL from Google search results is often achievable even when source deletion is not. The content may technically exist on an obscure server somewhere, but if it does not appear in Google search results, its practical impact on reputation is effectively eliminated.

Where Google refuses to de-index based on notice alone — which occurs primarily for content that Google's legal team assesses as potentially protected speech or public interest journalism — a High Court order directing de-indexing is the appropriate route. Delhi High Court has issued specific URL de-indexing orders against Google in several notable cases, and Google India's compliance with such orders is documented and consistent.

Section 79 vs Court Order: When Each Is Required

A Section 79 notice is the appropriate first step in almost all content removal cases. It is faster than court proceedings, costs significantly less, and produces compliance in the majority of cases where the content is clearly defamatory and the platform has a functional India legal team. The notice also creates the evidentiary record necessary for subsequent court proceedings — a platform cannot argue in court that it lacked actual knowledge of the content if it has received a formal advocate's notice identifying it.

A court order becomes necessary in three situations: first, when the platform refuses to comply with a properly served notice within the notice period; second, when the content is being published anonymously and unmasking the poster requires judicial direction (a John Doe or Ashok Kumar order); and third, when the content poses such immediate and severe harm that waiting for the notice period is not viable — in which case an ex parte interim injunction application on an urgent basis is appropriate.

The legal and practical costs of obtaining a court order are higher than notice-based compliance. A well-prepared interim injunction application takes several weeks to prepare, file, and obtain a hearing date, unless the matter is listed as urgent. Emergency cases at RepuLex — those requiring court proceedings within days rather than weeks — attract an emergency surcharge that reflects the additional advocate hours required for expedited filing and court attendance.

For most content removal cases, however, Section 79 notice compliance occurs before court proceedings become necessary. The platform's legal obligation under the IT Act, combined with the liability exposure of non-compliance, produces voluntary removal in the large majority of cases involving major Indian and global platforms. The legal escalation path exists to handle the minority of cases where platforms test their legal risk tolerance — and court outcomes in India consistently affirm the Section 79 obligation when the defamatory nature of the content is well-documented.