Why Your Password Manager's Architecture Matters More Than Its Feature List
Quick answer: What protects your passwords is not the word "encrypted" but whether the company can read your vault. Zero-knowledge managers encrypt on your device and never hold the key. Server-side encryption leaves the key with the provider. The 2022 LastPass breach showed the difference. Compare architecture, business model and jurisdiction before you compare features.
Feature comparisons miss the point. The encryption model, business incentives, and legal jurisdiction of your password manager determine whether your data is actually private.

Your password manager is arguably the most sensitive piece of software you use. It holds every credential, email accounts, banking logins, work systems, medical portals, in one encrypted vault. If that vault is compromised, everything is compromised.
Most password manager reviews compare autofill speed, UI polish, and browser extension quality. Those things affect daily convenience. But they tell you nothing about the question that actually matters: what stops the company running the server from reading your data?
The answer depends on three things most reviews skip: the encryption architecture, the business model behind the company, and the legal jurisdiction it operates under.
What "Encrypted" Actually Means for Your Passwords
Every major password manager describes itself as "encrypted." But that word covers a wide range of implementations, and the differences are consequential.
Server-side encryption vs. zero-knowledge
Server-side encryption (also called "encrypted at rest") means the company encrypts your data on their servers. The company holds the encryption keys. This protects against an outsider breaking into the server, but it does not prevent the company itself, or anyone who compromises the company, from accessing your data.
Zero-knowledge encryption (also called end-to-end encryption) means your data is encrypted on your device before it leaves. The server only ever sees encrypted blobs. The company does not hold a key that can decrypt your vault. Even if served with a court order, they cannot produce your passwords, because they structurally cannot access them.
How master password derivation works
In a zero-knowledge system, your master password is never sent to the server. Instead, the app uses a key derivation function (like Argon2 or PBKDF2) to generate an encryption key locally. Your vault is encrypted and decrypted entirely on your device. The server stores the encrypted vault and authenticates you, but cannot read the contents.
Zero-knowledge in plain language: Imagine locking your documents in a safe, then handing the safe to a storage company. They can store it and give it back to you, but they don't have the combination. That's what zero-knowledge encryption does for your passwords. The company stores your encrypted vault but never has the key to open it.

The practical difference: if a zero-knowledge password manager's servers are breached, the attacker gets encrypted data they cannot read. If a server-side encrypted system is breached and the keys are also compromised, the attacker gets everything.
The LastPass Breach: A Case Study in Why Architecture Matters
In August 2022, LastPass disclosed that an attacker had accessed their development environment. By December 2022, they revealed the full scope: the attacker had stolen copies of customer vault data, the actual encrypted vaults containing usernames, passwords, and secure notes.
This breach is instructive not because LastPass was uniquely careless, but because it demonstrated exactly how encryption architecture determines the real-world impact of a breach.
What happened
According to LastPass's own public disclosures: the attacker compromised a developer's home computer, used stolen credentials to access cloud storage, and exfiltrated backup copies of customer vaults. The encrypted vault data included website URLs stored in plaintext alongside encrypted username and password fields.
Why architecture mattered
LastPass uses zero-knowledge encryption for vault contents. So the stolen vaults were encrypted. But the strength of that encryption depended entirely on each user's master password. Vaults protected by weak or reused master passwords were vulnerable to offline brute-force cracking, and the attacker had unlimited time to try.
Security researchers subsequently reported evidence of vaults being cracked, with stolen cryptocurrency linked to LastPass vault data.
The lesson: "Encrypted" is not a binary state. Implementation details matter enormously. How the encryption is applied, what's encrypted versus stored in plaintext, and how master password strength is enforced all determine whether the encryption actually protects you in a breach scenario.
The breach also highlighted a jurisdiction point. As a US company (owned by GoTo, formerly LogMeIn), LastPass's breach response and disclosure timeline were subject to US regulatory frameworks, which have no single federal data breach notification standard comparable to the GDPR's 72-hour notification requirement.
Business Models Shape Privacy Decisions
A password manager's business model tells you something about its long-term incentives, and how likely it is that privacy will remain a priority.
Venture capital and growth pressure
1Password has raised $920 million in venture capital. VC funding isn't inherently problematic, but it creates structural pressure: investors expect returns, which means either an IPO or an acquisition. Both scenarios introduce uncertainty about future data handling practices. A company that's privacy-focused today may be acquired by a company with different priorities tomorrow.
Private equity and cost-cutting
LastPass was spun off from GoTo (formerly LogMeIn) as part of private equity transactions. Private equity ownership typically prioritizes profitability, which can mean reduced investment in security infrastructure, the kind of cost-cutting that's invisible until something goes wrong.
Subscription + privacy mission
Proton (the company behind Proton Pass) is a subscription-funded company headquartered in Switzerland. Founded by scientists who met at CERN, its business model is straightforward: charge for premium features, don't sell data. This alignment, where revenue comes from users, not from monetizing user data, creates different structural incentives than VC or PE ownership.
Open source as accountability
When a password manager's code is open source, security researchers can verify that the encryption works as advertised. This doesn't guarantee security, but it provides a layer of accountability that closed-source products lack. Among major password managers, Proton Pass, Bitwarden, and KeePassXC publish their source code. 1Password and LastPass do not.
The jurisdiction dimension
Where a company is headquartered determines which laws govern its data handling. US-based companies are subject to the CLOUD Act and FISA Section 702. Swiss companies operate under the Federal Act on Data Protection (FADP), which requires Swiss court authorization for foreign data requests. For a deeper look at how jurisdiction affects privacy, see our analysis of VPN jurisdiction, the same principles apply to password managers.
How Four Password Managers Compare on Architecture
Here's how four major password managers stack up on the structural factors that determine whether your data is actually private:
| Proton Pass | Bitwarden | KeePassXC | 1Password | LastPass | |
|---|---|---|---|---|---|
| Headquarters | Switzerland | US | Open source (no HQ) | Canada (US infra) | US (GoTo) |
| Encryption model | Zero-knowledge (E2EE) | Zero-knowledge (E2EE) | Local-only encryption | Zero-knowledge (E2EE) | Zero-knowledge (E2EE) |
| Open source | Yes (all apps) | Yes (all apps) | Yes | No | No |
| Independent audits | Yes (Cure53) | Yes (multiple) | Community-audited | Yes (multiple) | Yes (multiple) |
| Free tier | Yes (unlimited passwords) | Yes (unlimited passwords) | Yes (fully free) | No | Yes (1 device type) |
| Email aliases included | Yes (10 free, unlimited paid) | No | No | No (Fastmail partnership) | No |
| Business model | Subscription + mission | Open-core (freemium) | Volunteer/donations | VC-funded ($920M) | Private equity (GoTo) |
| Breach history | None publicly known | None publicly known | None publicly known | None publicly known | Multiple incidents (2022) |
| CLOUD Act exposure | No (Swiss jurisdiction) | Yes (US company) | No (local storage) | Partial (US infrastructure) | Yes (US company) |
Proton Pass

