Daily Readiness — Privacy Policy

Where this translation and the Korean original differ, the Korean version governs.

The conditions for using the Service are set out in our Terms of Service.


1. In short

  1. Your health data never leaves your iPhone or Android device. Sleep, heart rate, heart rate variability, wrist temperature and workout records are read, analysed and stored on your device only. We do not operate a server that receives them.
  2. Four things are stored on a server — your account details, error reports (crash and freeze records by default, everything else only if you opt in), a minimal usage signal that counts the days you opened the app (§2-4), and an app rating or feedback if you send one yourself (§2-5). Account details are your email address, a hash of your password, and your display language. Of the error reports, only records of the moment the app suddenly closed or froze (crashes and freezes) are sent by default (you can turn this off in Settings); which screens you opened, what you tapped and anything else that went wrong are sent only if you turn error reports on in the app (§2-3). The minimal usage signal is sent without asking and cannot be turned off — §2-4 sets out exactly what it carries and how to stop it. Health values and your daily score are in none of them.
  3. You can use every analysis feature without an account. Signing up is optional.
  4. We use no advertising identifier, include no third-party analytics, advertising or crash-reporting SDK whatsoever, and never sell or share your data with third parties. Error reports go only to our own server — no vendor sits in between.

  5. On Android we read from Health Connect, not Apple Health. We read fewer items than on iOS (13 read types), and the only thing we write to Health Connect is a nap you entered yourself. See §3-A.

  6. The Android build has no account feature, no error reporting and no minimal usage signal. The Android app does not declare the internet permission, so it sends no data off the device. The server-related parts of this document — §2-1 (accounts), §2-3 (error reports), §2-4 (the minimal usage signal), §5 (automatic logs), §7 (processors), §8 (international transfers), the server-side entries in §9 and §10 (account deletion) — therefore do not apply on Android.

2. What we collect

2-1. Stored on the server (only if you create an account)

Item Required / optional When Purpose Retention
Email address Required to have an account Sign-up Identifying your account, signing in, sending password-reset mail Until you delete your account
Password Required to have an account Sign-up Authentication Until account deletion (stored only as a hash — the plain password is never stored and cannot be recovered from what we hold)
Display language (one of ko/en/ja/es) Required (set from your device language, changeable) Sign-up, settings change Showing the app and authentication emails in the same language Until account deletion
Account identifier (UUID), sign-up time, email confirmation time, last sign-in time Required (generated automatically) Sign-up, sign-in Account management, spotting abuse Until account deletion
Sign-in session record — IP address, user agent (app and OS version), sign-in and refresh times Required (generated automatically) Each sign-in Keeping you signed in (a record kept by the authentication service), telling which country you signed up from (§5) While you stay signed in — signing out deletes that device's record, and deleting your account deletes all of them (§9)

If you never create an account, none of the above is collected.

2-2. Stored on your device only (never transmitted)

Item Required / optional Purpose
Health data read from Apple Health (HealthKit, iOS) or Health Connect (Android) Optional — the app runs without this permission (it simply cannot compute a score) Calculating your readiness score, condition level and workout suggestion. Android reads fewer items than iOS — see §3-A
Values derived from that data (daily summaries, scores, personal baselines) Optional (automatic once health access is granted) Reproducing calculations, showing your last 7 days
Today's step count counted by the device's motion sensor (iOS) Optional — only if you allow Motion & Fitness Showing steps on the step card when today's steps are not available from the Health app. Not stored on the device and not used in the score (§3, “Built-in pedometer”)
Naps (start and end time), caffeine (mg) and drinks (count) you enter yourself Optional — only if you log them Counting the nap towards your sleep, and caffeine and drinks towards that day's lifestyle record. Anything you allow write access for is saved into Apple Health; anything you do not stays on this device only (write access is asked for all three types together during first-time setup, and one type at a time on devices set up before this revision — see §3)
Date of birth (year, month, day) and biological sex Optional — the app works without them (you simply lose the age-based guidance) Working out the weekly activity range and target heart-rate zone that match your age. Your date of birth is also used for Today's Saju reading (on by default; you can turn it off in Settings) (§3-B)
Time of birth (hour and minute), country and time zone of birth Optional — used only if you enter it yourself in Today's Saju reading; if you don't, it stays “don't know” Calculating the Saju reading (§3-B). The country and time zone are used only to apply the standard time in effect when you were born
App settings (display language, notification time, sleep goal, onboarding state, celebration-card state, flags that stop us asking the same thing twice) Required for the app to work App behaviour
«How you get around» choices — «I get around by wheelchair» and «I walk slowly» (if you set them) Optional — the app works without them Used only to decide whether to read your daily activity as pushes instead of steps, and whether to lower our confidence in gauging your activity from your step count (§3). They do not change your readiness score or stage. Stored on your device only and never sent to a server
Usual weekly pattern (working/day-off per weekday, whether you wake without an alarm on days off, whether you work shifts — if you set these) Optional — the app works without it Used only to compare your sleep on days off with working days. Applied retroactively to past nights, which are recalculated. Stored on your device only and never sent to a server
Target bedtime (if you set one) Optional — the app works without it Used only to check whether a nap close to your target bedtime affected that night's sleep. Stored on your device only and never sent to a server
Morning check-in — how refreshed you felt on waking (1–5), afternoon sleepiness, and your answer to a follow-up question about whether fatigue from exercise is lingering (if you answer). From 1.7.0 these three questions no longer appear — only the answers you already gave remain, you can view and export them, and no new answers are added Optional — the app works if you skip it Used to show your past answers by date. Your answer about lingering fatigue from exercise is not used in the score. Stored on your device only and never sent to a server. If you tap 'Export as file', a file with your answers (the lingering-fatigue answer only for days the question was shown) and that day's wrist-temperature results (values produced by calculation, not the readings) is handed to the place you choose
Your device's time zone Required Determining which day counts as "today". If your device's time zone changes by two hours or more, the app reads it as travel or jet lag and detects it automatically — it keeps only the time-zone offset from UTC (not city names) for the last 28 days, on your device only, never sent to a server, and you can turn it off any time in Settings
Exercise rest days you declare (dates on which you turned on «Make today a rest day from exercise» on the Today tab — if you do) Optional — the app works if you never turn it on Used only to set that day's share of this week's activity target to 0 and to leave that day out of the 7-day completion rate. Not used for your readiness score, stage or exercise recommendations. Stored only on your device and never sent to our servers. Turning the switch off for a day deletes that day's record; «Delete all exercise rest days» in Settings deletes them all at once, and deleting the app deletes them too
State-of-mind entry — how you feel right now, one of five steps (if you answer) Optional — the app works if you skip it Used to show your past answers by date. Stored on your device only and never sent to a server. Not used in the readiness score or the condition level. On iPhone, if you allow writing to Apple Health's «State of Mind», it is written there too — we ask for that one type the first time you answer, and if you decline it stays on your device only
Notes on your day — if you tick any of: travel or time-zone change, vaccination, a change in the medicines you take, high altitude, shift work, alcohol or caffeine, a late meal or a late workout, or feeling unwell, we keep only which items you ticked and the date Optional — the app works if you skip it Used only to lower the confidence of that day's metrics or leave that night out of your usual baseline, never to name a cause. We never ask for medicine names, doses, vaccine types, clinics or symptoms. Kept on your device only and never sent to a server. On a day your device's time zone changes by two hours or more, the app turns on «travel or time-zone change» for you in advance — you can turn it off any time on the Notes on your day screen, and once you turn it off, it will not turn back on for the same trip
Sign-in session token Only if you have an account So you don't have to sign in every time

Date of birth and sex are looked for in your Apple Health profile first. If they are already written there, the app reads them (so you are not asked to type in something you have already entered); if they are missing, or you did not grant access, the app asks you once, at the point where the value is actually used. You may leave it unanswered, and if you decline we do not ask again. Either way, these values never leave your device.

We never ask for location access. The time zone is read from the iOS time-zone setting; we do not look up where you are. We also never ask for contacts, photos, microphone or camera access.

2-3. Error reports (crash and freeze records on by default · everything else opt-in)

These are the records that tell us what went wrong when the app freezes or a screen misbehaves. We ask once, on first launch, and if you do not turn them on nothing but the crash and freeze records below is ever sent — nothing is even queued on your device. You can turn them off at any time in Settings → Error reports; sending stops immediately and anything still held on the device is deleted. We also use the same records to see which features are used and which are not, so that we can fix the app. Nothing new is sent.

The minimal usage signal, which only counts the days you opened the app, is separate from this setting and is described in §2-4.

