My Little Days

Privacy policy

Effective date: 18 October 2026

On this page

Who we are

My Little Days is operated by Reticle Information Technology Pty Ltd. Contact us about support or privacy at contact@reticle.com.au.

The app is intended for parents and caregivers recording information about a child in their care. Please provide and share only information you are authorised to handle. The child does not need an account.

Personal records on your device

You can use personal record-keeping without signing in. The app stores your baby's profile, records, selected photo, reminders and play information locally; these are not automatically uploaded to our family service. Language, appearance and view preferences also stay on the device.

Signing in uses our authentication service, but signing in alone is not consent to upload an existing personal history. Initial family sharing requires the create/join confirmation. Signing back into an account already in a family restores that account's family access after verification.

Optional AI sleep suggestions

When available in your app, AI sleep suggestions require sign-in and separate consent. In version 0.2.3 (build 74) and later, Records → Sleep guidance provides an AI consent link with the sharing details. Choosing Enable AI gives that consent and enables AI with one tap, without a confirmation popup. The same button becomes Turn off AI while enabled. Signing in, joining a family or recording sleep does not by itself enable AI sharing. You can continue recording and viewing your history without enabling this feature.

After you enable it, the app sends the baby's age in days, time zone, current time, and sleep and feeding records for the previous seven complete local dates, excluding today, plus today up to the current time to our server. These records include start/end times, whether a timer is still running, feeding type and bottle milk amounts. A sleep period crossing the start of that date range retains its original start time. Our server sends these fields and the date boundaries used for the requested suggestions to OpenAI, which generates predicted sleep periods and windows in which to begin settling.

The app calculates age from the date of birth on your device; the full date of birth is not sent for an AI request. Names, photos, notes, growth measurements and other care records are not included. Our server uses your signed-in account and, where applicable, family membership/history identifiers to check access; those identifiers, record identifiers and breastfeeding side are not sent to OpenAI. Removing direct identifiers does not make detailed child sleep and feeding records anonymous.

TestFlight version 0.2.4 (build 77) requests predictions only for the remaining time until the next local midnight; older version 0.2.3 requests a plan for the whole current local day. Saved sleep records remain authoritative and are displayed separately. The separate AI consent also covers this context: the most recent accepted AI plan for that same day, including its generation time and sleep/settling times. When available in the current account, baby and time-zone context, this previous plan is sent through our server to OpenAI with updated records. It is context for a new estimate, not a new observed record. It is not reused after the day, account, baby, time zone or consent context changes.

While AI is enabled, opening the app or relevant view, or adding, editing or removing relevant sleep/feeding records can request updated suggestions, including starting or ending a timer. Version 0.2.3 updates automatically after relevant changes or a new local day, without a manual refresh button. Earlier builds may also offer Refresh AI suggestions. Normal family synchronisation, if enabled separately, is unchanged. AI suggestions are uncertain routine information, not medical advice or a guarantee of the best time to sleep.

Resumable AI tasks in version 0.2.3: after separate AI consent (renewed if an earlier consent did not cover temporary task storage), our existing server database temporarily stores the minimised request described above, its task status and its result. This allows generation to continue when you switch apps and lets the app reconnect to the same task. This AI-only storage does not create or change your recorded family history. The request contents, including any previous-plan context, are cleared when the task finishes, fails or is cancelled. Results expire at the next midnight in the request's local time zone and cannot then be retrieved. An hourly cleanup removes expired task rows in bounded batches; outages or a backlog can delay physical removal. Minimal cancellation and usage-limit records, without sleep/feeding contents or predictions, are eligible for cleanup after 48 hours. Database backup copies follow the backup retention described below; removal from the active database is not immediate removal from backups. Earlier synchronous versions do not save AI request contents or results to this task storage.

The device saves a task identifier and minimal matching information so it can reconnect after restarting. It does not add a second persistent copy of the submitted sleep/feeding records or AI forecast to this recovery information. Current builds no longer show the temporary AI debug panel included in some earlier TestFlight versions.

Choose Turn off AI in Records → Sleep guidance to stop future AI requests and clear the suggestions on that device, including previous-plan context. For resumable tasks, the app also requests cancellation and removal of the corresponding server results; if offline, it saves that request and sends it when it can reconnect. Work already sent to OpenAI cannot be recalled. Your saved records are not deleted. If the app reports that the off setting could not be saved, use Retry saving the off setting; stopping the current session's requests does not establish that the choice will persist after an app restart. The choice applies to the current account and baby context on that device, not automatically to other family members' devices.

