# Password Manager whose server cannot decrypt your data | Vault

> Vault only stores encrypted blobs (iv + ciphertext) on the server. AES-256 encryption happens in your browser, and the master password is never sent.

- **Source (source):** https://aistohire.com/vault-encrypted-password-manager-155/f/server-cannot-decrypt-your-data
- **Platform (platform):** AIstoHire
- **Language (language):** en

## In summary

- The server cannot read your passwords: it only stores encrypted blobs
- In Vault, the backend stores opaque blocks {iv, ciphertext}. It does not encrypt, does not decrypt, and never knows your master password.
- Three fields per entry and nothing more
- AES-256-GCM encryption in your browser
- The master password is never transmitted

## The server cannot read your passwords: it only stores encrypted blobs

Vault is a zero-knowledge password manager: all encryption and decryption occur in your browser using the WebCrypto API. Your master password is used to derive an AES-256-GCM key with PBKDF2 (310,000 iterations, SHA-256) which is marked as non-exportable, so even the app's own code cannot extract it. That key encrypts each entry before it leaves your device.

What travels to our servers for each login entry or secure note are exactly three fields: the initialization vector (iv), the ciphertext, and the entry type. Nothing more. The site, username, password, and notes are contained within the ciphertext, which for the backend is a meaningless base64 string.

From the vault itself, only public parameters are stored: the random salt, the number of PBKDF2 iterations, and a verifier encrypted with your own key. With these, your browser can re-derive the key and check if the master password you just entered is correct. That check happens on your device: the server never receives the master password, neither in plain text nor hashed, and would not be able to tell if it is correct or not.

The backend also has no code to attempt it. Its operations are to store, list, update, and delete encrypted blobs: it validates that the iv and ciphertext are not empty and stores them as is. There is no encryption or decryption function on the server, nor any key that would unlock it. If tomorrow someone compromised the database, they would take away unreadable data.

## What's included

- **Three fields per entry and nothing more** — the server only receives {iv, ciphertext, type}. The site, username, password, and notes are encrypted within the ciphertext.
- **AES-256-GCM encryption in your browser** — the key is derived with PBKDF2 and 310,000 iterations, and created as a non-exportable WebCrypto key. It is not stored on any server.
- **The master password is never transmitted** — it is not sent in plain text or hashed. The server does not store it and has no way to validate it.
- **Client-side validation with a verifier** — the server stores a small encrypted blob, and your device checks if the master password decrypts it. AES-GCM fails if the key is incorrect or if the data was tampered with.
- **A database leak does not expose secrets** — anyone who took the tables would see encrypted base64. Without your master password, there’s nothing to read.
- **There is no backdoor because there is no door** — the backend does not include any encryption or decryption routines. It’s not an internal policy; the code simply cannot do it.
- **Honesty about metadata** — the entry type (login entry or secure note) and creation and modification dates are stored in plain text, because the app needs them for sorting and listing. The content, never.
- **The trade-off you should know** — if you forget your master password, no one can recover your data. There’s no email reset, and that’s precisely the proof that the server cannot decrypt it.

## Frequently Asked Questions

### What exactly does the Vault server store for each password?

Three fields: the initialization vector (iv), the ciphertext, and the entry type (login entry or secure note), plus creation and modification dates. The site, username, password, and notes travel encrypted within the ciphertext with AES-256-GCM, so for the server, they are meaningless base64.

### Can AIsToHire or an employee see my passwords?

No. The Vault backend does not contain any encryption or decryption functions, and it does not store any key that could open your data. The AES-256 key is derived from your master password in your browser with PBKDF2 and is created as a non-exportable key, so it never leaves your device. It’s not an internal policy promise: it’s that there is nothing to decrypt with.

### What would happen if someone stole Vault’s database?

They would obtain encrypted blobs with AES-256-GCM, along with the public salt and the number of PBKDF2 iterations. Without your master password, these blobs are unreadable, and the master password is not on the server. The only clear information visible would be minimal metadata: whether an entry is a login entry or a secure note, and when it was created or modified.

### How does Vault know my master password is correct if it doesn’t send it?

