Start
Create a temporary browser room and receive a Session ID.
Pre-launch public information
Relay Sessions
Temporary encrypted browser rooms for intentional private conversations.
Start a temporary room, share a Session ID and Join Phrase, and approve each person before they enter. No account, username, phone number, email, or permanent identity required.
Relay Sessions is designed for ordinary HTTPS access in modern browsers when network policy allows. It is not general network access software.
Session ID
RS-4829-17
Where to knock
Join Phrase
shared separately
Invitation proof
Waiting room
2 people requesting access
Owner approves
Room state
temporary browser session
Gone when done
Private rooms with a code, a phrase, and a human at the door.
Relay Sessions is for people who intentionally choose a temporary space for sensitive conversations without creating accounts, usernames, phone numbers, emails, or permanent identities.
How the product works
A room owner starts a temporary session, gives invited people the information they need, and approves each person before they enter.
Invite
Set or generate a Join Phrase and share it carefully with intended participants.
Approve
Each joiner requests access and waits until the room owner approves entry.
End
The session ends without room history, inboxes, restore, or account recovery.
Four trust layers
The entry model is intentionally simple and human-readable.
Session ID
Where to knock.
Join Phrase
Proof you were invited.
Owner approval
A human at the door.
Encryption
The privacy boundary.
What Relay Sessions is for
Intentional private conversations that should not live permanently in everyday logged channels.
✓Temporary sensitive discussions
✓Incident and response rooms
✓Family or business conversations
✓Moving sensitive parts of a conversation out of everyday chat
Boundaries
What it is not
Relay Sessions is built for invited, temporary rooms. It is not designed for public discovery, stranger chat, or changing how a network allows access.
Not a social network
No public directory, profile system, inbox, or permanent identity layer.
Not a public chatroom
People enter only after receiving invitation details and owner approval.
Not access tooling
Relay Sessions uses ordinary HTTPS and depends on the network allowing the site.
RAM-only browser session design
Public Sessions are designed around temporary browser state. Refreshing or closing the page ends the browser session.
Gone when done
No room history. No inbox. No restore. No account recovery. No permanent identity required.
Safe invite sharing
Treat the Session ID and Join Phrase as separate pieces of an invitation.
When possible, share the Session ID and Join Phrase through separate paths. Avoid sending the full invite through one insecure or heavily logged channel.
FAQ preview
Short answers for the public trust site.
Do I need an account?
No. Relay Sessions does not require an account, username, phone number, or email address.
Can anyone join?
No. A joiner needs the Session ID, the Join Phrase, and owner approval.
Is there history?
No durable room history is part of the public Sessions design.