Share

Bitchat India Ban Explained

by Ritvik Pandit · July 26, 2026

Quick Facts

  • What happened: India’s Cyber Crime Coordination Centre (I4C), under the Ministry of Home Affairs, ordered GitHub to take down three Bitchat repositories — the main repo and its Android version — within three hours.
  • When: Notice issued 10:16 PM IST, July 23, 2026.
  • Legal basis cited: Section 79(3)(b) of the IT Act, 2000, and Rule 3(1)(d) of the IT Rules, 2021.
  • Why now: Downloads spiked 85% globally from India in one week, coinciding with the Cockroach Janta Party’s “Sansad Chalo” march on July 20, amid Delhi mobile-network restrictions.
  • Did it work: No. As of over 40 hours past the deadline, all three repositories remain live on GitHub — the software’s decentralized, open-source structure has no single point to shut down.
  • Who’s objecting: Jack Dorsey (Bitchat’s creator), the Internet Freedom Foundation, SFLC.in, and Access Now have all publicly questioned the order’s legal basis and proportionality.

An Open Letter to Jack Dorsey: Bitchat Is Brilliant Tech — But India Isn’t Silicon Valley’s Test Lab

Dear Jack,

Your post landed hard: “The government of India does not like technologies like Bitchat and wants it taken down.

” Within hours it had crossed two million views, and predictably, it framed India as just another government afraid of decentralization. From Bluetooth mesh networks to Bitcoin rails, you’ve spent a career building tools that don’t ask permission from central authorities — and on pure engineering merit, Bitchat is elegant. No phone number, no server, no internet dependency. For a protester standing in a dead zone in central Delhi, that’s genuinely useful technology.

But here’s what a one-line post from San Francisco can’t carry: India is not a single, uniform test case for decentralized communication. It is a country holding together a democracy of 1.4 billion people across some of the most contested, militarized, and ethnically fractured terrain on earth. And the same feature you’re proud of — a network with no registration, no central log, no phone number to trace — is not a hypothetical risk here. It has a track record.

The Numbers You Shared Prove the Government’s Point Too

Ironically, the growth data you cited to make your case is exactly what should give any security establishment pause. By your own numbers — sourced from Sensor Tower — India accounted for roughly 85% of Bitchat’s global downloads between July 17 and July 23, up from about 1% in the previous month. Downloads jumped thirty-two-fold in a single day on July 19. Daily active users touched 330,000, the highest the app has ever recorded anywhere.

That surge didn’t happen in a vacuum. It happened as the Cockroach Janta Party — the youth movement born out of satire after a remark comparing unemployed graduates to “cockroaches” — organized its largest march yet on July 20, the “Sansad Chalo” rally toward Parliament, timed to the opening of the monsoon session. As Delhi Police moved to block routes and reportedly activated signal jammers around Connaught Place, word spread on Instagram and Reddit for protesters to pre-download Bitchat before networks went dark. Within days, an app almost nobody in India had heard of became one of the most downloaded pieces of software in the country.

That trajectory is precisely the pattern a government watches for. A niche, purpose-built, anonymous mesh network going from irrelevant to nationally dominant in under a week, synchronized exactly with a period of mass unrest and police confrontation, is not just “citizens adopting resilient tech.” From New Delhi’s perspective, it’s a real-time demonstration of how fast an unregulated, untraceable communication layer can be provisioned at scale during a live law-and-order crisis — which is the same underlying capability that has already shown up in J&K’s terror networks and Manipur’s shutdown cycles, just compressed into days instead of years.

This Isn’t India’s First Rodeo With Offline Messaging

Go back to May 2023. India’s Ministry of Electronics and IT, acting on intelligence inputs, banned 14 messaging apps for use in Jammu & Kashmir. Buried in that list, alongside Threema and Crypviser, were Briar and BChat — both offline-capable, decentralized, mesh-style messengers built on the exact same premise as Bitchat: no phone number, no central server, hard to intercept. Interrogations of Lashkar-e-Taiba operatives later confirmed these tools weren’t theoretical curiosities — they were operational communication channels for coordinating with overground workers and handlers across the border.

That’s not paranoia. That’s a documented pattern, three years running, in the single most militarized region of the country.

Now overlay Manipur. Since May 2023, the state has recorded 47 separate internet shutdowns totaling over 5,000 hours — the second-longest disruption record in India after J&K. Not because the government enjoys cutting off 3.2 million people from their families, but because every previous cycle of unrest in the Meitei–Kuki-Zo conflict has been accelerated by unverified images, hate video, and coordination messages spreading faster than authorities could respond. Drone-dropped explosives, ambushed relief convoys, and militant attacks on civilians have all followed periods where digital coordination outpaced digital oversight. A tool that survives a total network shutdown and leaves no trace isn’t a neutral bystander in that environment — it’s the exact capability a security planner loses sleep over.

