How vaultfold keeps your passwords safe.
The short version: your vault is encrypted on your devices and we never have your key, and we publish exactly what vaultfold protects and what it cannot.
What if vaultfold's servers are hacked?
Today your vault lives in git or a folder you choose, not on a server of ours. We never have your key, so there is nothing readable for anyone to take from us.
What if someone copies my vault?
vaultfold is built on the assumption that your vault files will be copied one day. Without a key held on one of your devices, a copy is unreadable.
What if I lose a device or forget my passphrase?
We cannot reset your vault, because we cannot open it. Keep your passphrase somewhere safe. Two things are on the way:
- Coming soon: Add a new phone or device by scanning a QR code on a device you still have, and remove the old one so it cannot open anything new.
- Coming soon: A printable recovery kit gets you back in if every device is lost.
What happens when someone leaves?
When someone leaves, remove them in one step; vaultfold lists exactly which passwords they could see, so you know what to change and can tick each one off. They cannot open anything added after they are removed.
What can vaultfold not protect against?
vaultfold cannot protect a device that is already infected while it is unlocked, a person who has already seen a password, or a weak passphrase on a stolen device. The full list is in the threat model.
Read it for yourself
Read the threat model in full, and the decisions behind it. Coming soon: The core of vaultfold (the command line, the daemon, the file format, the protocols and the server) will be open source under Apache-2.0 when the repository goes public.