Help with Lull

Lull works out your cycles from what you log. A cycle begins on the first day you record a flow of light or stronger after a day without one. That's day 1. Once Lull knows where your current cycle started, it can predict your next day 1, and shows it with a date range and a confidence level rather than a single false-precision date.

So you'll need to log at least one period start before predictions appear, and roughly a full cycle before they mean much. As you complete more cycles, Lull has more history to average and the confidence improves.

Spotting is recorded and shown on your calendar, but it doesn't start a new cycle, so a few spotting days before your period won't shift day 1 earlier.

If you've set your cycle status to pregnant, breastfeeding or on birth control, Lull stops predicting periods. Cycle-based predictions aren't meaningful in those situations, and showing them anyway would be noise at best.

You can keep logging normally the whole time: flow, symptoms, moods and notes all still work. Change your cycle status back in Settings whenever you'd like predictions to resume.

Lull estimates ovulation as fourteen days before your predicted next period, and shades the seven days around it, five before through one after. That's the calendar method: arithmetic on your cycle history, not a measurement of your body.

Real ovulation shifts with stress, illness, travel and plain natural variation, and Lull has no way to observe it. That's why the fertile window is always labelled an estimate. Do not use it as contraception, and don't rely on it for conception timing without talking to a clinician. Nothing in Lull is medical advice.

It's off until you switch it on in Settings. When you do, iOS asks your permission, and Lull then mirrors what you log into Apple Health's Cycle Tracking and State of Mind: flow, spotting, discharge, symptoms, moods and your cycle status. A couple of symptoms Lull offers have no equivalent in Apple Health and stay in Lull only.

Lull also reads a small amount from Apple Health to show extra Insights cards: Apple's own cycle-deviation flags and Apple Watch wrist temperature. Those cards only appear if that data exists and you've allowed the read.

To stop syncing, switch Apple Health sharing off in Lull's settings. This also removes the samples Lull wrote to Health. Anything you or other apps put in Health directly is left alone. You can also review permissions in the Health app under Sharing, or in iOS Settings → Privacy & Security → Health.

The daily log reminder is optional. Turn it on in Settings and pick a time; it arrives every day, and changes take effect immediately, with no save button. It's data-aware, so if you've already logged the day, that day's nudge is quietly dropped.

There's also a one-off “Did your period start today?” prompt on the day Lull predicts your period will begin. Tapping either notification opens that day's editor.

Both need notification permission, which Lull asks for the first time you turn a reminder on. If you declined earlier, the toggle shows a link straight to iOS Settings → Notifications, where you can allow them again.

If you're signed in to iCloud with iCloud enabled for Lull, your entries sync automatically to your other devices through your own private iCloud database. There's no account to create and nothing to configure in the app. It uses the Apple Account you're already signed in with.

Without iCloud, Lull works exactly the same, but your data stays on that one device only. Nothing is lost; it simply doesn't travel.

Sync happens in the background and can take a moment. If a device looks out of date, check that it's online and that Lull is enabled under iOS Settings → your name → iCloud.

• One day: open that day and clear the entry.
• What Lull put in Apple Health: switch Apple Health sharing off in Settings, which deletes the samples Lull wrote.
• Everything: delete the app from your iPhone, then remove its iCloud copy in iOS Settings → your name → iCloud → Manage Account Storage.

There's no request to file and nobody to email, because your data was never on anyone else's server. See the privacy policy for the full picture.

No. Lull has no servers, no accounts, no analytics and no third-party SDKs. Your entries live on your iPhone and, if you use iCloud, in your own private iCloud database, which is tied to your Apple Account and cannot be read by the developer.

That also means bug reports carry no automatic diagnostics. If something goes wrong, describing what you did and what you saw is genuinely the only information available.