CIPHERROOM CHAT
Encryption, privacy and honest limits
Cipherroom is built for temporary, two-person conversations with no account and no intentional saved chat history. Its security depends on the app, both devices, the room secret and the person you are talking with. It is not an independently audited replacement for Signal.
End-to-end encryption for messages and media
Text, photos and voice memos are encrypted on the sender's device before transmission. The browser and Android app use room-secret-authenticated P-256 key agreement, PBKDF2/HKDF key derivation and AES-256-GCM encryption. The relay forwards ciphertext and does not receive the message decryption key.
Room secrets contain 128 random bits, represented by 26 Base32 characters. Use the generated secret rather than inventing a password. The app requires an authenticated encrypted peer hello before enabling messaging and rejects repeated or reflected encrypted packets.
Session verification
Both participants can compare a 60-digit safety code derived from their room and session keys. Compare the entire code through a trusted channel. Verification resets when session keys change. The code verifies the current session; Cipherroom does not yet provide persistent device identities or key transparency.
No intentional persistent chat history
The relay keeps room and connection state in memory, forwards encrypted packets and removes a room after its last participant disconnects. It has no message database, saved media directory or application chat log. Client messages, media and keys are held in device memory while needed. Ending the session clears the chat view and releases app-owned data where possible.
The browser does not intentionally save chat messages to local storage, IndexedDB, cookies or a service worker. Responses request no caching. Android app backup is disabled. Original selected photos remain in your photo library, and the operating system, keyboard, media decoders or memory management may retain copies. This is not a promise of forensic erasure.
Disappearing messages and device privacy
New messages and media disappear after 30 seconds, five minutes by default, one hour or room end. Local timers begin on display. The browser hides an active chat when the tab is hidden. Android covers chats on pause, blocks ordinary screenshots and uses the phone's system screen-lock challenge when a secure device lock is configured. Without a device lock it provides a visual cover only.
Android Tor routing and connection metadata
The native Android app includes Tor for chat, media and in-app updates, with no direct-network fallback. Tor keeps operational guard and network state in app-private storage. The website uses your browser's normal internet connection and does not provide Tor routing.
Network and hosting providers may observe timing, traffic size and connection metadata. The relay can associate the two active connections in a room. Tor is not a guarantee against traffic correlation, compromised devices or every form of tracking.
Important protections still missing
- Per-message ratcheting and post-compromise recovery: the current session key remains in use until rekeying. Theft of that key could expose recorded messages from that session.
- Post-quantum key agreement, persistent peer identities and automatic key transparency.
- An independent security audit of the complete application and protocol.
Cipherroom cannot make a conversation untraceable or prevent a recipient from recording it. A compromised phone, malicious recipient or altered website code can defeat confidentiality. For high-risk conversations, use an established, independently reviewed messenger and verify the other person's identity.
Signed Android updates
Download only from the official Android page. The v2.11 updater checks the APK checksum, package, version and production signing certificate. These checks help detect modified update files; they do not replace an independent security review.
Report a security concern
Contact sahilshah989888@gmail.com with the app version and steps to reproduce the issue. Do not include real chat contents, room secrets or signing keys. See the privacy policy for data handling details.