Failed AI response diagnostics: starting with the 18 October 2026 service update, newly created resumable AI tasks automatically retain failed response attempts and their failure details in our restricted server database to investigate errors, including an unsuccessful attempt followed by a successful retry. This applies to existing clients of the resumable AI service without an additional app update or a separate diagnostics prompt. These records can include response text, sleep or feeding times contained in that response, the failure reason, model, processing duration, and the limited account/task information needed for access control and deletion. They are private data, not anonymous telemetry. Successful responses are not copied into diagnostics, and we do not additionally retain the submitted input history or prompt for this purpose. Diagnostics are not written to ordinary application logs or sent to an additional AI provider.

Failed-response diagnostics expire seven days after the failure and are then unavailable for diagnostic inspection. The hourly cleanup removes expired rows; an outage or cleanup backlog can delay physical deletion. Once connected, turning off AI also clears the corresponding failed-response diagnostics. Account deletion and loss of the relevant family access also clear them. Database backup copies follow the separate backup retention described below. This seven-day diagnostic retention is separate from resumable task storage: request contents are cleared when the task ends, and ordinary task results expire at the next local midnight. AI remains optional; these diagnostics do not enable AI or upload records for people who have left it off. Previously uncaptured failures cannot be recovered.

Information used for optional family sharing

When you use account and family features, the service processes:

We use this information to authenticate you, provide shared records and reminders, control family access, synchronise changes and support the service. Health and care information may be sensitive even when the app is used only as a diary.

Creating a family uploads the information you review and confirm. After successful upload and local saving of the family data, the original personal data and recovery copies are cleared. Joining a family instead downloads and verifies the family's data, then replaces your personal data and recovery copies; your old personal history is not uploaded or merged. Export important personal information before either transition.

Who can see shared information

All active family members can see the family's records and download confirmed server data. Members can edit or delete their own records; the administrator has broader record-management permissions and controls shared profile/play settings. Administrators can remove members without advance notice.

Leaving, removal or signing out does not withdraw contributions already accepted by the family service. An offline device cannot detect a new access restriction until it reconnects. Once detected, the app clears the relevant family cache, drafts and unsent changes. Other members may already have exported copies; the app cannot recall those files.

Photos, reminders, Watch and widgets

The photo picker accesses the photo you choose, not your whole photo library. A personal avatar stays local. A family avatar is uploaded after the relevant confirmation and shared with family members.

Care notifications are scheduled on each phone after you opt in and grant system permission. In family mode, reminder rules are shared, but phone notification permissions and opt-in are not. Disabling alerts does not delete a shared rule. The family-entry push-notification feature is currently disabled.

The Watch companion and widgets use app information through Apple's device communication and shared-storage facilities. Watch-created records may be pending until processed by the phone and, for a shared family, accepted by the service. Widget information may be visible to people who can see your screen.

Payments and support

Optional one-time support purchases use Apple's in-app purchase system. The app receives product prices and transaction status to handle the purchase. It does not receive your payment-card details or Apple account details, upload purchase receipts to our family server, or associate support purchases with your baby, family or app sign-in. A fresh random purchase-attempt identifier is used for transaction handling, not your family/account identifier. Apple maintains its own payment and purchase records.

If you email support, we receive your email address and whatever information you include. We use it to respond and investigate the issue. Please redact private details and do not send passwords, sign-in codes or full family exports unless a specific, secure process has been agreed.

We handle support correspondence using Outlook and retain support emails for seven years.

Service providers, location and security

The family backend uses Microsoft Azure, and account authentication uses Microsoft Entra External ID. The family API and SQL database are hosted in Australia Southeast. The customer sign-in tenant reports its primary data location as Australian datacentres. These locations were checked on 5 October 2026; they do not establish that all security, support or provider processing stays in Australia. Apple separately provides app distribution, purchases and device services; a storage/share provider you choose handles files you export to it.

OpenAI is an additional service provider only for the optional AI sleep feature described above. Requests go through our server rather than directly from the app to OpenAI. The Australian location of our family database does not mean that AI processing stays in Australia.

This public support and privacy website is hosted by GitHub Pages. GitHub states that it logs and stores visitors' IP addresses for security, including visitors who are not signed into GitHub. Visiting the website is separate from uploading baby records to the family service. These pages do not add analytics, advertising scripts, contact forms or third-party fonts. See GitHub Pages data collection.

