India Orders GitHub to Pull Dorsey's Bitchat App

What happened

Jack Dorsey says the Indian government ordered GitHub to pull the source code for Bitchat, his Bluetooth-based, mesh-network messaging app, within three hours of receiving notice. Dorsey posted the disclosure on X on Friday, July 24, 2026, sharing what he described as a government notice directing GitHub to restrict access to three Bitchat repositories.

According to The Hindu, the order came from India's Cybercrime Coordination Centre (I4C) and is dated July 23, 2026. TechCrunch, however, reports the notice originated from India's Ministry of Home Affairs. Sources differ on which body issued the directive, and it's unclear whether these refer to the same action at different stages or two separate bodies involved in the process.

Why now: a download spike and a protest

The order followed a sharp surge in Bitchat's usage in India:

India accounted for roughly 85% of Bitchat's global downloads between July 17–23, 2026.
The app was downloaded more than 91,000 times in India over five days.
Downloads jumped thirty-two-fold on July 19 compared to the prior day.
By Thursday, July 23, daily active users in India exceeded 330,000.

Separately, users at a protest organized by the Cockroach Janata Party at Jantar Mantar were reportedly seen using Bluetooth-based messaging apps after temporary internet restrictions were imposed near the protest site. The report does not explicitly confirm a causal link between the protest and the timing of the takedown order — the connection remains circumstantial.

The government's stated rationale

I4C identified Bitchat and similar apps as capable of decentralized, peer-to-peer messaging over Bluetooth mesh networks — meaning they work without mobile networks, internet access, or centralized servers. The notice reportedly cited concerns that such architecture could be misused by "anti-national elements, terrorist organisations, organised criminal groups and cyber criminals" seeking to evade lawful detection.

Bitchat's design compounds the concern for regulators: it allows anonymous communication without mandatory user registration, phone number verification, or centralized logging. The order states this significantly impedes lawful interception, attribution, and investigation by law enforcement.

Dorsey's response was blunt: "The Government of India does not like technologies like Bitchat and wants it taken down."

Pushback on legal grounds — and on effectiveness

Two criticisms have emerged. Legal expert Mishi Choudhary said the legal provisions cited do not clearly authorize removing an entire software project based on how it functions, rather than because of specific illegal content it hosts or transmits.

The Internet Freedom Foundation raised a separate, practical objection: deleting a GitHub repository doesn't delete the app from phones that already have it installed, and the mesh network keeps functioning without servers. In other words, the takedown may not meaningfully curb usage — it may simply create legal and reputational exposure for developers and platforms without achieving the stated enforcement goal.

Several factual gaps remain in the public record: whether GitHub has complied with or is contesting the order, what specific statute(s) underpin the notice, whether the three targeted repositories differ from one another, and whether other Bluetooth mesh apps flagged by I4C are also facing removal orders.

Why founders should care

This case is likely to be watched closely by anyone building decentralized, offline-capable, or privacy-by-default products — and it carries several probabilistic signals worth weighing:

Architecture-based scrutiny is plausible, not just content-based scrutiny. Regulators appear willing to target an app's capabilities (anonymous, serverless, hard-to-intercept communication) rather than waiting for evidence of specific illegal use. Founders building similar systems should probably assume this risk exists even if their product has no illicit use cases on record.
Demand for offline communication tools may be real and significant. The rapid download and usage growth suggests users value connectivity-independent messaging during disruptions — but this same visibility may also accelerate regulatory attention, so fast adoption could be a double-edged signal.
Enforcement mechanics remain legally unsettled. The dispute over whether a takedown order can compel removal of an entire codebase — versus specific content — suggests compliance obligations for decentralized-app makers are not yet well-defined in this jurisdiction, which could mean prolonged ambiguity for founders operating similar products.
Platform dependency is a distribution risk. GitHub's position as an intermediary facing a government order highlights that founders relying on major code-hosting or app-distribution platforms may be exposed to takedown risk that's outside their direct control, and worth factoring into distribution and hosting strategy.

Founders in adjacent spaces — mesh networking, encrypted or anonymous messaging, offline-first apps — may want to monitor how this dispute resolves, including whether GitHub complies, contests, or seeks clarification, as it could set a precedent for how architecture-based takedown requests are handled going forward.