The Uncomfortable Truth About Dual-Use Technology

You didn’t build Bitchat for militants. Nobody is suggesting that. But the entire value proposition you’re marketing — resilience against shutdowns, zero registration, zero central logging — is identical whether the user is a student organizing a peaceful protest at Jantar Mantar or an overground worker relaying instructions from across the Line of Control. The technology cannot tell the difference, and neither, in the moment, can law enforcement. That’s not a flaw in India’s response; it’s the actual design tension of every anonymous mesh network ever built.

Most democracies eventually rediscover this. Encrypted, off-grid, unlogged communication is a genuine public good — until the same properties make an active insurgency’s job easier. The US, the UK, and the EU have all had versions of this fight over Signal, PGP, and Tor. India’s version simply plays out against a live-fire backdrop most Silicon Valley product debates never have to reckon with.

What I’m Not Arguing

I’m not arguing that India’s approach here was procedurally clean. Legal experts like Mishi Choudhary and organizations like the Internet Freedom Foundation have raised a fair point: Section 79(3)(b) governs intermediary liability, not blanket takedown authority — that’s traditionally Section 69A’s job. If the government wants to restrict a technology category on national security grounds, it should use the legal instrument built for that, not stretch an adjacent one. Access Now’s Namrata Maheshwari also makes a legitimate civil-liberties point: blocking an offline tool during an internet shutdown risks turning a temporary restriction into a total blackout for ordinary protesters who have nothing to do with militancy.

Those are fair criticisms of process. They are not, however, an argument that the underlying concern is manufactured.

The Ban That Isn’t Actually a Ban

There’s also a practical postscript here that neither side’s talking points fully capture. The takedown notice gave GitHub a three-hour deadline, issued at 10:16 PM IST on July 23. As of this writing, more than 40 hours later, all three Bitchat repositories are still live and accessible on GitHub. Unlike Telegram — a single company with identifiable servers that can be blocked at the platform level — Bitchat has no central switch to flip. It’s open-source and mirrored the moment anyone forks it.

That’s worth sitting with from both directions. For India, it’s a preview of how limited old-style takedown orders are against genuinely decentralized software — the legal notice asserts authority faster than the technology can actually be disabled. For you, Jack, it undercuts the “authoritarian crackdown succeeded” framing your post implied; if anything, the episode is a live demonstration that Bitchat’s architecture is exactly as censorship-resistant as advertised. Neither government overreach nor unstoppable decentralization is the full story — both are true at once, which is usually how these fights actually resolve.

The Actual Ask

Jack — you’re right about the technology. Decentralization is a legitimate answer to fragile, single-point-of-failure networks, and India’s own citizens benefit from that resilience daily. But “this technology is well-engineered” and “this technology should be allowed to operate without any oversight in an active insurgency zone” are two different claims, and conflating them in a two-line X post does a disservice to the actual complexity on the ground.

What India needs isn’t a binary choice between “ban Bitchat everywhere” and “let it run everywhere, no questions asked.” It needs a framework — geofenced restrictions in designated security-sensitive zones like J&K and parts of the Northeast, clear statutory backing instead of borrowed provisions, and a transparent appeal mechanism for developers and users caught in the crossfire. That’s a harder policy conversation than a viral post allows for. But it’s the one India’s sovereignty and its democracy both actually require.

Respectfully,


Sources referenced:

  • India orders GitHub to block Bitchat repositories — TechCrunch, americanbazaaronline.com, crypto.news (July 24, 2026)
  • Jack Dorsey (@jack) on X, sharing Sensor Tower download data for India, July 24, 2026
  • “India Tests Jack Dorsey’s App as Peaceful Protest Meets Police Force” — TheStreet Roundtable / Yahoo Finance (July 2026)
  • “From BBM to Threema: How Messaging Apps Fuel J&K Terror Networks” — Northlines
  • “Modi govt bans 14 instant messaging apps” — ThePrint / Deccan Herald (2023)
  • “Manipur’s Digital Darkness: Analysing Internet Shutdowns Amidst Conflict” — The Quint
  • “Manipur Shuts Internet in 5 Districts After Bishnupur Blast” — MediaNama (April 2026)
  • IFF statement on Bitchat blocking, July 24, 2026
  • SFLC.in statement on the Bitchat GitHub order, July 2026
  • “Indian government’s Bitchat ‘ban’ and why it did not work” — The Week (July 25, 2026)

Editorial note: The GitHub takedown order was issued by the Indian Cyber Crime Coordination Centre (I4C) under the Ministry of Home Affairs — not the Ministry of Electronics and Information Technology (MeitY). No public statement on this specific order was found from IT Minister Ashwini Vaishnaw at the time of writing.