Halea keeps a patient's cycle data on her phone. When she wants you to see it, she generates a report there and hands it to you — AirDrop, email, print — as a PDF you can read in a minute and file like any other. Nothing passes through us; there is no account on either side.
Fixture data — no patient behind it — produced by the same code that produces the real thing.
Average and current cycle length, current phase and day, next predicted period with its confidence, estimated luteal phase — and one flag, when the record earns it.
Cycle length against FIGO 2018 (24–38 days; regularity as a ≤7–9-day spread by age; menses ≤8 days) and, under 18, ACOG Committee Opinion 651. The flag names the range and the source. It never names a cause.
The review the patient saw when each cycle closed: length against her running average, period length, the symptoms that clustered and on which day, mood and energy trend.
Cycle length over the last twelve cycles against the typical range; basal body temperature across the current cycle with the period, fertile window and detected shift; symptom frequency by cycle day across cycles.
Times logged and average severity per symptom over the window; mood mix; medication adherence as days marked taken against days with any log — no day is assumed.
Resting heart rate, HRV, sleep and temperature from Apple Health or Health Connect — read-only, and only when the patient turned it on.
No portal, no login, no consent form for a third party to hold her data, because no third party does. If she stops using Halea, there is nothing anywhere to close.
Core tracking is free, forever, with no account. The report is part of it. If you would like printed cards for the waiting room, or have a question about what the report can carry, write to us.