A secure file transfer protects the files from everyone except the sender and the intended recipient, including the service in between. In practice that means end-to-end encryption, a link that only the recipient gets, and files that are deleted soon after they are downloaded. Encryption "in transit" alone, the padlock in your browser, is not enough when the provider can read the files once they arrive.
The three kinds of encryption you will see
Most services say files are "encrypted". That word covers three different protections.
| Type | What it protects against | Can the provider read your files? |
|---|---|---|
| In transit (TLS/HTTPS) | Someone on the network, such as public Wi-Fi | Yes, files are decrypted on arrival |
| At rest (server-side) | Stolen disks, some storage breaches | Yes, the provider holds the keys |
| End-to-end (client-side) | Network attackers, server breaches, the provider itself | No, only ciphertext reaches the server |
Almost every service uses TLS and encryption at rest. The difference is who holds the keys. If the provider holds them, its staff, a court order or an attacker with enough access can get readable files. With end-to-end encryption, the key is created on your device and never handed to the provider. This is also called zero-knowledge encryption. Our page on encrypted file sharing explains how it works and which services offer it.
What else makes a transfer secure
Encryption protects the files in storage. These controls limit who can reach them and for how long.
- Link expiry. A transfer that expires after 3 or 7 days can't leak in a breach two years later. Check that the provider actually deletes the files at expiry, not just hides the link.
- Password. Stops a forwarded or intercepted link from working on its own. Send the password through a different channel than the link, for example the link by email and the password by phone or text.
- Download limit. If you set the limit to 1 and the recipient can't download, you know someone else got there first.
- No account for the recipient. Fewer accounts means fewer passwords to phish. The recipient should only need the link.
- Where the data lives. For personal data under the GDPR, a provider that stores files in the EU keeps compliance simpler.
- Metadata. File names, sizes and email addresses are often stored unencrypted, even on end-to-end encrypted services. Name files neutrally if the name itself is sensitive.
Checklist: how to send confidential documents securely
- Use an end-to-end encrypted service, so the provider never holds a readable copy.
- Rename files that reveal sensitive details:
Contract-B.pdf, notJansen-divorce-settlement.pdf. - Set the shortest expiry that works for the recipient.
- Add a password and a download limit for anything confidential.
- Send the link yourself through a channel you trust, and the password through a second channel.
- Confirm receipt. Ask the recipient to confirm they downloaded the files, so you know the download count is theirs.
- Don't reuse the link. Make a new transfer for each recipient, so you can tell who downloaded what.
Sending documents with personal data: ID copies, payslips, tax forms
Often the job is one document: a passport copy for a rental application, payslips for a mortgage, a tax form for your accountant. These files are exactly what identity fraud runs on, so a few extra rules apply.
- Ask whether a copy is needed at all. Under GDPR an organisation should only collect a copy of your ID when it actually needs it, for example because a law requires it. Showing the document is often enough.
- Make a safe copy of your ID. Black out the parts the recipient does not need, such as the national ID number and the photo, and write on the copy who it is for and the date ("Copy for Smith Lettings, 15 Nov 2026"). A marked copy is far less useful to a fraudster.
- Don't send it as a normal email attachment. The attachment stays in your sent folder and the recipient's inbox for years. Send an end-to-end encrypted link that expires, and give the password by phone or text.
- Delete what you no longer need. Once the recipient confirms they have the file, there is no reason for a copy to stay online. Links that expire do this for you.
- Many or large files? A year of bank statements or a folder of scans works the same way; see how to send large files securely.
How RocketShare handles secure transfers
RocketShare is a browser-based file transfer service built around end-to-end encryption. Here is what happens when you send files:
- A new key for every transfer. Your browser generates a random 256-bit key with the Web Crypto API.
- Encryption before upload. Each file is encrypted in chunks with AES-256-GCM, each chunk with its own random IV. GCM also detects tampering: a changed byte makes decryption fail.
- The key stays out of our servers. The key goes in the link after the
#, the URL fragment. Browsers don't send the fragment to servers, so when you share the link yourself, RocketShare never receives the key. - Decryption on the recipient's device. The recipient's browser reads the key from the link and decrypts the files locally.
- Automatic deletion. Encrypted files are permanently deleted when the link expires. No backups of expired files are kept.
- Access controls. With a free account you can add a password and a download limit from 1 to 100,000. Expiry options run from 1 to 90 days, depending on plan.
- EU storage. Encrypted files are stored in Amsterdam, the Netherlands; account data in Frankfurt, Germany.
The full design, including the threat model, is in the security whitepaper. A shorter overview is on the security page.
Honest limits of RocketShare's model
No design protects against everything. These are the limits we think you should know before sending something sensitive.
- Whoever has the full link can decrypt the files. The key is in the link. If the link is forwarded, posted or read from someone's inbox, the files can be opened. A password adds a check, but the password is a server-side access control, not part of the file encryption.
- File names and other metadata are visible to RocketShare. File names, folder paths, sizes, the transfer title and message, and email addresses are stored unencrypted so the service can work. Only file contents are end-to-end encrypted.
- Email delivery passes the key through our servers. If you let RocketShare email the link, the key goes through our server once to send the email. It is not stored or logged, but copying the link and sending it yourself is the stronger option.
- A lost link means lost files. We can't recover the key.
- No virus scanning. We can't scan files we can't read. Recipients should use their own antivirus.
- A compromised device defeats any encryption. Malware on the sender's or recipient's computer can read files before encryption or after decryption.
- No independent audit yet. RocketShare's code is not open source and no third-party security audit has been published. RocketShare also has no two-factor authentication or SSO at the moment.
If you need encrypted file names, audited open-source clients or certifications such as ISO 27001, look at Proton Drive or Tresorit. They are storage products with a different price model, but strong choices for that requirement.
Secure file transfer for regulated work
Lawyers, accountants and healthcare practices often have a duty to take "reasonable measures" to protect client data. End-to-end encryption, short expiry and EU storage help meet that duty, but whether a tool is enough depends on your rules and your client's instructions. We have practical guides for lawyers, accountants and healthcare. None of this is legal advice.
Getting started
You can send up to 2 GB without an account at rocketshare.app, with a link that lasts 3 days. To add a password and download limit, create a free account; it includes 4 GB and 10 transfers per month. Paid plans start at $7 per month for 350 GB and are listed on the pricing page. For large files, see our guide on how to send large files.