Your people.
Your network.
Your conversation.

No. ChatABit creates identity keys on your device. Choose a display name and connect with nearby people; you can verify contacts using QR codes and safety numbers.

There is no guaranteed distance. Range depends on the phones, obstacles, radio conditions and available relays. Multiple hops can extend an available path, but they do not guarantee delivery. ChatABit does not add satellite or long-range radio hardware to a phone.

Yes. ChatABit can send messages over available Bluetooth and local Wi-Fi links without internet or cell service. Both people still need a direct connection, a path through participating devices, or a later store-and-forward opportunity. Stored messages have a limited retention window; delivery is not guaranteed. Live push-to-talk needs an active path. Compare mesh and internet messaging.

ChatABit end-to-end encryption protects direct and group message content between participants. Relays forward that content without reading it, but can see routing headers such as sender and recipient identifiers. Discovery can reveal nearby devices; traffic sizes and timing remain observable. Encryption does not make ChatABit anonymous. Read the security model and its limits.

ChatABit direct messages use rotating prekeys with secret retention of up to 14 days, rather than a per-message Double Ratchet. Initial or fallback messages may use static keys until a valid prekey is available. This model does not provide post-compromise healing. ChatABit group keys rotate when a member leaves or is removed; device links use ephemeral keys.

ChatABit is planned for Google Play and the App Store. It is not available from the stores yet. Download links will appear here when it launches; release dates and pricing will be announced.

ChatABit can use HaLow through compatible IP network equipment; the app does not add a HaLow radio to a phone. LoRa and satellite need additional hardware and transport implementations. Private internet relay hosting is coming soon; an available public relay service is not established. Local mesh messaging does not depend on that planned service.

ChatABit can include an automatic transcript when the sender enables voice-to-text on a supported phone. Recognition happens on the sender’s device, and the text travels through the encrypted conversation. Transcripts can contain errors. A supported speech model and permissions are needed; downloading a model may require internet. Phones without transcription can still receive transcripts.

You can delete a voice message for yourself, or request deletion of your own voice message for everyone. Recipients need to receive that request. Deletion cannot undo what someone has already heard or remove copies they made outside ChatABit.

ChatABit has a documented design target of roughly 50–100 nodes, not a measured capacity guarantee. Delivery depends on participating devices, available paths, radio conditions and operating-system background limits. Adding phones only helps reach another group if they create a usable route or carry stored messages across a gap.