Kaizen Privacy Policy

Last updated: 2026-05-19

This policy describes what Kaizen (“the app”, “we”) collects when you use it, how we use it, who processes it on our behalf, and how you can delete it. The policy is written in plain English so you can read it once and know.

What we collect

Authentication identifiers

• Apple user ID (when you sign in with Apple) — the opaque, app-scoped ID Apple issues. We never receive your Apple ID email unless you choose to share it.
• Google account “sub” identifier (when you sign in with Google) — the opaque, app-scoped ID Google issues for your account.
• Email address and password (when you sign in with email/password) — your email is stored; your password is hashed by Supabase Auth before storage and is never readable by us.
• Supabase-issued user ID — an opaque UUID we use internally to route every row of your data. This ID is created the first time you sign in.

Profile data

• Display name — the public handle you choose during onboarding.
• Email address — the one your auth provider returned, used to identify you on future sign-ins.
• Timezone — the IANA identifier of where you live (e.g. America/Los_Angeles), used so daily targets and logs line up with your local calendar.
• Daily reminder hour — the hour (0–23) at which you have opted to receive a notification reminding you to log your habits.

Habit data

• Habits you create — title, kind (time/count/binary), start value, current baseline, final goal, value unit, status, streak counter, 21-day counter.
• Daily logs — for each habit and each calendar day on which you logged: the raw actual value you entered, the target value the math engine computed, the outcome (Better, Perfect, or Off-day), and the proportional daily gain.
• Dashboard snapshots — the compounded total factor across all your habits for each day on which you logged at least one habit.

Telemetry events

We use TelemetryDeck to record discrete, anonymous events such as “app launched”, “habit created”, “habit logged” (along with the outcome bucket), “dashboard viewed”, “milestone 2× reached”, and “account deleted”. Each event is a single enum value with no free-form text. We do not attach your user ID, email, name, or any other personal identifier to telemetry events.