Privacy Policy - Kaizen

Kaizen is a personal focus and study app. Everything you create in it stays on your device. Two things do leave it, and this policy names both plainly: buying Kaizen Pro, and checking for app updates.

The short version

- No account, no sign-up, no password. Kaizen never asks who you are.

- Your study data never leaves your device. Goals, tasks, focus sessions, streaks, XP, levels, seals, interruption notes and settings are all stored locally and are not uploaded anywhere.

- If you buy Kaizen Pro, purchase information — not study data — goes to Apple and to RevenueCat, the service that validates the purchase so it can be restored later.

- No analytics, no advertising, no crash-reporting SDK, no tracking across apps. Kaizen never shows the App Tracking Transparency prompt, because it has nothing to ask for.

Where your study data lives

Everything you create in Kaizen — goals and tasks, focus sessions and their full history, streaks and streak freezes, XP and levels, earned seals, interruption reasons, study times and every setting — is stored on your device using standard on-device storage. It never leaves your phone. There is no cloud copy, no sync and no account to attach it to. If you delete the app, that data is gone; we cannot recover it, because we never had it.

Backups are yours to move. Settings → Data → Export backup writes your data to a JSON file on your device. Nothing is uploaded — the file exists only where you choose to save or send it. Once you share it, by AirDrop, Files, email or a messaging app, it is covered by whatever you shared it through, not by this policy.

Buying Kaizen Pro

Kaizen Pro is an optional purchase that adds features. Everything the app did before Pro existed is still free. Buying is the one part of Kaizen that talks to a purchase server.

Apple

The transaction itself is handled by the App Store using the payment method on your Apple Account. Kaizen never sees your name, email address, Apple Account or card details — Apple hands the app back a signed receipt and nothing more.

RevenueCat

Kaizen uses RevenueCat to validate that receipt and to remember that the purchase is active, so that "Restore purchases" works after a reinstall or on another device signed in to the same Apple Account. To do that, RevenueCat's SDK sends to RevenueCat's servers:

- the App Store transaction receipt for your purchase;

- a random, anonymous identifier the SDK generates on your device the first time it runs — it looks like $RCAnonymousID:…, is not derived from you or your hardware, and reinstalling the app produces a new one;

- basic technical information about the device, such as device model and OS version;

- the IP address of the connection, which is unavoidable for any network request. RevenueCat uses it to determine a country and then discards it; per RevenueCat's documentation the IP address itself is not stored.

Kaizen does not set a custom user ID, does not send customer attributes, does not use the advertising identifier (IDFA) and does not connect RevenueCat to any analytics or attribution service. RevenueCat's privacy manifest for its iOS SDK declares exactly one collected data type — purchase history — marked not linked to identity and not used for tracking, for app-functionality purposes. RevenueCat handles this data as a processor acting on our behalf; their own policy is at revenuecat.com/privacy.

No study data is sent. Not a goal, not a task, not a session, not a minute, not a seal. RevenueCat receives purchase metadata and nothing else.

If you never buy anything, none of the above ever happens.

App updates

Kaizen can deliver small fixes without a full App Store release, using Expo's EAS Update service. On launch the app asks u.expo.dev whether a newer bundle exists for its version and channel. That request carries no personal data — it identifies the app version, the platform and the update channel — but, like any network request, it reaches Expo's servers from your device's IP address. Offline, it simply doesn't happen and the app works normally.

Notifications

Kaizen can send local notifications — focus-session reminders, study-time alerts, streak and weekly review notices — that are composed and scheduled entirely on your device. There is no push server and no remote notification. Granting notification permission is optional; declining it does not limit any other part of the app.

Third-party services

Kaizen contains no analytics, advertising, attribution or crash-reporting SDKs. The complete list of third parties that ever receive anything:

- Apple — delivers the app and processes any purchase.

- RevenueCat — validates and stores the purchase record, as described above.

- Expo (EAS Update) — answers the update check, as described above.

That is the whole list. Nothing is sold, and no data is shared with data brokers or advertisers.

Tracking

Kaizen does not track you across other apps or websites, does not use the advertising identifier and does not build a profile of you. Nothing it collects is used for advertising.

App Store privacy label

Apple's "App Privacy" label for Kaizen reports Purchases as data collected, not linked to your identity and not used for tracking. That single entry exists because of the purchase validation described above. No other category applies.

Children's privacy

Kaizen asks no one — children included — for personal information. There is no account, no profile, no messaging, no advertising and no user-generated content that leaves the device. Purchases are charged to the App Store account holder's payment method and are subject to Apple's own family controls, such as Ask to Buy and Screen Time.

Your choices

- Use Kaizen free indefinitely. With no purchase, the update check is the only network request it makes.

- Decline notification permission; nothing else changes.

- Delete the app to erase all local data.

- To ask what a purchase record contains, or to have it deleted, email the address below. Deleting it may leave "Restore purchases" unable to find a Pro unlock; Apple keeps its own record of the transaction regardless.

Changes to this policy

If this policy changes — for example if a future version adds optional cloud sync — this document is updated and the hosted version reflects the same terms.

Contact

Questions about this policy: ahmetyadgarovjust@gmail.com