Privacy policy
Moraki keeps a record of your baby's care that you and the people you invite can all see. Your entries are stored on your phone and, once you sign in, on servers in the EU. Only people in your household see them. They are never sold, never used for advertising and never used to train any model. There are no analytics and no ads in the app.
1. Who is responsible for your data
The controller is CE Code Designs Ltd (Code Designs Ltd), a company established in Cyprus, which publishes Moraki. You can reach us at [email protected]. We have not appointed a data protection officer; write to that address about anything in this policy.
You use Moraki as a parent or caregiver. Your baby's details are entered by you, or by another adult in your household, not by the baby.
2. What we collect
Your account.
- Your email address, and the one-time code we email you to sign in. The code expires after 10 minutes.
- If you sign in with Apple or Google instead, that company confirms your email address to us. Apple lets you share a relay address instead of your real one. Google's sign-in token also carries the name and profile picture on your Google account; our authentication provider stores them with your account record, and Moraki does not show or use them.
- The name other caregivers see on your entries (a first name or a nickname, up to 40 characters), your relation to the baby if you choose one, and your role in the household: owner, caregiver or viewer.
- A record of your consent to health data being processed: which version you agreed to, when, and when you withdrew it, if you did.
Your baby. The name you type (often a nickname), date and time of birth, and birth weight.
What you log.
- Feeds (bottle amount and milk type, breastfeeding side and time), diapers, sleep, pumping, milk stock, weight, temperature, health notes, medication and appointments.
- Each entry also records when it happened, who logged it, who last changed it, and whether it was deleted.
- Notes, appointment details and questions are free text. We can't know what you type there, so we treat all of it as health data. An appointment can name a doctor or a clinic; that is the clinician's personal data, entered by you.
Crash reports. If the app crashes, it sends a report to our crash reporting service: the type of error, a shortened and redacted error message, where in the code it happened, the app version, and your device model and operating system. Before anything leaves the phone, the app removes who you are, your IP address, any request or response content and any field it has not explicitly allowed, and replaces quoted text, email addresses and IDs.
Feedback. If you send feedback from Settings, we receive your message (up to 2,000 characters), what it is about, the app version, platform and language, your user ID and the time. It is not linked to your household or your baby. Please leave health details out of it.
On your phone only. Your settings (night mode, language, reminders), changes waiting to be sent, and a record of any change the server refused stay on your phone. Feed reminders are worked out and scheduled on your phone; nothing about them is sent to us. Your session token is kept in your phone's secure keychain.
What we don't collect. No location, contacts, photos, phone number, postal address, payment details or advertising identifier. There are no analytics or advertising tools in the app.
You can use Moraki without an account. Your entries then stay on your phone and nothing about them reaches our servers.
3. Why we use it, and on what legal basis
| Purpose | Legal basis (GDPR) |
|---|---|
| Keep a record of your baby's care and share it with your household | Article 6(1)(b): providing the service you signed up for |
| Process health data: feeds, diapers, sleep, pumping, weight, temperatures, notes, medication and appointments | Article 9(2)(a): your explicit consent, asked on its own screen |
| Sign you in without a password | Article 6(1)(b) |
| Remind you a feed may be due | Article 6(1)(b), worked out on your phone |
| Find and fix crashes | Article 6(1)(f): our legitimate interest in an app that works, with health data kept out of crash reports |
| Read and act on feedback you choose to send | Article 6(1)(a) or 6(1)(f); it is sent only when you press send |
4. Health data and your consent
Everything you log about feeding, diapers, sleep, pumping, weight, temperature, medication, notes and appointments is health data. Every caregiver in a household, including a viewer who only reads, is asked for explicit consent on its own screen before it is processed. Nothing is pre-ticked, and saying no leaves the app working on your phone.
You can withdraw consent at any time in Settings → Privacy → Health data. Your entries then stay on your phone and stop syncing. Withdrawing does not delete anything already saved and does not close your account; to delete, see section 9.
Moraki does not interpret your entries. It adds them up and shows them, with no ranges, warnings or scores, and no decision about you is made automatically.
5. Your baby's data
Moraki is used by adults. Your baby cannot consent, so you consent on their behalf as someone with parental responsibility. Please only add people to your household whom you are happy to share your baby's record with.
6. Who can see it
- People in your household. Everyone you invite sees the same entries and who logged them. Someone removed from a household loses access to our servers straight away, but a copy already on their phone stays there; we cannot reach it.
- The service providers below, who process data for us under data processing terms and only to run Moraki.
Nothing is sold, used for advertising or used to train any model.
7. Service providers and where your data is kept
| Provider | What for | Where |
|---|---|---|
| Supabase (hosted on Amazon Web Services) | Database and sign-in: your account, your household and everything you log | Frankfurt, Germany (EU) |
| Sentry | Crash reports, with personal details removed as described above | EU (Germany) |
| Google Workspace | Sending the email with your sign-in code: your email address and the code | Google's infrastructure |
| Expo | Delivering app updates: when the app opens it asks for a newer version, which sends your phone's IP address, platform, app version and a random install id. No account, no household data | United States |
Your household's data is kept in the EU, and the app refuses to send crash reports anywhere but Sentry's EU service. Apple and Google distribute the app through their stores and, if you choose them, sign you in; they do that under their own privacy policies and may process data outside the EU. Neither receives your household's entries from us. Expo, which delivers app updates, is in the United States: the update check described above goes there, under the EU Standard Contractual Clauses in Expo's terms and Expo's certification under the EU-US Data Privacy Framework.
8. How long we keep it
| Data | Kept |
|---|---|
| Entries and your baby's details | For as long as the household exists. We don't trim a family's record on a schedule. |
| Deleted entries | Marked as deleted rather than removed, so every phone in the household learns of the deletion. Removed when the household is deleted. |
| Your account, name and role | Until you delete your account |
| Consent records | Kept after you withdraw, as evidence of what you agreed to and when. Deleted with your account. |
| Feedback | 24 months, or until you delete your account if that is sooner |
| Invite codes | Expire after 7 days; removed 90 days after being used or expiring |
| Sign-in codes | 10 minutes |
| Crash reports | 30 days |
| Data on your phone | Until you delete the app or its data. On iPhone, the sign-in token in the keychain can survive deleting the app. |
| Files you export | Yours, wherever you choose to keep them |
9. Your rights, and how to use them in the app
- Get a copy (access and portability). Settings → Your data → Export everything makes two files on your phone, a spreadsheet (CSV) and a complete one (JSON), including deleted entries marked as deleted. Feedback you sent is not in that export; email us and we will send it.
- Correct it. Every entry can be edited, and the baby's details can be changed by anyone in the household who logs entries.
-
Delete it. In Settings you can:
- leave a household that others share; the household and its entries carry on without you;
- delete a household, if you are its owner: the baby, every entry and every invite are deleted for everyone;
- delete your account: your email address, sign-in details, sessions, name and role in every household, consent records and feedback are deleted. A household where you are the only member is deleted with everything in it. A household others share stays, because its entries are their record of their baby too: the entries you logged remain and show as logged by someone who has left, and if you were the only owner, you choose who becomes owner before you go.
- Restrict or object. Withdraw consent in Settings → Privacy → Health data, or stop using the app. There is no profiling or marketing to object to.
- Anything else. Email [email protected]. We answer within one month.
You can also complain to the Office of the Commissioner for Personal Data Protection in Cyprus (dataprotection.gov.cy) or to the data protection authority where you live.
10. Security
Data travels encrypted (HTTPS/TLS). On our servers, database rules let a person reach only their own household's data, and health data can only be saved by someone who has consented. Your sign-in token is kept in your phone's secure keychain.
Entries on your phone are protected by your phone's own storage encryption; adding encryption of Moraki's own database is planned. Please use a passcode on your phone: it is what protects your entries if the phone is lost.
11. Notifications
Feed reminders are scheduled on your phone and never include an amount, a temperature or any other figure, so nothing about your baby's health appears on a lock screen.
12. Changes to this policy
If we change this policy, we will update the date above and tell you in the app. If a change affects what you consented to, we will ask for your consent again.
13. Contact
CE Code Designs Ltd, Cyprus · [email protected]