Security and encryption
| Item | Protection | Who can read it |
|---|---|---|
| Chat | End-to-end encrypted: AES-256-GCM (WebCrypto), random initialisation vector per message, room bound to the ciphertext. | Only people who have the full link. |
| Chat key | Generated in the browser, placed in the link fragment (#k=...), never sent to the server. |
Whoever has the link. |
| Audio and video | Encrypted in transit (DTLS-SRTP) between each browser and the SFU server. | The SFU server, which forwards the streams. This is not end-to-end. |
| Page and signalling | HTTPS and secure WebSocket, through your proxy. | The server. |
Good to know:
- The full link gives access to the chat: share it like a password. Someone arriving through a link without the key gets a new key and cannot read the others’ messages (they show as “Unreadable message”).
- No message is stored: the server only forwards ciphertext.
- The container runs without root privileges and checks itself through
/health. By default,/healthreveals neither the number of rooms nor the number of connected people.
End-to-end encryption of audio and video (“insertable streams”) is planned but not done yet.