Privacy Policy
Effective 28 October 2026
Data controller: C.E. CODE DESIGNS LTD
Contact: [email protected]
Website: https://moraki.app
1. Who we are
Moraki is a baby-care record-keeping application operated by C.E. CODE DESIGNS LTD, a company registered in the Republic of Cyprus under registration number HE472540, with its registered address at Akropoleos 4, Paphos, Cyprus.
We determine how personal information is processed to provide Moraki and are the data controller for the processing described in this Policy.
This Policy explains what information Moraki processes, how it is used and shared, how long it is retained, and the choices and rights available to users and to children through their authorised representatives.
For privacy enquiries or to exercise your rights, contact [email protected].
2. Information we process
Account and identity information
When you create an account, we process your email address, internal account identifier, authentication provider, account and sign-in metadata, and relevant security information.
Moraki supports email verification codes, Sign in with Apple and Google sign-in. Apple may provide a private relay email address. Google may supply a name and profile-picture URL through its authentication service, although Moraki does not display those profile details within the household.
Baby and care records
When an authorised guardian creates a shared household, Moraki stores the baby's name or nickname, date of birth and optionally birth weight.
Users may record breastfeeding, bottle feeds, milk and pumping information, sleep, diaper changes, temperature, symptoms and health notes, medication details, weight measurements, appointments and questions for healthcare professionals.
Entries include relevant dates, times, record identifiers and information identifying the household member who created or last changed them.
Health records and free-text notes can contain special-category personal data, including information about the child and, in some cases, the health or breastfeeding of a parent or another person.
Please enter only information that is necessary and appropriate for the baby's care and avoid including unnecessary information about other people.
Household information
We process members' chosen display names, relationships to the child where provided, roles, joining information, invitations and access permissions. A member's display name and the author of an entry can be visible to other authorised household members. Members' email addresses are not displayed to one another by default.
Agreements and permissions
We retain records of Terms acceptance, guardian declarations, caregiver agreements, health-data consent and withdrawals. These records include identifiers, the relevant purpose, text version, language and timestamps.
Feedback, technical and website information
If you submit feedback or contact support, we process your message, contact details and information needed to respond.
Our infrastructure may process IP addresses, device and application versions, authentication and security logs, error information and installation identifiers. Moraki uses crash reporting and update delivery, but does not currently use advertising or behavioural analytics SDKs.
Visitors to moraki.app may generate ordinary website and security logs. The website also stores a selected light/dark theme preference in browser local storage.
3. Local-only and shared modes
Moraki can be used without an account for local activity logging and several related functions. Local records are stored in an encrypted database on your device and are not uploaded to the Moraki household database while you use the app without signing in.
Some technical communications still occur when the app launches, including checking with Expo for application updates and crash diagnostics when relevant. These do not intentionally contain the baby's care entries.
Creating a baby profile, synchronising records, inviting other users and sharing household information require an account and appropriate authorisation.
If you subsequently create a household, eligible locally recorded information may be linked to it and uploaded after the required permissions have been granted. Joining an existing household with local entries involves a separate choice about adding those records.
4. Purposes and lawful bases
We process personal information for these purposes:
- Providing accounts, authentication and requested app functionality: performance of our agreement with adult users under Article 6(1)(b) GDPR, where applicable.
- Processing and synchronising the child's sensitive care information: the guardian's recorded, explicit authorisation and consent, with Article 6(1)(a) and Article 9(2)(a) GDPR as the proposed grounds, subject to applicable rules concerning parental authority and children's rights.
- Sharing records with invited caregivers: enabling the guardian-authorised household service, subject to appropriate permissions, confidentiality obligations and a documented lawful basis for each affected person's data.
- Processing health information about an adult contained in pumping records or notes: subject to an applicable Article 6 lawful basis and Article 9 condition for that adult's own health information. A guardian's consent for the child does not automatically establish consent for another adult.
- Security, fraud prevention, essential application updates and service reliability: our legitimate interests under Article 6(1)(f), where these are not overridden by individuals' rights and freedoms.
- Responding to privacy requests and meeting statutory obligations: compliance with legal obligations under Article 6(1)(c), where applicable.
- Retaining proportionate records necessary to demonstrate agreements or defend legal claims: applicable legal obligations or legitimate interests, assessed for the specific records and retention period.
Where we rely on legitimate interests, you may request information about the relevant balancing assessment and object where the GDPR provides that right.
The processing of children's and adults' health information receives additional protection. The final applicability of these legal grounds to all household-sharing situations requires the company's legal assessment.
5. Guardian authority and caregiver access
A person creating a shared household must affirm that they are the parent or legal guardian of the child, or otherwise have lawful authority to provide and manage the child's information.
This declaration is recorded but is not independently verified during ordinary registration.
An invited caregiver sees the proposed access role and is informed that joining can provide access to past and future household records. They must accept the caregiver agreement before accessing shared information.
Depending on their role, members can view, create, correct or delete records. Authorised caregivers may edit records entered by another caregiver. There are no separate privacy controls for individual categories such as medications or health notes.
Only invite people you trust. Information lawfully accessed, exported or shared by another person may remain in that person's possession after access is removed.
Where there is a dispute concerning parental responsibility or access to a child's information, we may request evidence, restrict disclosures while assessing the request and obtain legal advice. We do not determine custody or parental responsibility.
6. Consent and withdrawal
Guardians provide a separate affirmative authorisation for the cloud processing and sharing of the child's health records. We maintain a record of the relevant agreement and withdrawal.
You can review and withdraw relevant consent through Settings → Privacy → Review consent.
When a guardian withdraws while another guardian has valid authorisation, the withdrawing guardian's shared access and new synchronisation are restricted, but their own authored records remain accessible for viewing and deletion.
If the last authorising guardian withdraws, the shared household is paused. Members cannot create or share new baby records, invite new members or view other people's entries. They may still view and delete entries they personally created. Previously synchronised records are not automatically erased at the moment of withdrawal.
A guardian may reauthorise processing, arrange an eligible handover or delete the household.
Where a household remains paused because of an explicit guardian withdrawal, a warning is scheduled after 90 days and deletion may follow at least 30 days later if no valid authorisation is restored.
For non-material consent-text revisions, an earlier authorisation may remain effective for a transition period of up to 90 days. After that, sharing can pause pending renewed agreement. A text-version change alone does not trigger the explicit-withdrawal deletion countdown. Materially new processing requiring fresh consent will not begin without it.
A caregiver who withdraws their caregiver agreement leaves the household.
Withdrawal does not affect processing already carried out lawfully before withdrawal, and some information may be retained where another applicable lawful basis requires or permits it.
7. Service providers and international processing
We use the following providers for specific functions:
- Supabase: user authentication, database storage, household synchronisation and server functions; primary production region Frankfurt, Germany.
- Sentry: limited crash diagnostics processed in its EU environment; crash reports are retained for 30 days. IP storage is disabled and privacy scrubbing is configured.
- Expo / EAS Update: application updates. Technical information, including IP address, device/application details and an installation identifier, may be processed in the United States.
- Apple and Google: identity authentication where chosen by the user.
- Brevo: Delivery of email sign-in verification codes, operational notifications (including inactivity and paused-household warnings), and restricted deletion-journal communications. Brevo processes the recipient's email address and the information necessary to deliver these messages.
- A2 Hosting: website and support email hosting, reported as hosted in the Netherlands.
- Cloudflare: website delivery, DNS and security.
These providers do not all receive baby health information. The main cloud storage and synchronisation service for baby records is Supabase; authenticated members also receive the shared information on their devices.
Some technical information may be processed outside the European Economic Area, including through international providers or their subprocessors. Where required, we rely on applicable adequacy decisions or recognised transfer safeguards, including Standard Contractual Clauses. You may contact us for information about relevant safeguards.
We do not sell personal information, operate personalised advertising based on baby records or use those records to train AI models.
8. Storage and security
Local app records are held in an encrypted SQLite database using SQLCipher. The encryption key is protected through device secure storage.
Cloud records are protected through encrypted connections, service-provider storage controls and database access policies. Household access is restricted by account, membership and relevant permission rules.
Authorised company administrators may technically access production records where necessary for security, support, legal compliance or responding to a valid request. Such access should be limited and appropriately controlled.
No service can guarantee absolute security. You should protect your device, email account, sign-in credentials and any exported records.
Device backups managed by Apple and copies saved or shared by users operate under the relevant device and destination settings. Moraki cannot revoke files that have already been exported elsewhere.
9. Retention
We retain information according to its purpose and the implemented lifecycle:
- Active baby and household records: for the household's lifetime, unless earlier deletion or a legal requirement applies.
- Deleted individual entries: their content remains in a deletion state for up to 30 days, then is purged; limited synchronisation markers remain until the household is removed.
- Accounts: until account deletion.
- Consent and agreement evidence: retained during the account's lifetime and, after deletion, for a further three years in pseudonymous form under the current documented retention rule.
- Feedback: up to 24 months or until account deletion, whichever occurs first.
- Invitations: expire after seven days and are generally removed 90 days after use or expiry.
- Crash reports: 30 days.
- Inactive households: after 23 months without qualifying activity, an email warning is sent. Deletion can occur after 24 months if the warning conditions and at least 30 days' notice have been satisfied, with no intervening activity.
- Households paused following explicit final-guardian withdrawal: warning after 90 days, with possible deletion at least 30 days later if still paused.
- Deletion audit records: retained for 35 days. Restricted daily journal emails containing deletion identifiers are also retained for at least 35 days to assist backup recovery.
- Supabase daily backups: normally retained for seven days, after which deleted data ages out.
Retention periods may be affected by lawful requests, applicable legal obligations and narrowly justified exceptions.
10. Your rights
Subject to applicable law and verification, you may request access, correction, erasure, restriction, portability, withdrawal of consent or objection to certain processing.
You can use the app to edit entries, export information and leave or delete a household or account. The JSON/CSV export includes relevant household records and, when available, your own account and agreement information. It is not necessarily a complete copy of all technical logs or other information we hold.
For a wider request, or if you cannot access the app, email [email protected]. We normally respond within one month, subject to lawful extensions.
Requests about a child's information are assessed in light of parental authority, the child's interests and the privacy rights of other people. Additional verification may be necessary.
You may also lodge a complaint with the Office of the Commissioner for Personal Data Protection, Republic of Cyprus, or another competent data-protection supervisory authority.
11. Account and household deletion
In the app, use Settings → Leave or delete.
Deleting your account removes the account and its ordinary profile information. If you are the only member of a household, that household is deleted. A shared household may remain for other authorised members, including entries you previously created, subject to the applicable rights and safeguards.
Deleting a household removes its baby profile and shared records from the live service. Deletions propagate to other devices when they reconnect; devices remaining offline can retain previously downloaded information until then.
In-app deletion also attempts to revoke Moraki's Apple or Google access, where applicable. Manual deletion by email does not automatically revoke the provider-side connection.
For a full explanation, see https://moraki.app/data-deletion/.
12. Changes to this Policy
We may update this Policy when functionality, providers, legal requirements or data handling changes.
The current version will be published on our website. We will provide additional notification or obtain renewed agreement where required by law or the nature of the change.
13. Contact
C.E. CODE DESIGNS LTD
Akropoleos 4, Paphos, Cyprus
Registration number: HE472540
Email: [email protected]
Website: https://moraki.app