Encrypt before upload
Your phone or tablet encrypts each document before it is sent. Ciphertext goes to object storage through short-lived upload links. Document bytes do not pass through our API as readable files.
Keys stay with you
A master key protects your vault. It is wrapped by your password and by a recovery code (and can later be wrapped by other unlock methods). We store those wraps; we do not store a usable copy of the master key. Without your password or recovery code, the wraps are useless.
Metadata is encrypted too
Filenames, tags, notes, and folder structure are encrypted on the device. The server does not get a plaintext label like passport.pdf to index or inspect. Search happens on your device after unlock.
What “zero-knowledge” means here
Staff cannot open your documents to help with a support ticket. There is no admin view of file contents. The honest trade-off: if you lose both password and recovery code, access cannot be restored.
What we still see
Account email, authentication records, and technical metadata needed to run the service (for example object sizes and timestamps). See the Privacy Policy for details.
Mobile vs browser
The first client is the mobile app, where keys can sit behind the platform keystore and biometrics. A web vault is planned later; browsers re-download application code on each visit, which is a weaker trust model we will describe honestly when that ships.