Moving your data

Your history is yours: this guide covers bringing it in, keeping your phone's health app up to date, and getting it all back out. Everything here happens on your device, at your initiative — lunarlog never reads your other accounts, and it never touches your health store before you turn the connection on. Once a profile is bound and you have run the first import yourself, the import keeps itself current in the background: still on your device, and the import itself never writes.

Bringing history in from Clue

lunarlog reads the export Clue emails you as a .zip, and turns it into a profile here. During setup, Restore from backup or Clue export starts this; later, Your data in Settings does — the picker explains both choices: Choose a file: a JSON backup this app exported (Settings > Your data > Export my data), or the .zip Clue emailed you. Your data is added to this device — nothing already here is ever deleted.

In Clue, request the export. Clue emails you a .zip together with a one-time password for it.
In lunarlog, choose the downloaded .zip. When the app asks, enter the password from Clue's email into Export password and continue with Open export.
The import creates its own profile — A new profile will be created for this import. — named from Profile name. Confirm with Import.

Anything already logged by hand in lunarlog is never overwritten by an import — your own entries stay yours; the import fills the gaps. A day Clue recorded that you have since re-logged here keeps your version.

From Apple Health or Health Connect

On iPhone (Apple Health) and Android (Health Connect), lunarlog can import flow and spotting history, decided by you, one profile per phone.

The switch lives in Settings under Health: Apple Health sync — on Android the same tile names Health Connect — asks which profile's data this phone may sync. The import itself runs when you tap it: Bring in all available menstrual flow and spotting.

What the import reads, and what it never does:

It reads the flow and spotting history the health store makes available, not a recent window — Imports everything the health store makes available, not a recent window — and, once you have run it once, keeps itself current in the background as long as it still has the permissions it needs for that.
It never overwrites a value you logged by hand, and it never writes its imports back into the health store — the app's own writes are excluded by source, so the two directions cannot loop.
The first import is yours to start in Settings. Once a profile is bound and you have run the first import yourself, the same import also keeps itself current in the background — Apple Health tells lunarlog when new data lands, and Android checks Health Connect on a schedule — under the same rules: it never prompts, never shows a screen, never writes, and it stops if you unbind the profile or revoke the health permission. The background part needs its permissions to stay on. On iPhone that means all of lunarlog's write permissions in the Health app, because Apple does not tell an app whether it may read. On Android it means reading Menstruation and Spotting, and access to data in the background, in Health Connect; writing can stay off.
One profile is bound to the phone's health connection at a time; unbinding later stops both directions and deletes nothing.

Keeping your phone's health app up to date

The same switch works in the other direction. For the one profile you choose there, what you log in lunarlog is also written to Apple Health on iPhone, or to Health Connect on Android, so the other health apps you use see the same history.

It is off until you choose a profile, and it only ever writes that one profile. Every other profile on the phone stays out of the health app.
Only days you log after it is on, and allowed to write, get an entry of their own. Nothing already in lunarlog is sent on its own. One thing reaches back on Android: once a day in a period is written, the first and last day you logged for that period are written with it, even if the period began earlier.
Flow and spotting are written on both. On iPhone, so are the symptom tags its Health sync screen lists, every mood tag (as Mood Changes), cervical mucus, ovulation tests, and basal body temperature. On Android: each period's first and last day, cervical mucus, ovulation tests, and basal body temperature — but not symptoms or moods, because Health Connect has no categories for them; those stay in lunarlog.
A super heavy day is written as Heavy: neither health app has a level above it.
Edit or delete a day in lunarlog and its copy in the health app follows.
Turning it off, or taking away lunarlog's access, stops new writes and leaves what was already written where it is. To remove that, delete it in the health app itself.

All of this happens on the phone, between lunarlog and the health app. It sends nothing to lunarlog's servers.

Taking your data out

Getting a copy of your data

Settings → Your data → Export builds a file from the on-device copy. No account needed.

The export covers every profile and day entry on the device — owned profiles and shared ones alike. While signed in and online it additionally merges the account’s own server-side record, such as memberships and preferences.

The file is handed to the device’s share sheet, so the destination is always your choice. A second, clinician-readable format is offered from the same place.

On a shared or borrowed device, review the file before passing it on — it reflects everything that account can currently see.

Source: lunarlog app behaviour · Last reviewed 2026-09-11

Every format lives under Your data → Export my data and its neighbours, all built on-device and handed to your share sheet:

Export my data — a JSON file of every profile and day entry on the device, plus the account's server-side record when you are signed in. lunarlog can restore from its own backup the same way.
Export as CSV — spreadsheet-friendly tables of the cycle data.
Export clinical summary (FHIR) — one profile's cycle and symptom history as a file a clinic's records system can read (the FHIR R4 format), with the data marked as self-reported.
Export clinical summary (PDF) — a one-page PDF summary of the logged data, for an appointment.

Exports work fully offline and need no account — the file is built from the copy on your device. On a shared or borrowed phone, remember the file carries everything that device can see; review it before passing it on.