India Targets Bitchat Code as Protest Chats Spread

India’s apparent move against Bitchat signals a harder regulatory target: not just online speech, but software designed to keep working when the internet is cut. Jack Dorsey posted on X what he said was a notice from India’s Ministry of Home Affairs directing GitHub to restrict access to three Bitchat repositories within three hours, according to TechCrunch.

The dispute erupted as Bitchat India usage surged during student-led protests in New Delhi over alleged examination paper leaks. The demonstrations, called the “cockroach” movement, have drawn thousands demanding the resignation of Indian Education Minister Dharmendra Pradhan, while authorities imposed restrictions on marches toward parliament and tightened internet access.

The legal fight is bigger than one Jack Dorsey-linked app. XOOMAR analysis: India is testing how far public-order powers can reach when the communication tool has no central server, no phone-number identity layer, and no obvious operator capable of tracing users or removing specific messages.

India’s Bitchat crackdown turns protest messaging into a test case for offline apps

The notice Dorsey shared did not point to specific unlawful posts, messages, or files inside the repositories. That matters. The apparent complaint targets Bitchat’s architecture.

The notice said the app can let users communicate “even during network restrictions” and “internet shutdowns,” making it possible to “circumvent lawful restrictions” while hampering “lawful interception, attribution, and traceability.”

That framing shifts the question from content moderation to software legality. If a tool can be used during a shutdown, is that enough to restrict its source code? Digital-rights lawyers quoted by TechCrunch are skeptical.

Mishi Choudhary, founder of SFLC.in, told TechCrunch the document resembled recent government takedown notices, but the provisions it cited did not clearly authorize removal of an entire software project because of how it works rather than because it hosts specific illegal content.

Dorsey’s role adds visibility, but not the core issue. He has been pushing into communications software beyond social media, including the AI-agent group chat platform covered in Jack Dorsey Buzz Hits Slack With Open AI Agent Chat. Bitchat India is a more sensitive case because its usefulness rises precisely when conventional networks are restricted.

Bitchat’s offline model breaks the usual enforcement chain

Bitchat uses Bluetooth mesh-style communication to pass encrypted messages between nearby phones without relying on mobile networks, internet connectivity, central servers, accounts, or phone numbers. Each device can help relay messages through the local network.

That makes it very different from mainstream messaging and social platforms, where authorities can pressure a company, cloud provider, telecom operator, app store, or internet service provider.

The practical problem is blunt: removing a GitHub repository does not delete Bitchat from phones.

The Internet Freedom Foundation made that point directly:

“The order also fails on its own terms as deleting a repository does not delete the application from any phone that carries it, and the mesh keeps functioning without servers. What the takedown actually prevents is scrutiny of the underlying code,” the group said on X.

XOOMAR analysis: That is the enforcement gap India is trying to close. If the network cannot be shut off through telecom controls, authorities may look to GitHub, app stores, developers, and possibly users. But each step moves farther away from removing unlawful content and closer to restricting a class of software.

The legal fault line runs through code, not just speech

The apparent order was dated July 23 and apparently issued by the Indian Cybercrime Coordination Centre, or I4C, which operates under India’s Home Ministry. Related reporting from CoinDesk said the order cited Section 79(3)(b) of the IT Act. CryptoTimes reported that it also cited Rule 3(1)(d) of the IT Rules, 2021.

Those provisions are typically about intermediary obligations. The tension is whether GitHub is being asked to remove unlawful content, or whether it is being asked to remove open-source code because the government dislikes the capabilities it enables.

Before 2021, India typically relied on Section 69A of the IT Act and the 2009 Blocking Rules when it wanted content removed nationwide, Choudhary told TechCrunch. The Bitchat notice appears to take a different route.

That distinction is not procedural trivia. Section 69A-style blocking is associated with content restrictions. This apparent notice is aimed at repositories for a tool whose objectionable quality, according to the government’s own stated concern, is that it works without centralized control.

Raman Chima, global program director at the Association for Progressive Communications, told TechCrunch the notice went beyond targeting the messaging service itself.

“They’re [the Indian government] not just targeting the designated service provider, but they’re trying to say that open source development of this type of product … should not occur,” he said.