Crash and freeze records are sent by default, separately from this consent. If the app suddenly closes or freezes, iOS (MetricKit) hands the record to the app on its next launch, and the app sends only the error kind and code and the call order of the code that was running at that moment, together with the “Device and app” and “Install identifier” items below. We also send the names of up to 20 screens and features you passed through just before the app closed — we send them even if you have not turned error reports on. The names can only come from a list the app fixed in advance (for example the «Today» screen). Nothing you typed, no health value, no daily score and no time of day is included. Everything else in an error report is still sent only if you turned it on, as before. You can turn this off in Settings → Error reports → “Send crash and freeze reports”; sending stops immediately and any crash and freeze records not yet sent are deleted. Retention, deletion and the link to your account work the same as for error reports below.

What we send

Item Example
Screens and actions Which screens you opened, which buttons you tapped, which onboarding step you reached
App state Whether the analysis succeeded, found no data, or lacked permission; whether today's score appeared on screen
Error details Error kind, code and message; the sequence of function calls at the moment of a crash; the names of your last 20 actions
Device and app iOS version, device model (e.g. iPhone16,2), app version and build number, display language
Install identifier A random value (UUID) the app generates to tell this installation apart, together with a random secret that proves the identifier belongs to this installation. The server stores only an irreversible hash of the secret, never the secret itself. Neither is a device serial number or an advertising identifier

What we never send

Sleep duration, heart rate, heart rate variability, wrist temperature, respiratory rate, body weight, step count, workouts, nap times — every health value, and the daily score and condition level computed from them. Nor your email address, your password, or any free text you typed.

For the score we record a state, never a value: one of "score ready / still computing / no data / no permission". The number itself is never transmitted. Anything time-based is converted to a range (e.g. "0.5–2 s") before it leaves the device.

Email addresses, file paths and long random strings are replaced with placeholders on your device before an error message or call sequence is sent.

Link to your account: reports sent while you are signed in are linked to your account. If you are not signed in, only the install identifier remains and we cannot tell who you are. Deleting your account deletes the linked reports with it.

Deletion: Settings → Error reports → "Delete sent records" removes this device's records from the server; anything sent afterwards uses a new install identifier.

Only this device can delete or add to the records it sent. Knowing the install identifier alone is not enough to delete those records or to send records under that identifier — sending and deleting both require the secret above. The identifier and the secret are created when crash and freeze reports are on (the default) or when you turn error reports on, and are kept in this device's iOS Keychain. They stay there after you turn both off, so that you can still delete what was already sent, and because they are in the Keychain they may survive deleting and reinstalling the app.

What remains after deletion: when this device's records are deleted from the server (by “Delete sent records”, by deleting your account, or when the retention period ends), an irreversible hash of the deleted install identifier and the time of deletion remain, plus — if you deleted the records yourself — a verification value used to confirm again that the deletion was completed. They exist so that no records build up again under a deleted identifier and so that a completed deletion can be confirmed; they contain no account, IP address, record content or secret. These values are kept and not deleted (§9).

IP address: to block excessive requests we use the IP address a request comes from, but we do not store it as is. The server turns it into an irreversible value used only to count requests in 5-minute windows, and counts older than one day are deleted (§9). The server platform's API request log does, however, keep the IP address of each request for 7 days (§5).

2-4. Minimal usage signal (sent without asking · iOS build only)

Once a day, the first time you open the app that day, we send our server one fact: “this installation opened the app today.” It tells us how many people use the app and whether they keep using it after installing.

What is sent — six fields, and that is all

Field Value
Install identifier A random value (UUID) the app generates to tell this installation apart. It is neither a device identifier nor an advertising identifier, and it is a different value from the install identifier used for error reports (§2-3)
Date The date you opened the app (for example 2026-09-30). The time of day is not sent
Platform ios
App version for example 1.3.1
Build number for example 57
Whether you allowed health permissions We send how it went the first time you connected, as one of four things — you allowed them all · some were not allowed · we could not check · you postponed it (each goes out as a single word: ok · missing · unchecked · skipped). Which item it was, your health values and your daily score are not included. If you have not yet passed the connect step, we send the five fields without this one

What is not sent

This field is kept for 90 days only. After 90 days the per-installation record is deleted, and the daily totals we keep indefinitely do not hold this field (§9).

It is never joined to error reports. The two use different identifiers, different storage and different tables, and the server has no column that joins them. The app never puts both in one request.

Deleting and reinstalling the app produces a new value. The identifier lives in the device settings store and is removed with the app (§12). So our count of installations runs slightly high, and the share of people who keep using the app slightly low.

There is no setting to turn it off. You can delete what has been sent (§11), but while you use the app a new signal goes out the next day. To stop it, you have to delete the app.

The Android build does not send this signal (§1, item 6).

2-5. App ratings and feedback (only when you send them yourself)

If you give a star rating on the card inside the app, or write to us through “Send feedback to the developer” near the bottom of Settings, what you write is sent to our server and forwarded to a private Slack channel only we can see. If you do not send anything, nothing is created — dismissing or postponing the card stays on your device (§12).

What is sent

Item Value
Rating One of 1–5, if you gave a star rating
What you wrote The optional line you added to a rating, or the body of your feedback. It is sent exactly as you wrote it
Reply-to email address Only if you type it in. It is an optional field on the feedback form; we do not take your account email for this
Platform, app version, build number, display language, OS version So we know which build you wrote from. The device model is not sent

What is not sent

It is forwarded to the Slack channel we read. What you wrote, and the reply-to address if you gave one, are forwarded to a private Slack channel in the United States and stored there (§7, §8). Health values and your daily score are not included.

We keep it for two years (§9). If you want it removed, ask us the way §11 describes — because you can send it without an account we cannot tell who sent it, so tell us what you sent and we will find it and delete it.

The Android build does not send any of this to a server. Ratings stay on the device, and feedback is sent by your own mail app — the app does not transmit it — because the Android build has no internet permission (point 6 of §1). Once the mail is sent, its retention follows that mail service.

The app build that carries this feature ships after this publication. Until then none of the transmissions in this section happen.

3. Health data, in detail

The app reads the data below, strictly within what you allow on Apple's Health permission screen. What it reads is used only to compute your readiness score on the device.

What it writes to Apple Health is the three things you enter yourself in the app — naps, caffeine and drinks.

What you enter Stored in Apple Health as Unit
A nap (start and end time) Sleep analysis (sleepAnalysis) a time span
Caffeine Caffeine intake (dietaryCaffeine) mg
Drinks Alcoholic beverages (numberOfAlcoholicBeverages) number of drinks

A write happens when you fill a value in and tap save, and what is stored is exactly the value you entered. The app never writes back the health values it read or the score it calculated.

There is one exception, and it only runs if you switch it on. If you turn on Days with none in Settings, then for any day that ends with no caffeine or drink entry at all, the app records a zero on your behalf at 11:59 PM that day. The switch is off by default, applies only to days after you turn it on, and can be turned off again at any time.

The only value ever written this way is zero. Days another app already wrote to are left alone, today is never touched because it has not ended, and days before you turned it on stay as they are. Like every other write, this one only reaches Apple Health for the types you granted write access to; anything you did not stays on this device only.

Why record a zero: if a day you drank nothing looks the same as a day with no record at all, then abstaining gets buried as missing data when the recovery score is calculated. This feature exists to keep those two apart.

There are two moments when write access is requested. If you are setting the app up for the first time, we ask for write access to these three types (naps, caffeine, drinks) together with read access, right there in the same step. On a device that finished setup before this revision, you were not asked then, so we ask the first time you try to save an entry of that kind — and only for that one type: saving a nap asks only for the sleep type, saving caffeine asks only for caffeine.

Either way, the question comes from iOS's own permission prompt and you can decline. If you decline, that entry is not written to Apple Health, stays on this device instead, and the app carries on working. Allowing reading and allowing writing are two different things — granting one does not grant the other.

No entry you did not enter here is ever modified or deleted. A record you just saved can be removed with "Undo" for a short moment right after saving, and only that one record is removed. After that moment the app cannot remove it and you would delete it in Apple Health.

What is read (24 types, verified against the code, plus 3 profile characteristics):

The types the readiness score is built from:

  1. Heartbeat series (beat-to-beat intervals) — so the app can compute heart rate variability (rMSSD) itself
  2. Heart rate variability (HRV SDNN) — a fallback for days when the above is insufficient
  3. Resting heart rate
  4. Heart rate
  5. Respiratory rate
  6. Wrist temperature during sleep
  7. Sleep analysis (stages and duration)
  8. Workouts (type, duration, average heart rate)
  9. Step count — walking you never logged as a workout is counted toward this week's activity

Everyday entries that only nudge the score (it works fine without them):

  1. Breathing disturbances during sleep — this type only exists on iOS 18 and later, so it is not requested below that
  2. Alcohol entries (number of drinks)
  3. Caffeine entries — only what lands late in the day is counted
  4. Mindful minutes
  5. Blood pressure entries (systolic and diastolic)
  6. Blood glucose entries

