Baby Tracks

1. Who we are

Baby Tracks is developed and published by Cloud Heavy Industries Limited, a company registered in England and Wales with company number 17012201. In this policy, “we”, “us”, and “our” mean Cloud Heavy Industries Limited.

Questions about this policy can be sent to support@cloudheavyindustries.co.uk.

2. No Baby Tracks account

Baby Tracks does not ask you to register an account with Cloud Heavy Industries Limited. We do not operate an identity service or maintain a developer-held family profile.

If you enable iCloud sharing, each participant needs an Apple Account with iCloud enabled. Apple uses that account to authenticate access to the private CloudKit share. We do not receive the participant’s Apple Account password or payment-card details.

3. Information you can store in the app

You choose what to enter. Depending on the features you use, Baby Tracks can store:

• child profile information, such as names, dates of birth or due dates, sex, notes, measurements, profile colours, and photos;
• care records, such as sleep, feeding, pumping, nappy or potty, growth, activity, milestone, note, and photo entries;
• details inside those records, including dates and times, amounts, durations, observations, captions, and free-text notes;
• reminders, schedules, active timers, reporting preferences, units, regional terminology, themes, and other app settings; and
• household sharing details, such as caregiver names, email references, roles, invitation status, and CloudKit share metadata.

This information may be sensitive. It can include personal information about a child, caregivers, routines, feeding, growth, and other health-related observations.

4. Where app data is stored

Local storage

Baby Tracks stores its working database on your device using Apple’s native data-storage technologies. The app is local-first: records are created and remain available locally without a Baby Tracks server account.

Optional iCloud sync and sharing

If the household owner enables iCloud sharing, Baby Tracks stores the shared household in that owner’s private CloudKit database. Records made available to invited caregivers appear through each accepted participant’s shared CloudKit database.

Baby Tracks does not use CloudKit’s public database for household care data. Apple states that private and shared CloudKit database records are not visible to the app developer through the CloudKit developer portal. CloudKit data is subject to your iCloud settings, storage allowance, security, and Apple’s terms.

Cloud Heavy Industries Limited does not operate a separate server that receives or stores a duplicate of your child profiles, logs, photos, schedules, or household history.

5. How private sharing works

The household owner decides whether to enable iCloud sharing and whom to invite. Apple’s CloudKit sharing service handles the invitation and participant access.

Accepted participants can see shared household data and may be able to add, change, or delete certain records according to their Baby Tracks role and the CloudKit permissions applied to the share. Changes are then synchronised through iCloud to participating devices.

The owner can manage participants or stop sharing. A participant can leave the share. Removing access stops future CloudKit access, but it cannot make another person forget information they already saw or remove copies they independently exported or saved. Invite only people you trust.

6. On-device calculations and planning

Reports, summaries, wake-window estimates, and routine-planning suggestions are calculated on the device from the data available in the app. The planned launch version does not send care records to a remote artificial-intelligence provider.

These features support record keeping and routine planning. They do not provide medical advice, diagnosis, or treatment and are not a substitute for a qualified healthcare professional.

7. Photos, notifications, app lock, and widgets

Photos

When you choose a profile or care-log photo, Apple’s system photo picker gives the app access to the item you select. The selected image becomes part of the local record and, if iCloud household sharing is enabled, can be included in that private share.

Notifications

Baby Tracks asks for notification permission only when you enable a feature that needs it. Local reminders are scheduled by the operating system. iCloud may also deliver background CloudKit change notifications so shared records can update; these do not send care-log content to a Cloud Heavy Industries server.

App lock

If you enable app lock, authentication is performed by iOS using Face ID, Touch ID, or the device passcode. Baby Tracks receives only the result of the authentication attempt. We do not receive or store biometric information.

Widgets and Live Activities

If you add a widget or use a Live Activity, selected recent-care and active-timer information is made available locally to those system surfaces. Anyone who can see your unlocked device or its configured notification previews may be able to see that information.

8. Imports, exports, and files you share

Baby Tracks can prepare CSV and JSON files, PDF reports, and other user-initiated exports. The app shows a warning before preparing exports that may contain sensitive child and household information.

Exported information leaves the app only when you choose a destination using Apple’s share sheet, file picker, or another system feature. From that point, the destination service, recipient, or storage provider controls its copy under its own privacy terms. Store backup files securely and share them only with people you trust.

When you import a file, Baby Tracks reads the file you select to show a preview or restore data on your device. The app does not upload the imported file to us.

9. Information we do not collect from normal app use

The planned launch version of Baby Tracks does not:

• use third-party advertising, analytics, attribution, or cross-app tracking SDKs;
• collect advertising identifiers;
• profile families for advertising or sell child or household information;
• send care logs, child profiles, or photos to developer-operated servers;
• use a third-party crash-reporting SDK; or
• make private or shared household records visible through Apple’s CloudKit developer portal.

Apple may process technical and account information needed to provide iCloud, notifications, App Store distribution, and device services under Apple’s Privacy Policy.

10. Support correspondence

If you contact us, we receive the information you choose to send, such as your email address, message, app version, device type, diagnostic text, or an attachment. Do not send a child’s care database, photos, full export, passwords, payment-card information, or Apple Account credentials unless we specifically explain why a limited item is needed and you decide to provide it.

We use support correspondence to answer your request, troubleshoot problems, prevent abuse, and improve the app. Our lawful bases under UK data-protection law are performance of a contract or steps at your request, and our legitimate interests in supporting and securing the app. We keep correspondence only for as long as reasonably needed for those purposes and any applicable legal obligations.

11. Retention and deletion

Local app data remains on a device until it is deleted in the app, replaced by a restore, or removed with the app, subject to device backups and operating-system behaviour.

Data stored through iCloud remains subject to the household owner’s iCloud settings and actions. The owner can stop sharing and can manage Baby Tracks data through the app and Apple’s iCloud storage controls. Participants can leave a share. Files you export remain wherever you or a recipient saved them until deleted there.

Because we do not hold a developer-hosted Baby Tracks profile or care database, there is normally no copy of your app records for us to access, correct, export, or delete on your behalf.

12. Children’s privacy

Baby Tracks is intended for parents, guardians, and other adult caregivers. It is not directed to children and does not allow a child to create an account with us.

Adults using the app are responsible for deciding what information about a child to enter, who to invite to a household, and whether an export or photo should be shared.

13. Your data-protection rights

Data-protection rights can include access, correction, deletion, restriction, objection, and portability, depending on the circumstances and applicable law.

For app records held only on your device or in your private or shared iCloud databases, those records are not held in a developer system that we can search or change. You control them through Baby Tracks, the participating devices, the household share, exports, and your Apple Account settings.

For personal information we do hold—for example, a support email—you can contact us to exercise applicable rights. You may also complain to the UK Information Commissioner’s Office through ico.org.uk.

14. Security and limitations

Baby Tracks uses Apple platform security, local data protection, device authentication when app lock is enabled, and private/shared CloudKit access controls when iCloud sharing is used. No system can guarantee absolute security.

You can reduce risk by using a strong device passcode, enabling app lock, protecting your Apple Account, reviewing notification-preview settings, keeping devices updated, inviting only trusted caregivers, and storing exports securely.

15. Changes to this policy

We may update this policy to reflect changes made before release, new app features, legal requirements, or App Store disclosures. The revised policy will be posted on this page with a new “Last updated” date.

16. Contact us

For privacy questions, email support@cloudheavyindustries.co.uk or visit the support page.

Cloud Heavy Industries Limited is registered in England and Wales. Company number 17012201.