Encrypted file sharing
Encrypted file sharing before upload.
Share files with encryption that happens on your device, not just after files reach a provider’s server.
How browser encryption works
SecureTransfer uses the Web Crypto API in your browser to encrypt file data locally. Only encrypted data is uploaded for storage and delivery.
Encryption at rest vs end-to-end encryption
| Model | Who holds keys? | Provider can read? |
|---|---|---|
| Encryption at rest | Provider | Usually yes |
| End-to-end encryption | Sender/recipient browsers | No |
Why provider-held keys are different
If a service holds the encryption keys, its systems can technically decrypt files for scanning, previews, support, or legal requests. Zero-knowledge sharing avoids that by keeping the key out of the upload request.
Common use cases
- Contracts and invoices
- Client deliverables
- Financial records
- Design files and videos
- Private personal documents
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.
- How long do files stay available?
- You choose an expiry from short-lived links to longer storage options; files are deleted after expiry.
- Can I set download limits?
- Yes. You can set a maximum number of downloads for a transfer.
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 →