Messaging we genuinely can’t read
End-to-end encrypted team and deal messaging built on the open IETF MLS standard (RFC 9420). Keys live on devices, the server stores only ciphertext, and it’s on by default.
What you get
IETF MLS (RFC 9420)
Modern group-messaging cryptography via an independently audited open-source library — not a proprietary black box.
Forward secrecy
A compromised key can’t unlock past conversations, with post-compromise security as the group re-keys.
Server-blind delivery
The server is a blind relay of opaque ciphertext — it can’t read message or file content.
Encrypted attachments
Files shared in messaging rooms are encrypted client-side alongside the messages.
Disappearing messages
Per-room message TTLs for conversations that shouldn’t stick around.
Self-host or EU-hosted
The same server-blind guarantee whether we host it or you run it yourself.
Messaging is the fully end-to-end encrypted, server-blind path: keys never reach the server, and an automated two-browser test proves the plaintext never appears in anything the server stores.
Read the full security model →Messaging — questions
What encryption does messaging use?
The IETF MLS standard (RFC 9420) via an independently audited open-source library, providing forward secrecy and post-compromise security. All key material stays on devices.
Can you read my messages?
No. Messaging is server-blind — the server stores only ciphertext and we hold no keys. There is no readable content for us to access or be compelled to produce.
Does self-hosting change the encryption?
No — messaging is end-to-end encrypted whether we host it or you do. Self-hosting additionally keeps meeting media and documents inside your own infrastructure.
Explore the rest of the platform
Bring your meetings in-house.
Start encrypted in one click on our EU-hosted service — or run the whole platform on your own infrastructure. No plaintext ever touches a server you don’t control.