About Rekey
Password managers only warn you. Apple has promised a fix but only for Apple. Rekey helps you fix it in any Chrome browser.
Rekey started with a familiar, stupid little moment: another "your password was found in a data breach" email, one of dozens, and the realisation that no tool would actually do anything about it.
Your password manager will happily tell you which of your logins are weak, reused, or leaked. It'll show you a red number: 12, 30, 70 accounts at risk. And then it stops. Fixing them means doing 70 password resets by hand, one login flow at a time, so most of us never do. The warnings just pile up.
That's the gap Rekey works on, in Chrome on any computer, not just on Apple devices. It's a browser extension for the moment after a leak: it finds the logins that were exposed, opens each site with a strong new password ready, saves the new one when the change goes through, and keeps your previous password one click away until the change is confirmed. It's the part that comes after "your data was compromised," the boring, essential part.
Trust is the whole game
I read what people post about tools like this. The worry that comes up most isn't "will it work?" It's a deeper one: do I trust a new tool to touch all my accounts?
So I built the answer into the architecture instead of promising it on a page. Your passwords are encrypted on your own device with a master password only you know. Sync across your devices is optional and zero-knowledge: the sync server only ever stores ciphertext it cannot read, so even I can't see your passwords, and a leak of it would spill nothing but scrambled bytes. The code is open source on GitHub, so you don't have to take my word for any of it. And Rekey never needs access to your email. When it can't do a step itself, it hands that step back to you.
I'm building it in public
Before writing a line of product code, I did a hands-on teardown of nine competing password managers, read the exact complaints people post about this problem, and put up a waitlist to see if the need is real. It is. I publish what Rekey can change and what it can't, bugs included, rather than pretending to cover everything.
I also take the security consensus seriously: forcing password changes on a timer is bad advice, and NIST agrees. So Rekey doesn't push changes on a schedule. It asks you to change a password when there's a reason, like a reported breach.
Where it's at
Rekey is in beta and the waitlist is open. I test each build on my own accounts, and my studies report what went wrong as well as what worked. If any of this sounds like something you'd have wanted the last time that email landed, come along for the build.
Who's building it
Rekey is built by me, Alex McComas, an SEO specialist based in Toronto. It's a small, independent project. I started it because I needed it to exist and got tired of waiting for the big password managers to ship it.
I run every test on this site on my own accounts. Each study says how it was done and what it can't prove:
- Which password managers change a breached password for you
- Your password was in a breach: what to change, in what order
- How to change an at-risk password without getting locked out
- Locked out after changing an at-risk password
- Why a password was flagged as at risk
- Changed your password but the vault kept the old one
- Why the change password shortcut sends you to the homepage