Locked files
When a collection or entry is set to anything but Any AI, or is Hidden, its files in your folder are locked: encrypted, so AI apps on your computer see only scrambled bytes.
Why the folder needs locks
Any AI app you run on your computer (Claude Code, Codex, a script) can read every file you can read. No folder layout stops that. Kaizendex’s own AI asks or refuses, but an outside app cannot ask you first. So the app encrypts the files that the AI should not read freely.
What decides it
You do not lock files by hand. The AI setting decides:
| The collection or entry is set to | Its files in the folder |
|---|---|
| Any AI | Plain markdown files |
| Ask me first, Only my local AI, or No AI | Locked |
| Hidden (with any AI setting) | Locked |
The collection’s folder choice decides the rest:
| Folder choice | What an AI app finds |
|---|---|
| In the folder | The files, plain or locked as above |
| Database only | No entry files. The rows are in the read-only database copy, unless they are locked. |
| Not in the folder | Nothing |
One private entry inside an Any AI collection is locked on its own. It never sits in plain text beside its collection.
How a locked file works
- It is named by date and id, never by title, because a title can give away what is inside.
- Double-click it to open it in Kaizendex.
- It opens by itself while you are signed in to your computer. The key sits in your computer’s keychain (its built-in password safe). There is no Kaizendex password to remember.
- A new computer gets the key back after you sign in and Approve it on a device you have, or after a 72-hour wait (what skips the wait). Kaizendex keeps a recovery copy of the key with your account. This key opens only the locked files in your folder, which we never hold. It does not open end-to-end encrypted collections in the cloud: those need your own keys.
- All of the entry moves into the lock: its values, Block pages, Dashboards, history, search data and any chat that quoted it. When you lock something, the app offers Scrub older copies to clean up older plain copies.
- Some names stay plain: collection names, property names and tag names.
The folder belongs to the desktop app. A browser linked to the desktop app uses the desktop app’s key and keeps nothing itself. Before it shows a locked collection, the desktop app asks for a fresh unlock: Face ID, a fingerprint, Windows Hello or your computer password. A browser on a computer without the desktop app has no folder, but it still encrypts locked collections, with a key kept in the browser. If the browser clears that key, approve the browser again from another of your devices.
What works today
- Locked entries live in their own encrypted database,
locked.sqlite, beside the plain one. The app shows both as one, so screens and search work the same. - Locking moves the whole entry: its values, Block pages, history, search data and AI search data. Unlocking moves it back. If the app closes in the middle, it finishes the move the next time it opens.
- Chats and files follow the entry. A chat moves into the lock when a message names a locked entry (you mentioned it, or the AI read it), shows a locked photo, or talks with a locked agent. A photo or file a locked entry holds moves in too, with the text read from it. The history of every chat and file is kept in the lock. You see them as before.
- Old plain copies are cleaned. The first time, the app keeps one safety copy in its own backups folder, then cleans the plain database so no older copy of a locked entry stays in it. Deleted text is overwritten, not only marked as deleted.
- The key sits in your computer’s keychain. There is nothing to type.
- Backups and the ZIP keep locked entries encrypted.
- A browser linked to the desktop app shows locked collections and entries only after a fresh unlock (Windows Hello, or the computer password on Linux).
- Locked chats and photos are locked files too. In your folder, a locked chat is
Chats/<date> <id>.md.enc, and a photo or file a locked entry holds isAttachments/<month>/<id>.png.enc(its own extension, then.enc). The plain copy goes. Unlock the entry and the plain files come back. - Double-click a locked file and the desktop app opens at its entry. A locked chat opens the
Chats page. A locked photo shows a note: open it from its entry. A file from another
account, a damaged file, or a computer without the key gets a short note instead, never the
file’s text. On Windows the app opens
.encfiles; any.encfile that is not a Kaizendex locked file gets a short note too.
Not yet: the recovery copy of the key comes with accounts.
No lock on the whole folder
There is no switch that locks all of ~/Kaizendex. Disk encryption (BitLocker or FileVault,
which the app checks) already protects a stolen computer. Locked collections encrypt what is
sensitive. A lock on the whole folder would shut out you, Obsidian and your AI agents, and the
folder exists so they can use it.
The polite layer
The app also writes “do not read” rules for known agents into the folder: Claude Code
permission rules, .cursorignore, .aiexclude, and a line in AGENTS.md. Well-behaved
agents follow them. They are an extra layer, not the protection.