With a verifier. When creating the vault, your browser encrypts a small known value with your derived key and saves the result on the server. When unlocking, your device re-derives the key and attempts to decrypt that blob: AES-GCM fails if the key is incorrect. The check is local; the server only safeguards the encrypted blob.

### Can I recover my data if I forget my master password?

No, and that is a direct consequence of the model. Since the server cannot decrypt, it also cannot reconstruct your entries or offer you a password reset via email. Store your master password in a safe place before you start using Vault: that is the trade-off for nobody else being able to read your passwords.

- [Vault — End-to-end encrypted password manager](https://aistohire.com/vault-encrypted-password-manager-155)

## About the platform

**Vault — End-to-end encrypted password manager** — an app by AIstoHire. Available at: https://aistohire.com/vault-encrypted-password-manager-155/f/server-cannot-decrypt-your-data

### Other languages

- `es`: https://aistohire.com/es/vault-gestor-contrasenas-cifrado-155/f/servidor-que-no-puede-descifrar-tus-datos
- `fr`: https://aistohire.com/fr/vault-gestionnaire-mots-de-passe-chiffre-155/f/serveur-qui-ne-peut-pas-dechiffrer-vos-donnees
- `it`: https://aistohire.com/it/vault-gestore-password-crittografato-155/f/server-che-non-puo-decifrare-i-tuoi-dati
- `pt`: https://aistohire.com/pt/vault-gerenciador-senhas-criptografado-155/f/servidor-nao-pode-descriptografar-seus-dados
- `de`: https://aistohire.com/de/vault-ende-zu-ende-verschluesselter-passwort-manager-155/f/server-kann-deine-daten-nicht-entschluesseln
- `bg`: https://aistohire.com/bg/vault-menidzhar-na-paroli-s-kriptirane-ot-kray-do-kray-155/f/survarat-ne-mozhe-da-razshifrova-dannite-vi
- `ja`: https://aistohire.com/ja/password-manager-ango-ka-155/f/server-ga-fukugou-dekinai-password-manager
- `nl`: https://aistohire.com/nl/vault-wachtwoordbeheerder-met-end-to-end-versleuteling-155/f/server-die-je-gegevens-niet-kan-ontsleutelen
- `ko`: https://aistohire.com/ko/vault-bimilbeonho-gwanlija-amhohwa-155/f/seobeoga-bokhohwahal-su-eomneun-bimilbeonho
- `sv`: https://aistohire.com/sv/vault-losenordshanterare-med-end-to-end-kryptering-155/f/server-som-inte-kan-dekryptera-dina-data
- `da`: https://aistohire.com/da/vault-adgangskodemanager-med-ende-til-ende-kryptering-155/f/server-der-ikke-kan-dekryptere-dine-data
- `ar`: https://aistohire.com/ar/vault-mdir-klmat-mrur-mshfr-mn-trf-ila-trf-155/f/khadim-la-yastati-fakk-tashfir-bayanatik
- `no`: https://aistohire.com/no/vault-passordbehandler-med-ende-til-ende-kryptering-155/f/server-som-ikke-kan-dekryptere-dataene-dine
- `fi`: https://aistohire.com/fi/vault-paasta-paahan-salattu-salasanahallinta-155/f/palvelin-joka-ei-voi-purkaa-tietojasi
- `zh`: https://aistohire.com/zh/vault-end-to-end-encrypted-password-manager-155/f/fuwuqi-wufa-jiemi-nide-ziliao
- `pl`: https://aistohire.com/pl/vault-menedzer-hasel-z-szyfrowaniem-end-to-end-155/f/serwer-ktory-nie-moze-odszyfrowac-twoich-danych
- `he`: https://aistohire.com/he/vault-mnhl-sismaot-motspn-mktsh-lktsh-155/f/shereth-shelo-yachol-lefanei-ach
- `cs`: https://aistohire.com/cs/vault-spravce-hesel-s-koncovym-sifrovanim-155/f/server-ktery-nemuze-desifrovat-vasa-data
- `id`: https://aistohire.com/id/vault-pengelola-kata-sandi-terenkripsi-end-to-end-155/f/server-yang-tidak-bisa-mendekripsi-data-anda
