Zero-Storage streaming
Bytes flow device-to-device. There is no bucket, no queue and no temporary copy for anyone to leak, subpoena or scan.
Your browser encrypts every chunk with AES-256-GCM and streams it straight to the receiver over a WebRTC DataChannel. No upload. No server-side copy. The decryption key lives only in the link’s #fragment — browsers never send it to us.
A transfer tool where privacy isn’t a policy — it’s the architecture.
Bytes flow device-to-device. There is no bucket, no queue and no temporary copy for anyone to leak, subpoena or scan.
A fresh 256-bit key is generated per transfer with WebCrypto. Every chunk is authenticated, so tampering or truncation is detected.
Direct peer connections with STUN/TURN fallback, flow control and windowed acknowledgements for steady multi-GB throughput.
Links look like /r/ID#key=…. Fragments never reach servers, and we send Referrer-Policy: no-referrer everywhere.
Receivers stream decrypted data directly into a file via the File System Access API, so RAM stays flat even for huge files.
Pro users get memorable /s/your-name links and content-free delivery receipts: size, time, outcome — never names or contents.
Drop it into the app. A random AES-256 key is generated locally and never leaves your device except inside the link you share.
Send /r/ID#key=… over any channel. Keep your tab open — your device is the server.
The receiver proves it holds the key, accepts the file, and decrypts chunk by chunk while saving to disk.
| Data | Visible to P2P Streamer? | Why |
|---|---|---|
| File contents | Never | Encrypted in the browser, sent peer-to-peer. |
| File name & type | Never | Encrypted metadata frame inside the DataChannel. |
| Encryption key | Never | Only in the URL fragment; not sent in HTTP requests or referrers. |
| SDP / ICE candidates | Yes (transient) | Needed to connect the peers; deleted when the session expires. |
| Declared size, timing, outcome | Yes | Used for plan limits and your delivery log. |
Receivers prove possession of the key (an encrypted handshake bound to the session) before any file data is sent, and every chunk carries an authenticated counter to prevent reordering, replay and truncation.
Secure checkout by Paddle. Prices shown in your local currency when available.
For quick, occasional transfers.
For teams and creators who send big files daily.
/s/your-nameNo subscription. One token = one transfer up to 10 GB.
10 transfers · up to 10 GB each
50 transfers · best value
Yes. Because nothing is stored, the file streams from the sender’s device. Keep the tab open until the receiver finishes.
The key exists only in the link. If it’s lost, the transfer can’t be decrypted — by anyone, including us. Just start a new transfer.
Chrome, Edge and other Chromium browsers stream straight to disk. Firefox and Safari work too, but buffer the file in memory, so very large files are limited.
No. Receivers are signed in anonymously and only need the link.
Anytime, from the billing portal in the app. Pro stays active until the end of the paid period.