Vault encrypts and decrypts every password within your own browser: your master password never travels to any server.
If a password manager can read your data, the day it's breached, you're breached too. Vault is built to make that impossible.
Vault is AIsToHire’s password manager with end-to-end zero-knowledge encryption: https://aistohire.com/vault-encrypted-password-manager-155. When you enter your master password, the browser derives an AES-256 key from it using PBKDF2-SHA256 with 310,000 iterations and a random salt unique to your account. That key remains in memory and is not exportable: neither the app nor an extension can extract it from the browser.
Every login entry and every secure note is converted to JSON and encrypted with AES-256-GCM before leaving your device, with a different random Initialization Vector (IV) for each operation. The only thing the server receives is an opaque block {iv, ciphertext}: there are no titles, users, or URLs in plaintext. Upon unlocking, decryption happens again in your browser, entry by entry.
Your master password is never sent, not even to verify if it's correct. Vault stores a «verifier» encrypted with your own key: if it decrypts, the key is good; if not, AES-GCM fails and the Vault does not open. That is the same mechanism that guarantees data integrity, because GCM detects any manipulation of the ciphertext.
The practical consequence: if someone copied the entire database, they would get noise. Without your master password, there is no way to decrypt anything, and that password is not on the server. That also means there is no «password recovery» for the master password: that is the honest price of the zero-knowledge model.
The master password does not leave your device
it is used to derive the encryption key in the browser and is not transmitted or stored anywhere, not even as a hash.
AES-256-GCM with WebCrypto
authenticated encryption implemented by the browser itself, with a random IV for each operation and built-in tamper detection.
PBKDF2-SHA256 with 310,000 iterations
deriving the key takes computational time, which significantly increases the cost of any brute-force attempt on your master password.
The server only sees opaque blobs
it stores {iv, ciphertext} pairs without readable metadata, so a database leak won't reveal even a website name.
Validation without transmitting anything
the master password is checked by locally decrypting a verifier, not by sending it to a login API.
It's verifiable, not a marketing promise
encryption lives on the client, and you can see in development tools that what's sent over the network is already encrypted.

Create your free account, choose your master password, and start saving login entries that only you can read.