Effective August 25, 2026 — covering the Small Baby Care iPhone app, its Apple Watch companion, and its Home Screen Widgets.
This Privacy Policy describes how Small Baby Care — including its iPhone app, its Apple Watch companion app, and its Home Screen Widgets and Live Activities (together, "Small Baby Care," referred to throughout the rest of this policy as "Baby," "the App," "we," "us") — handles information. It applies to anyone who downloads or uses Baby ("you").
Baby is developed and published by Small Logix LLC, the developer of record with Apple's App Store. If you have questions about this policy or how Baby handles information, see Section 19, Contact Us.
We believe a privacy policy should be honest about what actually happens in the software, not a generic template. Here is the complete, literal picture as of this version of Baby:
The rest of this document explains this in the detail Apple's App Store guidelines, and good practice, expect.
All of the following is entered by you, stays on your device — and for certain items, is relayed directly between your iPhone and your own paired Apple Watch, never to us — and is never transmitted off your devices:
Name, date of birth, sex, an optional profile photo, and an optional theme color for each child profile you create.
Entries you choose to log, spanning: sleep sessions, feedings, diaper changes, growth measurements (weight, length, head circumference, and the percentile calculated from them), mood entries, medication doses and courses, medical notes, appointments (including any location you type in — addressed in Section 6), and milestone events, including any photo or note you attach to a milestone.
If you attach a photo — a child's avatar or a milestone memory photo — it's saved as a file on your device, encrypted with Apple's strongest on-device file-protection class, so it becomes unreadable the instant your device locks. It is never uploaded anywhere by Baby. Section 5 covers how the Camera and Photo Library are involved in capturing it.
App preferences you set, such as whether reminder notifications are turned on, are stored locally the same way.
Information you enter is used for exactly one purpose: to power the tracking, charts, reminders, and summaries you see inside Baby, for your own household's use. It is never included in an ad request, never used to build an advertising profile, is not analyzed by us in aggregate — we have no way to see it at all — and is not used for any purpose beyond showing it back to you inside the app.
Baby can request two pieces of system permission, both entirely under your control and both used only when you actively choose to add a photo:
| Permission | When it's requested | What Baby can actually see |
|---|---|---|
| Camera | Only if you tap "Take Photo" for a child avatar or milestone memory | The single photo you capture in that moment. Baby cannot access your camera at any other time. |
| Photo Library | Only if you tap "Choose from Library" | Baby uses Apple's system photo picker (PhotosPicker), which runs outside the app. Baby only ever receives the specific photo you tap to select — it is never granted access to browse, list, or read the rest of your photo library. |
Separately, when you choose to share or save a photo from within Baby, that action goes through Apple's own system Share Sheet, which can save a copy to your Photos app on your instruction. That save is performed by the operating system at your explicit request, the same as it would be from any other app's share sheet — Baby does not read your photo library to do this and requests no standing library-write permission.
When you type an address or place name into an appointment's location field, Baby uses Apple's MapKit address-lookup service to suggest matching addresses and to show a small map preview — the same technology behind the location field in Apple's own Calendar app. The text you type is sent to Apple to perform that lookup, governed by Apple's own privacy policy, not this one.
Baby does not request, access, or store your device's actual location at any time. This feature only ever processes an address you deliberately type, for the appointment record you're creating.
Baby shows a small banner ad, served through Google's Mobile Ads SDK (AdMob). This is a genuinely separate category of data from everything described elsewhere in this policy: your child's tracking data is never included in an ad request, never seen by Google's ad-serving systems, and never used to select which ad you're shown. Your tracking data (100% local, described throughout this policy) and ad-serving technical data (described here) never touch each other.
To serve and measure an ad, Google's SDK sends a request that can include technical information such as your device's advertising identifier (if available and permitted), IP address, general device information, app version, and ad interaction data (for example, that an ad was shown or tapped). This is governed by Google's own Privacy Policy, not this one — Baby itself never receives or stores this information; it passes directly between your device and Google.
Baby serves ads through a real AdMob ad unit under Small Logix LLC's own AdMob account. Baby does not request App Tracking Transparency (ATT) authorization, so ads are served on a non-personalized, contextual basis by default rather than using cross-app tracking identifiers. Baby's AdMob configuration reflects its actual audience and design: it is set up as an app that is not child-directed and does not enable under-age-of-consent tagging, because Baby is built for, marketed to, and operated by adult parents and caregivers — see Section 12 for the complete analysis.
Reminders — for upcoming appointments, medication doses, sleep/feeding predictions, and birthdays — are scheduled entirely on your device using Apple's local notification system. Baby does not use push notifications, has no notification server, and never generates or transmits a device push token. You can turn reminders off at any time from within Baby's own settings, in addition to iOS's system-level notification controls.
Baby stores your data using Apple's SwiftData framework, on-device, inside an App Group container — a private storage area shared only between the Baby app and its own Home Screen Widget and Live Activity extension, so your dashboard, widget, and lock-screen activity can all show current information. This container is not shared with any other app on your phone, and is never synchronized to iCloud or any other service by Baby.
Your Apple Watch, if you use the companion app, keeps its own independent local data store on the Watch itself — deliberate, so the Watch app keeps working even out of range of your phone. Actions you log on the Watch are relayed directly to your paired iPhone over Apple's on-device Watch Connectivity framework: a direct device-to-device relay between your own two devices, not a transmission to us or to any server.
Photos are additionally protected with Apple's strongest file-encryption class, becoming cryptographically unreadable the moment your device locks. Your general app data uses the standard protection every iOS app sandbox receives automatically, keeping it unreadable after a restart until you first unlock your device — deliberately balanced so your Home Screen Widget and Live Activity can still show current information at a glance without requiring an unlock, while your data stays protected against the realistic risk of a lost or powered-off device.
We do not sell your tracking data. We do not share your child's profile or any tracking entry with advertisers, data brokers, or analytics companies, and we have no technical ability to access, view, or export that data ourselves, because it never leaves your device to reach us. The outside parties involved in any part of Baby's operation are Apple, in its role as the maker of the operating system and frameworks Baby is built on (see Section 6 regarding address lookups), and Google, solely for serving the ad banner described in Section 7 — neither receives your tracking data. Installing Baby at all necessarily involves Apple's App Store and operating system, governed by Apple's own privacy terms.
We may disclose information if required to do so by law — for example, in response to valid legal process — but because Baby is not designed to give us access to your data in the first place, we would generally have nothing responsive to produce.
Baby is a tool for parents and caregivers to track information about their own child — it is operated by the adult caregiver, not by the child. This section explains, in detail, why Baby's design places it outside what U.S. and comparable children's-privacy frameworks regulate, and how that stays true even as Baby's feature set grows.
Under the U.S. Children's Online Privacy Protection Act (COPPA) and the FTC's implementing rule, obligations toward children under 13 attach to an operator in two situations: when a service is "directed to children," or when an operator has actual knowledge it is collecting personal information from a child under 13. Baby is neither.
Whether a service is "directed to children" turns on its actual audience and design, not merely on whether children are its subject matter. Baby's interface, onboarding, marketing, and every functional feature are built entirely around the adult parent or caregiver: an adult sets up each child's profile, logs every entry, reads every chart, and manages every notification and setting. There is no child-facing account, no character, game mechanic, or content designed to appeal to or be operated by a child, and Baby is not marketed to children in any respect. A record-keeping tool an adult uses to track information about their child is a materially different category — under COPPA and under the platform policies of both Apple and Google — than a game or content service built for a child to use directly.
COPPA's second, independent trigger — actual knowledge of collecting personal information "from" a child — likewise does not apply. Every field, entry, and interaction in Baby is performed by the adult user; a child is never asked for, and never submits, any information to the app. Baby has no chat, comment, sharing, or messaging feature through which a child could transmit anything to us or to any third party, and a child never creates an account, opens a session, or interacts with Baby's advertising SDK. The parent or caregiver is the sole source of everything entered into the app, including a child's own profile information.
Baby's one advertising integration (Section 7) is served to, and only interacted with by, the adult using the app. Consistent with Sections 12.1–12.2, Baby is configured within Google's Mobile Ads SDK as an app that is not child-directed and does not enable "under the age of consent" request tagging — the accurate reflection of Baby's actual audience. Ads are non-personalized and contextual by default (Baby does not request App Tracking Transparency authorization), and are never selected, targeted, or informed by any information about the child being tracked, because that information never reaches Google's advertising systems in the first place.
Baby's architecture keeps this analysis close to its simplest form: every piece of information about your child stays on your own device and your own paired Apple Watch. There is no account, no server, and no third party — including us — with any technical means to access it. The one exception, Google's ad-serving data (Section 7), is a wholly separate technical data flow that never includes, and is never combined with, anything about your child.
A future version of Baby may let a parent share a child's profile and tracking history with other adult caregivers they explicitly invite — for example, a co-parent or grandparent — so a household can coordinate care together (Section 15). That feature, if and when it ships, stays within the same closed model: information is shared only with the specific adult caregivers a parent chooses to add to their own child's profile, never with the child as a participant, never publicly, and never with advertisers or data brokers. Extending sharing to a small, parent-controlled circle of caregivers does not change Baby's status under this section — the audience remains the adults responsible for the child, not the child.
Newer state and international children's-data frameworks sometimes ask whether a service is "likely to be accessed by" a child, a broader test than COPPA's "directed to." Baby's real and intended user base — adult parents and caregivers managing their own household's care-tracking — is the controlling fact under essentially every framework in this space, for the same reasons set out above. This analysis reflects Baby's design as of this policy's effective date; if a future feature changed that picture — for example, adding anything a child could use directly — this policy would be updated accordingly.
Baby tracks information that relates to a child's health and development — sleep, feeding, growth percentiles, mood, medication doses, and medical notes. Baby is a personal record-keeping and informational tool for a parent's own use; it is not a medical device, does not provide medical advice or diagnoses, and any guidance or reference ranges shown in the app — such as growth percentiles or sleep and feeding guideline ranges — are general informational references, not a substitute for advice from your child's pediatrician.
Baby is not operated by a healthcare provider, health plan, or healthcare clearinghouse, and does not transmit health information to any such entity — accordingly, the U.S. Health Insurance Portability and Accountability Act (HIPAA) does not apply to Baby's handling of your data. Because your health-related entries are stored only on your own device and never transmitted anywhere, there is no server-side health data set for any third party — including us — to access.
Small Logix LLC and its personnel are not licensed medical, health, or childcare professionals acting in that capacity through Baby. Nothing displayed by the app — including growth percentiles, predicted sleep or feeding times, medication reminders, or milestone ranges — is a diagnosis, a treatment plan, or a recommendation specific to your child, and none of it should be treated as a substitute for the judgment of your pediatrician or another qualified healthcare provider. You are solely responsible for the decisions you make about your child's health, care, and development. If you ever have a health or safety concern about your child, contact your pediatrician or emergency services directly rather than relying on anything in the app. To the fullest extent permitted by law, your use of Baby and any information it displays is at your own risk.
Baby retains your data locally for as long as you keep the app installed, or until you delete individual entries yourself. Because there is no server, there is no separate retention period, backup, or copy kept anywhere by us after you delete something or delete the app — deletion on your device is complete and immediate.
Baby's current architecture is deliberately local-only. If a future version introduces the ability to share a child's profile and tracking history with other adult caregivers you invite (Section 12.4), optional cloud backup, or both, that version will only be released alongside an updated Privacy Policy describing, in specific detail, what would be shared or transmitted, with whom, where it would be stored, how it would be protected, and what choices you'd have — before that update reaches you. Nothing in a future version will silently change how your data is handled under this policy.
Because Baby does not transmit your data anywhere, using Baby does not involve any cross-border transfer of your data by us — your information simply stays on the device in your hand, wherever that is.
Baby relies on Apple's platform security — device encryption, sandboxing, and, for photos, complete file protection as described in Section 9 — to protect your data at rest. No local storage or software can guarantee absolute security in every circumstance (for example, a device that is stolen and unlocked by someone who already knows or has extracted your device passcode), but because Baby has no network transmission of your tracking data at all, the most common risk category for a typical app — data intercepted in transit, or stolen from a server — does not apply to the data described in Sections 1 through 6.
We may update this Privacy Policy as Baby changes. If we do, we'll update the effective date at the top of this page and, for any change that meaningfully affects how your data is handled, describe that change in the App Store release notes for the version that introduces it. Because Baby has no accounts or email addresses on file, we have no way to email you directly — please check this page from time to time, particularly before updating the app, if you'd like to stay current.
Questions about this Privacy Policy or how Baby handles information can be sent to:
privacy.smallbaby@smalllogix.com