Privacy

Designed to minimize identity exposure.

Relay Sessions is planned as a temporary browser-room product without accounts, usernames, phone numbers, emails, or permanent identities.

Identity requirements

  • No account required
  • No username required
  • No phone number required
  • No email required
  • No permanent identity required

Temporary room model

  • Temporary room state only
  • No durable room history
  • No inbox
  • No restore
  • No account recovery

RAM-only browser sessions

Browser sessions are designed to be RAM-only. Refreshing or closing the page ends the browser session.

Relay Sessions is designed for conversations that should end cleanly. It is not designed around stored room archives or recovery flows.

Invite sharing guidance

Users should avoid sending the full invite through a single insecure or heavily logged channel.

When possible, share the Session ID and Join Phrase separately. Relay minimizes identity and message exposure, but it does not claim that use is invisible or impossible to observe.

What we do not claim

Clear privacy language matters as much as privacy design.

Identity minimization

Relay Sessions reduces identity requirements, but it does not promise impossible privacy guarantees.

Operational limits

Networks and services can involve limited operational records needed to keep the service available.

Ordinary site access

Relay Sessions works only when the network you are using allows access to the site.

Temporary rooms

The product is for temporary private rooms, not general network access.

No general web relay

Relay Sessions does not carry unrelated web browsing traffic.

No policy override

Availability depends on local network rules and service availability.