Encrypted chat

Choose how messages are kept, then share the link.

Step 1 of 3

Keep messages

How it works

How to start

Choose how messages are kept, pick a room name, set a password of at least 16 characters that is hard to guess and share the link with the people you want to talk to. Rooms are created only here, so every room gets a strong password and an explicit message mode; opening the address of a room that does not exist leads back to this form. The link does not carry the key: everyone has to type the password, which you should share another way, for example in person or over a different app.

Messages

Every message is encrypted in your browser with AES-256-GCM. When you join, the password goes through Argon2id once, with 64 MiB of memory and 3 passes, so every offline guess is slow and memory-hungry. HKDF-SHA256 then splits the result into the message key, which also depends on the room's message mode, and a second, separate value that only proves to the server that you belong in the room. The server learns that value, never the encryption key, and the room on the server is named after a hash of it rather than after your room name. Every message also gets a second layer with forward secrecy, described below.

What the server sees and keeps

Rooms run on Cloudflare Workers. The relay forwards encrypted messages to the people in the room and does not store them. It keeps only the room settings, and deletes them when the room has been empty for 7 days. It does see when messages are sent, how many people are connected and, from the timing, when someone is probably typing. Every message is padded to one of a limited set of sizes, at least 512 bytes, so short messages and typing indicators look the same and longer ones only show their rough size. Presence signals and key exchanges carry post-quantum keys, so they are larger and the relay can tell them from short messages by size. Cloudflare, like any host, sees your IP address, and the room name appears in the page address you load.

History and disappearing messages

In the default mode each participant keeps the history in their own browser: the signed messages, sealed under a key derived from the room secret, so they survive a reload. Members who are online hand up to the last 200 messages to a newcomer, encrypted for that newcomer alone and still carrying every author's signature, so nobody can put words in someone else's mouth while passing history on. Forward secrecy protects what crosses the relay; what members' browsers keep, they can show anyone who joins with the password, which is what this mode is for. You can instead make all messages disappear between 5 seconds and a day after they are shown, and then nothing is kept. In any room, ending a single message with !N, such as !30, makes just that message disappear after N seconds, and it is left out of the stored history. The timer runs in each participant's browser, so a modified client or a simple screenshot can still keep a copy.

Calls

Voice and video calls use WebRTC. On top of its standard DTLS-SRTP encryption, your browser encrypts every audio and video frame, screen sharing included, with AES-256-GCM before it leaves, in the style of SFrame. Each participant creates a random media key on joining and gives it to every other participant separately: inside the encrypted room channel, sealed once more with a key only those two browsers share for this call (ECDH P-256 + ML-KEM-768). When someone leaves, everyone who stays switches to a new key, so whoever left cannot decrypt what follows. Frames that do not decrypt are dropped, never played, and a browser that cannot encrypt frames cannot join a call. Call setup travels through the room as encrypted messages. Media always goes through a TURN relay, so participants never see each other's IP addresses; the relay only forwards encrypted packets. Every participant connects to every other one, so calls work best in small groups.

Files

Files up to 128 MB are encrypted in your browser with a random key of their own, including the file name. The key and the download link travel only inside the encrypted message, so a file is protected exactly like the message that carries it, forward secrecy included. The encrypted file is uploaded to encrypt.click's own storage, or, if that fails, to backup hosts through encrypt.click's server (files up to 50 MB only). The hosts see only the encrypted file, its size and the uploading address. Uploaded files are deleted 24 hours after upload; the message stays in the history, the download does not.

Good to know

The chat is only as private as the password: anyone who has it can join and read along from then on. A password learned later does not open traffic recorded before, although in the default mode members who are online pass recent history on to whoever joins. A different password under the same room name is a separate private group that others never see, so if the page says the room does not exist although you expected others there, check the password. Up to 32 people can join a room.

Member keys

In every room your browser creates a signing key for that room and keeps it to itself; every message carries the public half and a signature, and anything unsigned is dropped, including history that other members pass on. Names are only labels: the random alias or whatever a member typed. Other members remember which key a name first appeared with and warn you when the same name, or one that only looks like it, shows up under a new key, which is what an impostor who knows the password would look like. The members panel shows a key code for each member, a short fingerprint of that one key, and a safety number derived from both your keys, which is the same on both screens: compare it in person or by voice. A new browser or device gets a new key, so expect that warning after you switch. The signature proves who in the room wrote a message, not who they are, and the password is still the only thing that lets someone in. The message mode is part of the room key, so the server cannot quietly turn a room with disappearing messages into one that keeps history. The key mark shows as four emoji and the safety number as seven emoji picked from a set of 64 symbols, covering 24 and 42 bits of the key fingerprints — enough to catch a casual mix-up, not a determined attacker, so compare them by voice or in person when it matters.

Forward secrecy

In every room the room key alone opens no message. Each browser creates fresh P-256 and ML-KEM-768 key pairs when it joins and keeps them in memory only. Every member has its own sending chain: each message is encrypted with AES-256-GCM under a key that HKDF-SHA256 derives from the chain, then the chain moves one step on and used keys are deleted. Every other member gets the current chain key separately, sealed under a key made from their two ephemeral keys (ECDH), a fresh ML-KEM-768 secret and a secret derived from the room password, inside the signed room channel as always. Someone who records the traffic and learns the password later cannot read the messages without breaking the key exchange, and once the session is over the keys needed are on no device any more. A future quantum computer that breaks P-256 would also have to break ML-KEM-768, so a recording stays closed even to someone who knows the password. Chains are replaced after 100 messages or 10 minutes and whenever someone leaves: the new chain goes only to members who answer, so whoever left cannot read on with the keys they had. Newcomers get each chain only at its current step, so nothing that crossed the relay before they arrived opens with their keys.

My rooms

Once you are in a room, the bookmark button next to the room link adds it to My rooms, a list shown on this page. It stays in this browser on this device and is never synced or sent anywhere. The room name, the label you give it, its mode and the time of your last visit are stored as they are, the same facts your browser history already holds. The password is stored only encrypted with AES-256-GCM, under a key that HKDF-SHA256 derives from the output of the WebAuthn PRF extension of a passkey created for this list, so only that passkey, unlocked with your fingerprint, face, PIN or security key, can release it. The key lives in memory for the open page only and is never stored. Where the browser or passkey cannot produce that output, the list keeps names only and you enter the password again. Forget removes one room; Forget everything removes the list and the passkey reference, while the passkey itself is deleted in your device or password manager.

View-once, burn and scheduled messages

A view-once message opens the first time anyone in the room taps it and then disappears for everyone, so in a room of three the first reader consumes it for all. Burning one of your own messages removes it for everyone: each member's browser drops its own copy once the burn arrives, and the relay never had one to drop. The burn travels as an encrypted message signed like any other, and it only counts when it comes from the same key that signed the message. A scheduled message waits in this browser only: it stays sealed under the room key in session storage, sends when its timer fires while this tab is open, retries for ten minutes if the room is offline and is then dropped with a notice. Closing the tab discards any scheduled sends.