A network observer on the same Wi-Fi
Sees TLS to Livara and nothing else. Zero access to message content, direct or group.
HeldLIVARA 0.9.53 / THREAT MODEL
Who seeswhat.
A threat model that only lists strengths is a brochure. This one names the relevant adversaries, says exactly what each gets, and then prints the list of things Livara does not claim.
Six people who might want your messages
Named, and answered.
Some get more than you might hope. They are listed anyway, in the same type size as the rest.
Livara's server or hosting infrastructure
Cannot read direct or group messages, media, or voice notes — all ciphertext is unreadable without device keys. Only routes encrypted packets and serves public channel posts.
HeldSomeone who steals your password
Cannot restore your encryption keys — the encrypted key backup requires your recovery phrase.
HeldSomeone holding your unlocked phone
Can see what is on screen. Device lock and biometric security protect against physical access.
Not heldA future quantum computer with recorded traffic
Protected by hybrid post-quantum cryptography (ML-KEM-768 + P-256) designed to resist quantum decryption attacks.
HeldA tampered download served by a middlebox
A checksum detects a mismatch against a trusted digest. If an attacker can replace both the APK and the displayed digest, matching hashes alone cannot establish authenticity.
HeldThe same table, everywhere on this site
Private text and media are sealed.
This table is printed identically on the home page, on the security page and here, because the answer should not depend on which page you landed on.
07
Seven rows, no shading.
LVR1 seals direct message content and media before upload. LGS1 provides full end-to-end encryption for private group messages, media, and attachments; public broadcast channels remain open by design.
The cryptographic detail ↗| What it is | Direct 1:1 | Groups | Channels |
|---|---|---|---|
| Message text | Sealed on your device | End-to-end sealed (LGS1) | Public broadcast channels |
| Text edits | Sealed on your device | End-to-end sealed (LGS1) | Public broadcast channels |
| Photos, video, files, captions | Encrypted before upload | Encrypted before upload | Public broadcast channels |
| Who you talked to | Routing metadata only | Routing metadata only | Public broadcast channels |
| When you talked | Delivery timestamps only | Delivery timestamps only | Public broadcast channels |
| Your password | Never leaves your device | Never leaves your device | Never leaves your device |
| Your private keys | Never leave your device | Never leave your device | Never leave your device |
Clear and transparent design
Boundaries you can verify
True security is built on transparency. Here is the exact boundary of how our end-to-end encryption, key management, and privacy models work.
Direct and Group Messages are Fully E2EE
All direct messages and private group conversations (text, media, attachments, voice notes) are encrypted end-to-end with device-held keys. The server stores only unreadable ciphertext that cannot be decrypted without your device keys.
Broadcast Channels are Public
Broadcast channels are designed for public distribution and are readable by design. Private groups and direct chats are strictly separated from public channels.
Group Calls Use Encrypted Peer Mesh
Group calls support over 500 participants with fully end-to-end encrypted audio, video, and screen sharing. Optional server recording switches to transport encryption under a visible REC state.
Device Security is Essential
Cryptographic keys reside securely on your device. A passcode or biometrics helps protect a locked device; malware, an unlocked device, or a recipient can still expose plaintext.
Encrypted Backup Requires Your Recovery Phrase
Your identity and encryption keys are encrypted before cloud backup using a 256-bit key derived from your recovery phrase. Keep your recovery phrase safe to restore your account.
Verifiable Cryptography & Proof Lab
We believe in verifiable security over marketing claims. The Proof Lab allows you to inspect, hash, and test our cryptographic primitives directly in your browser offline before installing.
Do not take this page on faith either
The checkable half is checkable now.
Hash the APK, run the handshake, corrupt a byte and watch the authentication reject it. All of it offline, in your own browser, before you install anything.