Backups, export and recovery
Your data comes back after a lost, broken or wiped device, and you can take all of it with you at any time. On every plan, your backup is Cloud Sync. With Cloud Sync off, it is your own backup of your folder.
A lost, wiped or new device
| Cloud Sync, Free | Cloud Sync, Pro | Cloud Sync off (desktop app) | |
|---|---|---|---|
| What brings it back | Cloud Sync | Cloud Sync | Your own backup of ~/Kaizendex |
| What you do | Sign in on the new device, then Move to this device. Approve it on the old device, or wait 72 hours. | Sign in. Approve the new device on one you have, or wait 72 hours. Cloud Sync fills it. | Install the desktop app, then Restore from my folder |
| What comes back | All your data, plus up to 200 MB of files | Everything, files included | What your backup holds |
| What does not come back | This device only collections, and files over 200 MB that were only on the lost device | This device only collections | Changes after your last backup |
| The lost device | If you find it again, it is read-only, with Move back | Remove it in Settings → Devices | — |
A new device gets your keys only after you Approve it on a device you already have. With no other device, it waits 72 hours, and we email you at once and alert your devices so you can cancel. A passkey bound to one device (a security key, or a passkey saved only on one device) skips the wait, and so do your recovery words, if you turned on end-to-end. A passkey synced by Apple or Google does not skip it. See What skips the wait.
Cloud Sync on Free
On Free, Cloud Sync covers one device. Its cloud copy is your backup.
- It keeps all your data, with no practical limit, plus 200 MB of files.
- It updates a few minutes after each change.
- Only your current device may write it. Earlier versions are kept, so a bad or old upload never replaces a good one.
- Files over 200 MB stay only on your device. The status mark says so, for example “1.4 GB of files are only on this computer”.
- The status mark at the bottom of the sidebar shows when it last synced. Click it to see what is in the cloud and what is not.
- For the curious: on Free, Cloud Sync is a sealed copy in file storage (R2), with no cloud box. See How Cloud Sync works.
A cleared browser
| Where you cleared it | What happens |
|---|---|
| A browser linked to the desktop app | Nothing is lost. Your data and files are in the desktop app and ~/Kaizendex. |
| A browser on its own, on Pro | Sign in again. Cloud Sync refills it. Changes made offline that had not synced are lost. |
| A browser on its own, on Free | Sign in again. Cloud Sync refills it. Changes that had not synced are lost, and so are files over 200 MB, which only this browser had. |
A counter warns you first. See Offline, and clearing your browser.
Go back in time
The desktop app keeps backups of its database in its own data folder: one every hour, kept two days, and one every day, kept a month. In Settings → Folder, Go back in time lists them. Pick one, and pick the whole account or one collection. The app first says what would change (“3 entries come back, 12 change”). Then it brings back what the backup had, as one step you can undo. It never deletes: work you did after the backup stays.
Locked collections and entries are backed up too, still encrypted: each backup has a twin in
backups/locked/, and going back brings locked entries back with the rest.
Example: on Tuesday a script you ran renamed half your Books. In Go back in time you pick Monday’s backup and the Books collection. The old titles come back; the book you added on Tuesday stays. Changed your mind? One Undo takes the whole step back.
From a terminal: kzx go-back --list, then
kzx go-back --to daily-20261106.sqlite --collection Books --dry-run.
For one entry, its own Version history (in the entry’s menu) is quicker: it lists every change to that entry, with who made it.
A broken database
The desktop app checks its database each time it opens. If the file is damaged, the app does not
open it. Repair puts the newest backup that passes its check in its place, and keeps the
damaged file beside it (main.broken-<time>.sqlite). The app then fills in newer changes from
the files in your folder and from Cloud Sync. From a terminal: kzx go-back --repair.
Only the folder is left
Restore from my folder reads your folder into any account, a new one too. It is in the
desktop app. Every entry goes through the normal rules, as if you typed it. Example: your
laptop dies, but your ~/Kaizendex folder is on a backup drive. Install the desktop app on a
new computer, sign in, and restore from that folder.
Locked files come back when the app has their key. See Locked files.
Restores never delete
Restore from my folder and Go back in time only add and update entries. They never delete one. Example: your folder backup is from last Monday. Since then you logged three runs. You restore from the backup, and the three runs are still there.
Many deletes at once
Deletes that come from outside the app pause when there are many at once: files gone from your folder, or a device that was away and sends a pile of old deletes when it comes back. Every device shows a card, such as “A device wants to delete 412 entries”, with Delete and Keep. Nothing moves to the Trash until you pick.
Your own deletes in the app do not pause. They have Undo, as always. If you deleted many things by mistake, open the Trash and click Restore all.
You lose every end-to-end key
When you turn on end-to-end, the app makes your 12 recovery words and offers a Recovery Kit: one page with the words, to print and keep safe. 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. A passkey that can unlock (Face ID or a fingerprint) is a bonus where it works. If only one way is left later, the app warns you. Accounts that never turn on end-to-end have no recovery words.
If you lose them all, the end-to-end cloud copy stays unreadable, by anyone, us too. If the desktop app still has the data, Restore from my folder makes a new key and uploads the data again. If you still have another device, it must approve the new key. The old cloud copy is kept for 30 days before it is replaced. Example: your Diary is end-to-end encrypted, and you lose your phone and your recovery words. Your laptop still has the Diary, so you restore it from the laptop’s folder.
Deleted for good, and your backups
When you delete something for good, it leaves the cloud copy at once, and each of your devices when it next connects. The backups expire within 30 days: the desktop app’s backups, and old restore points and file versions in the cloud. Out of our reach: your own backups (Time Machine, a backup drive, Git history, a cloud drive), exports, and what people you shared with already copied. See Trash.
Taking everything with you
| Way out | What you get | Where |
|---|---|---|
| Your folder | Every entry, file, chat and setting, plus a database copy | Desktop app (a linked browser uses the same folder) |
| Export everything | A ZIP with the same layout as the folder | Every app and every browser, every plan |
| Export as CSV | A spreadsheet copy, made once (it does not stay in step) | In the app |
The export includes the Trash.
Export everything today
In the desktop app, open Settings → Data sync → Export and click Download .zip. The
ZIP goes to your Downloads folder. It never writes over a file that is already there: a file
with the same name gets a number, such as (2). To save it somewhere else, use kzx.
From a terminal, kzx export --zip <path> writes the ZIP where you say, for example
kzx export --zip D:\Backups\kaizendex-2026-11-07.zip.
kaizendex-export.zip database/main.sqlite a fresh, whole copy of the database, the Trash included database/locked.sqlite your locked collections and entries, still encrypted folder/Collections/... every entry file folder/Settings/... the theme, the sidebar and other settings folder/Attachments/... your files folder/Chats/... your chats folder/AGENTS.md- The ZIP is written whole, or not at all. A failed export leaves no broken file.
- The ZIP never goes inside the folder it copies.
- What it leaves out: the folder’s own read-only copy (the database copy in the ZIP is
newer) and the app’s notes in
.kaizendex/. - Locked collections and entries are in
database/locked.sqliteand infolder/as.md.encfiles, both still encrypted.
On a copy of a real account, the ZIP held 5,098 of 5,098 entry files, and its database passed its own check.
Not built yet: Export as CSV, and Restore from my folder or from a ZIP.
When Pro ends
You pick one device that stays in Cloud Sync, under the Free limits: 200 MB of files and 30 collections. Your other devices keep their copy and keep working, but stop syncing. Nothing is deleted. The rest of the cloud copy (the other devices’ sync, files over 200 MB) waits 90 days, then moves to cold storage, and is deleted one year after Pro ended, unless you come back. We email you a week before and on the day.
The app asks you to open the desktop app on your computer once, so the folder catches up, and then shows “Your folder is up to date”. A browser on its own and a phone have no folder: use Export everything there. See When Pro ends.
Deleting your account
You can undo an account deletion for 7 days. After that, everything is gone within 30 days, once our backups expire. See Your account.