This is not like email or regular messaging apps. There is no inbox, no queue, and no offline delivery. If the other person is not currently in the room with you, your messages will not reach them — and theirs will not reach you.
Share the room link, agree on a time, and open it together. The chat only works while both of you are connected simultaneously.
Once a connection is established, messages, calls, and file transfers travel directly between your browser and your peer's browser using WebRTC — the same technology used in video calling apps like Google Meet , Zooom (browser version). No server ever sees your content.
There are no accounts, no logins, and no email addresses. You get a randomly generated identity when you first open the app. You can rename it to anything you like.
There is no sign-up flow, no password, and no phone number verification. Your identity is a random ID generated and stored only in your browser. Share a room link with someone and start chatting immediately.
A small Cloudflare Worker is used only for signaling — helping your browser and your peer's browser find each other and negotiate a direct connection. Think of it as a temporary introduction. Once the WebRTC connection is live, the server is no longer involved.
The server also enforces room capacity (max 2 peers) and handles moderation actions like bans. It stores nothing about your messages.
Files are sent directly to your peer over the WebRTC data channel — no upload to any server. The maximum file size is 200 MB.
When you send a file, your browser reads it fully into memory and splits it into 16 KB chunks. Each chunk is stamped with a transfer ID and a sequence number, then streamed to the peer one by one. If the send buffer fills up, sending pauses automatically until the peer catches up, so large files don't overwhelm the connection.
On the receiving end, chunks are reassembled in order and combined into a single file when the last chunk arrives. Both sides show a live progress bar during the transfer. Once complete, the file is saved to your browser's local storage (IndexedDB) so you can download it later even after the peer disconnects.
Because the entire file is held in memory during transfer, both sender and receiver use RAM equal to the file size while the transfer is in progress. On low-memory devices, very large files near the 200 MB limit may cause slowdowns.
Messages, received files, and your identity are saved in your browser's local storage (IndexedDB). This means:
- Clearing your browser data will permanently delete all chat history and received files. There is no cloud backup and no way to recover it.
- Private / incognito mode stores data only for the duration of the session. Closing the window erases everything.
- Switching devices or browsers means starting fresh — your history does not follow you.
- Your identity is tied to this browser. If you lose it, the other person will see you as a new unknown user when you reconnect.
If you want to keep a conversation, save important messages or files before clearing your browser data.