Skip to content

Privacy policy

Last updated

Draft for review. Not in force and not indexed. Open questions:

  1. Draft written from the app's code on 1 Nov 2026 and from MyBaby's policy. Not legally reviewed. MyBaby's policy was reviewed on 30 Aug 2026; that review does not cover this text.
  2. Company details: no postal address or OIB here, as in MyBaby's policy. GDPR asks for the controller's identity and contact details; confirm the address should be added.
  3. Section 9: health data in the EEA and UK needs explicit consent (GDPR Art. 9). The lead is adding a consent step to Welcome and onboarding (1 Nov); this section is true once that ships.
  4. Section 11: MyPregnancy's anonymous accounts are never deleted automatically (the app stays out of MyBaby's 90-day sweep on purpose). Keep it that way, or add an inactivity rule?
  5. Section 10: the commitments on requests from authorities (valid legal process only, notify the user where allowed) are a policy decision. Confirm or change.
  6. Section 14: minimum age. MyBaby says 16 without parental consent. Pregnancy apps are used by under-18s; confirm the age and wording.
  7. Section 18: asking for consent again in the app before a change applies is a promise the app cannot keep yet (no in-app notice). Keep it and build the notice, or soften to an email to signed-in users?
  8. Section 12: there is no export of the raw data in the app; the PDF covers contractions, kicks and the birth plan. Access requests go by email. Fine, or add an export?