Security

What is encrypted, what the server can still see, and what we rely on.

What is encrypted

  • Messages and files are end-to-end encrypted with MLS (RFC 9420).
  • Voice is protected with media keys taken from the same MLS groups.
  • The server never sees message content, files or voice.

What the server can see

End-to-end encryption protects content, not the fact that a service is in use. The server can see metadata:

  • who is in which group, and when;
  • IP addresses, which appear in access logs. Those logs are kept for 14 days.

Established libraries, no hand-written crypto

  • OpenMLS with the libcrux cryptography provider (formally verified primitives), for MLS groups.
  • LiveKit with E2EE frame encryption, keyed from MLS, for voice.

Sandboxed media process

Media is handled in a sandboxed process, separate from the rest of the app.

Responsible disclosure

If you find a security problem, please tell us privately before sharing it publicly: open a confidential issue on the project's GitLab (tick "This issue is confidential"). During the invite-only test, the GitLab project is open to testers; if you don't have access, ask the person who invited you.

← Back to home