Keys and encryption stay in your browser—chats are not stored or read in the clear on a server. Messages are end-to-end locked: even with a copy of the scrambled traffic, nobody can read it without the keys held by you and the people you invite.
Reload or close the tab and you lose this session—we don’t keep chats or room access on any server. If you were the one who created the link, a fresh load won’t quietly make you host again: you’d show up like any new joiner, and you can’t approve your own request. Only the link creator can admit people—other members in the room cannot—so if no link-creator session is left after a reload, no one can let you back in; you would need a new invite link.
P2P chat: after someone joins, messages go directly between peers. The private.biocrypt.net relay is only for join and approval — not for chat.
Your link
Send this to your guest. Room + keys live in the # hash.
Share opens the system share sheet, Copy puts the link on the clipboard, and Continue takes you to the room to wait for a guest and approve the join.
Share your invite link. Approve join requests when they appear below.
- No pending requests
After approval, WebRTC finishes on the relay; then the relay disconnects for chat.
-
Name
Waiting for the host to approve you…