A quiet feature update with an unquiet implication
On September 21, 2026, X expanded its "Under the Hood" transparency tool so that eligible users — accounts at least a year old that posted 10 or more times in the prior month — can download a report showing whether any of their posts were withheld to comply with a government's legal demand, and which country made it. X framed the move as a response to "people's appreciation of more transparency into government-required content filtering," per its September 19 announcement on the X Open Source account (TechCrunch). It is a modest, mechanical change: a JSON file, not a dashboard. But it lands directly on top of a legal fault line that India has spent a decade trying to paper over.
The collision X didn't mention
Section 69A of India's Information Technology Act, 2000 lets the central government order any intermediary to block content on grounds spanning sovereignty, security, public order, and incitement to cognizable offences (Section 69A text, Indian Kanoon). The procedure for issuing those orders is governed by the Information Technology (Procedure and Safeguards for Blocking for Access of Information by Public) Rules, 2009 — and Rule 16 of those rules mandates that "all information relating to the request and complaint received and the actions taken in each case shall be confidential." As MediaNama first flagged, this creates a direct incompatibility: if X's report tells an Indian user their post was withheld and names India as the requesting country, that disclosure is itself information about a blocking action — precisely what Rule 16 was written to suppress (MediaNama). A ministry official told PTI, per MediaNama's reporting, that X "will have to comply with Indian law" — but neither X nor the Ministry of Electronics and IT has said how a per-country transparency report squares with a rule built on non-disclosure by design.
Why the confidentiality rule exists — the steelman
It's worth stating the government's strongest case fairly before dismantling it. Section 69A orders sometimes concern live national-security matters, ongoing investigations into terrorism financing, or content tied to communal violence where premature disclosure of which government requested a takedown, or the existence of a request at all, could tip off bad actors, compromise intelligence sources, or itself inflame the underlying unrest. Confidentiality provisions in blocking regimes are not unique to India — many democracies restrict disclosure of national-security-linked orders for similar reasons, at least for a limited window. A blanket, permanent gag, however, is a different animal from a time-boxed one, and that is where India's regime has drawn sustained legal fire.
The courts are already circling
This isn't a hypothetical tension — it's already in litigation on two fronts. The Software Freedom Law Centre filed a public interest petition (W.P.(C) 161/2025) before the Supreme Court in February 2025 challenging Rules 8 and 16 as violations of Articles 14, 19, and 21, arguing Rule 16 "enforces secrecy, preventing affected users from knowing or challenging content removal" and produces a chilling effect on speech; the Court issued notice to the Union government and MeitY on March 3, 2025 (SFLC.in litigation tracker). Separately, X Corp itself is fighting the government in the Karnataka High Court over the "Sahyog" portal, arguing the government is using Rule 3(1)(d) of the 2021 IT Rules to issue blocking-equivalent orders that bypass Section 69A's own (thin as they are) procedural safeguards entirely — creating, in X's words, two parallel blocking tracks that "eviscerate" the statute (LiveLaw). Under the Hood doesn't create this fight. It hands the Supreme Court's petitioners a live, user-facing demonstration of exactly the harm they're alleging.
What proportionate regulation actually looks like
We've argued before that content-moderation transparency is a net public good, not a threat to platform operations or national security when implemented with reasonable safeguards — and X's move here, imperfect as it is, is directionally correct. The proportionate fix isn't to force X to strip India from its report, nor to accept indefinite blanket secrecy. It's what the SFLC petition and the Delhi High Court's Tanul Thakur v. Union of India line of reasoning both point toward: publish an anonymized aggregate count of Section 69A orders and their broad legal basis on a rolling delay, while keeping genuinely sensitive operational details (specific investigations, sourcing) confidential. Several democracies already do a version of this for national-security-linked orders — confidentiality calibrated to actual harm, not a permanent default. Absolute secrecy protects bureaucratic convenience, not security; it also breeds exactly the assumption of overreach that platforms like X, and courts, are now being forced to litigate in public.
The bigger picture
X's transparency expansion isn't really an India story — it's a stress test that happens to have found India's regime first, because India's confidentiality rule is unusually absolute and unusually contested in court right now. Other jurisdictions with less categorical secrecy mandates will not generate the same collision. But every government that relies on opaque takedown mechanisms should read this as a preview: platform-side transparency tooling is getting better and cheaper to ship, and it will keep surfacing exactly the gaps that confidentiality rules were built to hide. The Supreme Court's ruling on Rule 16, whenever it comes, will now be adjudicating a live product feature, not an abstract harm.