Where your data lives
Your data lives on your devices. Cloud Sync keeps a copy in the cloud: it is your backup, and on Pro it keeps all your devices the same.
Cloud Sync is on when you sign up, on every plan:
- Free: Cloud Sync for one device, with 200 MB of files.
- Pro: Cloud Sync for all your devices, with 50 GB of files.
With the desktop app, your computer also keeps all of it in a folder you name and place,
~/Kaizendex by default. Only in the desktop app can you turn Cloud Sync off. Then your data
lives only on that computer.
See Cloud Sync.
Today: all on your computer
The first build is local only. There is no account, no Cloud Sync and no phone app yet. Your data lives on one computer:
| Place | What it holds | Who writes it |
|---|---|---|
Your folder, the name and place you chose (~/Kaizendex by default) |
one markdown file per entry, settings, chats, photos and files, a read-only database copy, and the live database in its hidden .kaizendex folder |
the engine writes the database; the folder sync writes the files, and your edits come back in through the engine |
The app data, ~/.kaizendex/app-data |
your photo store, the backups, the paired browsers, AI models, the app’s window settings and its start log; the database too, when your folder is on a cloud or network drive | only the desktop app and kzx |
| The Windows keychain | your OpenRouter key and the key for locked items | the desktop app |
~/.kaizendex/location.json |
a small note that says where your folder, its database and the app data are | the first-start screen and a move |
Example: you tick “Morning run” as done. The engine saves it in .kaizendex\main.sqlite, and
within a second Collections/Workouts/Morning run.md in your folder says so too.
- You choose the folder on the first start, as Obsidian makes a vault. See Your folder.
- Three settings move them, for tests:
KZ_DATA_DIR(the database),KZ_FOLDER(your folder) andKZ_LOCATION_FILE(the note above). WithKZ_DATA_DIRorKZ_FOLDERset, the note is not read. - Nothing of yours lives in
%APPDATA%. Windows keeps the files that a program started from a Store app like Claude Desktop (an agent, a terminal,kzx) writes to%APPDATA%in that app’s own folder, shows them only to its programs, and deletes them when that app is removed or reset. So the note and the app data sit in your home folder, which Windows never copies that way. The desktop shortcut, start at login, a terminal and Claude Desktop all read the same note and open the same database, photos and backups. - Once the note exists, it decides. Only the places it names are used. An account left in
%APPDATA%(even an empty one a shortcut once made) is never opened. - An account made before this still keeps its photos and backups in
%APPDATA%\Kaizendex, or in Claude Desktop’s copy of it, until you move them (Settings → Your data, orkzx data move). Until then the app andkzxopen Claude Desktop’s copy by its real path when the real one holds no account, wherever you start them from. Only Claude Desktop’s copy is looked at, never another app’s. - Two accounts are never a silent choice. If both of those places hold an account, the app opens the one changed most recently and tells you where the other one is. Nothing in the other one changes.
- The app never starts an empty account in place of yours. If no account is found but your
folder holds entries, the app says so instead and leaves your folder alone. If the note points
to a folder that is gone, the app shows Find my folder, never an empty account. Each start is
written to
logs\start.login the app data. - Private collections are locked in the folder: encrypted
.md.encfiles, named by date and id. See Your folder. - A paired browser stores nothing. See The browser and the desktop app.
Everything below about Cloud Sync, plans, phones and other computers comes later.
The database is in your folder
Your folder holds your entries as files, your photos, and the database. The database sits in
the .kaizendex folder inside it:
Kaizendex/ .kaizendex/ main.sqlite your data locked.sqlite your locked items, encrypted vectors.sqlite search by meaning Collections/ Attachments/ Settings/ Chats/- It is hidden only so it is not moved or changed by mistake. Windows and macOS hide a name that starts with a dot.
- It is still yours, and still there. Any file app (turn on Show hidden items) or any SQLite tool can open it. Show in Explorer in Settings → Your data goes straight to it.
- Do not edit it while Kaizendex is open. To change data from outside, edit your folder’s
files or use
kzx. - On a cloud or network drive, the database stays on this computer. A live database in a folder that OneDrive, iCloud Drive, Dropbox or Google Drive uploads while it is written can break. So when your folder is on one of them, or on a network drive, the database stays in the app data, and Settings → Your data says so in one line. The app checks this at every start.
- The backups and the photo store are in the app data,
~/.kaizendex/app-data, outside your folder, so deleting your folder does not delete them. Each photo in your folder’sAttachmentsis the same file as the store’s (a hard link), so it is kept once.
Settings → Your data
To open it, click your account in the top-left corner (“Daniel’s Kaizendex”), then Your data in the Settings sidebar, under Storage.
One page shows where everything is: Your folder, Database, Backups and App data, each with its path, its size and Show in Explorer (Show in Finder on a Mac).
- Move into my folder shows when the database is not in your folder yet. It also moves your
photos and backups to
~/.kaizendex/app-datawhen they are still in%APPDATA%. - Move on App data shows when only the photos and backups are still in
%APPDATA%. - Change… picks a new place. Your folder and its database move there.
A move is checked before it starts: it shows what moves, and it says when kzx or a Claude
Code session has the database open (close them first). Then Move starts the app again and
moves the database before anything opens it:
- It copies each database with SQLite’s own backup, never a plain file copy.
- It checks the copy: no damage, the same rows in every table, the same newest change, and locked items still open with your key.
- When your photos and backups are still in
%APPDATA%, it copies them to~/.kaizendex/app-dataand checks them: the same files and sizes, and every photo’s checksum. - It switches the note
~/.kaizendex/location.jsonto the new places. - It keeps the old files in
before-move-<date>in the app data for 30 days.
If a check fails, nothing changes: your data stays where it was. In a terminal, the same move
is kzx data move --to <folder>. It is a dry run, which shows what would move and how big it is
(backups can be a few GB, and the disk needs that much free space) and changes nothing; add
--apply to move. kzx data where prints every place: your folder, the database, the photo
store, the backups, the start log, window settings, paired browsers, AI models and the note.
Two kinds of things
You keep two kinds of things in Kaizendex: your data, which is small, and your files, which are big. Both live on your own devices first. Cloud Sync keeps a copy of your data, and of your files up to your plan’s allowance.
| Your data | Your files (attachments) | |
|---|---|---|
| What it is | Entries and their values, Block pages and Dashboards, collections, views, settings and history | Photos, videos, audio, PDFs and other files you add |
| Size | Small. An account with 90,000 entries is about 41 MB. | Big. One file can be up to 2 GB. |
| Where it is stored | In a database on each device, and in Cloud Sync | As real files, once on each device that keeps them, and in Cloud Sync. |
| How much Cloud Sync keeps | All of it, on every plan | Free: 200 MB. Pro: 50 GB. |
The database is SQLite: a whole database in one file. It keeps a record of each file (its name, its size, a fingerprint and which entry uses it), never the file itself. A fingerprint (checksum) is a short code made from the file’s bytes, so the same file always gets the same code.
Example: you log “Morning run” with a distance of 5.2 km and a photo, run-map.png. The
title and the 5.2 km are data. The photo is a file.
Every device keeps its own copy of your data, because it is small. That is why every tap is instant and works offline. Files are big, so not every device keeps all of them:
- The desktop app keeps every file.
- On Free, your one device keeps every file, a phone too. A browser on its own keeps them in browser storage.
- On Pro, a phone and a browser on its own keep previews and recent files. They download any other file from Cloud Sync when you open it.
- A phone on Pro keeps the last 12 months of your data in full. Older entries load when you open them.
A copy on a phone is not a backup. Your backup is Cloud Sync. With Cloud Sync off (desktop app only), your backup is your own copy of the folder.
Every place, in one picture
Where everything lives
Example: you have 2 GB of photos and files.
| Where you use the app | Your data | Your 2 GB of files |
|---|---|---|
| Desktop app | Its database, in your folder’s hidden .kaizendex folder (in the app data when your folder is on a cloud or network drive). Mirrored as markdown files in ~/Kaizendex. |
All 2 GB on your computer, once, as real files in ~/Kaizendex/Attachments/2026-10/… |
| Browser, linked to the desktop app | Nothing stored in the browser. It uses the desktop app’s database. | Nothing stored in the browser. It shows them from your computer. |
| Browser only, Pro | Its own copy, in browser storage | Small previews and the files you opened lately, in a small cache you can empty. Any other file downloads from Cloud Sync when you open it. |
| Browser only, Free | Its own copy, in browser storage | All 2 GB in browser storage. Cloud Sync keeps 200 MB of them. The app says “1.8 GB of files are only in this browser”. |
| Phone (later) | Its own copy. On Pro: the last 12 months, plus anything you open. | On Pro: previews and recent files, in a cache you size (2 GB by default). Any other file downloads when you open it. By default, files wait for Wi-Fi. On Free: every file, on the phone. |
| Cloud Sync, Pro | Your data, apart from everyone else’s | A copy of every file. 50 GB is included. |
| Cloud Sync, Free | Your data, as a sealed copy | Up to 200 MB |
| “This device only” collections and entries | Never synced: not in Cloud Sync, not on your other devices, on any plan | Their files never leave the device either |
“Browser only” means a browser on a computer without the desktop app. On a computer with the desktop app, the browser links to it. See The browser and the desktop app.
The desktop app’s live database is in your folder, in .kaizendex. Its backups are in the
app data, ~/.kaizendex/app-data in your home folder, on every system. Only the engine writes
the database, so no outside program can skip the app’s checks. See
Your folder.
Free and Pro
- Free puts one device in Cloud Sync. A desktop app and the browser linked to it count as one device. Its cloud copy is your backup: all your data, plus 200 MB of files. Sign in on a second device, and the app offers Move to this device, or Pro to use both.
- Pro puts all your devices in Cloud Sync. They stay the same within seconds, with 50 GB of files. Your agents and automations also run in the cloud while your devices are off. See Devices and sync.
Where: three choices
Each collection, and each entry, has a Where setting:
- Cloud Sync (the default): on your devices and in the cloud.
- Cloud Sync, end-to-end encrypted (later): the same, but only your devices hold the key.
- This device only: it never leaves this device, not even its name.
Example: your Diary is end-to-end encrypted, and one entry in it, “Therapy notes”, is This device only. See Cloud Sync.
Inside Cloud Sync
For the curious, Cloud Sync has two parts inside:
- The cloud box (Pro). It is your own small private database at Cloudflare, apart from every other user’s. It passes your changes between your devices, and it runs your agents and automations.
- File storage (R2), Cloudflare’s file storage. It holds your photos and files.
Free has no cloud box: its Cloud Sync copy is a sealed copy in file storage. The full story is on How Cloud Sync works.
What else we keep
| Place | What it holds | Who has it |
|---|---|---|
| Our account database | Your account, your plan and your AI credit balance. Never your entries, notes, photos or chats. | Every plan |
| Stripe (the payment company) | Your card details. You type them into Stripe, never into us. | People who pay |
Who can read it
On plain Cloud Sync (the default), your data is kept apart from everyone else’s, and support opens it only when you allow it, for a set time, and the access shows in your log. A new device gets your data only after you approve it on a device you have, or after a 72-hour wait. But Kaizendex can technically read it: a rogue insider, a court order or a serious bug could. With end-to-end encryption (later), your devices lock a collection with a key only they hold, so nobody else can read it.
On your computer, your login and disk encryption (BitLocker on Windows, FileVault on a Mac) protect your data. The app checks for disk encryption and recommends it. Every layer is on How your data is protected.