Hosting and authentication services process operational and security information, which can include account identifiers, IP addresses, approximate location inferred from IP addresses, browser and operating-system details, event times, sign-in outcomes and technical error details. IP-derived location is not GPS or precise location collected by the app. See Microsoft's sign-in log information. Microsoft's published retention period for External ID activity logs is seven days; separately exported logs and other provider records can have different retention periods. Disabling optional application logging does not eliminate provider-managed security or service records. See Microsoft's log-retention information.

Our service providers operate internationally. Depending on the service, support, security and other processing may occur outside Australia, including in the United States and other countries where providers operate. We do not promise Australia-only processing. Provider information is available in the Microsoft Privacy Statement, Apple Privacy Policy and GitHub Privacy Statement. These describe provider practices and do not replace our responsibilities for information we handle.

The app uses HTTPS for family-service communication and account-based access controls. These measures do not make exported files encrypted or prevent an authorised family member from copying information. No system can guarantee absolute security.

Retention and deletion

Personal records remain on your device until removed or replaced through an app operation. The app's iOS SQLite directory, including personal records, family cache and pending changes, is excluded from system backups. Keep a manual export if you need a separate copy. Exported JSON is unencrypted; you control copies saved outside the app.

Shared data is retained to provide the family history until the applicable record, family or account-deletion process removes it. Ordinary sign-out, leaving or removal retains accepted contributions. Deleting an individual record is subject to family permissions; pending offline deletion is not server-confirmed deletion.

You can initiate account deletion in the app: sign in under More → My account, then choose Delete account in More. A family administrator must first complete the ownership-transfer or eligible family-closure steps shown in Family sharing. Once the service accepts deletion, account access stops while data cleanup and identity-account deletion are processed. The app reports progress and confirms completion only after the service does.

Account deletion removes family records you created or last edited, including records another member originally created. Closing a family removes its shared content, including former members' contributions. Neither operation restores personal data previously replaced during family activation. A record disappearing from visible history does not establish that all operational records or backup copies have expired; deletion/status and synchronisation records require separate retention handling.

The family database is configured for a seven-day point-in-time restore window, with no weekly, monthly or yearly long-term backup retention policy. This was verified on 5 October 2026. Deleted information can remain in existing backups until those backups expire. Azure may retain the backup chain needed for that restore window for up to an additional week; the seven-day restore setting is not a promise that every underlying backup copy is erased seven days after a record is deleted. See Azure SQL backup retention.

The service retains a deletion-status receipt containing an account identifier, operation identifier, receipt hash, status and processing timestamps. The temporary email field is cleared during account-data cleanup. It also retains closed-family status identifiers and timestamps. These support deletion-status checks, prevention of access by old credentials and safe handling of retries. They are not anonymised merely because names and emails have been removed.

We have selected a seven-year retention target for these limited deletion/status records. They do not currently expire automatically and may remain longer; seven years is not a guaranteed erasure deadline. This does not delay deletion of account or baby content for seven years. Active-family operation receipts also have no time-based expiry; they protect synchronisation against repeated operations and are removed by the relevant account/family cleanup processes. Contact us if you need help with a delayed deletion or retained information.

Uninstalling the app does not delete your service account. Deletion cannot recall exports held by you or other members, and does not remove Apple's independently maintained purchase records.

Your choices and privacy requests

You can stay in personal offline mode, decline photo/notification permissions, leave AI sleep suggestions off or turn them off, change permitted records, export data, leave a family or request account deletion. Changes to shared access require service confirmation. Some shared information may belong to or affect other family members.

For access, correction, deletion assistance or a privacy complaint, email contact@reticle.com.au with the subject My Little Days privacy. Describe the issue without sending unnecessary child or health information. We will assess the request, verify identity where needed, investigate and explain the outcome or any limitation. We will not ask for your password or sign-in code.

Rights to access, correct, delete, restrict or object to processing, or obtain a copy of information, depend on the laws that apply to your circumstances. Contact us to make a request. This policy does not limit rights you have under applicable law.

If you remain concerned, you may contact the privacy regulator relevant to your circumstances. Information about Australian privacy rights is available from the Office of the Australian Information Commissioner.

Changes to this policy

We will keep the published policy up to date and show its effective date. Material changes to data handling will be explained through an appropriate notice and consent process where required. The website's own data-handling practices must be disclosed separately where they differ from the app.