wolffish relay

How it works

Meet. A desktop and a mobile device both dial out and meet here under an unguessable 256-bit rendezvous ID — no accounts, no port forwarding, at most two sockets per tunnel.

Move. Every frame is sealed end-to-end on the devices before it arrives. The relay forwards ciphertext verbatim — it cannot read, alter, or replay anything.

Forget. Zero retention by construction: no storage, no logs, no analytics. When the sockets close, nothing remains anywhere.

What it can and cannot do

• Cannot readFrames are sealed on-device with ChaCha20-Poly1305 under keys the relay never sees.
• Cannot forgeDevices authenticate each other with pinned keys and a pairing secret shared by QR, never over the network.
• Cannot alterEvery frame is authenticated — one flipped bit fails the tag and is discarded.
• Cannot replayFresh keys each session, with a strictly increasing counter. Past traffic stays unreadable even if a device key later leaks.
• Can seeWhile sockets are live: two IP addresses, the rendezvous ID, and the timing and size of frames. Recorded nowhere.

What is stored here

• Databasesnone
• Logs & tracesnone
• Analyticsnone
• Accountsnone
• Message historynone
• In memoryTwo live sockets and a role tag, for as long as both devices are connected.

The storage meters read 0 B after a verification run moved 249 MB through this relay. Nothing was written, so there is nothing to delete, leak, or subpoena.