How your data is protected
Your data lives on your devices: your computer, a browser, a phone. Cloud Sync keeps a copy in the cloud, on every plan. Each place has its own lock. This page shows every place, its lock, and who could read what is in it.
The short answer
- On your computer, your computer login and disk encryption protect your data. Collections you lock are also encrypted by the app.
- On the way to the cloud, everything travels encrypted.
- In the cloud, your data is encrypted on disk and kept apart for each person. Support opens it only if you allow it, for a set time.
- Plain Cloud Sync means “we won’t look”. Kaizendex could still technically read it.
- End-to-end encrypted means “we can’t look”. Only your devices hold the key. You choose it per collection or per entry: see End-to-end encryption (optional, later).
- “This device only” collections and entries never go to the cloud.
- A new device needs your Approve on a device you already have, or a 72-hour wait. So someone who gets into your email cannot take your data.
Two kinds of things you keep
| Kind | What it is | Size | Where it is stored |
|---|---|---|---|
| Your data | entries and their values, Block pages and Dashboards, collections, views, settings, history | small: an account with 90,000 entries is about 41 MB | in a database on each device, and in Cloud Sync |
| Your files | photos, videos, audio, PDFs and other files you add | big | as real files, once on each device that keeps them. The database keeps only a record of each file: its name, size, fingerprint and entry. In the cloud, Cloud Sync keeps files apart from your data. Free keeps up to 200 MB of files in the cloud, Pro 50 GB. |
A fingerprint is a short code worked out from the file’s bytes. Two copies of the same photo have the same fingerprint.
Example: the entry “Morning run” holds 5.2 km and a note. That is data. The photo
run-map.png on it is a file. On your computer it sits in
~/Kaizendex/Attachments/2026-10/run-map.png.
Every place, at a glance
Every place, one by one
| Place | What is kept there | Its lock | Can Kaizendex read it? |
|---|---|---|---|
| Your computer (desktop app) | your ~/Kaizendex folder with every file and your database (on a cloud or network drive, the database stays in the app data); the photo store and the backups, in the app data, ~/.kaizendex/app-data |
your computer login and disk encryption; locked collections are also encrypted by the app | No. It is on your computer, not with us. |
| A browser linked to the desktop app | nothing of its own: only what is on screen, in memory | the desktop app’s; the browser is paired once, and locked, end-to-end and Hidden items need a fresh unlock | No. |
| A browser without the desktop app | its own copy, in the browser’s private storage | your computer login and disk encryption; locked collections are encrypted, with a key kept in the browser | No. |
| Your phone (later) | its own copy, inside the app | your phone’s lock; locked collections are encrypted, with the key in the phone’s key safe (Keychain or Keystore) | No. |
| Cloud Sync on Pro: your data | a copy of your data | layers 1 to 3 below | Technically yes. End-to-end collections: no. |
| Cloud Sync on Pro: your files | a copy of every file, up to 50 GB | layers 1 to 3 below | Technically yes. End-to-end collections: no. |
| Cloud Sync on Free: a sealed copy | your data and up to 200 MB of files | sealed (encrypted) on your device before upload, then layers 1 and 2 | Technically yes: we keep a recovery copy of its key. End-to-end collections: no. See Cloud Sync on Free. |
| Our account database | your email, sign-in links, plan and AI credits; never your entries | layers 1 and 2, and access rules | Yes. We need it to run your account. |
For what each place holds in more detail, see Where your data lives. For the technical parts, see How Cloud Sync works (technical).
The four layers in the cloud
Everyone gets the first three layers. The fourth is what “we cannot read your data” really means.
| Layer | Protects against | Can Kaizendex read it? | Who has it |
|---|---|---|---|
| 1. Encrypted on the wire (TLS, the lock in your browser’s address bar) | someone listening on the network | yes | everyone |
| 2. Encrypted on disk. Cloudflare, our cloud provider, encrypts all your data, every file and every account row on its disks. | a stolen disk in a data centre | yes | everyone |
| 3. Kept apart per person, plus access rules. You reach only your own data, never another person’s. Each part of our cloud reaches only what it needs. Support cannot open your data without your permission. | other users, a bug, nosy staff | technically yes: a rogue insider, a court order or a serious bug could | everyone |
| 4. End-to-end encrypted (optional, later). Your devices lock the data and files with keys only your devices hold, before upload. | us, Cloudflare, a breach, a court order | no | the collections and entries you set to “Cloud Sync, end-to-end encrypted” |
Our side, in plain words
- 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.
- Cloud Sync finds your data from your verified sign-in, and checks it again.
- Parts that take outside traffic (webhooks, chat channels, public pages) cannot open your data directly. A public page is a published copy, made when you publish.
- Webhooks: we check each service’s signature when it offers one. Your webhook address is private to you. What arrives is data, never an order to the AI.
Cloud Sync on Free
Free has Cloud Sync for one device. Its cloud copy is your backup. There is no separate backup product.
- Sealed before it leaves. Your device encrypts the copy before upload. We store only scrambled bytes. It updates a few minutes after each change.
- 200 MB of files. Your data (text, numbers, settings) has no practical limit. Files over 200 MB stay only on your device, and the app says so: “1.4 GB of files are only on this computer”.
- The key comes back after an Approve or a 72-hour wait. We keep a recovery copy of the key with your account, so a new device can open the copy. The key goes only to a new device you approved on your old one, or after a 72-hour wait (what skips the wait). A separate key service locks the recovery copy, and every release shows in your log.
- Only your current device writes the copy. We also keep earlier versions, so a bad or old upload never replaces a good one.
- So, honestly: the copy is scrambled, but we hold a way to open it. The app never says “we cannot read your cloud copy”. End-to-end collections are the exception: your devices lock them with your own keys first, so our recovery copy cannot open them.
- Not kept forever. The Free cloud copy is deleted after 12 months without a sign-in, after warning emails.
On Pro, Cloud Sync also keeps all your devices the same within seconds, with 50 GB of files. More: Devices and sync and Backups, export and recovery.
What we still see with end-to-end encryption
Even for end-to-end collections, we see what we need to run your account and sync:
- 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.
What is built from your data
The search index, AI search, the read-only database copy, chats, AI receipts, run history and summaries are as private as the data they came from. A chat that quoted an end-to-end collection is stored end-to-end. See Your privacy choices.
Changes only you can make
Changes that open up your data, such as Where, the AI choice, sharing or adding a device, need
you: in the app, on one of your devices, after a fresh check. The folder, kzx, MCP and agents
can only suggest them. See Changes only you can make.
On your computer
Disk encryption
Kaizendex does not encrypt your main database. Your computer login keeps other people out. Disk encryption protects everything on the disk if the computer is lost or stolen: BitLocker on Windows, FileVault on a Mac. The app checks whether it is on, and recommends it.
So nothing can ever lock you out of your own data: no Kaizendex password, no key to lose.
There is also no lock on the whole ~/Kaizendex folder. Disk encryption already covers a stolen
computer, and a lock on the whole folder would shut out you, Obsidian and your AI agents.
Locked collections
A collection or entry is locked when its AI setting is anything but Any AI, or when it is Hidden. Then:
- its rows live in a second database that is encrypted (SQLCipher, an encrypted kind of SQLite);
- its files in your folder are encrypted
.encfiles, named by date and id, never by title; - the key sits in your computer’s keychain (its built-in password safe), so locked files open by themselves while you are signed in to your computer.
Example: you make a collection “Super private” and set its AI to No AI. The entry “Hello
world” goes into the encrypted database. In your folder, its file is
Super private/2026-10-30 4f2a9c1e.md.enc. An AI app on your computer sees only scrambled
bytes.
Sign-in tokens and keys never sit in your folder.
More: Locked files.
“This device only”
A collection or entry set to This device only stays on one device. It never goes to Cloud Sync or to your other devices, not even its name, so no server holds it. This works on every plan.
- A link to it from another collection syncs only as a hidden id. Your other devices show “A private item”.
- It is never sent to a cloud AI model. The AI receipt shows “1 private item”.
- “Version this folder with Git” never pushes it.
- If your
~/Kaizendexfolder is inside OneDrive, iCloud Drive, Dropbox or Google Drive, the app warns you: the cloud drive uploads the folder, This device only collections included.
A browser linked to the desktop app uses the desktop app’s data. So a “This device only” collection you make in that browser lives in the desktop app on your computer, and never goes to the cloud either.
A browser linked to the desktop app
The desktop app serves the app to your browser itself, at a local address on your computer, from the signed code inside the desktop app. Each browser pairs once with a short code and gets its own secret. Only that computer can reach the link. Locked files, end-to-end collections and Hidden entries need a fresh unlock (Face ID, a fingerprint, Windows Hello or your computer password) before the browser shows them. See The browser and the desktop app.
A browser without the desktop app
A browser on a computer without the desktop app keeps its own copy in the browser’s storage. Clearing browser data deletes that copy, except what is in Cloud Sync. A “This device only” collection in that browser is lost when you clear it. The app asks the browser to keep the data, and shows how many changes exist only in this browser. See Offline and clearing your browser and The browser and the desktop app.
Uploads
Your files go up through our Worker (a small program on our cloud). It checks the file’s size and your allowance, and files every upload under your account. A file is stored once per person, by its fingerprint. Storing a file once works per person only, never across people.
Make it safer
- Install the desktop app. Your data and files then sit in your own
~/Kaizendexfolder, and the browser on that computer links to it. - Turn on disk encryption (BitLocker or FileVault).
- Keep Cloud Sync on. Its cloud copy is your backup, so a lost computer is not lost data.
- Lock sensitive collections: pick any AI setting other than Any AI, or Hidden.
- For the most private collections, choose “Cloud Sync, end-to-end encrypted” (later), and keep the Recovery Kit with your 12 recovery words safe.
- Protect your Apple or Google account with two-step sign-in. A passkey synced through it is only as safe as that account.
All the steps: Keep your data safe.