RelayP2P

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.

Your browserkeys generated here
DTLS 1.3 · direct data channelfiles · chat · nothing in between
Peer's browserkeys generated here
Signaling server

Introduces the two browsers, then steps out of the way.

HANDLESroom codeconnection handshake
NEVER HANDLESfile byteschat messagesencryption keys

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.

Visible to our servers
Room code and expiryNeeded to match two browsers to the same room.
IP addresses during the handshakeUsed to negotiate the connection, not logged with transfers.
Connection type and timingDirect or relay, so we can show status and bill credits.
Account email and credit balanceOnly if you sign in. Guests leave none of this.
Never visible to us
File contentsBytes travel browser to browser inside the encrypted channel.
File names and sizesTransfer metadata rides the same peer-to-peer channel.
Chat messagesPeer-to-peer, gone when the room closes.
Encryption keysGenerated in the browser, per room, and never exported.

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.

01
Encrypted in your browserThe key stays with you and your peer.
02
Held as opaque chunksStored only until your peer collects them.
03
Purged after deliveryChunks are deleted the moment the transfer completes.

UNDER THE HOOD

The short technical version.

TRANSPORTWebRTC data channels
ENCRYPTIONDTLS 1.3
KEY SCOPEper room, browser-generated
SIGNALINGHTTPS, handshake only
NAT TRAVERSALSTUN, TURN fallback
RELAY STORAGEclient-side encrypted chunks
ROOM LIFETIME24h of inactivity
AI PROCESSINGtext extracted locally

Don't take our word for it.

Read the protocol, audit the client, or tell us what we missed.