Your privacy choices
Every collection and every entry has one Share & privacy panel. You choose there where it lives, who can see it and what AI may read. An entry follows its collection until you change it there; then the entry’s own choice wins.
Where it lives: you choose per collection
Privacy here is not all or nothing. Each collection, and each entry, picks one of three places:
| Where | What it means |
|---|---|
| Cloud Sync (the default) | On your devices and in the cloud. Kaizendex protects it: encrypted on the network and on disk, and kept apart from every other person’s data. We can help you recover it. On Pro, agents in the cloud can use it. |
| Cloud Sync, end-to-end encrypted | The same, but your devices lock it before it leaves them, and only your devices hold the key. Not even Kaizendex can read it. Agents in the cloud read it only if you give them a key for that collection. |
| This device only | It never leaves this device, not even its name. It does not appear on your other devices at all, and it is not in the cloud. |
End-to-end encrypted means only your devices hold the key. See End-to-end encryption.
Example: you keep three collections, and each one picks its own place.
- An entry can differ from its collection. Workouts is in plain Cloud Sync, but the entry “Physio notes” inside it can be end-to-end encrypted, or This device only.
- The starting value for new collections is in Settings → Cloud Sync. It is Cloud Sync unless you change it.
- Cloud Sync for everything can be turned off only in the desktop app. Then your data lives only on that computer. A browser on its own and a phone always use Cloud Sync, because a browser can lose its data when it is cleared and a phone has no folder. Any single collection or entry can still be This device only there. See Devices and sync.
Changing it later
Changing Where is a change only you can make: you
make it in the app, after Face ID, a fingerprint, Windows Hello or your device password. The
folder, kzx, MCP and agents can only suggest it.
- To This device only: the app deletes the cloud copy and the copies on your other devices. First it asks you, and lists those devices.
- A shared collection must stay in Cloud Sync. Making it This device only stops the sharing, after a warning.
- A shared collection cannot be end-to-end encrypted. Sharing an end-to-end collection (with people or as a public page) switches only that collection to plain Cloud Sync, after a warning. When you stop sharing, you can turn end-to-end on again. Publishing its setup to the Library does not: your entries never go out, so it stays end-to-end. See Sharing turns end-to-end off.
- From This device only to Cloud Sync: the app uploads it, and your other devices get it.
This device only in a browser linked to the desktop app means your computer: the browser uses the desktop app’s data, so the collection lives in the desktop app and never goes to the cloud.
This device only keeps its name too
A “This device only” collection stays on its device, and so does its name. Example: your Diary is This device only, and the Workouts entry “Morning run” links to the Diary entry “Tired legs”.
- On your other devices, the link shows as “A private item”. Only a hidden id syncs, never the title.
- In AI chats, Diary is never sent to a cloud AI model. The AI receipt shows “1 private item” instead.
- With Git, “Version this folder with Git” never pushes Diary’s files.
- In a cloud drive: if your
~/Kaizendexfolder sits inside OneDrive, iCloud Drive, Dropbox or Google Drive, the app warns you: “Your cloud drive uploads this folder, This device only collections included.” See Your folder.
The choices in the panel
| Choice | Options | Default | Set on |
|---|---|---|---|
| Who can see it | Only me · People (view, comment or edit) · Anyone with the link · Public | Only me | Collection or entry |
| Where it lives | Cloud Sync · Cloud Sync, end-to-end encrypted · This device only | Cloud Sync | Collection or entry |
| AI | Any AI · Ask me first · Only my local AI · No AI | Any AI, with nothing kept | Collection or entry |
| Hidden | No · Yes | No | Collection or entry |
| In the folder | In the folder · Database only · Not in the folder | In the folder | Collection only |
What works today (the desktop app, and a browser paired with it): press Share in the top bar of a collection or an entry. The panel has AI, Hidden and, for a collection, In the folder. Who can see it and Where come with sharing and sync. A change shows at once; if it is refused, the panel says why in one line.
Each choice has its own page: What AI may read, Hidden entries, Locked files, End-to-end encryption, Devices and sync and Share with people. For the lock on each place that holds your data, see How your data is protected.
The entry wins, both ways
An entry’s own choice can be stricter or looser than its collection. Your Health collection asks first, but one entry can be No AI. A private collection can still have one shared entry.
The entry’s panel says plainly what it does:
- “Follows Health, except 2 settings.”
- “Only this entry. Health: Ask me first.” with a Use Health’s button to go back.
The AI choice also sets the folder
With Any AI, the entry’s file in your folder is plain text. With any other AI choice, or with Hidden, the file is locked (encrypted), because AI apps on your computer cannot ask you first. A single private entry inside an Any AI collection is locked on its own.
What is built from your data is as private as its source
The app builds things from your data: the search index, AI search, the read-only database copy in your folder, chats, AI receipts, automation run history and summaries. Each one follows the strictest choice of the data it came from.
Example: your Health collection is end-to-end encrypted. You ask the AI “Did my sleep change after the blood test?”, and the answer quotes Health. That chat is stored end-to-end encrypted too. Search over Health runs on your device, never in the cloud.
One rule, everywhere
The engine works out the choice for each entry once, and applies it everywhere: in storage, sync, the AI, scripts and automations, the folder and Cloud Sync. No part of the app has its own copy of the rule.