Types that never enter the score at all, and are used only for the guidance text:

  1. Time spent in daylight — this type only exists on iOS 17 and later, so it is not requested below that
  2. Body composition entries (weight, lean body mass, body fat percentage) — whichever of the three exist
  3. Irregular heart rhythm notifications and atrial fibrillation history — the notification and the record your Apple Watch made are taken as they are. The app makes no judgement of its own from them
  4. High and low heart rate notifications — a record of notifications your Apple Watch sent. The heart rate at which those notifications go off is a value you chose on the watch yourself, and the app does not read it: it receives only the fact that you were notified
  5. Notifications about breathing during sleep — a record of notifications your Apple Watch sent by itself after looking at many nights. Item 10 (breathing disturbances during sleep) is a value per night; this one is the notification the watch sent
  6. Active energy (active calories) — used to sort the time you spent moving into intensity levels (light, moderate, vigorous), and the activity detail screen shows that day's estimate together with how reliable it is. It fills in stretches where heart rate and steps can't tell the intensity, and it does not change your readiness score or stage
  7. Stand hours — the hour-by-hour record your Apple Watch keeps of whether you got up and moved in that hour. Used only to count the waking hours in which movement was confirmed, and it does not change your readiness score or stage
  8. Cardio fitness (estimated VO₂ max) — the value your Apple Watch estimates from outdoor walks and runs and writes to the Health app. The app does not measure it; it only reads what is already there
  9. Wheelchair pushes — used to read the daily activity of people who get around by wheelchair as pushes instead of steps. Pushes are never converted into a step count. A low push count never takes points away

The app also reads the three characteristics written in your Apple Health profile. They are listed apart from the numbered types because they are not entries that accumulate day by day, but values recorded once in the profile.

You allow each type separately, and anything you leave off is never read. Items 10–15 are not needed to produce a readiness score; they only move a score that has already been worked out slightly up or down. Items 16–17 and the three characteristics do not change the score at all — they are used only for the single line of guidance under the daily health card, as a reference alongside the workout suggestion, for the card that congratulates you on a new measurement, and to work out the activity range and target heart-rate zone that match your age. Item 18 neither raises nor lowers your score — it is used only to leave the heart rate variability of a night with a notification out of the recovery reading. The value for that night is kept, and there is no path in the app by which these records take points away. Items 19 and 20 do not enter the score either — they have a single use. If you have such a notification on record within the last seven days, a single line of guidance appears at the bottom of the related metric detail screen: "If these notifications continue, consider talking it over with a healthcare professional." (heart rate notifications on the resting heart rate detail, breathing notifications on the breathing rate detail). We do not count how many notifications there were, we do not read the values attached to them, and once you dismiss the line it does not come back until a new notification arrives. All three (items 18–20) are judgements your Apple Watch has already made: the app has no feature that looks at your heart rate or breathing and decides on its own that it is high or low. Item 21 does not change your readiness score or stage either — when the app sorts your active time by intensity, it only fills in stretches that heart rate and steps cannot tell. Turning calories into intensity needs your weight, so the weight from item 17 is used with it. The calorie values themselves are not stored; only the result, minutes of activity by intensity, is kept. Item 22 does not change your readiness score or stage either — the app takes the record your Apple Watch has already made as it is and counts, among your waking hours, the hours in which movement was and was not confirmed. Hours you were asleep are not counted. The records themselves are not stored; only the number of hours for each day is kept. Item 23 does not change your readiness score or stage either — it is used only to show the value and where it sits among people of a similar age (an age range), and to choose walking or cardio suggestions within the same stage. It stays on your device and is not sent to any server.

Item 24 and the wheelchair characteristic do not change your readiness score or stage either — they are read only if your profile says you use a wheelchair, and only to read your daily activity as pushes instead of steps. Pushes are never converted into a step count, so there is no path for them into the activity score and a low push count never takes points away.

The «How you get around» choices in the app's settings do not change your readiness score or stage either (the same on iOS and Android). «I get around by wheelchair» only makes us read your daily activity as pushes, as above, and «I walk slowly» never raises or lowers your step count — it only lowers our confidence in gauging your activity from that step count. Both are stored on your device only if you set them, and are never sent to a server (§2-2).

What the on-device database keeps is derived values and summaries:

We do not read immunisation or medication records from the Health app. The app only knows what you tick yourself. None of this is sent to any server, and none of it is stored in iCloud. Signing in changes nothing about this — your account and your health data are not linked.

Built-in pedometer — Motion & Fitness (iOS)

When today's step count is not available from the Health app (because you have not connected it, or there is no value for today yet), the app counts your steps since midnight with the iPhone's motion sensor and shows them on the step card in the Today tab. At that point iOS asks for the Motion & Fitness permission.

3-A. Health data read and written on Android (Health Connect)

On Android the app reads health data from Health Connect instead of Apple Health. The principle is the same as on iOS — we read only the items you explicitly allow on the permission screen, and we use them only to compute your readiness score on your device. Neither that data nor anything derived from it is sent to any server, stored in any cloud, shared with or sold to third parties, or used for advertising.

3-A-1. What we read (13 types)

Items that build the readiness score:

  1. Sleep sessions (stages and duration) — actual sleep time and sleep efficiency
  2. Exercise sessions (type and duration) — this week's cardio and strength load
  3. Steps — so walking that was never recorded as a workout still counts toward the week
  4. Resting heart rate
  5. Heart rate variability (rMSSD) — we read the value your device maker has already computed. Unlike iOS, the app does not read raw heartbeat intervals and compute it itself
  6. Respiratory rate

Items we only show you — they never move the score:

  1. Heart rate (samples through the night) — the shape of your heart rate while you sleep. Item 4 is a single value per day and cannot describe a night, so we read this separately. It does not raise or lower your readiness score
  2. Skin temperature — we only show how far it drifted from your own usual. There is no absolute reference for it, so it stays out of the score

Not used in the score — shown only as reference values on your workout screen:

  1. Weight — together with items 10–11 below, a reference shown on your workout screen
  2. Lean body mass
  3. Body fat percentage — for items 9–11 we show only the measured value and the change since your previous measurement on today's workout screen, and leave one card in your feed on a day you measure again. We never judge them as good or bad, and the app keeps no separate store of measurements (only that day's values in the feed card are saved on your device)

Read only if you turn on cycle and hormone context (§3-C):

  1. Menstruation periods and menstrual records — we ask for this permission only after you turn on the menstrual cycle item under «Cycle & hormone context» in Settings and give separate in-app consent. It does not appear on the permission screen when you first connect. We use dates only and do not read flow or type; turning the item off deletes those dates and everything derived from them (§3-C)

Not used in the score, shown only in the «Cardio fitness» section of the activity detail:

  1. Cardio fitness (estimated VO₂ max) — the same as item 23 on iOS. We only read the value your watch estimated during exercise and wrote to Health Connect; the app does not measure it. It is used only to show that value, the trend between values from the same device, and where it sits among people of similar age, and it does not change your readiness score or stage

You can allow each item separately, and anything you leave off is not read.

3-A-2. What we write (1 type)

The only thing we write to Health Connect is a nap you entered yourself (one sleep session). It is written at the moment you press save, with exactly the start and end time you entered — as a single interval without sleep stages, marked as a manually entered record and tagged with an identifier this app assigns.

Write permission is requested together with the read permissions when you first connect. If you did not allow it then, we ask again at the moment you try to save a nap. If you decline, the nap is not written to Health Connect and stays on your device only; it still counts towards your readiness score. You can write that same entry later with "Save to Health Connect again" on the nap log screen — the app never resends it on its own. The Settings screen also shows you how to turn write access on.

The nap log kept on your device. To confirm that a save really finished, and to retry without writing the same nap twice when a response is lost, the app keeps two things in its on-device database:

Sleep records read from Health Connect are not kept in this log. A nap that has not been confirmed as written to Health Connect is never shown as written.

Entries are deleted automatically after 180 days. Log entries for a nap whose day is more than 180 days in the past are deleted from the device the next time the app reads your health data. Records already written to Health Connect are not touched.

You can undo naps one at a time. Pressing undo in the list on the nap entry screen deletes that nap only. In Health Connect the app finds and deletes that record by the identifier it assigned — never by a time range — so sleep records written by other apps are not deleted.

We never write back values we read or scores we computed, and we do not modify or delete records you did not enter in this app.

3-A-3. One special permission

Health Connect has special permissions that are separate from the data types; this app asks only for reading historical data. The app works if you decline it.

If you uninstall and reinstall the app, all permissions are gone and the 30-day limit starts over.

3-A-4. How this differs from iOS, and why

iOS and Android users read the same document, so we spell out what differs and why. We did not choose to make them different; the two platforms offer different things.

