How Your Data is Handled
We believe in transparency. Here’s a visual guide to what happens to your data during a transfer.
Your Privacy, Your Keys: True Client-Side Encryption
Unlike many other services, encryption here happens entirely in your browser. Your file is encrypted locally before it’s uploaded, and the secret key is stored only after the “#” in the URL — a part of the link that never reaches our servers. This “zero-knowledge” approach means we can’t see or reconstruct your data, even if we wanted to. It can take a bit longer than server-side encryption, but that extra time ensures true privacy and exclusive control over your files.
Scenario 1: Default Encrypted Transfer
The most secure method for server transfers, using zero-knowledge encryption.
Your Device
You select a file to send.
In-Browser Encryption
The file is encrypted on your device before it's sent.
Our Server
The encrypted, unreadable data is temporarily stored.
In-Browser Decryption
The receiver's browser decrypts the data.
Receiver's Device
The original file is reconstructed.
Scenario 2: Unencrypted Transfer
Used for 6-digit codes, public Shares, private Lockers, and Pastes. Not recommended for sensitive data unless a password is added.
Your Device
You select a file or text.
Plain Data
The data is sent without browser encryption.
Our Server
The original file/text is stored (temporarily or permanently).
Receiver's Device
The receiver accesses the data directly.
Scenario 3: Peer-to-Peer Transfer (Torrents & Rooms)
For maximum privacy, your data never touches our servers.
Sender's Device
You initiate a P2P transfer.
Direct Connection
A secure, direct link is made to the receiver.
Receiver's Device
The file streams directly to the receiver.