That is the sharpest legal issue in the case. If Bitchat messages do not pass through a central company server, the developer may not be able to identify users, preserve logs, moderate conversations, or comply with conventional takedown demands. A government can argue that creates investigative risk. Civil-liberties groups can answer that the same design protects lawful protest, private reporting, and emergency communication during shutdowns.

Both points can be true. The law still has to decide whether potential misuse is enough to suppress code.

Sensor Tower data shows why Bitchat India became urgent fast

The usage spike was dramatic. Sensor Tower told TechCrunch that India accounted for about 85% of Bitchat’s global downloads between July 17 and July 23, up from about 1% over the previous 30 days.

Bitchat was downloaded more than 91,000 times in India over the past five days, after downloads jumped thirty-two-fold on July 19 from the previous day. Daily active users in India reached more than 330,000 on Thursday, the highest level recorded for the app in the country.

Those numbers do not prove unlawful use. They do show why a niche app can matter during concentrated unrest.

A protest tool does not need national penetration to become operationally relevant. It only needs density in the right places: campuses, protest sites, transit corridors, or neighborhoods where internet service is unreliable or suspended. Local media reported that some protesters downloaded offline messaging apps, including Bitchat and Briar, after internet services were suspended.

XOOMAR analysis: That is the state’s dilemma. Shutdowns are meant to reduce coordination. Offline mesh tools reduce the effectiveness of shutdowns. The more shutdowns are used, the more attractive those tools become.

GitHub is caught between government process and open-source scrutiny

GitHub did not confirm to TechCrunch whether it had received the document. The repositories remained accessible from India on Friday. GitHub also pointed TechCrunch to its public repository of government takedown requests, which did not contain any recent requests related to Bitchat.

The company’s position, as described by Rose Coogan, GitHub’s principal online safety counsel, is process-heavy and transparency-focused:

“When we receive a complete government takedown request, we notify the affected account owners and give them an opportunity to appeal,” Coogan said. “We share every government takedown request we take action on publicly.”

That process matters because repository takedowns can have second-order effects. They may not stop installed apps, but they can reduce code review, security auditing, forks, and public accountability. For open-source advocates, that is not a side issue. It is the point.

This is also where startups and security teams should pay attention. The governance question around who controls critical software infrastructure shows up in very different contexts, including enterprise tooling debates like Abstract Security Funding Wagers $25M Against SIEM Lock-In. In Bitchat’s case, the pressure point is not vendor lock-in. It is whether a code host becomes the easiest chokepoint when the app itself lacks one.

The next fight moves to phones talking directly to phones

Users face a messy tradeoff. Bitchat India offers resilient communication when networks fail or are restricted. But users in protest settings may also face legal uncertainty, device searches, misinformation risk, or exposure if authorities treat use of offline coordination tools as suspicious.

Developers face a different lesson. Privacy-first and offline-capable projects now need legal threat models alongside technical ones. If a product is built to avoid central control, governments may respond by targeting distribution channels, source-code repositories, app stores, or contributors.

The immediate evidence to watch is narrow and concrete:

• GitHub action: Whether any Bitchat repositories are restricted in India or added to GitHub’s public takedown database.
• App availability: Whether Bitchat remains accessible through Apple’s App Store and Google Play in India.
• Legal basis: Whether Indian authorities defend the notice under intermediary rules, blocking powers, police powers, or a new theory aimed at software architecture.
• Protest use: Whether documented Bitchat usage remains tied to peaceful coordination, or whether authorities cite specific unlawful incidents.

The thesis weakens if the notice disappears without enforcement, GitHub records no takedown, and app distribution continues unchanged. It strengthens if India escalates from repository pressure to app-store restrictions or broader rules for offline messaging tools.

The next phase of messaging regulation will not be fought only on platforms. It will be fought at the edge of the network, on phones talking directly to phones.

Impact Analysis

• India’s action could expand regulation from online content to the design of communication software itself.
• The case tests whether governments can restrict tools that function during internet shutdowns.
• A crackdown on source-code repositories could raise major free-speech and digital-rights concerns for developers and users.