iOS (§3) Android (§3-A) Why
24 read types + 3 profile characteristics 13 read types ① Health Connect has no data type at all for some items — alcohol, sleep breathing disturbances, time in daylight, stand hours (on Android, hours with movement are counted from hourly steps). ② Body composition (weight, lean body mass, body fat percentage) was left out of the first release and is read from 2026-10-02 (items 9–11 in §3-A-1). Skin temperature was added on 2026-09-05 (item 8 in §3-A-1). ③ Mindfulness is not yet available in the stable client. ④ What iOS reads as two types (beat-to-beat intervals and HRV SDNN), Android reads as one (rMSSD — see the next row). ⑤ Cardio fitness (VO₂ max) is read on iOS since 2026-10-03 and on Android since 2026-10-26 (item 13 in §3-A-1) — the Android app now has a screen that shows it (the «Cardio fitness» section of the activity detail), so it asks for the permission. ⑥ Wheelchair pushes are read on iOS only (item 24 in §3) — Google Play rejected this permission as a «minimum scope» violation on 2026-11-12, so from 2026-11-17 Android no longer asks for it. The «I get around by wheelchair» choice in «How you get around» (Settings) stays — pushes are never converted into a step count, and a low push or step count never takes points away. ⑦ Blood pressure, blood glucose and caffeine are read on iOS only — the Android app has no feature that uses these records yet, so from 2026-10-05 it no longer asks for those permissions. ⑧ Active calories are read on iOS only (item 21 in §3) — the Android app has no feature that shows this value on screen, so from 2026-10-09 it no longer asks for that permission. On Android, intensity is sorted using steps, heart rate and workout records only. ⑨ Menstrual records are read on both platforms only if you turn on cycle and hormone context and consent (§3-C) — on Android this is item 12 in §3-A-1, and on iOS it is described in §3-C separately from the 24 types above. Contraception, pregnancy and menopausal status records are read on iOS only, because Health Connect has no such types (§3-C)
Reads raw heartbeat intervals and computes rMSSD in the app Reads the rMSSD the device maker computed Health Connect does not expose raw heartbeat intervals. Same name, different number
Writes 4 types to Apple Health (nap, caffeine, drinks, state of mind) Writes 1 type (nap) Health Connect has no data type for alcohol or state of mind, and caffeine writing has not been added yet
Reads date of birth and sex from the Apple Health profile Does not read them from the health app. The app asks you once, where the value is actually used, and stores the answer on your device only Health Connect has no profile fields such as date of birth or sex
Cannot tell whether read access was granted, so it infers from arriving data The app knows the actual permission state Health Connect reports it. The connection screen states a fact instead of a guess

Items that cannot be read are left out and the remaining ones re-normalised. So the same person can get different scores on an iPhone and on an Android phone. Neither platform is systematically more generous — the direction depends on which items happened to be readable that day. The score detail screen shows what the app is actually looking at.

3-A-5. Revoking access, and deletion

You can revoke access at any time: device Settings → Security & privacy → Health Connect (or the Health Connect app, depending on your device) → App permissions → Daily Readiness.

Deleting the app deletes the derived data on your device. The original data in Health Connect is not affected — manage it in Health Connect itself.

3-B. Today's Saju reading (on by default, can be turned off in Settings)

Today's Saju reading is on by default. If your date of birth is available, the app calculates your Saju (the Four Pillars) from it — and from your time of birth, if you entered it yourself — on your device and shows today's reading as a card. Without a date of birth nothing is calculated. If you turn it off in Settings > Today's Saju reading, none of the following calculation happens. It has no effect on the readiness score, condition level or workout recommendation.

What is used Your date of birth (§2-2 — already used to work out your age), plus the time of birth (hour and minute) and country and time zone of birth, used only if you enter them yourself. You can answer “don't know” for the time, and it is then calculated without it. You choose the country yourself; we do not request location permission or look up your location
Where it is calculated On your device only. The calculation uses no network, and the reading is built from fixed wording shipped in the app. Nothing is sent to a server or an AI service to write or polish Saju text
What stays on the device Time, country and time zone of birth and whether the feature is on; a record of when we suggested the feature (so we do not keep asking); and the day's Saju entry in your feed (pillar values calculated from your date of birth — six or eight integers). The home screen widget receives one line of today's reading (§12)
Does it leave the device No. Even with error reports on, only the fact that you changed the Saju setting is recorded — never your date of birth, time or country of birth, or the Saju characters
Turning it off or clearing it You can turn it off or clear it in Settings → Today's Saju reading. Turning it off deletes the pillar values of past Saju entries; clearing it also deletes the time, country and time zone of birth. Your date of birth stays, because it is used for the age-based activity range

3-C. Cycle and hormone context (optional, off by default)

Cycle & hormone context in Settings has five separate items (menstrual cycle · hormonal contraception or hormone therapy · pregnancy · after birth · around menopause). Each is independent and all are off by default. If you leave them off, none of the following happens — nothing is read and nothing is stored. When you turn one on, we ask for separate in-app consent for that item (we do not bundle it with the health permission screen) and record the time of that consent and the policy version on your device.

What we use Dates only for the items you turn on — the start and end of a cycle, the day hormonal contraception or therapy started or stopped, and the start of pregnancy, of the period after birth, or of menopause. We do not read flow, type, or test results. We do not calculate or show fertile windows, ovulation days, the chance of pregnancy, or whether a cycle is "abnormal"
Where we read it Apple Health on iPhone: menstrual records (the date and the "cycle start" mark only) · contraception records (start and end dates only — the method is not kept) · pregnancy records (start and end dates only) · menopausal status records (iOS 27 or later — dates only; whether a record says perimenopause or menopause is looked at only to pick the dates and is not kept). Pregnancy and menopausal status records are read only if you turn on "pregnancy" or "around menopause", and if Health has no such record we use the date you enter yourself. Android Health Connect: menstruation periods and menstrual records (dates only). Health Connect has no contraception, hormone therapy, pregnancy or menopause records, so for those we use only dates you enter yourself. On both devices, hormone therapy dates come only from what you enter. We ask for read access after you turn an item on and agree, and only for that item
Where it is calculated On your device only. No network is used, and nothing is sent to a server or an AI service to put this context into words
What stays on the device The consent record for each item you turned on (item, time, policy version), the dates for those items, and values derived from those dates. Answers you type yourself, such as "I trained hard before pregnancy", also stay on the device (§12)
Does it leave the device No. Even with error reports on, we do not send the fact that you turned this on — unlike other settings, not even an on/off marker is recorded. This context also never appears in the home screen widget, on the watch, in notifications, or in shared images
Turning it off or deleting You can turn each item off on its own. Turning it off deletes that item's consent record, its dates, and everything derived from them, and the days that were adjusted are calculated again without this context. The heart rate, sleep, and temperature records we already read are not part of this item, so they stay. The app cannot take back read access you granted in Health (Android: Health Connect), so Settings shows you where to turn it off (§11)

4. Notifications

On Android, too, every notification is a local notification created on your device. Android sends two today. The morning reminder comes once a day at the time you choose (10 am by default) and suggests checking today's condition and workout — if you've already seen today's score in the app, it starts the next day. You change the time in the app's settings and turn it off from your phone's notification settings. The bedtime reminder fires only if you accept the app's one-time offer or turn it on in settings. On Android 13 and later the app asks for notification permission; if you don't allow it, the app keeps working as before (you just won't see the notifications). No push server or push token is used. The home screen widget draws whatever the app last computed and stored on the device, so seeing the widget update does not mean a notification is coming.

5. Logs created automatically

When you use account features (sign-up, sign-in, password reset, account deletion), the server platform records the logs below automatically. We do not gather these deliberately — the authentication service writes them itself, and we consult them only to diagnose failures, to check for abuse, and to tell which country you signed up from.

Log What it contains Retention
Authentication audit log Event type (sign-up, sign-in, reset request…), email address, timestamp, user agent (app and OS version), IP address 7 days (the log retention period of our Supabase Pro plan)
Sign-in session record IP address, user agent (app and OS version), sign-in and refresh times While you stay signed in. Signing out deletes that device's record right away, and deleting your account deletes all of them. If you delete the app without signing out, the record stays until you delete your account
API request log Request path, method, response code, timestamp, IP address, user agent — kept not only for account features but also when error reports, the minimal usage signal, or app ratings and feedback are sent 7 days (same)
We use the IP address of your sign-up to tell which country you signed up from. That lookup happens on our own server, and we do not send your IP address to another company in order to do it. We do not resolve your city or anything finer — all that is kept is the country. The IP address used for this is the one in the “Sign-in session record” in the table above, and that record stays on the server for as long as you stay signed in. Apart from the records in the table above, we do not store your raw IP address anywhere. The country is used only to notify us of a new sign-up (§7); it is not stored as part of your account.

No health data appears in these logs — it never reaches the server, so it cannot be logged.

6. Tracking, advertising, third parties

7. Processors

We rely on the following processors to provide and operate account features.

Processor Service Data handled Location
Supabase, Inc. Account authentication, database hosting, sending authentication email Email address, password hash, display language, account identifier, the logs in §5 AWS Seoul region (ap-northeast-2)
Amazon Web Services, Inc. Cloud infrastructure underneath the above Same Seoul region
Slack Technologies, LLC Receiving our operational notification of a new sign-up, and receiving app ratings and feedback (a private channel only we can see) Email address, time of sign-up, the country you signed up from, sign-up method (Apple, Google, email…), app and OS version / rating, what you wrote, reply-to email address (only if you typed it in), platform, app version, build number, display language, OS version United States

