Private group chat by link, no signup

Yes. When you create a room, your browser generates a random 256-bit AES-GCM key (the same cipher Signal, WhatsApp and TLS use) and embeds it in the invite link after a # symbol. The part after # is a long-standing browser convention for "client-only data" — it never gets sent in any HTTP request, so our server literally cannot see the key. Messages are encrypted in your browser before being sent to peers and decrypted only by browsers that have the same key.

No. The chat is fully anonymous — you only pick a display name, which is shared with the people in your room. No email, phone number, or registration required.

Up to 12 people per room. It works best with 2–8 — the mesh topology means every peer connects to every other peer, so very large rooms can drain phone batteries.

Your connection drops and you leave the room. Messages live only in the participants' browser memory — once everyone leaves, all peer connections close and the room becomes unreachable. Nothing is stored on our server.

The public Chat Room is a single anonymous channel per language, like a global café. Private Chat creates a separate isolated room only for people you invite, with end-to-end encryption and no message persistence on our server.

Yes — anyone with the full invite link (including the #k= part) can join and decrypt messages. Share the link only with people you trust, just like a Google Doc share link.

Yes. It works in any modern mobile browser (Chrome, Safari, Firefox, Edge, Yandex Browser). You can scan the QR code to join from another phone or tablet.

Our server is only used to introduce peers to each other (the initial handshake). After that, encrypted messages flow directly between browsers — and they're encrypted with a key our server never sees. We do not (and cannot) log message content. Aggregate, content-free telemetry (room created, peer joined, message sent) is recorded for product improvement.

The encryption uses standard AES-256-GCM with a fresh random key per room — the same primitive used by Signal, WhatsApp, and TLS. Caveats: anyone with the invite link can read messages, the protocol does not yet provide forward secrecy or sealed sender, and there is no identity verification. For routine private conversations among friends, this tool is appropriate. For threat models that need protection against your phone being seized later, or against a specific targeted attacker, use Signal.