Zero-Knowledge vs Zero-Trust Encryption

The Encryption Illusion

Updated for 2026

In December 2022, LastPass told users about a breach. Their message was calm: passwords were "encrypted." Vault content was "secured."

By 2025, over $438 million had been stolen from LastPass users. The theft came straight from their "secure" vaults.

How? LastPass held the keys.

Your security team must know this before picking a cloud tool. It applies to any tool that handles sensitive files — including PII anonymization platforms.

Server-Side vs. Zero-Knowledge Encryption

Most cloud tools say they "encrypt your files." But they use server-side encryption (SSE). Here is what that means:

LastPass held the keys. That was the fatal flaw. Attackers broke in and got both the ciphertext and the tools to crack it. They used social tricks, weak password brute-force, and old account metadata.

Why This Matters for GDPR Article 25

GDPR Article 25 (Privacy by Design) is clear. Controllers must use "appropriate technical and organisational measures." These must be built in from the start.

The European Data Protection Board (EDPB) has added that this includes cryptographic data minimisation. The system itself must block access to records. Access controls alone do not cut it.

A vendor who holds your keys cannot meet Article 25 in its strict form. Here is why:

1. A breach of their system could expose your records.
2. A subpoena on the vendor could hand over your content.
3. A bad employee could view your files.
4. A supply chain attack could expose everything.

The German Federal Commissioner for Data Protection (BfDI) has issued guidance on this. So has the Austrian Datenschutzbehörde. Both say zero-knowledge is the best technical choice for high-risk processing.

The SaaS Breach Reality Check

The AppOmni / Cloud Security Alliance 2024 report found a 300% rise in SaaS breaches from 2022 to 2024. The key facts:

• Time to breach: 9 minutes (once measured in hours)
• Third-party role in breaches: doubled year-over-year (Verizon DBIR 2025)
• Conduent breach: 25.9 million records exposed (Social Security numbers, health files)
• NHS vendor breach: 9 million patients exposed

Policy words are no longer enough. Strong architecture is the minimum standard. This applies to all high-risk processing.

What True Zero-Knowledge Architecture Looks Like

A real zero-knowledge system has these clear traits:

1. Client-side key derivation Your key comes from your password. A memory-hard KDF (Argon2id, bcrypt, or scrypt) runs on your device. The key never leaves it.

2. Client-side encryption Your content is encrypted before it leaves your browser or app. The server only gets ciphertext. Without the key, that ciphertext is useless.

3. No server-side key storage The vendor keeps no keys, no key pieces, and no key backups. You use your own recovery phrase to regain access.

4. Cryptographic verifiability The system must be well-documented. It must be open to audit. Vague "end-to-end encryption" claims with no technical detail are a red flag.

How anonym.legal Implements Zero-Knowledge

anonym.legal's zero-knowledge login uses:

• Argon2id key derivation: 64MB memory, 3 iterations — the OWASP choice for high-security apps
• AES-256-GCM encryption: Runs fully in your browser or desktop app before any content is sent
• 24-word BIP39 recovery phrase: The only way to restore access — not stored by anonym.legal
• Zero server-side key access: anonym.legal servers only get AES-256-GCM ciphertext they cannot decrypt

A full anonym.legal server breach would yield only encrypted blobs. Without each user's key — which lives only on their device — these blobs are useless.

See our security and compliance overview and compliance documentation for full details.

The Vendor Evaluation Checklist

When you pick a cloud tool for sensitive records, ask these questions:

Architecture questions:

• Where does encryption happen — on your device or on the vendor's server?
• Who creates the keys?
• Where are keys stored?
• Can the vendor hand over plain-text copies of your content if served a subpoena?
• What happens to your files if the vendor is bought out?

Breach resilience questions:

• If the vendor's system is fully breached, what records are exposed?
• If a vendor employee goes rogue, what content can they see?
• If a supply chain attack hits the vendor, what is exposed?

Regulatory questions:

• Can the vendor show documentation for GDPR Article 25?
• Has an outside auditor reviewed the system?
• Is there an ISO 27001 or SOC 2 cert that covers encryption?

Any vendor that cannot answer "zero — content is encrypted before leaving your device" to the breach questions is using server-side encryption. Check our FAQ and glossary for more terms.

The Use Case: German Health Insurer Due Diligence

A compliance officer at a large German health insurer (Krankenkasse) needed a cloud anonymization tool. The task: process policyholder complaint logs. The DPO had four requirements:

• Vendor cannot access policyholder records
• No processing outside Germany
• GDPR Article 32 technical measures documented
• DPA-reportable breach risk is minimized

A large US anonymization SaaS failed the first item. Their support team could reset user vaults — proof of server-side key access. A second tool kept processed text for 30 days for "audit trail" use — again, server-side access.

anonym.legal met all four criteria. The DPO could write: "Even a full vendor breach yields no usable policyholder records — keys exist only on our workstations." GDPR Article 32 documentation was done in four hours.

View our case studies for more real-world examples.

The ICO Enforcement Precedent

In December 2025, the UK Information Commissioner's Office fined the LastPass UK entity £1.2 million. The reason: "failure to implement appropriate technical and organisational security measures."

The fine was not for the breach itself. It was for the architecture choices that made the breach so harmful. Bad KDF settings, exposed metadata, and server-side key storage all played a role.

Regulators now ask: did the system limit breach impact? Zero-knowledge architecture answers that clearly. It is the best proof of that intent.

When Zero-Knowledge Architecture Isn't the Right Fit

Zero-knowledge encryption has trade-offs. These matter for some use cases:

Recovery complexity: If users lose their keys, their files are gone for good. There is no back door. High staff turnover or weak key-management habits make this a real risk.

Collaboration friction: Encrypted content can only be shared if the other party has the right decryption tools. This is slower than a simple link share in standard cloud apps.

Regulatory edge cases: Some regions require law enforcement access to records by court order. Zero-knowledge systems block this by design. That may cause legal issues in financial services or telecom, where lawful intercept rules apply.

Computational overhead: Argon2id key derivation and AES-256-GCM encryption both add delay. This matters most for real-time, high-volume processing.

For teams processing millions of documents per day, a hybrid approach may work better. Encrypt only the most sensitive fields. Keep metadata open. See pricing plans for volume tiers.

Conclusion

"We encrypt your files" is not a security promise. It is a marketing phrase that needs scrutiny.

The real questions are simple. Who holds the keys? Where does encryption happen? What is exposed if the vendor's systems are breached?

For teams processing sensitive records under GDPR, HIPAA, or similar rules, these architecture choices shape both your legal risk and your real breach exposure.

LastPass encrypted their users' content. Zero-knowledge architecture would have made the 2022 breach a non-event. The $438 million stolen from users was the cost of an architectural shortcut.

anonym.legal uses zero-knowledge architecture for PII anonymization. Argon2id key derivation runs in your browser or desktop app. AES-256-GCM encryption happens before any content leaves your device. anonym.legal servers store only ciphertext they cannot decrypt. Learn more on our about page or explore the token system.

Sources

• AppOmni SaaS Security Report 2024
• EDPB Guidelines on Privacy by Design
• ICO LastPass Enforcement Action (December 2025)
• Verizon DBIR 2025
• ETH Zurich: Password Managers Less Secure Than Promised