A password manager appears to present a paradox. It can produce the password for your bank, shopping account or email on demand, yet a well-designed service may say its staff cannot read any of them. The trick is that the service stores an encrypted vault, while the information needed to unlock it is controlled on your device. The manager is holding a sealed box and helping you move it between devices; it does not need a copy of your key.¹
That is the design principle. Particular products implement it differently, and the promise has limits. It is worth following one password from the moment you save it to the moment you use it.
The vault is locked before it travels
When you enter a site password into a manager, the app can encrypt the vault on your own device before sending a copy to a synchronisation server. Encryption turns readable entries into data that should be unintelligible without the correct cryptographic key. In Bitwarden's documented design, encryption and key management occur in the client, and its servers do not hold the user's master password or vault-decryption keys.¹
The server can store and return the encrypted data so that your phone and computer remain in step. It needs to know enough to run your account and deliver the right vault, but it need not see the secrets inside. The phrase zero knowledge is often used for this arrangement. It is a product-security term rather than a guarantee that the provider knows literally nothing about you: an account email or other operational information may still be visible to it.²
Consider a physical analogy. You lock a notebook in a box at home and ask a courier to store and deliver copies of the locked box. The courier can move it but cannot read the notebook if you keep the only key. Real encryption is more complex than a metal lock, and the analogy does not address compromised software, but it explains why storage and knowledge of contents can be separated.
What the master password does
A master password, or account passphrase, is usually the secret you remember. It is used to help derive a cryptographic key that unlocks the vault. A key derivation function deliberately makes the transformation computationally costly. That matters if an attacker obtains an encrypted vault and tries many guesses offline: each guess should take more work than simply checking a fast list of words. Bitwarden documents support for PBKDF2 and Argon2id in its key-derivation options.¹
A strong, unique master passphrase remains important because an attacker who can guess it may eventually decrypt stolen vault data. Some managers add a second secret kept on your devices. 1Password, for example, combines an account password with a randomly generated Secret Key, which it says never travels to its servers. The Secret Key is meant to make a stolen server copy harder to attack even if the human-chosen password is guessable.³ This is a particular product design, not a feature to assume every manager has.
The distinction between a password's hash and encryption can be confusing. Websites normally should store a one-way password hash to check a login without needing to retrieve the original password. A password manager, by contrast, must retrieve the site password so it can fill it in or show it to you. It therefore needs reversible encryption for the contents of the vault, protected by keys that the provider should not possess. OWASP explains why hashing and encryption serve different jobs.⁴
How does the service know you may sign in?
Authentication and decryption are related but separate. A service can check that you are authorised to receive your encrypted vault without being able to open it. Once the app has the vault, it uses secrets available on your device to decrypt entries for you. Some products have additional devices, recovery arrangements or organisational features that alter the details, so an absolute claim about every password manager would be misleading.¹,³
This separation has an uncomfortable consequence: if you lose the secrets required to decrypt the vault, the provider may not be able to reconstruct them for you. Bitwarden says it cannot retrieve or reset a forgotten master password in the way an ordinary website might. It offers account-recovery routes in some circumstances, but those depend on what was set up beforehand or what access remains on another device.⁵
It also explains why syncing is useful without being equivalent to giving the provider your passwords. A cloud copy can help you recover from a broken laptop, provided you still have what is needed to unlock it. A local-only manager avoids a remote vault copy but creates different backup responsibilities. The UK's National Cyber Security Centre describes both on-device and cloud-sync approaches and their respective risks.⁶
What encryption cannot protect
The vault must be decrypted somewhere for you to use it. If an attacker controls an unlocked device, tricks you into revealing the master secret, or captures a password when it is filled into a fraudulent website, the strength of the encrypted server copy may not help. Password managers are software and can have vulnerabilities; a successful compromise can expose many accounts at once. The NCSC stresses these risks while judging that managers can still improve security by making unique passwords practical.⁶
A good manager also cannot change the fact that the websites you visit have their own security. Its advantage is that it can generate a distinct password for each site, limiting the damage if one site's password is leaked and tried elsewhere. NIST recommends password managers for this reason and advises protecting the manager account with multifactor authentication where supported.⁷
The answer to the paradox is a division of labour. The service stores and synchronises an encrypted vault; your device, with your unlocking secrets, turns it back into readable passwords when needed. That architecture can keep a provider from knowing the contents it carries. Its success still depends on the manager's implementation, a strong account secret, sound recovery plans and the security of the device on which the vault is opened.