SecureVault
Establishing private session…
aes-gcm · fragment-key · burn-on-read · zero-knowledge
SecureVault
Establishing private session…
aes-gcm · fragment-key · burn-on-read · zero-knowledge
FAQ
Common questions about one-time secret links, self-destructing messages, and encrypted file sharing.
Create a SecureVault link with your password, share only that link, and optionally add a passphrase. The password is encrypted in your browser and can self-destruct after viewing.
A temporary encrypted URL that reveals a secret a limited number of times. After the view limit is reached, SecureVault permanently deletes the ciphertext.
Yes. Set a view limit and lifetime so the message burns after reading or expires automatically. Later visits show that the secret is gone.
Yes. Switch to the File tab, choose a file up to 2 MB, and create a link. The file is encrypted locally; recipients decrypt and download it in their browser.
Usually yes for sensitive values. Email keeps a long-lived copy in inboxes. A burn-after-reading encrypted message link reduces leftover copies in chat and email history.
No. Encryption happens in your browser. We only store ciphertext, and the key stays in the URL fragment that never reaches the server.
No. Create a link, share it, and the recipient opens it — no sign-in required.
We cannot recover it. Without the fragment key (and passphrase, if used), the ciphertext is useless.