Nurtlina: Baby Feeding Tracker
Data safety overview
Last updated: 18 August 2026
This page is a plain-language transparency summary. The current production build and third-party SDK behavior must also be reflected accurately in the Google Play Data safety form.
| Data category | When | Purpose |
|---|---|---|
| Baby and care records | Entered locally; sent off-device when backup/sync is used | App functionality, backup, sync, export |
| Email, display name, account ID | Google sign-in | Authentication, account and family management |
| App interactions and coarse usage metrics | Firebase Analytics | Analytics and product improvement |
| Crash and device/app diagnostics | Firebase Crashlytics | Reliability and troubleshooting |
| Purchase and entitlement information | Google Play / RevenueCat | Payments, Pro access, restore purchases, fraud prevention |
| Device or advertising identifiers, IP address, ad interactions | AdMob for eligible Free users | Advertising, measurement, fraud prevention |
Key practices
- Core care logging works locally and does not require the network.
- Data is encrypted in transit when sent to connected services.
- Baby names and note text are not sent as analytics events.
- Synced baby care records are not used for advertising targeting.
- Account deletion is available in-app and through an external request.
- Nurtlina requests no location, contacts, camera, or microphone permission.
User controls
You can deny notification permission, disable reminders, sign out, delete individual records, export supported records, or delete your account and associated data. See the Privacy Policy for details.