8. International transfers

9. Retention and deletion

Data Retention How it is destroyed
Account details (email, password hash, language, identifier) For as long as the account exists; deleted immediately on request Removed from the database at once. It may persist in operational backups for up to 7 days and disappears as those backups expire
Authentication and API logs 7 days Deleted automatically by the platform
Sign-in session record (IP address, user agent, sign-in times) While you stay signed in Signing out deletes that device's record right away. If you did not sign out, it is deleted together with your account. It may remain in operational backups for up to 7 days (§5)
Error reports — screens and actions 90 days Deleted automatically each day
Error reports — errors and crashes 180 days Deleted automatically each day (we need this long to see whether the same fault comes back a season later)
Error reports — install identifier and device details 400 days after last activity Deleted automatically each day. You can also delete them yourself in Settings (§2-3)
Error reports — deletion ledger (hash of a deleted install identifier, time of deletion, verification value) Kept Not deleted. It cannot be turned back into the original identifier and contains no account, IP address, record content or secret (§2-3)
Error reports — request counts (an irreversible value derived from the IP address) 1 day The IP address itself is not stored in these counts. Counts older than one day are deleted while new requests are processed. The server platform's API request log keeps the IP address for 7 days (§5)
Minimal usage signal — per-installation records (install identifier and date) 90 days Deleted automatically each day. You can also delete them yourself in Settings (§11)
Minimal usage signal — daily totals (no identifier) Kept indefinitely Not deleted. They hold only how many installations there were per date, platform and build, never which installation opened the app
App ratings and feedback (rating, what you wrote, the email address you typed in) 2 years Deleted automatically each day. Tell us what you sent and we will delete it sooner (§11)
App ratings and feedback — request tally (IP address irreversibly transformed) 7 days The raw IP address is never stored in this tally. A tally older than seven days is deleted while handling a new request. The server platform's API request log keeps the IP address for 7 days (§5)
The on-device list of days you opened the app, and your rating history (used to decide when to show the rating card) 120 days Only dates — never the time of day or how many times. Deleted automatically on the device and never sent to a server
Derived health data on your device Until you remove it Deleted when you delete the app
Time-zone offset log (for automatic travel/jet-lag detection) 28 days Used only to automatically detect travel or jet lag; entries older than 28 days are deleted automatically on your device. We do not store city names or location, and turning it off in Settings deletes it immediately
Per-night detailed metric records on your device (each night's derived metric values and that night's stage assessment) 180 days Each time the app loads your health data, records for nights older than 180 days are deleted automatically on the device. This does not apply to the other derived data in the row above, such as readiness scores and sleep records
Notes on your day Until you delete them You can delete them any time in Settings, and they go when the app does
Original data in Apple Health Not managed by us Managed by you in the Apple Health app

10. How to delete your account

In the app: Settings → Account → Delete account → confirm.

The app calls a server function, which verifies from your session token that you are the account holder and then deletes the account. When the account goes, your profile row (email and language) is deleted along with it by a database constraint. Afterwards you may sign up again with the same email address; the old account's data is not recoverable.

By email: write to contact@apochopo.com. Please send it from the address you signed up with so we can verify it is you.

Health data on your device is independent of your account. Deleting the account leaves device data in place; deleting the app removes device data but leaves the account. To remove both, delete the account and then delete the app. Original data in Apple Health is unaffected either way.

11. Your rights and how to exercise them

You may at any time ask to see, correct, delete, or stop the processing of your personal data.

What you want How
See what is stored Settings → Account shows your email address and display language. For a copy of anything else, ask us by email
Change display language Settings → Language
Change password Sign-in screen → Forgot your password → reset via the emailed link
Change email address By email (in-app change is not yet available)
Delete account and personal data §10
Cut off health data access iOS Settings → Privacy & Security → Health → Daily Readiness, and revoke permission
Stop notifications iOS Settings → Notifications → Daily Readiness, or in the app's settings
Delete what has been sent (error reports and the minimal usage signal) Settings → Error reports → “Delete what was sent”. One action deletes both; anything sent afterwards uses a new identifier
Delete a rating or feedback you sent Write to contact@apochopo.com. Because you can send it without an account we cannot tell who sent it, so tell us what you sent (part of what you wrote and roughly when) and we will find it and delete it

12. Storage used on your device

Storage Contents
App database (app-private area) The derived health values in §3, app settings, your morning check-ins (if you answered), your state-of-mind entries (if you answered — one of five steps per date and window), notes on your day (if you ticked any)
One file in the app group container Today's score, level and suggestion text for the widget, plus one line of today's reading if Today's Saju reading is on
iOS Keychain Sign-in session token; the error report install identifier and secret (§2-3). Keychain items may remain after the app is deleted
Device settings store Display language and similar display preferences, the install identifier for the minimal usage signal (§2-4), and the list of days you opened the app with your rating history (§2-5)

All of these sit inside the iOS app sandbox, so no other app can read them, and iOS file protection encrypts them when your device has a passcode or Face ID set. Deleting the app deletes the app database, the app group file and the stored settings.

Storage works differently on Android.

Storage Contents
App-private database (SQLite) The derived values and summaries described in §3-A — daily metrics, personal baselines, workout records, daily readiness scores, feed entries, sync position markers, your morning check-ins (if you answered — how refreshed you felt, afternoon sleepiness and your lingering-fatigue answer for each date, and whether you skipped), your state-of-mind entries (if you answered — one of five steps per date and window), notes on your day (if you ticked any — per date: the items you ticked, «none of these», or that you skipped)
App-private settings file Display language, date of birth and sex (if you entered them), your target bedtime (if you set one), your usual weekly pattern (if you set one), your «How you get around» choices (if you set them), your error report choice, flags so we do not ask you the same thing twice, and the list of days you opened the app with your rating history (§2-5)
The same database — app usage (only if you turned usage access on) One row per day of totals: the seconds and sessions during which the screen was on and unlocked, how many of those a shopping app was in front, the measurement quality, the time zone, and the interval actually measured. No package names, no screen class names, no raw events (§13)
The same database — nap log (only if you entered a nap) The start and end time and time zone of naps you entered, and the progress record of each save (whether it was written to Health Connect, the record ID returned, the affected dates, the readiness score before and after). Sleep records read from Health Connect are not kept here, and entries are deleted automatically after 180 days (§3-A-2)

13. Security measures

Only measures actually in place are listed.

Additionally, on Android

Android — app usage (digital habits)

Besides the Health Connect permissions above, the Android build declares one more: usage access (android.permission.PACKAGE_USAGE_STATS). It is not a runtime permission — you have to turn it on yourself, in the system Settings screen called "Usage access" — and the app only checks whether it is on. If you do not turn it on, none of what follows happens.

What is read The moments an app comes to the foreground and leaves it, the moments the screen turns on and off, the moments the device locks and unlocks, and the moments it shuts down and starts up. Those events also carry the app's package name and the screen (Activity) class name
What is stored One row per day, in the app-private database on your device only. That row holds the date, the measurement quality, the seconds and the number of sessions during which the screen was on and unlocked, how many of those seconds and sessions a shopping app was in front, the version of the shopping-app list, the version of this layer, the time zone, whether the day is closed, the start and end of the interval actually measured, and when it was computed
What is not stored Package names, screen (Activity) class names and raw events are not stored — the table has no columns for them at all, and a test reads the table definition to keep it that way. The events exist only in memory while the daily totals are counted, and there is no logging path that could write them down
How long it is kept Until you delete it. The window used to judge your stage is the seven days up to yesterday, but older daily rows are kept so we can show you a trend, and the app does not delete them on its own
Does it leave the device No. The Android build declares no internet permission at all (first item above) and automatic backup of app data is off
Can you delete it Yes. Deleting from the digital-habits detail screen removes the daily rows, the stage-decision journal and the related settings in one action. If you revoke usage access in system Settings, the app deletes those records by itself. Uninstalling the app removes them too

One thing does keep package names. For the apps you yourself switched on or off in the shopping-app list, the package name stays in the app-private settings file, because that is your choice (§12). It does not leave the device either, and the deletion above removes it as well.

iOS does not have this feature. The iOS build does not read app usage — we are waiting on Apple's Screen Time entitlement — so this section applies to Android only.

14. Responding to a breach

15. Children under 14

16. Medical notice

Daily Readiness is not a medical device and does not diagnose, treat or prevent any disease. The scores and guidance it shows are information to help you decide how hard to train and when to rest — they are not medical determinations. For health decisions, consult a healthcare professional.

17. Contact

18. Changes to this policy

