Available for hire — privacy-first apps, engineering, and business-idea work.contact@flowdesk.tech
Flowvault

Flowvault · Restore

Restore from an encrypted backup.

Drop a .fvault file to recreate a vault on this instance. The file itself is still zero-knowledge — every slot stays encrypted under its original password, we simply write the ciphertext and its KDF/volume metadata back into Firestore at the slug you choose. Restoring never needs a password; reading afterwards still does.

flowvault.flowdesk.tech/s/

The slug must be new — restoring on top of an existing vault is intentionally blocked to avoid silent clobber. Pick a fresh URL, or delete the old one first by letting it expire.

← Back to home

How does this stay zero-knowledge?

A Flowvault backup is exactly what the server already has for that vault: an opaque ciphertext blob plus the Argon2id salt and KDF parameters. No password is embedded, and individual notebooks are still packed inside the hidden-volume format — including any decoy passwords you might have added. The file alone is indistinguishable from random bytes without a password, modulo the thin JSON envelope.

Don't have a backup yet? Open any vault and use Export → Encrypted backup in the top toolbar.

Or head back to the home page to open an existing vault.