Two codes, two different jobs
A Decoy Vault and a Duress Vault solve different problems, and it's worth being precise about which one does what before you're relying on either.
The Decoy Vault opens on a second code and shows exactly what you stocked it with in advance — a set of ordinary files you chose. It's for the situation where you need to unlock something, and an empty vault would itself be suspicious.
The Duress Vault is a third code that opens an empty vault and wipes your real ones as it does. And it isn't left as a conspicuous empty shell afterwards: that vault becomes your main vault, as though nothing else had ever been on the device. It's for the situation where the files genuinely cannot survive the unlock — not diverting attention, but making sure there's nothing left to find. Which one applies depends entirely on what you're facing, and both are configured by you ahead of time, not improvised in the moment.
One vault, not two separate tools
Source material tends to live wherever you were when you received it — a phone in the field, a laptop back at the desk. Vaultine runs on Windows, macOS, iOS and Android, so it's the same encrypted vault either way, not a phone app you also have to remember to mirror onto a laptop.
Folder import matters here too: an existing folder of documents comes in as a folder, not as thirty individual files added one at a time.
Nothing to compel
Vaultine has no account system and no server that holds your files or your encryption key. The key is derived from your code, on your device, and it never leaves. That's a design decision with a practical consequence: there is no vendor-side copy of your source material for anyone to request, subpoena or breach — because it was never there to begin with.



