Sign-in and keys
You sign in without a password: with Google, a code we email you, or a passkey. The keys that open your data stay on your devices. A new device gets them only after you Approve it on a device you already have. If you lost every device, the new one waits 72 hours, and you can cancel the wait. So someone who gets into your email still cannot take your data.
Ways to sign in
Every plan has an account, Free too. You sign up in one step, on the first screen.
| Way | What it is |
|---|---|
| Sign in with your Google account. We keep Google’s id for you and your email, never your Google password. | |
| Email code | Type your email address. We email you a 6-digit code; type it where you started. It works for 10 minutes, once. The first time, this makes your account. |
| Passkey | Your face, fingerprint or device PIN (Face ID, Touch ID, Windows Hello). Most passkeys are synced: Apple or Google copy them to your other devices. A passkey can also be bound to one device: a security key (a small USB or NFC key, such as a YubiKey), or a passkey saved only on one device. |
There is no Kaizendex password, so there is no password to forget or reset.
One email, one account. Google and the email code open the same account when the email is the same. We only join them when the email is proven: by the code, or by Google saying it checked the address. Typing someone else’s address makes nothing, so nobody can take your account by signing up first.
After your first sign-in with Google or a code, Kaizendex offers to add a passkey, so the next sign-in is one touch. You can say “Not now”.
To delete your account or change your passkeys, you prove it is you once more: with a passkey you already have, or, if you have none yet, with a new code we email you (or by signing in with Google again).
Want no email at all? Sign up with a passkey and no email address. We then send you no emails. You also get a recovery code automatically: a 16-digit code. It is for the day you lose your passkey and all your devices. Then the code starts the 72-hour wait, because we have no email to warn you. It works once: after you use it, the app gives you a new one.
We store the recovery code only in a scrambled form (a keyed hash), so nobody can read or guess it from our database.
A new device needs your Approve
Signing in proves who you are. It does not yet give a new device your keys. Before a new device gets your data, a device you already have must agree.
-
You sign in on a new laptop.
-
Your phone shows “New laptop wants to join. Approve?” Both screens show the same 6-digit number. Check that they match.
-
Tap Approve on your phone. The new laptop gets your keys, and your data opens there.
The two devices work out the 6-digit number from their own keys. Our server does not send it. So when the numbers match, you know the two devices talk to each other directly.
The same Approve tap is needed to add a device, to Move to this device on Free, and to change how you sign in. These are changes only you can make.
Lost every device? A 72-hour wait
If you lost every device, there is no device left to tap Approve. Then the new device waits 72 hours before it gets your keys.
- At once, we email you, and every device you have shows an alert.
- You can cancel the wait from any of your devices, or from the email.
- After 72 hours, if nobody cancelled, the new device gets in.
The wait is there for one reason: someone who gets into your email can sign in as you. The 72 hours give you time to see the email and cancel.
Example: someone gets into your email and signs in on their own computer. Your laptop shows “A new computer is waiting to join. Not you? Cancel.” You tap Cancel, and they get nothing.
What skips the wait
Only things that you alone hold skip the wait.
| You have | Skips the wait? | Why |
|---|---|---|
| A passkey bound to one device: a security key, or a passkey saved only on one device | yes | it never leaves that one device, so only you hold it |
| Your 12 recovery words, only if you turned on end-to-end encryption | yes | only you have them |
| A synced passkey, kept in your Apple or Google account | no | it is only as safe as that account |
| The 16-digit recovery code | no: it starts the wait | it is for accounts with no email |
Example: you lose your phone and your laptop on a trip. At home you sign in on a new laptop with your security key. The laptop gets your keys at once, with no wait.
Recovery words, only with end-to-end
Your 12 recovery words exist only if you turn on end-to-end encryption. The app makes them then, and offers a printable Recovery Kit: one page with the words. They open your end-to-end data on a new device, and they skip the 72-hour wait.
An account that never turns on end-to-end has no recovery words and no extra step.
The recovery words and the recovery code are two different things:
| Recovery words | Recovery code | |
|---|---|---|
| What it is | 12 words | 16 digits |
| Who has it | accounts that turned on end-to-end | accounts with no email |
| What it does | opens your end-to-end data; skips the 72-hour wait | starts the 72-hour wait; works once |
Sign out everywhere
Settings → Devices lists every signed-in device and browser, with when it was last used. Sign out everywhere signs out all of them except the one in your hand. Use it if you lose a device or think someone else signed in.
The keys that protect your data
| Key | What it opens | Where it lives |
|---|---|---|
| Device key | Proves a device is yours when it syncs | The device’s safe chip (Secure Enclave, Android Keystore, TPM) or a browser key that cannot be copied out |
| Locked-files key | Your locked files and the encrypted part of the database | Your computer’s keychain. A recovery copy is kept with your account. |
| Cloud Sync key (Free) | The sealed copy that Cloud Sync keeps for you on Free | Your device. A recovery copy is kept with your account. |
| End-to-end keys | Your collections and entries set to “Cloud Sync, end-to-end encrypted” | Only your devices. We never hold them, not even a recovery copy. Your 12 recovery words can open them on a new device. See End-to-end encryption. |
Sign-in tokens and your OpenRouter key also stay in the keychain, never in your folder.
- Your OpenRouter key is the key your chats use (see
Choose your AI). Settings → Plan & billing → Your OpenRouter
key shows it the way OpenRouter does: the start, dots, the last four characters. Example:
sk-or-v1-f33••••••••••••••••4cc6. The full key never reaches the app’s page, a log or an error. - A green check and “Connected to OpenRouter” mean OpenRouter accepts the key. A red line means OpenRouter refused it, for example because you deleted it there.
- Remove deletes the key from the keychain, after you confirm. Replace saves a new key in its place.
- A paired browser sees the same masked key and status. It can never read, set or remove the key.
Your devices
Settings → Devices lists every device on your account, and every browser paired with your desktop app. Remove device stops it from syncing. Removing a device also changes the key of every end-to-end collection it could read, so it cannot open new changes.
On Free you have one device. Signing in on a second one says: “Free covers one device. Move to this device, or go Pro to use both.” Moving needs an Approve tap on the old device, or the 72-hour wait. Then the old device keeps a read-only copy, with Move back. A browser linked to the desktop app on the same computer is not a second device.
Who can see your account
Our account database holds who you are and what you pay: your email (or none, if you use only a passkey), your sign-in links, your plan and your AI credits. It never holds your entries.
- Support access happens only when you allow it in Settings: for a set time (24 hours by default), and only for what you choose. It shows in your log, and it ends by itself. End-to-end collections stay closed even then.
- Recovery copies of your keys are locked by a separate key service. No one person on our side can open them with data access alone. Every time a copy goes to a device, it shows in your log. End-to-end keys have no recovery copy.