Encrypted private chat
In private sessions that are enabled and cleared for release, message content is end-to-end encrypted. The server stores ciphertext for that content and still processes account, device, and delivery metadata. Availability depends on client version and server configuration; production may roll out in stages.
Device trust
When your account already has an online device, a new device needs approval from an existing one. If no other device is online, the server policy may auto-approve.
What you control
Accepting or declining friend requests, signing out devices, and other controls that already ship. Full user-level block, report, and appeal flows are not advertised as live until they exist.
Protocol and limits
Messaging builds on the Matrix ecosystem. Threat models have boundaries: transport paths, metadata, and direct links each have limits. “Direct” is not automatically safer than server relay.
Claims we will not make
- Absolute / military-grade security
- Messages never touch a server
- The server learns nothing at all
- LAN is absolutely safe or fully offline-capable