Last updated: 29 August 2026.
The short version
- We collect only what the product needs to work.
- Your health data is never sold, never shared with advertisers, and never used to target you with anything.
- You can export everything or delete everything, yourself, from your account, at any time.
- The free tier is funded by optional affiliate links on ingredients, not by your data.
What we collect, and why
Account basics. Name, email and password (stored hashed), or your Google/Apple sign-in. Used to sign you in and send the emails you've asked for.
What you tell the planner. Symptoms, household size, diet, real-life preferences and, if you share them, period dates. Used for one thing: building and timing your weekly plan.
Daily check-ins. Your sleep, mood, flush and energy scores, period logs and notes. Used to find patterns between what you cooked and how you felt, shown only to you, and assembled into a GP report only when you press the button.
Health profile. Menopause stage, HRT status, conditions, intolerances and medication notes, if you choose to add them. Used to filter and time what we suggest (for example, keeping soya-heavy meals away from levothyroxine timing). All of it is optional; the planner works without it.
Connected apps. If you connect Apple Health, Oura or Clue, we pull the specific fields you approve (sleep, cycle dates) to pre-fill your check-ins. Disconnecting stops the pull immediately and you can delete what was imported.
The special-category point, made plainly
Check-ins, cycle dates and your health profile are "special category" data under UK GDPR, the law's highest tier of protection, and we treat them accordingly: collected only with your explicit consent, encrypted at rest and in transit, kept on servers in the UK/EEA, and never processed for advertising or profiling beyond the insights you see in your own account. Our lawful bases are consent (health data) and contract (running your account).
What we never do
- Sell your data. Not anonymised, not aggregated, not ever.
- Share health data with advertisers, data brokers, insurers or employers.
- Run third-party advertising or tracking pixels on signed-in pages.
- Email you more than you agreed to, or make unsubscribing a puzzle.
Who we do share with
The minimum set of processors any service needs, each under contract, each receiving only what their job requires: our hosting provider (UK/EEA servers), our email provider (your address and newsletter preferences), and our payment provider (payment details, which we never see, if you subscribe). Supermarket basket links pass your shopping list items to the retailer you choose, only when you click, and nothing else. If the law compels disclosure, we insist on due process and tell you unless legally barred.
Community
Community posts are public to members under the display name you choose; pseudonyms are the default and fine by us. Your stories never automatically include your check-in or health data; you choose every word you publish, and you can edit or delete your posts at any time.
Cookies
Essential cookies for sign-in and security, plus privacy-respecting, cookieless analytics on public pages that count visits without identifying you. No advertising cookies, so no cookie-wall theatrics.
Your controls
- Export everything: one click in your account produces your recipes, plans, check-ins and profile as JSON and CSV.
- Delete everything: also one click, also in your account. Deletion is real: backups purge on a 30-day cycle.
- Correct anything: every field we hold is editable in your account.
- Withdraw consent: turn off check-ins, disconnect apps, or empty your health profile without closing your account.
For anything this page doesn't cover, email [email protected]. You also have the right to complain to the UK Information Commissioner's Office (ico.org.uk), though we'd appreciate the chance to fix it first.
Changes to this page
If we change anything material, we'll email account holders before it takes effect and keep the previous version available. Quiet edits to privacy policies are exactly the behaviour this page exists to rule out.