Livara privacy: What is on the disk.

Direct conversations

One-to-one message bodies and media are encrypted on your device. Current secure chats use the hybrid-PQ LVR1 ratchet; the server stores ciphertext, routing metadata, timestamps, receipts and the public material clients need. It cannot open the content.

Groups and channels

Private group conversations are end-to-end encrypted using LGS1 sender keys. Every message, edit, photo, video, file attachment, voice note and caption is encrypted on user devices before upload. Only active group participants have the keys to decrypt group content.

Public broadcast channels are designed for open distribution and are readable by design. Group metadata — such as timestamps and delivery routing — is stored to enable real-time synchronization across web and Android.

Livara AI

In the web app and Livara App, AI is included by default when you accept the account rules during signup. This one-time consent covers all your current and future chats for answers, reminders, summaries and related AI features. Existing accounts are asked once. Relevant message text, including private messages decrypted on your device, may be sent to Livara's configured AI service. You can turn AI off in Settings at any time. Text completion is requested with Ctrl+Space. This consent does not enable model training.

The standard Android app retains its own AI controls and consent flow. AI output can be wrong; review answers before relying on them.

Credentials and recovery

Login uses SRP, so your password is never transmitted during authentication; the server holds a verifier instead. Recovery format v7 uploads only an encrypted identity bundle and authenticates its identity epoch and backup generation. It needs your recovery phrase and does not restore chat history or ratchet sessions.

What the service stores

• Username, profile fields, privacy preferences, contacts and chat folders
• Dialog membership, messages, reactions, receipts, edits, deletes and sync cursors
• LVR1 direct ciphertext and LGS1 private-group ciphertext
• Opaque encrypted private attachment objects; channel content remains readable
• Push tokens when you enable notifications; encrypted-message mobile pushes contain only a generic wake event
• Operational security records such as revoked-token signatures

Media access

Message, profile, story and wallpaper media requires authentication and an object-level permission check on every request. Media is not placed in a cross-account service-worker cache, and unattached or expired uploads are cleaned up automatically.

What you can do

Export your account data, clear your copy of a conversation, delete messages where your role allows it, sign out of a device, or delete the account entirely after proving your password.

Contact

Privacy questions go through the existing Livara support channel. The canonical copy of this page is at https://livara.org/privacy, and it is updated when the implementation changes rather than on a schedule.