Encrypted File Sharing
Share files with end-to-end encryption so only authorized recipients can read the content.
Send a due-diligence pack to outside counsel without it sitting readable in anyone's inbox or drive.
End-to-end encrypted file storage where plaintext never touches the server. Encrypted manifests and policy-based access by design.
What it does
Share files with end-to-end encryption so only authorized recipients can read the content.
Send a due-diligence pack to outside counsel without it sitting readable in anyone's inbox or drive.
Protect sensitive snapshots and collaborate on intermediate research outputs with controlled visibility.
Circulate an unpublished cohort dataset to three collaborators while the paper is still under review.
Encrypt and share remote repositories while preserving traceability and confidentiality across teams.
Keep a security-sensitive codebase mirrored off-site without handing the source to whoever hosts it.
Sync local encrypted directories across devices without exposing plaintext in transit or at rest.
Start an analysis on the office workstation, finish it on a laptop, and never leave a readable copy in between.
Apply fine-grained access control for hosted web applications with policy-based permissions.
Give a contractor access to one project for the length of an engagement, and take it back in a click.
How it works
The guarantee is a property of the design rather than a promise about our staff.
Your files are encrypted on your own device, before anything is sent. The passphrase that unlocks them is yours, and it does not travel with the file.
What reaches our servers and our storage is unreadable. File names, folder structure and file types are scrambled along with the contents, so even the shape of your work stays private.
Unlocking happens back on a device you trust. You decide who holds a key — only you, named teammates, your whole team, or anyone with a link.
Being straight about it
The same design that keeps us out keeps us from helping in a few places. Those are here rather than in the small print.
Who it is for
Questions
No. Files are encrypted before they leave your device, and we never receive the key. What we hold is unreadable to us, and that is a property of the design rather than a promise about our staff.
The project cannot be opened again. There is no reset link and no back door for us to use on your behalf — the same reason nobody else can open your files. Keep passphrases in a password manager, and use a policy that shares the key with your team so one person is never the single point of failure.
Account and billing details, that a project exists, and the ordinary operational facts of storage — roughly how much is held, and when it changed. Not the contents, not the file names, not the folder structure.
Locking and unlocking happen on your own device, in the background, while you work. The place people notice Vault is the moment of choosing who gets a key, which is the decision you wanted to make consciously anyway.
Talk to us. Vault is already built so that the storage it runs against holds nothing readable, which makes the deployment conversation a short one.
Request access below. We will set up your first project with you, help you pick a sharing policy that matches the sensitivity of the work, and share the design documentation your security team will want to read.
Vault is granted rather than signed up for. Say what you are storing and who needs to open it, and we will tell you whether it fits.