Direct conversations
One-to-one message bodies and media are encrypted on the client with keys derived from participant P-256 keys. The server stores ciphertext, routing metadata, timestamps, membership, receipts, and the public-key material needed by clients.
Groups and channels
Group and channel messages are protected in transit with HTTPS/WSS and by server-side membership and role checks. Their content is stored in a form the server can process; Livara does not currently describe those conversations as end-to-end encrypted.
Account credentials and recovery
Login uses SRP (Secure Remote Password), so the password itself is not sent during authentication. The server stores an SRP verifier. A direct-chat private-key backup is uploaded only after client-side encryption and requires the recovery phrase to restore.
What the service stores
- Username, profile fields, privacy preferences, contacts, and chat folders
- Dialog membership, messages, reactions, receipts, edits, deletes, and sync cursors
- Direct-chat ciphertext and group/channel message content
- Authorized media objects and push-subscription or mobile push tokens when enabled
- Operational security records such as revoked-token signatures
Media access
Uploaded message, profile, story, and wallpaper media requires authentication and an object-level permission check. Media is not placed in a cross-account service-worker cache, and unattached or expired uploads are cleaned up automatically.
Your controls
You can export account data, clear your copy of conversation history, delete messages where your role permits, sign out, and delete your account after password proof. See Security for the implemented cryptographic details.
Contact
Privacy questions can be sent through the existing Livara support channel. This page changes when the implementation changes; the canonical copy is at https://dreamorth.com/privacy.
Last updated: July 18, 2026