Swiss jurisdiction, zero-knowledge encryption, and fully open source apps audited by Cure53. The free tier includes unlimited passwords and 10 email aliases, a feature that reduces your phishing surface by letting you use a unique email per site. Part of the broader Proton ecosystem (mail, VPN, drive, calendar), which allows a single subscription to cover multiple privacy tools.
The trade-off: it's a newer product (launched 2023) with a smaller extension ecosystem than older competitors. Team and enterprise features are still maturing.
Bitwarden

The leading open-source password manager, US-based but with a transparent codebase and multiple independent audits. Its free tier is generous and its self-hosting option gives technical users full control. Business and enterprise plans are competitively priced.
The trade-off: US headquarters means CLOUD Act exposure. Self-hosting mitigates this but requires technical setup and maintenance.
KeePassXC

A fully offline, open-source password manager. Your encrypted database lives on your device, no cloud, no servers, no company that could be compelled to hand over data. This is the strongest possible architecture for data sovereignty.
The trade-off: no cloud sync (you manage syncing yourself via Dropbox, Syncthing, etc.), no mobile app from the KeePassXC project (though compatible apps like KeePassDX exist), and no built-in sharing features.
1Password

Well-regarded for its user experience, particularly for families and teams. Uses zero-knowledge encryption and has undergone multiple independent security audits. The Watchtower feature provides useful security monitoring.
The trade-off: closed source, no free tier, VC-funded with acquisition risk, and reliant on US cloud infrastructure (AWS). Canadian headquarters offers some jurisdictional benefit over US companies, but the US infrastructure dependency limits that advantage.
LastPass

