Your data stays on your device
Self-improvement data is deeply personal — habits, moods, and journals reveal a lot about your life. KaiZenly+ is built so that data belongs entirely to you. Every claim below is verifiable against the app’s source code and documentation.
No developer server and no custom backend — the app does not send your data to the developer.
No mandatory login or account — normal use works fully offline.
No analytics SDKs, no advertising IDs, no background tracking or reporting.
All data lives on your device in an encrypted database.
Local backups are encrypted and protected by a password only you know.
Google Drive backup is optional and uploads an already-encrypted file to your own Drive.
What is stored, and where
Your data is stored in a database on your device, and that database is encrypted. The key that unlocks it stays on your device and never leaves it.
Local preferences (theme, onboarding state, parachute balance, schedules) are stored on the device.
A backup is saved as a single encrypted file, locked with a password you choose. The backup password is never stored and cannot be recovered by the app.
System-level cloud backup and device transfer are turned off, so your encrypted data is never copied off the device automatically — it stays on your phone.
What the developer receives
Nothing. There is no developer server or backend that your data flows to. The app has no analytics SDK, no advertising identifiers, and no background reporting. Normal use does not require a network connection at all.
This isn’t a corporate product with a data pipeline behind it — it’s built by one solo student developer with no company server to run. Keeping everything on your device is the honest, simplest way to protect your data: there is no central place for it to leak from, because it never leaves your phone in the first place.
Encryption, in plain words
Your data is encrypted. You don’t need to know the technical details — what matters is that the app, the database on your device, your backups, and the backup file that gets sent to Drive are all encrypted.
- The app’s data on your device is encrypted.
- Your local backups are encrypted.
- The backup file sent to Google Drive is already encrypted before it leaves your phone.
- A backup is unlocked by a password only you know — never stored, never sent anywhere.
Google Drive backup
Google Drive backup is optional, manual, and opt-in (and currently still
in testing). When you enable it, you link your own Google account and the app uploads one
already-encrypted backup file to your private Drive app folder (appDataFolder),
which is hidden from your normal Drive file list and only accessible to KaiZenly+. Backups
go to your Drive — never to the developer. The Google OAuth client IDs
only identify the app to Google; they don’t route data anywhere else.
Focus & Zen Shield data
The Accessibility service used during active focus sessions reads only package and class names for enforcement. It does not read message text, passwords, keystrokes, window titles, or screen content. Blocked attempts and app rules stay in the local encrypted database.
Journal media
Photos and voice notes you add to journal entries are copied into app-private storage and are never shared.
Honest about what it is
To keep this page honest, a few things KaiZenly+ is clear about:
- The repository is private — all rights reserved.
- It does not have “zero permissions” — focus protection genuinely needs some permissions, each explained on the Permissions page.
- It is a focus and habit tool — not medical, therapy, or mental-health treatment.
The formal documents
This page is the friendly overview. For the formal versions, see the Privacy Policy, the Data Safety declaration, and the Terms & Conditions.
Changes & future features
If server, backend, AI, or MCP features are ever added, this page will be updated before any data behavior changes. Those features are only a possible future direction today.
Last updated: June 23, 2026