About KeyMe Pass
We want to get password management right, so that more people actually use it — instead of scrambling at the moment they need a password most.
Why we build this
Most people know they should use a different password for every site. Knowing it isn't the hard part.
Reusing one password everywhere usually isn't laziness. Before good tools existed, it was the only way to get through the day. So passwords end up scattered across notes, chat histories and browser prompts, and switching devices means losing them.
What makes it worse is the gap in time. A site gets breached, and the email account, cloud storage and payment methods fall with it. Few people trace that back to one convenient shortcut taken years earlier.
So we're not building a tool that remembers passwords. We're trying to make the right thing cost less than giving up on it. Autofill, passkeys, cross-device sync — these look like separate features, but they all serve one purpose: making the secure path the easy one.
The real opponent of a password manager isn't memory. It's the thought: just reset it, deal with it later.
What we believe
Building a product means making choices. These three shaped what KeyMe Pass became.
Where your data lives is your call
Our first sync option was WebDAV, before we built any cloud of our own. You can keep your vault on your own server, or use storage we host, and move it whenever you want. A vault belongs to the person who made it — it shouldn't be leverage for keeping them around.
Local use is fully open
Autofill, two-factor codes and passkeys are all unrestricted, and there is no cap on how many entries you keep locally. A password manager is only worth anything once every password is actually in it. Gating that behind entry counts or feature tiers turns the product’s core use into bait.
We stay out of your data
The master password is never uploaded or backed up, and we cannot reset it. That's what zero-knowledge requires, and it's a rule we agree with — a password we could reset is one someone else might reset too. This means a forgotten master password can only be recovered with your recovery key, so please keep it somewhere safe when you set it up.
All three point the same way: people should be free. Free to choose who holds their data, free to hand it to no one, and free to leave at any time.
Where we are now
From the first commit in November 2025, there's been an update every month since. The milestones, newest first:
- November 2026
Windows release
The Windows app arrived on the Microsoft Store, and the browser extension on Edge Add-ons.
- July 2026
macOS desktop
Desktop development began, bringing platform coverage to seven.
- June 2026
Passkeys
Saving, syncing and signing in with passkeys — what comes after passwords, and we moved on it early.
- March 2026
Autofill
Integrated with system-level autofill on iOS and Android, so the vault works inside other apps and browsers.
- February 2026
Browser extension
Work began on the Chrome extension, extending filling from mobile to desktop browsers.
- December 2025
WebDAV sync
The first sync option was WebDAV rather than our own cloud. Letting people keep data on their own server was a direction set from the start.
- November 2025
Project started
iOS, Android and HarmonyOS began together. Local encrypted storage for passwords and IDs came first.
Development continues. Release notes in the app spell out what changed in every version.
How we protect it
Your vault is encrypted on the device before it goes anywhere. The backup server only ever holds ciphertext.
- AES-256-GCM encryption, with keys derived from your master password via Argon2id on-device
- With sync off, data never leaves the device at all
- With sync on, content is already encrypted before upload
- The master password is never uploaded or backed up, and we cannot reset it
Contact us
Product issues, feature requests, security reports and partnership enquiries all reach us directly.
- Operating entity
- Shenzhen Yuduoduo Network Technology Co., Ltd.
Reporting a security issue
Found a vulnerability? Email us with "Security" in the subject and we'll prioritise it. Please hold off on public disclosure until a fix ships — that protects the people using the product right now.