
SECURITY
We can't leak what
we never receive.
Relay connects two browsers over an encrypted WebRTC channel. There is no upload step, so there is no copy on our side to breach, hand over or forget to delete.
Introduces the two browsers, then steps out of the way.
PRINCIPLES
Private by architecture, not by policy.
A privacy policy is a promise. These are constraints built into how Relay works.
End-to-end encrypted
WebRTC data channels use DTLS 1.3. Keys are generated per room and never leave the two browsers.
Nothing stored
Direct transfers never touch a disk on our side. There is no upload, no bucket and no retention window.
Rooms expire
Rooms close after 24 hours of inactivity. Chat history and file lists vanish with the room.
No account required
Guests can send without an email or a password. We can't lose data we never asked for.
AI reads text, not files
Work with AI extracts text locally in your browser. The file stays on your device; only that text reaches the model.
Open protocol
Signaling and relay formats are documented. Audit the client, or self-host the relay.
DATA WE TOUCH
What our servers see, and what they never do.
WHEN DIRECT ISN'T POSSIBLE
Cloud relay carries sealed boxes.
Some networks block peer-to-peer traffic. Signed-in users can route through our relay instead. The file is encrypted before it leaves your browser, so the relay moves data it cannot open.
UNDER THE HOOD
The short technical version.
Don't take our word for it.
Read the protocol, audit the client, or tell us what we missed.