1. The MIT License

BitChat is released under the terms of the MIT License. You are free to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the software, subject to the conditions of the license:

Copyright (c) 2026 Java-Mx and BitChat Contributors

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

2. Decentralized Peer-to-Peer Mesh Relay Model

By running BitChat, your instance operates as an autonomous node in a decentralized mesh network:

  • Packet Forwarding: In multi-hop mesh mode, your node may receive and forward encrypted packets destined for other peers within radio or network reach. Your node cannot read the encrypted contents of forwarded packets.
  • Local Resource Use: The application utilizes your device's Bluetooth radio adapter, network interfaces, CPU, and RAM.
  • No Content Moderation: Because BitChat operates without central servers or administrators, the authors and contributors cannot monitor, censor, filter, or moderate messages broadcast over radio or local networks. You are solely responsible for compliance with applicable local telecommunications laws and regulations.

3. Cryptographic Key Ownership & Recovery

Your cryptographic identity (Ed25519 public and private keypair) is generated and stored exclusively on your device in ~/.bitchat/identity.json:

  • There is no central registry, backup server, or password reset mechanism.
  • If you delete or lose access to your local identity key, your peer cryptographic identity cannot be restored by the maintainers or any third party.

4. Disclaimer of Warranties & Operational Risk

BitChat is experimental communication software. The software is provided "AS IS", without warranties of uptime, delivery guarantees, or physical radio range. In particular:

  • Do not rely on BitChat as your sole communication channel during critical life safety emergencies.
  • Radio transmissions over Bluetooth Low Energy and local UDP broadcasts are subject to environmental interference, range limitations, and packet loss.

5. Third-Party Notices & Acknowledgements

BitChat incorporates and relies on high-quality open-source libraries:

  • PyO3 & Maturin: Rust/Python FFI bridge and build toolchain (Apache-2.0 / MIT).
  • Textual: Rapid Python terminal application framework (MIT).
  • Bleak: Cross-platform Bluetooth Low Energy client library (MIT).
  • Cryptography: Python cryptographic recipes and primitives (Apache-2.0 / BSD).