1. Fundamental Privacy Commitment: Zero Telemetry

BitChat is designed from first principles as an autonomous, localized, peer-to-peer communications tool. The application incorporates:

  • No Central Servers: There is no BitChat server, account service, registration portal, or signaling directory.
  • No Telemetry or Tracking: BitChat contains zero analytics libraries, crash-reporting SDKs, usage trackers, or phone-home routines.
  • No Marketing Consent: We do not ask for or collect names, email addresses, phone numbers, device serial numbers, or payment data.

2. Local Data Inventory: What Is Stored on Disk

BitChat stores only the minimum configuration and cryptographic identity required for operation on your local machine under ~/.bitchat/ (or %USERPROFILE%\.bitchat\ on Windows):

  • identity.json: Contains your local Ed25519 identity keypair (32-byte public key and private seed). Created with restricted POSIX file permissions (0600).
  • identity.json.lock: A temporary file lock used to prevent race conditions during concurrent local access.
  • identity.json.corrupt.<timestamp>: An emergency backup created if corruption is detected during startup.
  • config.json: User preferences such as active transport mode, TUI theme selection, and sound/notification settings.
  • bitchat.log: Local diagnostic log file containing timestamped application state messages. Contains no message contents or cryptographic private keys. Rotated automatically.

3. Ephemeral RAM-Only Data: What Is Never Stored on Disk

To protect user privacy and communication confidentiality, the following data items exist exclusively in volatile process memory (RAM) and are completely discarded when BitChat exits:

  • Chat Messages: Sent, received, and forwarded messages are stored only in memory for the active TUI session. BitChat does not persist chat history to disk.
  • Noise Session Keys: Symmetric cipher states established via the Noise XX protocol are held in memory and destroyed when peers disconnect or the application closes.
  • Peer Discovery Tables: Discovered peer lists, RSSI radio values, and network routes are repopulated dynamically upon every startup.

4. Radio & Network Disclosures

When you enable physical transports in BitChat, your device broadcasts localized signals:

  • Bluetooth Low Energy (BLE): Advertises a standard service UUID F47B5E2D-4A9E-4C5A-9B3F-8E1D2C3A4B5C with characteristic A1B2C3D4-E5F6-4A5B-8C9D-0E1F2A3B4C5D. Physical Bluetooth observers in radio range can detect packet transmissions and your hardware Bluetooth MAC address.
  • Local Area Network (LAN): Periodically broadcasts UDP discovery packets on port 41234 to the local subnet and accepts incoming peer connections on TCP port 41235. Other devices on your local Wi-Fi or Ethernet network can observe your local IP address and listening ports.

5. Uninstallation and Data Removal

When you uninstall BitChat via bitchat --uninstall or through your operating system package manager:

  • Standard Uninstall: The application executable and system shortcuts are removed, but your local ~/.bitchat/ identity folder is preserved so you do not lose your cryptographic peer identity if you reinstall.
  • Complete Scrub: To permanently delete all cryptographic keys, configurations, and logs, execute:
    bitchat --uninstall --remove-user-data

6. Contact & Questions

Questions regarding data handling or privacy architecture may be submitted through our GitHub repository issue tracker or via private security advisories.