Version Effective Main changes
v1 2026-08-14 First draft
v2 2026-08-18 Rewritten against the actual implementation. Added display language; new sections on automatic logs, retention, processors, international transfers, exercising your rights, security measures, breach response and children. Published in 4 languages
v3 2026-08-20 Covers the new self-entered nap. §3 and §13 now state that the app writes to Apple Health for that one nap (a sleep entry) only, correcting the earlier "never writes" wording
v4 2026-08-20 Adds six everyday entry types to what is read (breathing disturbances during sleep, alcohol, caffeine, mindful minutes, blood pressure, blood glucose). Because the set of types read has grown, §3's list and the on-device storage description were updated together
v5 2026-08-30 Error reports (opt-in) introduced. The app can now send screens, actions and error details to our server when it freezes or fails, so §1, §2-3, §6, §9 and §11 were updated along with the privacy manifest shown on the App Store. Off by default; even when on, no health values and no score are sent. Announced in-app seven days before it takes effect
v6 2026-08-30 More is now stored on the device. Time spent in daylight and body composition (weight, lean body mass, body fat percentage) were added to what is read, and biological sex and date of birth are now read from the Apple Health profile — or asked for, if they are not there — so §2-2 and §3 were updated. Nothing changed about what is transmitted: every new value stays on the device and none of it appears in error reports. Takes effect on the same day as v5 (revised 2026-08-27, before v5 took effect)
v7 2026-09-11 Step count was added to what the app reads, and what the app writes to Apple Health grew from one type (naps) to three (naps, caffeine, drinks). Step count is used so that walking you never logged as a workout still counts toward this week's activity, which means it does enter the score (§3, item 9). Caffeine and drinks are written only when you enter them yourself and tap save, and write access is asked for one type at a time (§3, §13). Neither is ever sent to a server.
This entry was broadened before it took effect. As revised on 2026-08-28 it covered step count alone and was due to take effect on 2026-09-06. On 2026-09-03, before that date, writing caffeine and drinks was added (the direct-entry feature on the Today tab), so it was folded into the same v7 and the effective date moved to 2026-09-11 — leaving it at 09-06 would have given only three days' notice, which would break the seven days §18 promises (revised 2026-09-03)
v8 2026-09-21 If you turn on Days with none in Settings, the app may now write a zero to Apple Health without you tapping save. Until this revision, every write this app made was the result of a person tapping save. The switch is off by default; it applies only to days after you turn it on, only to days with no caffeine or drink entry at all, and the only value it writes is zero (§3). Nothing is sent to a server.
The same revision also rewrites how §2-2, §3 and §13 describe when write access is asked for. Since 2026-09-11 the app asks for write access to naps, caffeine and drinks together with read access during first-time setup. Until now this document described only the other path — asking for a single type the first time you try to save that kind of entry — which is still exactly what happens on devices that finished setup before this revision, so both cases are now written out. The number and kinds of types asked for are unchanged (three), and no new permission is requested
v9 2026-09-16 Revised in one go for 1.3.0. ① Android support: the app reads from Health Connect rather than Apple Health; the 11 read types, 1 write type (a nap you entered) and 1 special permission (historical reads) are set out in the new §3-A. Naps you enter stay in an on-device log that is deleted automatically after 180 days, and can be undone one at a time. App usage on Android (digital habits, usage access permission) is described in §13. The Android build has no account, no error reporting and no internet permission. ② Built-in pedometer on iOS: when steps are not available from the Health app, the app counts steps on the device with the Motion & Fitness permission and shows them — nothing is stored or sent (§3). ③ How error reports identify an installation: the install identifier is paired with a secret only this installation holds, which protects sending and deleting (the server keeps only a hash); after deletion an irreversible deletion ledger remains; and the IP address is used, never stored as is, for one day of request counting (§2-3, §9, §12). The content sent in error reports has not grown
This version took effect on the day it was published (2026-09-16), and changes how changes are announced from this version on. Other changes are announced in the app when we make them and take effect on the day they are published (start of §18). Until now this document promised notice 7 days before other changes took effect; this version was not given that period — an operator's judgement for a very early stage with very few users. The content of v8 (Days with none), which was due to take effect on 2026-09-21, is included unchanged in this version and takes effect with it. v8 was never published on the web and never took effect on its own
Added 2026-09-16 — ④ Today's Saju reading (optional, off by default): if you turn it on, the app calculates Saju on your device from your date of birth and your time and country of birth. Nothing is sent to a server or an AI service, and turning it off deletes the pillar values of past Saju entries (§2-2, §3-B, §12).
Added 2026-09-17 — ⑤ Target bedtime (optional): if you set one, it is stored on your device only and used only to check whether a nap close to that time affected that night's sleep. It is not sent to a server (§2-2, §12).
Changed 2026-09-16 — on Android the app no longer requests background reads. It does not read Health Connect while it is not open, and the only special permission is reading historical data (§3-A-3, §13).
Changed 2026-09-17 — per-night detailed metric records are kept on your device for 180 days, and records for older nights are deleted automatically on the device. Retention of other derived data is unchanged (§9).
Added 2026-09-18 — ⑦ Morning check-in (optional): if you answer how refreshed you felt on waking (1–5) and how sleepy you were in the afternoon, the answers are stored on your device only and used to show your past answers. They are never sent to a server (§2-2, §12).
Added 2026-09-18 — ⑦ Morning check-in: only when you tap 'Export as file' yourself, the app creates a file containing just your answers (how refreshed you felt, afternoon sleepiness, and whether you skipped) numbered by day instead of dated, plus the type of device, and hands it to the app you choose (Files, Mail, etc.). The app never sends it on its own; once handed over, the file is kept according to that app's practices.
Added 2026-10-03 — ⑧ Notes on your day (optional): we store only the items you tick and the date (travel or time-zone change, vaccination, a change in your medicines, altitude, shift work, feeling unwell and so on) on your device, and use them only to lower the confidence of that day's metrics or leave that night out of your usual baseline. We never ask for medicine names, doses or vaccine types, and nothing is sent to a server (§2-2, §9, §12).
Added 2026-09-19 — ⑨ Automatic travel and jet-lag detection: if your device's time zone changes by two hours or more, the app detects travel or jet lag automatically. It keeps only the time-zone offset from UTC (not city names) for the last 28 days, on your device, never sent to a server, and you can turn it off any time in Settings (§2-2, §9).
Added 2026-09-28 — ⑩ Irregular heart rhythm notifications and atrial fibrillation history (one more item we read): used only to leave the heart rate variability of a night your Apple Watch flagged out of the recovery reading. The value for that night is kept and no points are taken away because of these records. The app makes no judgement of its own from them (item 18 in §3).
Added 2026-10-03 — ⑥ Usual weekly pattern (optional): if you set a working/day-off pattern, whether you wake without an alarm on days off, and whether you work shifts, it is stored on your device only and used only to compare your sleep on days off with working days. It applies retroactively to past nights. It is not sent to a server (§2-2, §12).
v10 2026-09-29 A usage-statistics purpose and a minimal usage signal were added. ① New purpose: the error reports you opted into are also used to see which features are used and which are not, so that we can fix the app — nothing new is sent (§2-3). ② New minimal usage signal (iOS build only): once a day we send only “this installation opened the app today” — the install identifier, the date, the platform, the app version and the build number, and nothing else. It is sent without asking and there is no setting to turn it off: you can delete what has been sent, but to stop it you have to delete the app (§2-4, §11). It carries no health values, no daily score and no record of screens, and it is never joined to your account or to your error reports. ③ The country you signed up from: we resolve the country — and only the country — from your sign-up IP address on our own server, without sending that address to another company (§5). ④ One more processor — Slack: to tell us about a new sign-up we send the email address, the time and the country to a private channel in the United States (§7, §8).
This version took effect on the day it was published (2026-09-29), with no 30-day notice period. §18 promises 30 days' notice before a change that is to your disadvantage or otherwise significant, and we consider this revision to be one — it adds something that is sent without asking and cannot be switched off. We gave no notice period anyway because the app is still pre-launch and almost nobody uses it yet (13 sign-ups as of 2026-09-28 — 5 of them our own accounts — and 2 installations with error reporting switched on). That is an operator's judgement, and v9 skipped its 7-day period for the same reason (the row above). Once the app has real users, we will apply this clause again. The app build that sends the signal, and the sign-up notification, ship after this publication — until then the only thing transmitted is the error reports of §2-3.
v11 2026-10-01 Two more items are read (18 → 20 types). ① High and low heart rate notifications and ② notifications about breathing during sleep — both are a record of notifications your Apple Watch sent, and they have a single use: if such a notification is on record within the last seven days, a single line of guidance appears at the bottom of the related metric detail — "If these notifications continue, consider talking it over with a healthcare professional" (items 19–20 in §3). Your score does not change — there is no path in the app by which these two enter the score or the baselines. We do not count how many notifications there were, we do not read the values attached to them (such as the threshold heart rate you chose on the watch), and once you dismiss the line it does not return until a new notification arrives. The fact that you dismissed it stays on the device (the existing "marker so we do not ask again" row in §12). We do not read electrocardiograms (ECG) — those are recordings you took yourself and have already seen the result of, and that permission opens not only the classification but the voltage waveform. The Android build is unchanged: Health Connect has no matching record, so this line does not appear there.
This version takes effect on the day it is published (2026-10-01). Because it is a change that grows what we read, we treated it as an "other change" under §18 and made it effective on publication — nothing more is sent to a server, both items are allowed or refused individually on Apple Health's permission screen, and if you refuse, only the line of guidance is missing; the app works exactly as before.
v12 2026-10-02 More items are read — active calories (iOS 20 → 21 types · Android 11 → 13 types). ⑥ Reading active calories (and weight on Android): used only to sort active time by intensity; does not change your score or stage and never leaves your device (§3 item 21, §3-A-1 items 12–13). The calorie values themselves are not stored — only the result, minutes of activity by intensity. On iOS, weight was already read as part of body composition (§3 item 17), so the only new item is active energy; on Android, turning calories into intensity needs your weight, so weight is read with it.
This version takes effect on the day it is posted (2026-10-02). For the same reasons as v11 we treat it as an «other change» under §18 — nothing more is sent to a server, you decide on each item separately in the Apple Health or Health Connect permission screen, and the app works as before if you say no (stretches whose intensity is unknown simply stay «unknown»).
Added 2026-10-01 (Android) — we now also read lean body mass and body fat percentage (weight was already being read for active calories above, and the same value is now also shown as a reference on the workout screen — 15 Health Connect read types, items 13–15 in §3-A-1). iOS has read these since v6, so there is no new use: a reference on the workout screen and one feed card on a day you measure — the score does not change and nothing is sent to a server.
We also read stand hours (iOS 21 → 22 types) — the hour-by-hour stand record your Apple Watch keeps (item 22 in §3) is used only to count the waking hours in which movement was confirmed. It does not change your score or stage; the records themselves are not stored, only the number of hours for each day is kept on your device. Nothing is sent to a server, and you can leave just this item off on the Apple Health permission screen. Android is unchanged — Health Connect has no such record, so hours are counted from hourly steps.
Added 2026-10-02 — ⑦ App ratings and feedback (only when you send them yourself): if you give a star rating in the app or send us feedback, your rating, what you wrote, the reply-to address you typed in (optional) and your platform, app version, build number, display language and OS version are sent to our server and forwarded to a private Slack channel in the United States that only we read, where they are kept for two years (§2-5, §7, §8, §9, §11). They are not tied to your account, your error reports or the minimal usage signal, they carry no health values and no daily score, and the device model is not sent. The list of days you opened the app and your rating history — used to decide when to show the rating card — stay on your device (§12). The Android build sends none of this to a server: feedback is sent by your own mail app and the app does not transmit it (point 6 of §1). Because nothing is created unless you choose to send it, we treated this as an “other change” under §18 and made it effective on the day of publication. The app build that carries this feature ships after this publication.
v13 2026-10-04 The morning check-in export now carries more — that day's wrist-temperature results. ⑦ Morning check-in export: the file also carries that day's wrist-temperature results — how far above your usual it ran, smoothed over three days; how many days were measured and how many ran in a row; whether another signal was present alongside it; what the calculation concluded; and how far that day sat from your usual. The temperature readings themselves (how many degrees) and heart-rate intervals are not included — everything in the file is a value produced by calculation. If more than one device supplied temperature that day, we pick neither and write «multiple». These values do not change your readiness score or stage. The app never sends it on its own; once handed over, the file is kept according to that app's practices (§2-2).
This version takes effect on the day it is published (2026-10-04). We treated it as an «other change» under §18: not one item more leaves your device, the file is created only when you tap 'Export as file' yourself, and nothing happens if you don't.
v14 2026-10-04 More items are read — wheelchair pushes (iOS 23 → 24 types · Android 15 → 16 types) and the «uses a wheelchair» characteristic in your Apple Health profile (2 → 3 characteristics). They are used only to read the daily activity of people who get around by wheelchair as pushes instead of steps (§3 item 24, the characteristics list, and §3-A-1 item 16). Pushes are never converted into a step count — so there is no path for them into the activity score, a low push count never takes points away, and in that case your activity score rests only on the workouts you record. On iOS the app reads that fact only if your Health app says «wheelchair user»; if it is not set there, nothing is read and your activity is read as steps, exactly as before. Android has no «uses a wheelchair» item, so it reads pushes only on days that have push records.
This version takes effect on the day it is posted (2026-10-04). We treat it as an «other change» under §18 — nothing more is sent to a server, you decide on each item separately in the Apple Health or Health Connect permission screen, and the app works as before if you say no (your activity is read as steps).
v15 2026-10-05 Fewer items are read on Android (16 → 13 types) — we no longer ask for blood pressure, blood glucose or nutrition (caffeine) records. The Android app had no feature that actually used these three records, yet it was asking for access to them. So that we do not ask for access to data we do not use, we removed the three permissions from the app (§3-A-1 · §3-A-4). Even if you had already allowed them, the app does not read these records — you can withdraw the permission in Health Connect's app permissions screen. The iOS app has not changed.
This version takes effect on the day it is posted (2026-10-05). It only reduces what is read, so we treat it as an «other change» under §18 — nothing new is read and nothing is sent to a server.
v16 2026-10-05 We corrected what we say about the IP address kept in sign-in session records. Up to the previous version, §5 said “The IP address itself is stored nowhere beyond the logs in the table above.” In fact, the sign-in session record that our authentication service (Supabase) keeps to hold you signed in contained your IP address for as long as you stayed signed in, and it is also the value we read to tell which country you signed up from. We now describe this record in §2-1, §5 and §9, and also state that the API request log contains the IP address and user agent. Where error reports, the minimal usage signal and app ratings and feedback say the raw IP address is not stored, that refers to the request tally each feature keeps itself — we added that the same requests stay in the server platform's API request log, with the IP address, for 7 days (§2-3, §2-4, §2-5, §9). Signing out deletes that device's record, and deleting your account deletes all of them. This applies only to the account feature of the iOS app. Nothing new is collected or sent — the document was saying less than what was already happening, and this corrects it.
This version takes effect on the day it is published (2026-10-05). As a factual correction, we treated it as an “other change” under §18.
v17 2026-10-06 The app's settings now have «How you get around» — «I get around by wheelchair» and «I walk slowly». If you get around by wheelchair we read your daily activity as pushes instead of steps, and if you walk slowly we leave your step count as it is and only lower our confidence in gauging your activity from it (§2-2 · §3). Your choice in the app comes before the defaults — iOS looks at the «wheelchair user» entry in your Health app profile, and Android at whether the day has push records, only when you have not made a choice (§3-A-1 · §3-A-4). Both choices are stored on your device only (§12) and do not change your readiness score or stage. No new health data is read.
This version takes effect on the day it is posted (2026-10-06). Nothing new is read and nothing is sent to a server, so we treat it as an «other change» under §18.
v18 2026-10-09 Fewer items are read on Android (13 → 12 types) — we no longer ask for active calories burned. The Android app used active calories only as a supporting value to sort active time by intensity and never showed it on screen. So that we do not ask for access to data whose use you cannot see, we removed this permission from the app (§3-A-1 · §3-A-4). On Android, intensity is now sorted using steps, heart rate and workout records only. Weight is still read, but its only use is the body-composition reference on your workout screen. Even if you had already allowed it, the app does not read this record — you can withdraw the permission in Health Connect's app permissions screen. The iOS app has not changed (active energy is still read on iOS, item 21 in §3).
This version takes effect on the day it is posted (2026-10-09). It only reduces what is read, so we treat it as an «other change» under §18 — nothing new is read and nothing is sent to a server.
v19 2026-10-10 The morning check-in has one follow-up question — whether fatigue from exercise is lingering. ⑦ Morning check-in: if you answer the question asking whether fatigue from exercise is still lingering («Mostly yes» · «No» · or that you skipped it), that answer is also stored on your device only. It is not used in the score and is never sent to a server (§2-2, §12). The question appears only on the mornings it applies to, not every morning. If you tap 'Export as file', this answer is included in the file too — only for days the question was shown, and the app never sends it by itself. No new health data is read.
This version takes effect on the day it is posted (2026-10-10). Nothing new is read or sent to a server — one more answer is stored on your device — so we treat it as an «other change» under §18.
v20 2026-10-10 We corrected how this policy describes notifications on Android. Up to the previous version, §4 and §13 said that Android has no notifications and that the app requests no notification permission, but since 2026-10-04 the Android app also sends a bedtime reminder — a local notification created on your device that fires only if you accept the app's one-time offer or turn it on in settings. On Android 13 and later the app asks for notification permission at that point, and it keeps working if you don't allow it (§4·§13). The notification is created on your device and nothing is sent to a server. Nothing new is read, collected or sent — we corrected a description that no longer matched what the app already did.
This version takes effect on the day it is posted (2026-10-10). It corrects a factual description, so we treat it as an «other change» under §18.
v21 2026-10-10 Android now has a morning reminder. Once a day at the time you choose (10 am by default), a local notification suggests checking today's condition and workout. You change the time in the app's settings and can turn it off from your phone's notification settings. On Android 13 and later the app asks once for notification permission after your first score; if you don't allow it, the app keeps working as before (§4, §13). Notifications are created on the device and nothing is sent to a server. Nothing new is read, collected or sent.
This version takes effect on the day it is published (2026-10-10). Because nothing collected changes, we treated it as an "other change" under §18.
v22 2026-10-13 Settings now has «Cycle & hormone context» (optional, off by default). Its five items (menstrual cycle · hormonal contraception or hormone therapy · pregnancy · after birth · around menopause) each start off, and turning one on asks for separate in-app consent for that item. We use only the dates of the items you turn on, on your device, and never send them off it (§3-C). If you turn on the menstrual cycle item, your morning check-in adds one question about how uncomfortable your body feels today; that answer is also stored only on your device and is deleted when you turn the item off. On Android we read menstrual records from Health Connect only after you turn on the menstrual cycle item and consent — Android reads go from 12 to 13 types (item 13 in §3-A-1). If you leave these off, nothing changes.
This version takes effect on the day it is published (2026-10-13). What is newly read and stored is off by default and only happens for people who turn it on and give separate consent.
v23 2026-10-15 On iPhone, if you turn on "pregnancy" or "around menopause" in «Cycle & hormone context», we read the dates of the pregnancy records and menopausal status records (iOS 27 or later) you keep in Apple Health. Before, both devices used only dates you entered yourself. We read dates only, never send them off your device, and delete them when you turn the item off (§3-C). We ask for Health access only after you turn the item on and consent. Android does not change — Health Connect has no pregnancy or menopause records. If you leave these off, nothing changes.
This version takes effect on the day it is published (2026-10-15). What is newly read is off by default and only happens for people who turn it on and give separate consent.
v24 2026-10-15 ④ Today's Saju reading is now on by default. If your date of birth is available, the app calculates your Saju on your device and shows today's reading; if you would rather not, you can turn it off in Settings (turning it off deletes past pillar values). We collect nothing new, and your time and country of birth are used only if you enter them yourself. Nothing is sent to a server or an AI service (§2-2, §3-B).
v25 2026-10-15 ⑤ The service name changed from “Today's Workout” to “Daily Readiness”. Only the name changed; the information we handle, why, and for how long stay the same.
v26 2026-10-24 Records of the moment the app suddenly closed or froze (crashes and freezes) are now sent by default. Until now they were sent only if you had turned error reports on. What is sent is only the error kind and code, the call order of the code that was running at that moment, app and device version, and the install identifier; it never includes which screens you opened or what you tapped, the names of your recent actions, health readings or your daily score. You can turn this off in Settings → Error reports → “Send crash and freeze reports”; sending stops immediately and anything not yet sent is deleted. Screen and action records and all other error reports are still sent only if you turn them on. Devices that answered “Not now” to error reports will also send crash and freeze records (§1, §2-3, §6).
This version takes effect on the day it is published (2026-10-24). Because it adds something that is sent without asking, we considered it a change that §18 says we announce 30 days ahead, but we did not set that period — as of 2026-10-18 only 3 of 55 iOS installs showed us their crashes, so we learned a day late that the app was closing right after launch (operator's judgement, the same reason as v10).
v27 2026-10-26 Android reads one more item — cardio fitness (estimated VO₂ max; Android 13 → 14 types). iOS already read it (item 23 in §3). On Android, too, we read the value your watch estimated and wrote to Health Connect and show it only in the «Cardio fitness» section of the activity detail (item 14 in §3-A-1, §3-A-4). The app does not measure it, it does not change your readiness score or stage, and it never leaves your device. The iOS version is unchanged.
This version takes effect on the day it is posted (2026-10-26). For the same reason as v14 we treated it as an «other change» under §18 — nothing more goes to our servers, you decide item by item on the Health Connect permission screen, and the app keeps working if you do not allow it (the cardio fitness section simply keeps saying it has not been read yet).
v28 2026-10-31 Two things now leave your device without us asking. ① The minimal usage signal gained one field (five → six fields). We send whether you allowed health permissions the first time you connected, as one of four things — you allowed them all · some were not allowed · we could not check · you postponed it (§2-4). Which item it was, your health values and your daily score are not included, and this field is deleted after 90 days. We are adding it because today we have no way to count — to fix the connect guidance we need to know how many people get no score because permissions were not allowed, and screen records exist only for people who turned error reports on, so as of 2026-10-27 we can see 8 of 94 installations. ② We now send the names of up to 20 screens and features you passed through just before the app closed (§2-3). Until now we sent them only if you had turned error reports on; from this version we send them even if you have not. The names can only come from a list the app fixed in advance, and nothing you typed, no health value and no daily score is sent, as before. Without knowing which screen the app died on we cannot fix that problem, and turning off Settings → Error reports → «Send crash and freeze reports» stops the record itself. The app version that carries both (1.6.0) ships after this posting.
This version takes effect on the day it is posted (2026-10-31), with no 30-day notice period. §18 promises 30 days' notice before changes that are unfavourable or important to you, and we judged both ① and ② to fall under it, since more leaves your device without us asking. We still set no period, for the same reason as v10 and v26 — few people use the app yet (94 installations as of 2026-10-27), and while we cannot tell how many people failed to connect, those people keep seeing no score. This is the operator's judgement, and we will apply the clause again once more people use the app.
v29 2026-11-03 The morning questions have been replaced by a single «How are you right now?», and the iPhone writes one more type to Apple Health. ① The three morning check-in questions (how refreshed you felt, afternoon sleepiness, the lingering-fatigue follow-up) no longer appear from 1.7.0. The answers you already gave remain as they are: you can view them under Settings → «Past morning check-ins» or export them to a file, and no new answers are added (§2-2, §12). If you want them gone, deleting the app removes them with it (§9, §11). ② Instead, the Today screen asks how you feel right now, one of five steps, once in the morning (05:00–13:00) and once in the afternoon (14:00–21:00) — no notifications are sent, and if you close it with the X we do not ask again in that window. The answer is stored on your device only and is not used in the readiness score or the condition level (§2-2). ③ On iPhone that answer is also written to Apple Health's «State of Mind» (3 → 4 write types; §3, §3-A-4, §13). We ask for that write permission for that one type, the first time you answer; if you decline, the answer stays on your device only. iOS 17 and earlier have no such type, so there the answer stays on the device. On Android, Health Connect has no mood type, so the answer is stored on the device only — no new Health Connect permission is requested (§3-A). Nothing new is sent to any server.
This version takes effect on the day it is posted (2026-11-03). Nothing more leaves your device (Apple Health is on the same device), the new entry exists only if you answer, and it is not used in the score — so we treat it as an «other change» under §18.
v30 2026-11-09 We added two features that work only on your device — nothing more is sent to our servers. ① Exercise rest days: dates on which you turn on «Make today a rest day from exercise» on the Today tab are stored on your device, so that day's share of the activity target becomes 0 and the day is left out of the 7-day completion rate (§2-2). You can delete them by turning that day's switch off or with «Delete all exercise rest days» in Settings. ② Active calories (iPhone): a value the app already read (item 21 in §3) is now shown on the activity detail screen as an estimate with how reliable it is. Nothing new is read, and your readiness score and stage do not change.
This version takes effect on the day it is posted (2026-11-09). Nothing more leaves your device, new records are kept only when you set them yourself, and they are not used for your readiness score, so this counts as an «other change» under §18.
v31 2026-11-17 Android reads fewer items (14 → 13 types) — it no longer asks to read wheelchair pushes. Google Play rejected this permission as a «minimum scope» violation on 2026-11-12. The «I get around by wheelchair» choice under «How you get around» in Settings stays — if you set it, your steps are read as «unknown» so your activity score rests on the workouts you record rather than your steps, a protection that does not depend on this permission. Even if you had already allowed it, the app no longer reads this record — you can withdraw that permission from the Health Connect app-permission screen. The iOS version is unchanged (wheelchair pushes are still read on iOS, item 24 in §3).
This version takes effect on the day it is posted (2026-11-17). This change only reduces what we read, so this counts as an «other change» under §18 — nothing new is read or sent to our servers.
v32 2026-11-19 We corrected what we said about people who get around by wheelchair. v14 and v31 said that if you declare «I get around by wheelchair», your activity score rests «only on the workouts you record». In fact, if your device has recorded steps, those steps also go into the activity score. It remains true that pushes are never converted into a step count, and that a low push or step count never takes points away. The app's calculation has not changed, and nothing new is read or sent.
This version takes effect on the day it is posted (2026-11-19). It corrects a wrong description, so this counts as an «other change» under §18 — nothing new is read or sent to our servers.