Widely used due to its early market entry and free tier. Uses zero-knowledge encryption. Has undergone independent audits.
The trade-off: the 2022 breach eroded trust significantly. Private equity ownership (GoTo) raises questions about long-term security investment. The free tier is limited to a single device type (mobile or desktop, not both). US jurisdiction means full CLOUD Act exposure.
Features That Actually Protect You
Beyond encryption architecture, some features provide genuine security benefits, and others are primarily marketing.
Features worth evaluating
Email aliases. Using a unique email address for every site means a breach at one service doesn't expose your real email to phishing attacks on other accounts. Proton Pass includes this on the free tier, most competitors charge extra or don't offer it at all.
Passkey support. Passkeys replace passwords with cryptographic key pairs, eliminating phishing risk entirely. Support is expanding across the industry, and it's worth checking whether your password manager supports them.
Two-factor authentication. Your password manager should support 2FA for its own login (hardware keys, TOTP). This is table stakes, but worth verifying.
Export capability. A good password manager makes it easy to leave. If exporting your data is difficult or restricted, that's a red flag about the company's priorities.
Features that matter less than you'd think
Dark web monitoring. Several password managers advertise scanning the dark web for your credentials. In practice, this is largely a marketing feature. Services like Have I Been Pwned provide this for free, and the alerts are reactive, they tell you after a breach, not before.
Who Should Use What
If architecture and jurisdiction are your priority: Proton Pass offers the strongest combination of zero-knowledge encryption, Swiss jurisdiction, open source code, and independent audits. The free tier is genuinely useful, unlimited passwords plus 10 email aliases.
If open source and self-hosting matter most: Bitwarden gives you the option to run your own server, with a mature codebase and regular audits. Be aware of the US jurisdiction trade-off.
If you want zero cloud dependency: KeePassXC keeps everything local. No server, no company, no jurisdiction concerns. Best for technically comfortable users willing to manage their own sync.
If you need enterprise team management: 1Password's team and family features are mature and well-designed. Understand the VC-funding and US infrastructure trade-offs, and evaluate whether they're acceptable for your use case.
If you're still on LastPass: Consider migrating. The 2022 breach, combined with private equity ownership and US jurisdiction, makes a compelling case for switching. Check our password managers category for EU alternatives.
How to Switch Password Managers
Most password managers support CSV export and import, making the switch straightforward:
- Export your current vault (Settings → Export → CSV or encrypted format)
- Import into your new password manager (most accept CSV directly)
- Verify that all entries imported correctly, spot-check a few logins
- Secure your new account with a strong, unique master password and enable 2FA
Delete the exported CSV file immediately after importing. It contains all your passwords in plaintext. Empty your trash/recycle bin too, deleted files are recoverable until overwritten.
The process typically takes 15-30 minutes. Run both managers in parallel for a week to catch any entries that didn't import correctly before deactivating the old one.
Related Resources
- Proton Pass. Swiss-based, zero-knowledge password manager
- Password Managers category. All EU alternatives in this category
- Why Your VPN's Jurisdiction Matters. The same jurisdiction principles applied to VPNs
Have thoughts on password manager security? Reach out on Mastodon, Bluesky, or LinkedIn.
Frequently asked questions
What is zero-knowledge encryption in a password manager?
Zero-knowledge means your vault is encrypted on your device before it ever reaches the company's servers. The server stores only encrypted blobs, and the company does not hold a key that can decrypt your data. Even if served with a court order, the provider cannot produce your passwords, because they structurally cannot read them. It is the difference between locking your safe at home (zero-knowledge) and asking a storage company to lock it for you with their own key.
How bad was the 2022 LastPass breach really?
The attackers stole encrypted copies of customer vaults. The vault contents were encrypted, but website URLs were stored in plaintext, and the strength of the encryption then depended entirely on each user's master password. Vaults protected by weak or reused master passwords were vulnerable to unlimited offline brute-force cracking, and security researchers later reported evidence of vaults being cracked, with stolen cryptocurrency linked to LastPass data. The lesson is that "encrypted" is not binary; implementation details determine whether encryption actually protects you in a breach.
Is Proton Pass safer than 1Password?
On architecture, Proton Pass has structural advantages: Swiss jurisdiction (no CLOUD Act exposure), fully open-source clients, Cure53 audits, and a subscription business model with no VC exit pressure. 1Password is closed source, US-infrastructure-based, and VC-funded ($920M raised), which means it relies on company policy rather than verifiable code for many of its privacy claims. Both use zero-knowledge encryption, so for typical threat models they are both safe; the difference is whether you want to verify it or trust it.
Does Bitwarden's US headquarters expose it to the CLOUD Act?
Yes for the hosted Bitwarden service. Bitwarden is US-headquartered, so the CLOUD Act applies to it as a company. Self-hosting Bitwarden on European infrastructure mitigates this because the data plane is then under your jurisdiction, not the company's. The open-source codebase is the same in both cases; what changes is who can be compelled to act on your data.
Should I self-host my password manager?
Only if you can run the infrastructure reliably. A self-hosted password manager that's down when you need to log in, or that loses your backup, is worse than a managed service from a privacy-aligned provider. Bitwarden and Vaultwarden are realistic self-host options for technical users. For everyone else, picking a provider with the right architecture (Proton Pass) gives most of the benefit without the operational risk.
Is KeePassXC a serious option in 2026?
Yes, for the right user. KeePassXC is fully offline; your encrypted database lives on your device with no server in the loop. That is the strongest possible architecture for data sovereignty. The trade-off is that you handle syncing yourself (via Syncthing, a private cloud, or USB), there is no first-party mobile app (KeePassDX is the most common Android companion), and sharing requires manual coordination. Best for technically comfortable individuals or small teams that value independence over convenience.
Products Mentioned
Related Articles
Why Your VPN's Jurisdiction Matters More Than Its SpeedPrivacy & Security

GDPR-Compliant Software: The Complete Guide for 2026Privacy & Security
Ready to Switch to European Alternatives?
Explore our directory of 400+ European alternatives to US tech products.
Browse Categories