Your family’s records, with sharing when you choose it
Baby Tracker: Bottles & Growth helps adult caregivers keep bottle feeds, nappies and growth measurements together. Everyday tracking works on your iPhone without creating a Baby Tracker account.
Operator: Dave Giblin
Privacy and support contact: Dave Giblin — babytracker@launchcx.com
Policy updated: 12 October 2026
This policy covers local tracking in version 1.0.1 and the optional Shared care features in version 2.0. The Shared care sections apply only if your installed version includes those features and you choose to use them. They do not mean version 2.0 has been approved or is available in your App Store yet.
Tracking on this iPhone
The app keeps the information you enter in its protected local storage. This can include baby names, birthdays or expected dates, birth context, feeding and nappy records, notes, growth measurements, country, time zone and unit preferences. Older backups may include saved reports and original source files. The app uses these records to display your history, totals, patterns and growth charts.
If you do not enable Shared care, your tracking records stay in the app on this iPhone unless you choose to export or back them up. The app has no advertising or analytics integration and does not use care records for advertising or model training. Contacting support and visiting the support website involve the separate services described below.
Optional Shared care in version 2.0
In Settings → Shared care, you can choose a baby and start sharing. This sends that baby’s profile, family details and complete bottle, nappy and growth history, including recorded notes, edit information and entries marked as deleted, to Apple’s CloudKit service. Future supported changes are shared too. Other baby profiles, saved reports and original imported files are excluded.
The records are stored in a private iCloud area owned by the person who starts the share. That person invites another caregiver using Apple’s sharing controls. Invited caregivers can view and edit the selected baby’s shared records. There is no public-access option. Each caregiver uses their own Apple Account; do not share Apple passwords. Apple may show participants’ Apple Account identity in its invitation and sharing interface.
The app stores the care payload in CloudKit encrypted fields and keeps a local copy on each participating iPhone. Apple provides the cloud storage and sharing infrastructure. The developer’s Live Activity relay does not receive this complete care history. This policy does not promise universal end-to-end encryption across every device, backup, export and service.
Sharing needs an internet connection and working iCloud access. A record saved on one iPhone may be waiting to upload or download on another. The app shows pending changes, the last shared copy received and changes that need review. Sharing is not a separate historical backup: changes and deletions can reach both phones. Keep your own backup.
Remote Live Activities and notifications
Local bottle timers and optional reminders remain available without sharing. In version 2.0, when you use Shared care with Show on the Lock Screen enabled in Settings → Timers & notifications, a limited relay service can ask Apple Push Notification service to start, update or end a bottle Live Activity on the other caregiver’s iPhone. Live Activities are enabled by default in the app and can be switched off. Sharing itself is optional.
The relay is operated for Baby Tracker using Supabase hosting and database services in Singapore. It processes installation identifiers, device credentials, shared-room and bottle identifiers, Apple push tokens, permission and delivery information, and bottle timer state: preparation, start and deadline times, feeding status and revision. These identifiers are opaque rather than names, but they link requests and timer state to participating devices and the shared baby. They are not anonymous data.
The relay does not receive baby or caregiver names, milk type, volumes, growth measurements, notes, full care history, Apple passwords or your backup password. Its purpose is to authenticate participating devices, route Live Activities, prevent stale updates and operate the service. We do not use these records for advertising, behavioural analytics or model training.
Baby names are not included in Live Activities or nappy alerts. Remote relay messages omit milk type and amount. On-device Live Activities may show milk type and amount if you enable Show milk type and amount. Your Apple settings control notification previews and where these surfaces appear. Focus, connectivity and iOS delivery limits can delay or suppress alerts; they are not a guaranteed monitoring service.
Shared nappy notifications are optional and off by default. You can enable them under Settings → Shared care → Nappy notifications. Apple’s CloudKit notifications use an entry marker and show a generic pee or poo message, without the baby’s name or notes. Ordinary bottle reminders are scheduled locally through iOS. Notification permission is requested when you choose to enable an alert feature.
Relay retention and controls
Switching off Live Activities stops new remote starts on that iPhone and clears its registered activity tokens; it does not delete the shared iCloud history or all relay authorization information. Use Stop sharing as owner or Leave shared baby as an invited caregiver to end that shared access. If the app reports a connection or disconnection error, retry when online.
The relay cannot check Apple’s sharing permissions directly. The owner’s app checks participants with iCloud and renews remote-activity authorization for up to 24 hours. If access changes outside the app, a removed caregiver may continue receiving minimal bottle timer updates until the owner’s app detects the change or the existing authorization expires. Open the owner’s app and refresh Shared care after changing participants. Revocation cannot retract a notification or Lock Screen content already delivered; iOS controls how long that content remains visible.
The relay uses an hourly cleanup schedule. Activity-update tokens that have not been refreshed for 24 hours are removed; inactive device start tokens are cleared after 24 hours. Stored active timer state is eligible for removal one hour after its deadline, and short-lived markers used to prevent duplicate starts or finished bottles restarting are eligible after 48 hours. Failed activity updates and endings can be retried using the retained token and current timer state, with retry counts and scheduling times kept alongside the token. Hashed security rate-limit counters are eligible after two hours. Cleanup runs periodically, so these are eligibility thresholds rather than a promise of deletion at the exact minute.
Stopping a share clears its push tokens and active timer state and disables its registered devices. Leaving a share clears that installation’s push tokens. Opaque room/device authorization records and revocation markers are retained for reconnection and to prevent an old invitation from restoring revoked access; they do not have a fixed automatic deletion period. Contact us about retained service information. Provider infrastructure logs and backups have their own retention and deletion arrangements, and are not covered by these application-table cleanup periods. Infrastructure may process IP addresses and request metadata to deliver and secure the service.
Backups and exports are your choice
Settings → Backup & export lets you save readable CSV/JSON files or a password-encrypted .mayabackup file to a destination you choose. The app does not send the file or backup password to the app operator. CSV and JSON are readable files: anyone with access to them can read their contents. Files you save with or share through another service follow that service’s terms and privacy practices.
You can import an encrypted backup or complete JSON export from the app before or after setup. The app lets you review the profiles and additions and keeps existing records. The import is processed on this iPhone. An original source file preserved with an import may include information that the tracker cannot display; it remains available under Original imported files and may be included in later complete exports or backups. Original imported files are not part of Shared care.
The app’s working local record store is excluded from device backup. Shared care synchronizes the selected shared baby; it is not automatic backup of every local baby, report or imported file. Deleting the app or losing the phone can lose records that exist only locally or have not finished sharing. Keep a current encrypted backup outside the app and its password separately. A file stored only on the same phone does not protect against losing the phone. We cannot recover a forgotten password, missing backup or lost local records.
Keeping, leaving and deleting records
Deleting an individual entry hides it from normal history, but a copy marked as deleted remains in the store and in exports/backups, and is synchronized for a shared baby. This prevents older copies from restoring a deleted entry.
In version 1.0.1, Settings → Delete records from this iPhone clears the local record store. In version 2.0, use Settings → Reset this app to review the local reset and shared-room options. A local reset removes the app’s local record store, including imported source files and saved reports; it does not by itself delete the owner’s iCloud room. The owner can use Shared care → Find or manage rooms to delete an owned iCloud room. Read the confirmation for the option you select and save a backup first if needed.
The owner can manage invitations or stop sharing; an invited caregiver can leave. Ending shared access prevents future access through that share, but cannot erase records another person has already downloaded, copied or exported. Stopping sharing does not by itself delete the owner’s private iCloud room. Delete independently saved backups, exports and other copies separately. Appearance and other device preferences are separate from baby records. There is no separate Baby Tracker sign-in account to delete; your Apple Account is managed with Apple.
When you contact support
Support is handled personally by Dave Giblin. Email sent to babytracker@launchcx.com is forwarded to Dave’s personal mailbox, where he reads and replies to it. The services that deliver, forward and store email process the message as part of that service.
If you choose to contact support, your message may include your name, email address, description of the issue and any attachments. We use that information to reply and investigate the reported problem. Please send only what is needed. Do not send your Apple password, verification codes, backup password or a full baby-record export. Remove personal details from screenshots. Support email is separate from the records stored inside the app; contacting us does not give us access to your app’s record store.
How long support information is kept
From this policy’s effective date, our support-retention policy is to keep a conversation while the issue is open and for necessary follow-up, for up to 12 months after resolution. We delete it sooner when it is no longer needed. We remove unnecessary baby records and sensitive attachments promptly. If an attachment was needed to investigate an issue, we delete it within 30 days after resolution, unless an identified continuing need requires it.
A specific legal obligation, dispute or other documented continuing purpose may require a limited exception. In that case, we keep only the information needed for that purpose and review the need until it ends. We review the working support mailbox monthly, including sent mail and deleted-item folders.
These time limits apply to support copies under our control. Deleting a message from the working mailbox may not immediately remove an email provider’s technical logs or backup copies; those are governed by the provider’s own retention and deletion arrangements. We do not promise that every provider copy disappears immediately.
Support websites and other services
We have not added a contact form, advertising, analytics tools or cookie-based tracking to these public support and privacy pages. Our website hosting providers may process technical information, such as IP addresses, browser information and requests for pages, to deliver, secure and operate their services. Their technical-log retention periods are separate from the support-email policy above and are governed by their own service terms; no fixed period is promised here.
Opening a source, privacy or support link uses your browser. The app does not attach baby records to those links. Email and hosting services may process information in other countries as part of their operation; their processing locations, safeguards and retention arrangements are governed by the relevant service terms and settings. Shared care and the Live Activity relay are described above; other local records are not attached to these links.
Apple handles App Store transactions and payment information. The app does not receive your payment-card details. Apple’s optional diagnostics and any file-storage provider you choose operate under their own settings and privacy policies. This policy does not claim that those separate services process no data.
Privacy requests and changes
You can view, edit and export available records in the app. We cannot recover your local record store, Apple Account or forgotten backup password. For questions about shared access, retained relay information or information you sent to support, email babytracker@launchcx.com, addressed to Dave Giblin. Include the app version and the nature of the request without sending unnecessary baby records, passwords, private invitation links or device credentials.
Apple, Supabase, email providers and website hosting services may process information in countries other than your own. The relay database region is Singapore; other processing locations, safeguards, infrastructure logs and backups depend on the relevant service and its settings. We will update this policy when the app’s data handling changes and show the new date.