Why in the News
In July 2026, Bitchat's developer Jack Dorsey shared a document which he described as a notice sent to GitHub by India's cyber crime coordination unit. According to news reports, it sought the removal of access to repositories linked to Bitchat's code. This sparked a debate on security, open-source software and the right to private communication.
A notice shared by a developer, a government's final public order, and a ban actually enforced on a platform are different things. In the early July reporting, GitHub had not confirmed receiving the document and the related repositories were reported to be available. So the news of a notice alone should not lead to the conclusion of an immediately enforced blanket ban on the app.
What is Bitchat?
Bitchat is a peer-to-peer messaging app. Peer-to-peer means that participating devices can communicate directly with one another. In its local mode, nearby devices connect over Bluetooth Low Energy and can pass messages onward.
In an ordinary internet messaging service, a message travels through the network to a server. In a local Bluetooth mesh, the nearby devices themselves become part of the network. So this local contact can work even without mobile data. But it would be wrong to read it as an unlimited facility to message any corner of the world without the internet.
How Does a Mesh Network Work?
Suppose device 'A' is not directly within the radio range of 'C', but 'B' is available in between. In a favourable situation, a message can travel from 'A' to 'B' and then on to 'C'. Several such steps are called multi-hop relay.
This is useful only when there are enough capable devices in between and they are in a position to forward the message. Distance, walls, the radio environment, the device's battery and the software's behaviour affect performance. So no single distance or time can be assumed as guaranteed in every place.
Two different transport routes: the current project description also mentions the option of internet-based Nostr relays alongside the local Bluetooth mesh. The local mesh does not need the internet, but global contact over Nostr requires the internet. This is the current technical description; it is not a claim that every feature was identical in every version of July.
What is a Code Repository?
A repository is an organised place for a software's source code and its associated development record. GitHub is a platform for hosting such projects and working on them together. Source code is like the instructions for building an app; it is not the same as the copy of the app already installed on a user's phone.
That is why removing access to a repository and deleting the app from every phone do not have the same effect. But reduced availability of source code can affect independent audit, improvement and collaboration. Being open source also does not mean that code is automatically secure or free of flaws.
Encryption Does Not Mean Complete Anonymity:
The purpose of end-to-end encryption is to keep the content of a message protected so that only the intended parties can read it. Even so, a nearby radio observer can in some situations see information such as the proximity of devices, or the timing or size of messages. Such information is called metadata.
The project's own privacy material also acknowledges metadata and device-related risks. If the recipient's device is compromised, the message content too can be exposed. So 'no phone number required' should not be made a synonym for 'identity can never be exposed' or 'monitoring is impossible in any situation'.
Security Arguments and Concerns for Rights:
The security side: the July notice quoted in reports had expressed apprehensions that such a structure creates difficulty for unlawful activity, identification and lawful investigation. This is a concern about alleged misuse; it is not a fact that every use of an app is criminal.
The rights side: digital rights groups argued that the possible misuse of a communication technology should not by itself be a sufficient basis to block an entire open-source project. That is those groups' legal objection, not a court's final decision in the matter.
Civic use: uses such as local communication under limited connectivity can be beneficial. Still, in a crisis it should not be treated as a substitute for authorised emergency services or trusted public warning. Technology should be assessed on the basis of its use, real risk and the law in force.
The Difference Between Section 79 and Section 69A:
Section 79 of the Information Technology Act, with certain conditions, gives intermediaries exemption from liability for third-party content. It is commonly called 'safe harbour'. This protection is not unlimited, and the law carries conditions and exceptions.
Section 69A is a provision related to directions for blocking public access. Its basis, procedure and statutory safeguards are a separate question. The July reports linked the notice to Section 79(3)(b) and the related rules, while the October report said the message sent to an app store mentioned Section 69A. The two steps should not be conflated as the same legal action.
This distinction is for understanding the law. This article neither decides the validity of any original order not obtained, nor advises circumventing any ban.
What Changed in October?
An independent report of 3 October 2026 described Bitchat not being found in India's app stores and the text of Apple's message shared by Dorsey. That message was said to mention a demand from India's Ministry of Electronics and Information Technology and a reference to Section 69A. The report also observed unavailability on Google Play, but did not make clear the status of directions received by Google or internet service providers.
That is the finding as of that report, not an independent availability check of 24 October for every user. The original government order was not independently obtained for this article. Keeping the July notice and the October app-store status separate is necessary for factual accuracy.
The Policy Test:
In the debate between security and rights, a clear legal basis, a reason linked to real risk, a necessary limit and a system of review are important. Without understanding a technology's limits, calling it either completely safe or completely dangerous would both be wrong. A transparent process and verifiable claims are conditions of better digital governance.
Mains Style: Practice Question
How can a balance be struck among security, private communication and open-source development in regulating decentralised communication technologies? (150 words, 10 marks)
Answer Outline
Introduction: Decentralised communication can reduce dependence on centralised networks. Alongside its civic benefits, it can also bring difficulties of misuse and investigation.
Main Body: Regulation should be tied to specific risk, a clear legal basis and due process. Action against source code, distribution platforms and installed apps has different effects. Encryption protects the privacy of messages, but it does not remove metadata and device risks. Open source helps independent audit, yet it is not an automatic guarantee of safety. Broad bans and targeted action should be assessed by their real effect, the burden on rights and the availability of less restrictive measures. Giving the affected party an opportunity to respond and seek review builds trust.
Conclusion: The balance will come not from declaring a technology blameless or dangerous without examination, but from a transparent and evidence-based process.
Sources and Limitations
- The project's current technical description (read): https://github.com/permissionlesstech/bitchat/
- The project's material on privacy and residual risks (read): https://github.com/permissionlesstech/bitchat/blob/733098bb/docs/privacy-assessment.md
- Independent report of 24 July 2026 (read): https://techcrunch.com/2026/07/24/indias-move-against-jack-dorseys-bitchat-sparks-legal-debate/
- Account of the July notice and the legal questions (read): https://www.thehindu.com/news/national/disabling-bitchat-in-india-explained/article71262179.ece
- Later report of 3 October 2026 (read): https://techcrunch.com/2026/10/03/jack-dorseys-bitchat-disappears-from-app-stores-in-india-after-government-order/
- Text of Section 79 (read): https://indiankanoon.org/doc/844026/
- Text of Section 69A (read): https://indiankanoon.org/doc/10190353
- Limitations: The July notice is a claim shared by the developer; the original government order was not independently obtained. The October app-store unavailability is based on the 3 October report, not an independent availability check of 24 October. The technical description is based on the project's self-published documents, not an independent security audit. The texts of Sections 79 and 69A were read from a secondary legal-text repository; the fully updated Act was not verified from the primary source.