Meyer Digital Martina Meyer (sole proprietorship) Seefeldstrasse 178 8008 Zurich, Switzerland Email:
2. EU Representative (Art. 27 GDPR)
For users residing in the European Union, we have appointed an EU representative under Art. 27 GDPR as the point of contact for supervisory authorities and data subjects.
Cornelius Matutis (Attorney at Law) Email:
3. Overview
Nourli is an app for tracking feeds, sleep, diapers, and other daily data around babies. This privacy policy informs you about which personal data we collect, how we process it, and what rights you have.
We take the protection of your data and your child's data very seriously. Nourli shows no advertising and does not sell data. To improve the app and the website, we use Microsoft Clarity, and on the website additionally Google Analytics for audience measurement. Form inputs, baby names, health data and notes are technically masked. In the app we additionally count a small, conclusively defined list of technical product events in our own database - for example which setup step was shown. No free text is ever involved. You can object to the website analytics at the end of this page; app analytics and product events are switched off in the app under Menu → Privacy. See Section 9 for details.
4. What data we collect
Account data
Email address (when signing up via Magic Link, Apple Sign-In or Google)
Display name (optional, only visible when sharing is enabled)
User ID (internally generated)
An account is required to use the app (no guest mode). Without an account, no data storage or cloud sync is possible.
Breastfeeding times (start, end, duration, side, pauses)
Bottle feeds (amount in ml, milk type, time)
Solids (type, amount, tolerance notes)
Water (amount, time)
Optional: notes and mood of the child after the meal
Pumping and stash data
Pumping times and amounts, side
Milk stash (fridge, freezer, fed, given away)
Stash adjustments
Sleep data
Sleep times and type (nap, night sleep, contact sleep, stroller)
Bedtime attempts and night wakings (time, optional note)
Fussing and crying periods (time, duration)
Diaper and health data
Diaper type (wet, stool, both)
Stool color, notes on diaper rash, cream use
Reflux / spit-up (amount, observations)
Weight history
Vitamin D administration
Data in the breastfeeding log export
When you create a breastfeeding log export for a midwife or pediatrician, you can optionally include your name, the child's name, date of birth and birth weight as header information in the PDF. These additional details are stored locally in your app settings.
Technical data
Device type and operating system version (for app compatibility)
App version, build number
Crash reports (Sentry): error message, location in the program code, device type, operating system and app version, internal user ID. Values that could contain names, amounts, notes or health data are stripped automatically before the report is sent. See Section 9 for details.
Your device's push token, if you allow notifications (see Section 8)
Anonymous usage telemetry (Microsoft Clarity): visited screens, tap/scroll interactions, device class, app version, anonymized IP. Form inputs, baby names, health data and notes are fully masked in session replays (Sensitive Data Masking). See Section 9 for details.
Product events: eight fixed technical events (such as "setup step shown" or "purchase attempt"), each with timestamp, platform, app version, your internal user ID and a short addition from a fixed set of values. No free text, no amounts, no names. See Section 9 for details.
5. Note on special categories (health data)
Feeding, pumping, diaper, sleep, weight and vitamin D data may allow conclusions about the health of your child. This data is considered specially protected personal data under the GDPR (Art. 9 para. 1) and the Swiss FADP (Art. 5 lit. c).
The processing of this data is based on your explicit consent (Art. 9 para. 2 lit. a GDPR / Art. 6 para. 7 FADP), which you provide when using the app. As a parent or legal guardian, you also provide this consent on behalf of your child. Children under 16 cannot give their own effective consent (Art. 8 GDPR).
You can withdraw your consent at any time by deleting your account in the app (see Section 13).
6. Sharing with caregivers, midwives and professionals
Shared use with caregivers
You can invite partners, family members or other carers to view your child's data in real time and add new entries. The invitation is sent via an invitation link.
Invited persons need their own Nourli account.
Only data you have entered or explicitly shared is visible - access is technically protected by Row-Level Security rules.
You can remove caregivers at any time; access is revoked immediately.
You are responsible for informing the invited persons about this data processing.
Breastfeeding log export for professionals
You can create a breastfeeding log as a PDF or spreadsheet file (CSV, XLSX) and forward it yourself to your midwife or pediatrician. The export happens locally on your device.
7. Where the data is stored
Locally on your device
All data is primarily stored in a local database (SQLite) on your device (iPhone, iPad or Android device). The app works fully offline.
Cloud synchronization
With your account, data is synchronized with our backend provider so you can access it on multiple devices and caregivers can view it.
Provider: Supabase Inc., San Francisco, USA
Server location: Amazon Web Services (AWS), region eu-central-2 (Zurich, Switzerland)
Purpose: data backup, sync between devices, sharing with caregivers, file storage for voice recordings from the beta phase (see Section 9)
Legal basis for transfer to the USA: EU Standard Contractual Clauses (SCCs) under Art. 46 para. 2 lit. c GDPR plus a Data Processing Addendum with Supabase. The physical data storage remains in Switzerland.
Apple Watch, Widgets and Live Activities
If you use the Apple Watch app, iOS widgets or Live Activities, the data needed for display (current session, latest entry, duration) is synchronized between devices via Apple's WatchConnectivity and WidgetKit. This synchronization runs locally via Apple's frameworks; no additional transfer to us or third parties occurs.
8. Notifications
Reminders (local)
Nourli can remind you of scheduled times for feeds, pumping or diaper changes. These reminders are generated locally on your device via Expo Notifications; no data leaves your device for this.
Messages from us (push)
In addition, during the first days after you sign up we send up to three messages to help you get started (for example if no baby profile has been created yet, or nothing has been logged yet). These messages are generated on our server and delivered to your device through a push service.
What we store for this: your device's push token (a delivery address issued by the operating system), your user ID, your app language, and which message has already been sent. The message text contains the baby's first name if one is stored.
Delivery path: Expo (Expo Push Service, USA) hands the message to Apple Push Notification service (iOS) or Firebase Cloud Messaging (Android). These services only see the delivery address and the message text, no other account data.
Legal basis: legitimate interest in introducing you to the app (Art. 6(1)(f) GDPR), limited to the onboarding phase. No advertising.
Objection: disable notifications in your device's system settings, or contact us informally at . The push token is deleted once the device is no longer reachable or when you delete your account.
9. Sub-processors
Service
Purpose
Location
Supabase Inc.
Authentication, database, cloud sync
USA (company), Switzerland / AWS eu-central-2 Zurich (data)
Apple Inc.
Apple Sign-In, In-App Purchase (iOS subscription handling)
USA
Google LLC
Google Sign-In, Google Play Billing (Android subscription handling)
USA
Microsoft Corporation
App and web analytics via Microsoft Clarity (heatmaps, session replays, anonymized)
EU / USA
Google Ireland Limited
Website analytics via Google Analytics 4 (audience measurement, no advertising features)
EU / USA
Expo / EAS
App build service, over-the-air updates, delivery of push messages
USA
Functional Software, Inc. (Sentry)
App crash and error reports
USA
OpenAI, L.L.C.
Speech-to-text conversion (Whisper API) for voice-based entry
USA
Anthropic, PBC
Content extraction from the transcript (Claude API) for voice-based entry
USA
Resend, Inc.
Transactional emails (Magic Link, invitations)
EU region
Apple and Google receive only the data necessary for authentication (email or identity token). Beyond that, we only store the account data you have confirmed in our database.
Payment processing (Apple In-App Purchase / Google Play Billing)
Paid subscriptions and lifetime purchases are processed exclusively through the platform stores:
iOS: Apple In-App Purchase (Apple Inc., USA / Apple Distribution International Ltd., Ireland for EU purchases)
Android: Google Play Billing (Google LLC, USA / Google Ireland Ltd. for EU purchases)
We have no access to your payment data (card number, bank details, address). Apple and Google process payment, invoicing, taxes and refunds independently. From Apple/Google we only receive a pseudonymized confirmation (receipt/token) of your purchase, the product identifier and the start/expiry dates of a subscription, to validate the unlocked features server-side.
App analytics (Microsoft Clarity)
To improve the app user experience, we collect anonymized usage data using Microsoft Clarity.
Provider: Microsoft Corporation, One Microsoft Way, Redmond, WA 98052, USA
What is collected: visited screens, tap/scroll interactions, session duration, device class, operating system, app version, anonymized IP, aggregated heatmaps and session replays
What is NOT collected: form inputs, names, baby names, notes, health data, amounts, images. All content with personal or health data is automatically masked via Clarity's Sensitive Data Masking feature.
Retention: Microsoft deletes Clarity data after no more than 13 months
Legal basis: Legitimate interest in product improvement and error analysis (Art. 6 para. 1 lit. f GDPR)
Opt-out: at any time via Section 18 of this page, in the app under Menu → Privacy, or informally at
USA transfer: Microsoft Corporation is certified under the EU-US Data Privacy Framework; EU Standard Contractual Clauses (SCCs) apply additionally.
Website analytics (Google Analytics)
On the nourli.app website we additionally use Google Analytics 4 to understand which pages are found and read. Google Analytics is not used in the app.
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland; for users outside the EEA, Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA
What is collected: pages viewed, referrer, approximate location at city level, device type, browser, operating system, screen size, language, session duration, truncated IP address
What is NOT collected: name, email address, account data, baby names, health data. The website processes none of this through Google Analytics.
Advertising features: disabled. We run no advertising, use no Google Signals and no ad personalization. The data is not shared with third parties for advertising purposes.
Retention: 14 months
Legal basis: your consent given via the cookie notice on the website (Art. 6(1)(a) GDPR)
Withdrawal: at any time via Section 18 of this page, or informally to
USA transfer: Google LLC is certified under the EU-US Data Privacy Framework; EU Standard Contractual Clauses (SCCs) apply additionally.
Product events (our own collection, no third parties)
So that we can see where people get stuck - for instance at which setup step they stop - the app counts a small, conclusively defined list of technical events. This data goes to no third party; it sits exclusively in our own database (Supabase, EU / AWS Ireland, see Section 7).
Which events: setup step shown · app opened on a calendar day (counted at most once per day) · pricing page shown · purchase attempt with its outcome · blocking technical error · plus three events for the voice feature (entry point visible, introduction seen, recording started). Other events are technically impossible: the database rejects anything not on this list.
What is stored: the name of the event, the timestamp, platform and app version, your internal user ID, and a short technical addition from a fixed set of values - such as the name of the setup step reached, the product identifier of a purchase attempt, or an error code.
What is NOT collected: free text of any kind, baby names, amounts, notes, health data, times from your child's day, email address. Error messages are deliberately not sent, only the error code - a message is free text and could contain names.
Not anonymous, but without content: these events are tied to your internal user ID. Without it we could not tell whether ten people took one step each or one person took ten - which is precisely the question. No conclusions about your entries or your child's health can be drawn from them.
Write-only: the app can only send these events, never read them back. They are evaluated internally and in aggregate only.
Retention: 90 days. After that a daily database job deletes the rows automatically.
Legal basis: legitimate interest in product improvement (Art. 6 para. 1 lit. f GDPR).
Objection: the same toggle as for app analytics, in the app under Menu → Privacy. Switching it off also deletes whatever is still unsent on your device. Or informally at .
Crash reports (Sentry)
If the app crashes or hits a technical error, we send an error report to Sentry so we can find and fix the problem.
Provider: Functional Software, Inc. (Sentry), 45 Fremont Street, San Francisco, CA 94105, USA
What is collected: error message and location in the program code, device type, operating system and app version, timestamp, internal user ID
What is NOT collected: baby names, amounts, notes, health data, email address. Any value that could contain such details is stripped on the device before the report leaves it; app log lines are not attached.
Legal basis: legitimate interest in a stable, error-free app (Art. 6(1)(f) GDPR)
Objection: informally at
US transfer: based on the EU Standard Contractual Clauses (SCCs) pursuant to Art. 46(2)(c) GDPR.
Voice-based entry (AI services)
If you use the optional voice feature, your recording is transmitted to OpenAI (Whisper API) for speech-to-text conversion, and the resulting text to Anthropic (Claude API) for content extraction.
What is transmitted: the recording or the resulting text, the baby first name stored in the app (for matching when you manage several profiles), your device's time zone and the time of the recording (so phrases like "half an hour ago" resolve correctly). If you correct an already recognised, not yet confirmed entry by voice, that entry is sent along for matching. No account identifiers, no email address, no device ID. The providers can only link the data to you if you record identifying details yourself.
No training: both providers contractually do not use data submitted via their APIs to train their models; short-term retention only for abuse monitoring.
Deletion: the audio file is deleted from your device once your review is complete; only the entries you confirm are stored permanently.
Quality improvement (beta): to further develop the voice feature, we store the recording, the transcript, the automatically detected suggestions and your corrections on our servers (Supabase, see above) for a maximum of 2 months. This data is not public, is not shared with third parties and is not used to train third-party AI models; it is deleted automatically once the period expires.
US transfer: both providers are certified under the EU-US Data Privacy Framework; EU standard contractual clauses (SCCs) apply in addition.
Legal basis: performance of contract when using the feature (Art. 6 (1) (b) GDPR); for quality improvement, our legitimate interest in developing the feature further (Art. 6 (1) (f) GDPR).
Web analytics
On the nourli.app website we use Microsoft Clarity and Google Analytics 4 (both described above). No other analytics tools are used. You can object to both at the end of this page.
10. Forms, waiting lists and feedback
Independently of the app, you can send us information through forms on the website or from within the app. This data is held in the same database described above (Supabase, EU/Ireland).
Waiting lists (e.g. Android version, early access): email address, optionally first name. Purpose: to notify you once, as soon as the offering is available. Legal basis: your consent when submitting the form (Art. 6(1)(a) GDPR). Deletion: after the notification or on your request, at the latest 12 months after receipt.
Midwife and professional forms (partner programme sign-up, feedback): name, email address, practice or institution, role and your free-text entries. This information is stored and additionally delivered to our mailbox by email (sent via Resend, see table above). Purpose and legal basis: handling your enquiry, pre-contractual communication (Art. 6(1)(b) GDPR) or legitimate interest in evaluating the feedback (Art. 6(1)(f) GDPR).
Public professional directory: If you take part in the partner programme as a midwife or professional and we approve your registration, your name and profile address become publicly visible on nourli.app. Your email address is not published. You can withdraw the publication at any time, informally.
Feedback from the app: If you send us feedback from within the app, we store your text together with your user ID so we can reply to follow-up questions. Legal basis: legitimate interest in improving the app (Art. 6(1)(f) GDPR).
Form entries are not used for advertising and are not passed on to third parties.
11. Purpose and legal basis
Purpose
Legal basis
Provision of app functions (tracking, sync, export)
Contract performance (Art. 6 para. 1 lit. b GDPR / Art. 31 para. 2 lit. a FADP)
Onboarding messages by push during the start phase
Legitimate interest in introducing you to the app (Art. 6 para. 1 lit. f GDPR)
Voice-based entry (transcription + extraction)
Contract performance when using the feature (Art. 6 para. 1 lit. b GDPR)
Waiting lists and forms on the website
Consent (Art. 6 para. 1 lit. a GDPR) or pre-contractual communication (lit. b)
12. What we do NOT do
We show no advertising
We do not sell or share any data with third parties for marketing purposes
We do not create advertising profiles and do not use cross-platform advertising identifiers
We do not transmit any health data, baby names, notes or input contents to analytics providers or other third parties
Microsoft Clarity records no input contents, no baby names, no amounts and no notes - all such content is masked in the app via Sensitive Data Masking
In the app we do not use Google Analytics, Firebase Analytics, Mixpanel or Amplitude - on the website, Google Analytics 4 is used for audience measurement (see Section 9). On Android, Firebase Cloud Messaging is used solely to deliver notifications (see Section 8), not for analytics.
The product events in Section 9 contain no free text - the database rejects anything not on the list given there. They show which step was reached, not what you entered
Crash reports (Sentry, see Section 9) contain no usage profiles and no contents of your entries - they document technical faults, not your behaviour in the app
13. Retention and deletion
Local data: Deleted when you uninstall the app or use the data reset function.
Cloud data: Deleted when you delete your account - baby profiles, all recorded entries, caregiver links, settings and push tokens are removed immediately. They may remain in the backend provider's technical backups for up to 30 days.
Delete account: At any time under Menu → Account → "Delete account and all data".
Individually deleted entries: When you delete a single entry in the app it disappears immediately and is marked as deleted in the cloud. That marker is required so the deletion also reaches your other devices and any caregivers - without it the entry would return on the next sync. Marked entries are permanently removed from the database at the latest when you delete your account.
Voice recordings (beta): Recordings, transcripts and corrections from voice-based entry are deleted automatically after no more than 2 months (see section 9).
Product events: deleted automatically after 90 days (see section 9). If you switch them off in the app, whatever is still unsent on your device is deleted immediately as well.
Invitations and tokens: Time- or usage-limited; invalidated immediately upon revocation.
14. Your rights
Access (Art. 15 GDPR / Art. 25 FADP)
Rectification (Art. 16 GDPR)
Deletion (Art. 17 GDPR / Art. 32 FADP)
Data portability (Art. 20 GDPR) - export as CSV, XLSX or PDF in the app
Our EU representative under Art. 27 GDPR is named in Section 2 and is based in Germany; you may contact them directly with any concern at any time.
16. Medical disclaimer
Nourli is a documentation tool and not a medical device within the meaning of the EU Medical Device Regulation (MDR 2017/745) or the Swiss Therapeutic Products Act (HMG). The app does not replace medical advice, diagnosis or treatment. For health questions about your child, please contact your pediatrician, midwife, or parent counseling service.
17. Changes
We reserve the right to update this privacy policy as needed. The current version is always available in the app and at nourli.app/en/privacy. For material changes, we will inform you actively via the app.
18. Analytics consent
On your first visit we ask, via a notice at the bottom of the screen, whether we may measure. Without your consent no analytics service is loaded - neither Microsoft Clarity nor Google Analytics. Your choice covers both together and is stored locally in your browser, so it applies per browser and device. If you clear your browser data, we ask again.
You can change your choice at any time:
The app is separate: you will find the toggle there under Menu, Privacy. It covers both the app analytics and the product events described in Section 9.
Meyer Digital · Martina Meyer · Seefeldstrasse 178 · 8008 Zurich ·