Only you can open your vault.
Everything is encrypted on your device before it syncs through your iCloud. We can't read it, Apple can't read it, and nobody can reset your password and get in.
The same protection on every plan. The full design is in the security whitepaper.
What that means for you.
You don't need to know how the encryption works to get the benefit. Here's what it does for you.
A breach gets nothing readable
Your vault is scrambled before it leaves your device. Even if someone broke into iCloud, there would be nothing to read.
A lost phone stays shut
ZZPass locks itself after the time you choose, opens with Face ID or Touch ID, and after five wrong guesses it locks for a while, longer each time, up to 15 minutes.
Guessing is slow by design
Your password is stretched 650,000 times before it becomes a key, so each guess at it takes real effort.
Shared stays in the group
Shared items are encrypted for each member. Remove someone and the group gets a new key, so they’re out for good.
Copied passwords don’t linger
Passwords and codes you copy clear themselves from the clipboard after 60 seconds.
Fake sites get nothing
AutoFill only offers a login on the site it belongs to, so a lookalike page gets no suggestion.
Things we can't do, even if asked.
These aren't promises. They follow from how ZZPass is built: your key is made on your device and never sent to us.
- Read your vaultPasswords, notes, cards, 2FA codes and passkeys are only readable on your devices.
- Reset your passwordThere's no "forgot password" email that lets someone else in. You hold the ways back.
- Open your shared groupsOnly the people in a group hold its key.
- Hand your vault overIt never comes to us, and iCloud only has the scrambled copy, whoever asks.
- Read a TimeCapsuleThe key we hold is sealed to the people you chose. We only know when to release it.
- Sell what's in your vaultWe can't read it, so there's nothing to sell. No ads, no investors.
Locked tight. Never locked out.
Nobody can reset your password for you, so ZZPass gives you your own ways back in.
- Face ID or Touch ID on a device that's already set up
- Your printed Emergency Kit, kept somewhere safe
- Emergency Access, so your family can get in if something happens to you (Premium)
Don't take our word for it. Check.
One developer, nothing to hide. Here's what you can look at yourself.
The security whitepaper
Every key, every algorithm, how sharing and recovery work, and what ZZPass doesn't protect against.
Read the whitepaper →The server code
The small servers behind TimeCapsule, Emergency Access and usage stats are open source:
Apple's privacy label
The App Store lists ZZPass as "Data Not Linked to You". Nothing is used to track you.
See it on the App Store →Usage data you can switch off
ZZPass sends anonymous usage stats and crash reports, never passwords, notes, names or email. Turn off Share anonymous usage data in Settings → Security and anything not yet sent is deleted.
The short version.
| Vault encryption | AES-256-GCM, on your device |
|---|---|
| Key from your password | PBKDF2-SHA256, 650,000 rounds, random 128-bit salt |
| Sync | Your iCloud (CloudKit), which only ever receives encrypted data |
| Sharing | ECDH P-256 + HKDF-SHA256 per member, new group key when someone is removed |
| Passkeys | ECDSA P-256 (ES256) |
| Mac app updates | Signed with Ed25519 |
Key hierarchy, threat model, escrow and telemetry are all in the security whitepaper.
Found a security issue?
Please tell us before telling anyone else. Good-faith research is welcome, and covered by safe harbor.
- security@zzpass.comPlease don't open a public GitHub issue.
- Disclosure policy →What's in scope, and how we handle reports.