Vault locks your files on your own device, before anything is sent. What reaches our servers is unreadable — the contents, the file names, the folder structure, all of it.
That one idea covers a lot of ground: sharing confidential files, holding unpublished research, protecting a codebase, syncing a working folder across machines, and deciding who may open a hosted app.
The same project, before and after it leaves your device. The second state is the only one anybody else ever sees.
Most storage answers these with policy — who is allowed to look, and who promises not to. Vault answers them with arithmetic.
Who can read the file contents
UsuallyYou, and whoever operates the service
With VaultOnly the people you give a key to
Who can see file and folder names
UsuallyVisible to the provider in plain text
With VaultScrambled along with the contents
If the storage is breached
UsuallyAttackers walk away with your documents
With VaultAttackers walk away with noise
If a rogue employee goes looking
UsuallyAccess controls are the only thing stopping them
With VaultThere is nothing readable to find
If someone with legal power demands the data
UsuallyThe provider can hand over your files
With VaultWe can only hand over what we hold: ciphertext
No plugins to install for your recipients, and nothing for your team to remember beyond a passphrase.
Worth knowing before you adopt it, rather than after:
01
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.
02
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.
03
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.
One encryption model, applied across the places sensitive work actually lives.
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.
Who is it for
Teams handling confidential files across legal, finance, operations, and client delivery.
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.
Who is it for
Research labs, principal investigators, and collaborators sharing intermediate experiment results.
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.
Who is it for
Distributed engineering teams building sensitive codebases and internal security tooling.
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.
Who is it for
Researchers and hybrid teams who work locally first and need secure multi-device continuity.
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.
Who is it for
Platform admins and product owners managing role-based access for internal or external users.
Private Data Snapshots · Synced Local Directories · Encrypted File Sharing
Encrypted Remote Repositories · Hosted App Access Control · Synced Local Directories
Encrypted File Sharing · Hosted App Access Control
Convenience and confidentiality pull against each other, so Vault makes it an explicit choice rather than a default you never saw.
The key is never kept anywhere. Every time a project is opened, someone has to supply the passphrase. The strongest of the four, and the one Vault starts you on.
Best for
Board papers, patient data, anything you would hand-carry
The key stays on one machine you control, so routine work does not stop to ask twice. Nothing is added to what the server knows.
Best for
Your own laptop — never a shared or borrowed machine
Every teammate's device gets its own sealed copy of the key, which only that device can open. People can be added or removed without re-encrypting a single file.
Best for
Working groups, project teams, and long-running collaborations
A link that opens the project without an account. The most convenient and the weakest of the four, and Vault says so in the interface when you pick it.
Best for
Previews and handoffs you would be comfortable emailing
Most security promises ask you to believe in a provider's staff, controls and good intentions. Vault removes the question: we cannot read what we never receive in readable form.
File sharing, research snapshots, repositories, synced folders and app access all sit on the same protection. One thing to learn, one thing to explain to your auditor.
Protected work can be kept current straight from the pipeline your team already runs, so nothing depends on someone remembering to re-upload the latest version.
Vault is built by the Neurasense cryptographic research team and documented in a full design paper we share with prospective customers under agreement.
Access comes with a walkthrough: choosing the right sharing policy per project, handling passphrases properly, and getting your first team moved across.
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.
Access is granted by request. Tell us what you need to protect and we will set up the first project with you, or walk your security team through the design.