Privacy Policy for Napling

Last updated: October 31, 2026

What we collect

Your baby's logs: we don't receive them. Napling lets you log feeds, naps, and pumping, add one photo of your baby, and enter a birthdate (used for age-based nap-window guidance). We cannot see those entries, the birthdate, or the photo — they stay on your device and in your own private iCloud, and are never sent to our server.

Separately, Napling sends two kinds of data to a server we operate:

• Usage analytics (on by default; you can turn them off in Settings) — a short list of events described below. These are pseudonymous: they are tied to a random ID, not your name, but they are not strictly anonymous.
• Feedback you send — only if you open the feedback form and tap send.

Usage analytics

Napling sends pseudonymous, on-by-default usage analytics to a server we operate. The events are:

• app_open — with a flag for whether it was a cold start
• first_launch
• purchase — product id, App Store transaction id, and whether it was a purchase or a restore
• paywall_view — where the paywall was shown from
• feature_used — the name of a feature or action, such as feed_logged, pump_logged, nap_started, or nap_ended
• error — an error domain and a numeric code
• opt_out — recorded when you turn analytics off

Alongside each event we record the time it happened and a random ID generated on your device when you first install the app — not an Apple device identifier and not shared with any other app — plus app version, iOS version, device model (e.g. "iPhone16,2"), language, and your 2-letter country.

Care actions are included, in a limited way. Events such as feed_logged, pump_logged, nap_started, and nap_ended are sent with a timestamp, so the timing of when you log these actions is sent to us. They carry no amounts, notes, names, birthdates, or photos — and never the content of your baby's logs — but over time the timing of logging actions can reflect a daily routine.

Because purchase events include the App Store transaction ID, the analytics data is pseudonymous rather than anonymous: that ID could in principle be tied to an App Store purchase. We do not use it to identify you.

We do not store IP addresses in our application; an IP is hashed with a key that rotates daily, used only to rate-limit abuse, and then discarded. Analytics never goes to an ad network or an analytics SDK. Nothing is sold.

You can turn analytics off at any time in the app's Settings. Opting out stops new events from being sent and asks our server to delete what it holds for your install. Using "Delete My Analytics Data" in Settings deletes the events, install record, and purchase records we hold for your install from our server. It does not remove copies of feedback already posted to Slack (see below).

Feedback you send

Napling has an optional feedback form. If you send feedback, we receive the message text you wrote, the app version, and the iOS version. Please don't include your baby's name or health details. Feedback is sent to our server, stored for 180 days, and a copy is posted to a private channel in Slack, which we use to read it. It is not linked to the random analytics ID. We can't reply from within the app. To have your feedback deleted, email us at the address below.

How long we keep data

• Raw analytics events: 90 days
• Per-install summary (device model, locale, country, number of app opens, whether the app was purchased): 13 months
• Purchase records, including the App Store transaction ID: 25 months
• Feedback: 180 days on our server. Copies posted to Slack are kept under our Slack workspace's settings and are not removed when you delete your analytics data.

Service providers

• Railway hosts the server that receives analytics and feedback.
• Slack receives a copy of each feedback message so we can read it.
• Apple provides iCloud/CloudKit (sync and sharing) and the App Store and StoreKit (purchases). Apple's handling of this data is described in Apple's own privacy policy.

Data sent to our server and to Slack may be processed in the United States.

Where your data lives

• On your device. Feed, nap, and pumping entries, your baby's birthdate, and the baby photo are stored locally on your iPhone.
• In your iCloud. If you are signed in to iCloud, Napling syncs your data through Apple's CloudKit to your private iCloud database — storage that belongs to your Apple account, protected by Apple, and inaccessible to us.

Sharing care with a partner or caregiver

Sharing is free. When you invite a partner, grandparent, or other caregiver to co-track your baby, Apple's CloudKit sharing sends an invitation to the people you choose. Only invited participants can see the shared data, and sharing never passes through any server of ours.

• Participants can see each other's Apple ID name or email address through Apple's share interface.
• Participants get read-write access to the shared baby's records: they can add, edit, and delete entries.
• You can stop sharing, or remove a participant, at any time from the app's share settings. This stops future syncing, but it may not remove data already on that person's device.

Photos

When you add a photo of your baby, Napling receives only the photo you explicitly pick — it has no access to the rest of your photo library. The photo is stored and synced the same way as the rest of your data: locally, and through your own private iCloud if enabled. It is never sent to our server.

Children's Privacy

Napling is intended for use by parents and caregivers to track information about their children, not for use by children themselves. We do not knowingly collect any data directly from children. Napling has no advertising and no social network or messaging features; the only person-to-person feature is the invite-only caregiver sharing described above.

Changes to This Privacy Policy

If a future feature ever changes any of the above, this policy will be updated before that feature ships, with the effective date revised.