Who publishes these pages
About bitchat.cc
bitchat.cc is an independent guide. We explain the Android app, mirror the signed release files, and publish the checksums next to the buttons. We do not build bitchat, we do not run its relays, and we do not operate a chat network of our own.
What “mirror” means here
When a GitHub release is current, we download the signed APKs from that release and store them on this server. The download page prints the SHA-256 that GitHub published for each asset. After every refresh we check the file on disk against that hash before we link it. If the hash ever disagrees, the button should come down until it is fixed.
The copy on this site is for people who want the file from a single readable page, with the install steps beside it. GitHub remains the canonical release. Both copies should be byte-for-byte identical. If they are not, do not install either one until you know why.
Who we are not
- Not bitchat.free, the project site.
- Not the permissionlesstech GitHub organization.
- Not Verse Communication PBC, the name on the Play listing.
- Not Block, and not Jack Dorsey. The app was announced publicly by Jack Dorsey in 2025. That fact does not make this website his.
- Not Google, and not Apple. Store links are outbound links.
How the articles are written
The guides are original explanations of public project behavior: the README, the v2.0.1 release notes, and the documented protocols those notes name. We do not paste the upstream README. We also do not invent features to fill a page. Where a gesture or a default might change between versions, the article says so.
Pages on this site were last reviewed on 2026-10-05. The mirrored release is v2.0.1, published 11 August 2026.
Advertising
The layout is prepared for Google AdSense. Advertising cookies are not loaded unless a publisher id is configured. The privacy policy describes what that means if ads are turned on later. Ads, if they appear, are labeled by Google’s own units. They are not part of the download buttons.
Contact
Use the contact form for corrections, broken hashes, or a takedown concern about a file on this domain. App bugs and feature requests belong in the upstream issue tracker, where the people who ship the APK can see them.