Run the checksyourself.
Five working instruments, not a badge in a footer. Hash the Android build against the digest published here, generate real keys, seal a message and then break it. Everything runs in this tab; the page has no upload endpoint to send anything to.
0% verified
0 of 5 checks completed on this device.
Is this file ours?
An APK is just bytes, and bytes can be swapped anywhere between our server and your phone — a hostile network, a mirror, a helpful friend with a modified build. There is exactly one way to know. Drop your download below: it is read in slices, hashed on this device, and never leaves it.
Prefer your own tools? Run sha256sum on Linux, shasum -a 256 on macOS, or certutil -hashfile … SHA256 on Windows. You should not have to trust this page either.
Watch a message become unreadable
Two identities are generated in your browser the moment you press the button. They agree on a secret over P-256 ECDH without that secret ever existing on the wire, stretch it through HKDF-SHA-256, and seal your text with AES-256-GCM. What comes back is what a relay would actually be holding.
Two keys should never look alike
A fingerprint is a short, readable stand-in for a public key. It is how you notice that the person you have been talking to for a year suddenly has a different one. Press it a few times.
Confirm none of this phoned home
A privacy claim you cannot audit is a slogan. Your browser keeps its own record of every request a page makes. This lab snapshots that record when it opens and shows how many it has made since. The better test is to turn your network off and run everything above again.
What this page cannot prove
A verification page that claims to settle everything is just a longer advertisement. Here is the exact edge of what you have established.
- The APK bytes you selected match the digest published on this site
- The small browser demonstrations behave as displayed on your machine
- A single altered bit is refused, not silently accepted
- Distinct identities produce distinct, comparable fingerprints
- None of these checks required our servers to be involved
- That our server does not log who you message, and when — it does
- That channel content or every control event is hidden from us — it is not
- That LGS1 membership resists a compromised server — it does not
- That this bench proves the complete LVR1 or LGS1 composition — it does not
- That your own device is free of malware reading your screen
- That a future release behaves like this one — check every build
- That this page is honest, if you never verify anything on it
| What it is | Direct 1:1 | Groups | Channels |
|---|---|---|---|
| Message text | Sealed on your device | LGS1 sender-key sealed | Server can read it |
| Text edits | Sealed on your device | LGS1 sender-key sealed | Server can read them |
| Photos, video, files, captions | Encrypted before upload | Encrypted before upload | Server can read them |
| Who you talked to | Server knows | Server knows | Server knows |
| When you talked | Server knows | Server knows | Server knows |
| 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 |
The ones people actually ask
How do I check that a Livara APK has not been tampered with?
Download the APK, then use the Proof Lab on this page to compute its SHA-256 digest in your own browser and compare it, character by character, to the digest published beside the download. The file is never uploaded — the hashing runs entirely on your device. If the two digests differ, the file is not the build published here and should be deleted rather than installed.
Does the Proof Lab send anything to Livara's servers?
No. Every instrument runs locally using primitives your browser already ships. The page counts its own network requests using the browser's resource timeline and shows you the number, so the claim can be checked rather than trusted. You can also disconnect from the network and run every instrument again.
Is the encryption demo the real Livara encryption?
It runs real P-256 ECDH, HKDF-SHA-256 and AES-256-GCM primitives used by Livara, but it is not the complete LVR1 or LGS1 protocol. LVR1 also has a classical double ratchet and an ML-KEM-768 epoch ratchet; LGS1 has signed sender chains distributed inside LVR1. This lab proves the local primitives and tamper rejection, not the whole composition or an external audit.
What happens if someone changes one byte of an encrypted message?
The AES-256-GCM authentication tag fails and the receiver rejects the message outright. It does not show a corrupted or partially decrypted version. You can trigger this yourself in the Proof Lab: seal a message, flip a single bit, and watch the decryption be refused.
Checked it? Then install it.
Not before. That order is the entire recommendation, and it applies to every app you install, not only this one.