How SecureChat works
A direct, encrypted line between the people in a room.
AES-256-GCMGetting started
- Create a room. Pick a name, a room ID, and a strong password (the dice button generates one).
- Invite people. Copy the invite link, which holds the room ID only, and send the password through a different channel.
- Join. Others enter the same room ID and password.
- Talk. Chat, share files up to 20 MB, or start an end-to-end encrypted voice call from the people list.
Security and privacy
Your browser stretches the room password with PBKDF2 (600,000 rounds) and splits the result into separate keys for text and files, for voice, and for the room's hidden address. Everything is sealed with AES-256-GCM. Unauthenticated connections are dropped, and the host stamps each sender's name so members cannot impersonate each other.
- Ephemeral. Messages live only in browser memory.
- Voice is end-to-end encrypted with the room key. The call screen shows AES-256-GCM end-to-end + WebRTC only after it has actually decrypted audio from your peer, and Standard WebRTC when it fell back.
- What servers can see. The public PeerJS signaling server and STUN/TURN servers see IP addresses and temporary IDs, never message or voice content.
Use your own server
By default SecureChat uses the free public PeerJS server to introduce browsers to each other. It sees IP addresses and temporary connection IDs, never messages or voice. For more privacy, open Connection server on the start screen, tick Use my own server and enter your address. Invite links carry the server address, so guests connect to the same one.
- Run a PeerJS server:
npx peerjs --port 9000 --path / - Put it behind HTTPS (for example nginx or Caddy), which gives you
wss://. - Optional: run
coturnfor your own STUN/TURN and list it under STUN / TURN servers.
Everyone in a room must use the same server. Your messages stay end-to-end encrypted either way.
Compatibility
Chrome, Edge, Firefox and Safari 15.4 or newer support encrypted voice. If a browser or the other person can't, or the extra layer can't be verified, the call switches automatically to standard WebRTC encryption and the call screen says so.
Strict corporate networks can block direct connections. When that happens the connection falls back to a relay, which still only carries encrypted data.