Private file sharing
Private file sharing without handing over your content.
Share files without giving a file sharing provider the practical ability to open and inspect your documents.
Private sharing compared
| Method | Privacy risk | Best for |
|---|---|---|
| Copies live in inboxes and mail servers | Non-sensitive small files | |
| Google Drive | Provider-managed account permissions and keys | Collaboration |
| WeTransfer-style services | Convenient, but usually not zero-knowledge | Simple public-ish delivery |
| SecureTransfer | Provider stores encrypted blobs without the key | Private file delivery |
Provider cannot read files
SecureTransfer receives encrypted data and metadata required to operate the transfer. The file contents are encrypted before upload, and the decryption key stays in the share URL fragment.
Why the key-in-fragment pattern matters
The fragment portion of a URL is the part after #. Browsers keep it client-side and do not include it in HTTP requests, which helps keep the decryption key away from the server.
Frequently asked questions
- Is SecureTransfer end-to-end encrypted?
- Yes. Files are encrypted in your browser before upload and decrypted in the recipient’s browser.
- Can SecureTransfer read my files?
- No. The decryption key is stored in the URL fragment, which is not sent to the server.
- Do recipients need an account?
- No. Recipients can open the secure link and download without creating an account.
Ready to send private files?
Upload files from your browser, choose expiry and download limits, then share an encrypted link. Recipients do not need an account.
Send a secure file →