End-to-end encryption
End-to-end encrypted means only your devices hold the key. Your devices lock the data before it leaves them, so the cloud copy is scrambled for everyone else. Not even Kaizendex can read it.
It is optional, and you choose it per collection or per entry. It is one of the three values of “Where” in the Share & privacy panel:
| Where | In the cloud? | Can Kaizendex read it? |
|---|---|---|
| Cloud Sync (the default) | yes | technically yes, but we do not look |
| Cloud Sync, end-to-end encrypted | yes, locked | no |
| This device only | no | no: it never leaves the device |
Example: your Workouts stay in plain Cloud Sync. Your Health collection is Cloud Sync, end-to-end encrypted. Inside Workouts, one entry “Physio notes” can be end-to-end encrypted on its own. It does not have to be all or nothing.
Who it is for
- Most people: plain Cloud Sync. If you lose every device, you sign in on a new one, wait 72 hours, and everything comes back. You need no recovery words.
- Privacy-minded people: end-to-end encryption for the collections that matter. It works on every plan, Free too: privacy is not a paywall. Turning it on gives you 12 recovery words to keep safe. If you lose every way back, nobody can open that cloud copy, not even us.
Your other collections stay plain, so one end-to-end collection does not change how the rest of the app works.
Turn it on
The first time you set a collection or an entry to end-to-end, the app sets up your ways to unlock it.
-
Open the collection’s Share & privacy panel and set Where to Cloud Sync, end-to-end encrypted.
-
The app makes your 12 recovery words: twelve ordinary words, in order, that only you have. It offers a printable Recovery Kit: one page with your words. Print it or write the words down, and keep it away from your devices.
-
End-to-end turns on only when you have two ways to unlock: this device plus your recovery words, or this device plus another of your devices.
Example: you set Health to end-to-end on your laptop. The app shows your 12 words and offers the Recovery Kit. You print the kit and put it in a drawer at home. Your laptop and the words are your two ways, so Health turns end-to-end. Later end-to-end collections use the same words.
A passkey that can unlock (Face ID or a fingerprint) is a bonus where your device and browser support it. It is not one of the two ways, because not every device supports it yet.
Accounts that never turn on end-to-end have no recovery words and no extra step.
How a new device unlocks
Your account and your keys are separate. Signing in gets you into your account (Google, an email link or a passkey). To open your end-to-end data, the new device also needs one way back:
| You still have | Then |
|---|---|
| Any signed-in device | Everything. You can make a new set of recovery words, and a new Recovery Kit, there. |
| Another of your devices, nearby or not | Tap Approve on it. Both screens show the same 6-digit number first, so you know it is your new device. The two devices work out that number from their own keys; our server does not send it. |
| Your 12 recovery words | Type them, or read them from your Recovery Kit. Everything unlocks. They also skip the 72-hour wait. |
| A passkey that can unlock (a bonus, where your device supports it) | Sign in with it. Your data opens, often with no extra step. |
Your ~/Kaizendex folder on a computer |
In the desktop app, Restore from my folder makes a new key and uploads your data again. If you still have another device, it must approve the new key. The old cloud copy is kept 30 days before it is replaced. |
| None of these | The end-to-end cloud copy stays unreadable, by anyone, including us. |
The app checks that you have at least two ways back. If only one is left, it warns you in Settings → Security & keys.
What still works, and what changes
Almost everything runs on your own devices, so almost nothing changes.
| Feature | With end-to-end encryption |
|---|---|
| Tracking, views, dashboards, the folder | No change: they run on your device. |
| Search | Runs on your device. By default, search vectors (numbers that stand for meaning) are made on your devices only: the desktop app makes them with its own model, and they sync locked, like your entries. Phones and the web never send an end-to-end entry’s text out to make vectors; they use the synced vectors plus word search. With no desktop app, the collection is found by word search only, unless you tick Let the AI route make search vectors in its AI settings. Only you can tick it, in the app. Its text then goes through OpenRouter to make them, and the app tells you so. On phones and the web, a question you type may go through OpenRouter to become a vector: only the question, never your entries. This never happens for a collection set to Only my local AI. See Search. |
| AI chat | Runs on your device. With a cloud model, the question and the rows it needs go to the model company and are not kept. With a local model, nothing leaves. A chat that quotes an end-to-end collection is stored end-to-end too. |
kzx and MCP on your computer |
No change. Your computer can already read your own data. “No AI”, locked files and Hidden still apply. |
| Data from services (Whoop, health) | Locked to your key the moment it arrives. Your next device opens it. |
| Sharing with people | Turns end-to-end off for that collection, after a warning. See Sharing turns end-to-end off. |
| Public pages | The same: a public page turns end-to-end off for that collection, after the same warning. A public page is a copy that anyone can read. |
| The Library | No change. A listing holds only the setup and made-up sample entries, never your entries, so the collection stays end-to-end. |
| Agents in the cloud (Pro) | Read an end-to-end collection only if you give them a key for that collection. |
| A cloud MCP address (later) | Reads an end-to-end collection only with a key you give that connection. |
Agents while your devices are off
On Pro, your agents and automations can run in the cloud while your devices are off. They cannot read a locked collection on their own. For each end-to-end collection you choose one of three:
- Give your agent a key for it. You approve the agent like a new device and pick what it may open: “Workouts, Sleep: yes. Diary: no.” It opens them in memory only while a job runs, and stores nothing readable. Giving a key is a change only you can make. Each collection your agent holds a key for shows a badge: “Your agent can read this”, with Remove.
- Run it on your own computer in the desktop app, while the computer is awake. The keys never leave your devices.
- No cloud agent for that collection.
More: The agent home.
Sharing turns end-to-end off
Kaizendex has no shared end-to-end collections. To share an end-to-end collection with people or as a public page, the app first switches it to plain Cloud Sync. It warns you before it does:
Sharing turns off end-to-end for this collection. We can read it, like any Cloud Sync collection.
- End-to-end entries inside it switch too. The same warning lists them.
- This device only entries are never shared. They stay on your device.
- Your other end-to-end collections stay locked.
- When you stop sharing, you can turn end-to-end on again.
- Publishing to the Library is different. Only the setup goes out, never your entries, so the collection stays end-to-end.
Example: you share your end-to-end Health collection with your partner Sam. The app shows the warning, and you tap Share. Health is now plain Cloud Sync, and Sam sees it. The entry “Therapy notes” in Health is This device only, so it stays on your laptop and Sam never sees it. Your Diary stays end-to-end. Months later you stop sharing Health and set it back to end-to-end.
Checks that do not rely on our server
End-to-end encryption should hold even if our server did something wrong. So your devices check for themselves:
- The 6-digit number on an Approve tap comes from the two devices’ own keys, not from our server. A match proves the two devices talk to each other directly.
- Numbered changes. Every device numbers its changes and links each one to the one before. If a change goes missing or comes back twice, your devices notice and show it.
- Removing a device changes the key of every end-to-end collection it could read. The removed device cannot open anything new.
Example: you get a new phone. Your laptop shows “New phone wants to join. Approve?”, and both screens show “482 913”. The numbers match, so you know the phone talks to your laptop directly. You tap Approve.
What we can still see
End-to-end encryption hides your content, not the fact that you use Kaizendex. We still see:
- your email and plan
- how much you store, and when you sync
- how many devices you have
- which shared spaces you are in, and with whom
- your IP address (your internet address) when you sign in
We never see the entries, titles, notes, photos, chats, collection names or settings inside an end-to-end collection.
Not the same as locked files
Locked files protect your folder from AI apps on your computer. End-to-end encryption protects your cloud copy from everyone outside your devices, us included. They do different jobs, and you can use both.
How it works, in short
- Every device makes its own key pair. The private half stays in the device’s safe chip (Secure Enclave, Android Keystore, TPM, or a browser key that cannot be copied out).
- Your devices lock every change, value, Block page, photo and thumbnail before it leaves (XChaCha20-Poly1305, from audited libraries). The cloud stores and orders those lines, but cannot read them.
- We never hold your end-to-end key. It is never stored readable on our side, and we keep no recovery copy of it. Each of your devices keeps its own locked copy.
- You can also set an encryption password. The key is then made from it (with Argon2id), and the app refuses a weak password. Your devices and your 12 recovery words are still the main ways back.
More: How Cloud Sync works (technical).