The chairman of Parliament’s IT panel told reporters that Mark Zuckerberg should apologise for the temporary removal of a reel by Prime Minister Narendra Modi, and he warned that safe harbour under Section 79 could be taken back if that apology does not come, according to the source. The same account says Meta apologised in the meeting, attributing the removal to an algorithmic error, and that opposition MPs pushed back against any move to revoke safe harbour. That is the episode. The larger question is what safe harbour is in India, and who can touch it.

What Section 79 Actually Says

Per the source, Section 79 of the IT Act grants intermediaries immunity from liability for third-party content, provided they comply with due diligence requirements and lawful government directions. That is the perimeter. It is not a blanket pass for everything a platform does, and it sits on top of obligations that the government can lawfully set. The source does not go beyond that summary, and it does not reproduce the text of Section 79, but it does put the two key conditions on the table, due diligence and lawful directions.

That framing matters in this week’s controversy. The source account describes a brief removal of a Prime Ministerial reel, a request from the government for an explanation, and a meeting with platforms and ministries. Within that context, the warning about safe harbour is a political and procedural signal. It is not, on the face of the source, a change in a platform’s legal status. The report does not say safe harbour has been lost. It does not describe any document that would do that work.

A warning can change a room. It does not, by itself, change a law.

Who Can Actually Strip It

The source places the comments with the chairman of the Parliamentary Standing Committee on Communications and Information Technology. Parliamentary committees in India question officials, summon companies, and write reports, but this article does not say the committee issued a legal directive. It quotes the chairman’s remarks to reporters and notes that the meeting included senior officials from Meta, Google, YouTube, X and Snapchat, along with representatives of MeitY and the MHA. It also says the government sought an explanation after the reel’s removal.

Just as important is what the source does not say. It does not cite a court order. It does not describe a notice that strips safe harbour. It does not report a formal regulator action. It states that Section 79 immunity exists, conditioned on due diligence and lawful directions, and it relays a warning from a panel chief. Those are different things. A panel statement creates pressure, but it is not the same as an adjudication.

Opposition MPs, the article notes, opposed any move to revoke Meta’s protection and contextualised the conversation within broader regulatory concerns like child sexual abuse material, deepfakes and cyber fraud. That skirmish underscores the politics around safe harbour. Immunity is a legal shield for intermediaries, but fights about it are often framed as fights about power, speech and platform responsibility.

How The Reel Dispute Was Framed In The Room

According to MPs present, the report says, Meta apologised in the meeting and attributed the takedown to an algorithmic error. One MP is quoted describing that apology and an assurance that Meta would amend its algorithm. Meta did not respond to the publication’s request for comment. The committee, per the chairman’s opening remarks summarised in the piece, sought a complete audit trail of the removal and restoration of the reel and asked Meta what safeguards it had introduced to prevent similar incidents.

This is the pattern the source allows us to describe. An episode triggers scrutiny, the government seeks an explanation, a committee stages a meeting with major platforms and ministries, and the platform at the center offers an apology and a diagnosis of what went wrong, in this case an algorithmic error according to MPs present. No further facts about internal decision-making are provided in the source.

What Safe Harbour Does Not Do

The temptation in a high profile takedown is to treat safe harbour like a switch. The source provides a narrower view. It says the immunity exists for third-party content, as long as due diligence and lawful directions are followed. That is a rules based posture, not a blanket for any action a company or user takes. The article does not say that safe harbour guarantees the permanence of any given post, nor does it say that removing a post triggers automatic loss of protection. It does not outline any threshold that would lead to revocation. It does not describe any immediate enforcement mechanism in the hands of a parliamentary committee. Those absences are telling about the limits of what is known from this episode.

The Broader Agenda In The Meeting

The chairman’s remarks, as summarised in the article, suggest the committee’s review went beyond the Prime Minister’s post. The report lists cyber fraud, misinformation, deepfakes, AI-generated content, platform transparency and compliance with Indian laws as topics that came up. That matters, because it shows the conversation was not only about one reel. It was also about the ongoing friction between large platforms and lawmakers over a growing list of harms and responsibilities.

Opposition MPs in the same meeting, according to the report, supported stronger regulation in areas like CSAM and fraud, but argued that criticism of the government should not be treated as anti-national content. One MP is quoted as saying this is about regulating technology and not democracy. The debate over safe harbour sits inside that larger disagreement over what counts as harm and how the state should respond.

The Bottom Line

From the single source here, three things are clear. First, Section 79 safe harbour exists as immunity for third-party content, conditioned on due diligence and lawful directions. Second, the committee chairman issued a warning and sought an apology, which is pressure but not the same as a legal decision. Third, Meta apologised in the room according to MPs, calling the removal an algorithmic error, and the committee asked for an audit trail and safeguards. Everything beyond that would be speculation, and this moment already has enough of the real thing.