An iCloud sync period tracker with no cloud company in the middle

Why most "cloud-synced" period trackers are a privacy mess

When a typical period tracker syncs across your devices, what's actually happening is: your iPhone uploads your cycle data — your periods, symptoms, sexual activity, pregnancy status — to the app company's servers. Those servers hold a copy. You give them an email, they make you an account, and now your most sensitive health data lives somewhere a marketer, a data broker, a breach, or a subpoena can reach it.

Hoo-Ha takes the opposite approach. Sync happens through Apple's CloudKit private database, which is end-to-end encrypted under your Apple ID. Apple holds no key. Hoo-Ha operates no servers at all. Your iPhone and iPad mirror data through your own private iCloud — and nothing in between can read it.

How CloudKit private sync works (the short version)

• Your Apple ID is the gate. Sign in to iCloud on iPhone and iPad — the same account — and Hoo-Ha's database mirrors between them automatically.
• End-to-end encrypted. The same encryption layer iMessage and Notes use. Apple's servers store opaque bytes they can't decrypt.
• No Hoo-Ha account exists. There's no email signup, no password, no profile on a Hoo-Ha server — because there is no Hoo-Ha server.
• Off by default. You opt in via Settings → iCloud Sync. Toggling off stops new writes from syncing. To fully remove cloud data, iOS Settings → Apple ID → iCloud → Manage Storage → Hoo-Ha.
• Per-Apple-ID, not Family-shared. Family members can install Hoo-Ha via Family Sharing without paying, but each person's data syncs to their own private database.

What syncs (and what doesn't)

What syncs: cycle dates, period flow, BBT, cervical mucus, LH tests, mood, symptoms, sleep, lifestyle, vitals, journal entries, pregnancy data, postpartum data, breastfeeding sessions, diaper logs, multi-baby info, ultrasound photos, bump photos, symptom photos, settings, custom fields, derived formulas.

What does NOT sync, by construction: biometric / Face ID journal-lock setup (per-device security state), local notification schedules, the widget's cached data, and your encrypted local backup archives. Those all live in per-device storage outside the synced database — so sync leaves them alone, and your devices stay independently secure.

What this means in plain language

• You can log your morning BBT on your iPhone and have it appear on your iPad before you even sit down.
• If you get a new iPhone, sign into iCloud, install Hoo-Ha, and your cycle history is just there.
• Your partner can't see your data unless you actively use the local peer-to-peer partner share feature.
• If you ever decide you don't want Hoo-Ha syncing, you turn the toggle off — there's no "data deletion request" workflow, because there's no company holding your data.

What about Flo, Clue, Stardust, etc.?

Most of the big period-tracking apps run on their own infrastructure — when they "sync to the cloud," they mean their cloud. Natural Cycles, Flo, and Stardust all hold copies of your data on company-controlled servers. Even Drip, which is local-first and open-source on Android, doesn't have a real cross-device sync story on iPhone.

Hoo-Ha's approach is structurally different: there is no Hoo-Ha cloud. We could not give your data to a marketer, a data broker, an insurance company, or a court — because we don't have it. Apple holds the encrypted bytes; you hold the key.

See how the offline-only mode works →  ·  Full security architecture →  ·  Compare to Flo & Clue →