When you use Send, your files are encrypted on your device before anything is uploaded. That means:
No one (not even Hivenet) can read your file contents
Files stay encrypted while stored across the distributed network
The only way to decrypt the file is with the unique download link
This is called end-to-end encryption and it’s baked into every transfer by default. You don’t need to turn it on. You can’t turn it off. It’s just how Send works.
What kind of encryption does Send use?
We use AES-256 encryption to secure each chunk of your file. It’s a strong, industry-standard algorithm used for everything from cloud storage to banking systems.
In simple terms: Your file is locked with a key only your link can unlock — and that key is never shared with us.
What if I add a password?
Adding a password gives your transfer an extra layer of encryption. Even if someone gets the download link:
They won’t be able to open the file
They’ll be prompted to enter the correct password first
We never store or recover your password. It’s all handled in the browser
You’ll need to share the password separately (e.g. over chat or in person).
What about metadata?
We don’t collect or store:
File names
File contents
User messages
Recipient info (since you share the link yourself)
We only keep temporary logs for performance and security — and only for as long as needed to deliver your file.