LivaraPrivate messenger, home

Livara threat model: Who sees what.

Livara 0.1.68 · adversary by adversary

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.

01 · 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.

01

A network observer on the same Wi-Fi

Sees TLS to Livara and nothing else. Zero access to message content, direct or group.

Held
02

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.

Held
03

Someone who steals your password

Cannot restore your encryption keys — the encrypted key backup requires your recovery phrase.

Held
04

Someone holding your unlocked phone

Can see what is on screen. Device lock and biometric security protect against physical access.

Not held
05

A future quantum computer with recorded traffic

Protected by hybrid post-quantum cryptography (ML-KEM-768 + P-256) designed to resist quantum decryption attacks.

Held
06

A 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.

Held

02 · The coverage line

Private text and media are sealed.

This table is printed identically on the home page, the security page and here, because the answer should not depend on which page you landed on. Seven rows, no shading.

The cryptographic detail
What the Livara server can and cannot read in direct chats, private groups, and channels
What it isDirect 1:1Private groupsChannels
Message textSealed on your deviceEnd-to-end sealed (LGS1)Public broadcast channels
Text editsSealed on your deviceEnd-to-end sealed (LGS1)Public broadcast channels
Photos, video, files, captionsEncrypted before uploadEncrypted before uploadPublic broadcast channels
Who you talked toRouting metadata onlyRouting metadata onlyPublic broadcast channels
When you talkedDelivery timestamps onlyDelivery timestamps onlyPublic broadcast channels
Your passwordNever leaves your deviceNever leaves your deviceNever leaves your device
Your private keysNever leave your deviceNever leave your deviceNever leave your device
Filled dot: the server cannot read itRing: the server can see it

03 · Architecture and boundaries

Boundaries you can verify.

The exact edge of how the end-to-end encryption, key management and privacy model work — the same facts, without the adjectives.

Architecture

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.

Architecture

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.

Architecture

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.

Architecture

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.

Architecture

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.

Architecture

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.

Questions

The model, as questions.

Are Livara direct and group messages end-to-end encrypted?

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.

Are Livara broadcast channels encrypted?

Broadcast channels are designed for public distribution and are readable by design. Private groups and direct chats are strictly separated from public channels.

How are Livara group calls protected?

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.

Does encryption protect an unlocked or compromised device?

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.

Can I restore my keys without the 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.

Can I verify Livara's cryptography myself?

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.