Privacy guides
Livara vs SimpleX, Signal, Session & Threema
Choose a messenger around your contacts, devices and threat model. This comparison separates account requirements from message encryption. Features and beta availability can change; consult the linked official documentation before deciding.
Content reviewed ·
| Criterion | Livara Chat | SimpleX Chat | Signal | Session | Threema |
|---|---|---|---|---|---|
| Registration and identifiers | No phone number; username, password and verified email. | No phone number or global user identifier; connection-specific addresses. | Standard registration uses a phone number; Android beta also documents paid phone-free Signal Login with an account ID. | No phone number or email; generated Account ID. | Generated Threema ID; linking phone or email is optional. |
| Message encryption | LVR1 hybrid P-256 + ML-KEM-768; LGS1 private groups. | End-to-end encrypted conversations with per-connection keys. | Signal Protocol; published hybrid post-quantum key agreement and ratchet specifications. | End-to-end encryption; see current protocol documentation for version-specific guarantees. | End-to-end encryption; documented Ibex protocol for one-to-one conversations. |
| Metadata model | Central service processes account, participant and delivery metadata. | No global user IDs; separate relay queues reduce linkability. | Central service with metadata-reduction mechanisms including sealed sender. | Decentralized onion routing separates origin and destination visibility. | Contact lists and groups managed on devices; service still handles delivery. |
| Group messaging | Encrypted private groups; public broadcasts have different boundaries. | End-to-end encrypted groups. | End-to-end encrypted groups. | Encrypted private groups; public broadcasts have different boundaries. | End-to-end encrypted groups. |
| Platforms | Android beta and web. | Android, iOS and desktop clients. | Android, iOS and desktop clients. | Android, iOS and desktop clients. | Android and iOS; desktop/web availability depends on client version. |
| Source and verification | Private application source; public architecture and release hashes. No published independent audit is established here. | Open source; published security assessments linked by SimpleX. | Open-source clients and protocol specifications; inspect the scope of any independent research separately. | Open source; its FAQ links a Quarkslab audit with a defined historical scope. | Open-source mobile clients; published external audits with version-specific scope. |
An audit or open-source license is not a guarantee of security. Compare the reviewed version, scope, unresolved findings and your own needs. Livara publishes this comparison as the product's maker.
Sources and further reading
- SimpleX · Metadata model
- SimpleX · Source and verification
- Signal · Registration and identifiers
- Signal · Registration and identifiers
- Signal · Message encryption
- Signal · Metadata model
- Session · Source and verification
- Threema · Source and verification
- SimpleX · Platforms
- Signal · Platforms
- Session · Platforms