BubBasic privacy.

Nothing leaves your device unless you turn on iCloud sync; then it goes only to your iCloud and invited participants, where the developer cannot see it.

Who this notice covers

This notice covers the BubBasic iPhone app and the BubBasic pages on www.basicapps.com.au. BubBasic is developed by Sean Meehan in Melbourne, Australia.

Privacy questions or complaints can be sent to sjmeehan9@gmail.com. Describe the issue without attaching care records or identifying a child.

The short version

The BubBasic app has no developer server, advertising, analytics, tracking or third-party SDK. It does not require a BubBasic account. Care data is stored locally. Optional iCloud sync uses Apple CloudKit in the Apple Account already on the device and, for a shared child, Apple's private sharing with people the owner invites.

The developer does not receive, inspect, sell or use your care records. You control them in the app and through your Apple services.

The BasicApps production website separately uses cookieless Cloudflare Web Analytics for aggregate traffic measures, and AWS Amplify creates ordinary hosting request logs. Those website services do not receive BubBasic care records from the app. Details are in the Website visits section below.

Information the app handles

You may enter a child's name, date of birth, growth-reference setting and care history. Care history can include sleep, nursing, bottle feeds, nappies, pumping, solids, medicine, temperature, growth, baths, notes, dates, durations and measurements.

BubBasic uses this information only to provide the logging, timer, report, widget, import, export and optional sync features you choose. This information may be sensitive. Do not enter anything you do not want stored on your iPhone or, when sync is enabled, in your iCloud and an invited participant's shared view.

Local storage, widgets and recovery

BubBasic stores a versioned JSON snapshot in private App Group storage on the iPhone. The App Group allows the app and its widget extension to read and write the same state. A small per-child widget snapshot contains event dates and active timer dates so iOS can render relative times and timers.

The app coordinates writes, validates replacements and keeps a local backup. If the primary file is unreadable and the backup is valid, BubBasic restores the backup and warns that recent changes may be missing. If both copies are unreadable, it blocks writes and offers recovery choices instead of silently replacing history.

Optional iCloud sync and sharing

Sync is off by default. If you turn it on, BubBasic sends records to Apple CloudKit in your private iCloud database. Accepting a child-sharing invitation is the only other action that turns on sync, and BubBasic explains that consequence before acceptance.

If you invite a co-parent, Apple exposes that child's shared zone to accepted participants. Invited participants can see and change the shared child's records. An owner can revoke access; a participant can leave. Apple transports and stores the records, but the developer does not operate a care-data server or have a tool for reading private or shared records.

CloudKit encrypts data in transit and at rest. Selected sensitive fields use CloudKit encrypted values. End-to-end protection for those fields depends on the user's Advanced Data Protection configuration. BubBasic does not claim that every CloudKit field or configuration is end-to-end encrypted.

Import, export, reports and the iOS share sheet

When you select a Huckleberry CSV through the iOS document picker, BubBasic reads and processes it locally. BubBasic creates CSV exports and text reports locally, then passes them to Apple's share sheet.

You choose the destination, such as Files, Mail, AirDrop or another app. That destination's privacy practices apply after you share. BubBasic does not upload imported files, exports or reports to the developer.

Device and iCloud backups

Local app data may be included in an iPhone backup when device backups are enabled. iCloud records and backups are controlled through your Apple Account and iOS settings. Apple's handling of those services is described in Apple's Privacy Policy.

Removing data from BubBasic does not necessarily remove an older copy from an Apple-managed device backup. CSV exports, recovery files, reports and screenshots are ordinary files after you save or send them, and must be removed separately from every destination.

Retention, deletion and payload-free markers

Local care data remains until you edit or delete it with BubBasic's controls, erase BubBasic data on that iPhone, or remove it through an applicable device restore or uninstall flow. An unsynced entry is removed locally immediately.

When an entry has previously synced, BubBasic removes its care payload locally and keeps only the minimum deletion operation needed for CloudKit acknowledgement. The server record becomes a payload-free tombstone containing deletion state and modification timing. That marker remains until its child zone is deleted so an older device cannot restore the care record.

Deleting an owned synced child records a marker without a child name, date of birth or care payload, then deletes the child's iCloud zone and share after acknowledgement. A participant instead uses Leave shared child.

The online-only Delete iCloud copy action confirms a private reset marker, deletes every child zone and share you own, exits shares owned by other people, removes those shared-in cached children and turns sync off. Owned history is preserved automatically as a detached local copy on that iPhone. Erase Data on This iPhone is a separate action and does not delete iCloud data.

Step-by-step instructions for entries, children, the complete iCloud copy, local data, shares, backups and exported files are in BubBasic support.

Apple Account changes and encrypted-key recovery

Each time BubBasic opens or returns to the foreground, it closes its widget and iCloud routes before checking the Apple Account on the iPhone. If the check is temporarily inconclusive, shared children remain hidden and widget actions and iCloud changes stay blocked until a retry verifies the account.

After a confirmed iCloud sign-out or Apple Account change, BubBasic removes known shared-in cached children and keeps known owned history as detached local data. Some v1.1 histories do not contain enough information to classify safely as owned or shared. BubBasic hides those histories and shows only their count until you explicitly choose Keep on This iPhone. That choice reveals them as detached local data; it does not turn on sync or upload anything.

Detached history is not uploaded to the current or a later Apple Account unless you separately choose Upload This Local Copy for that verified account.

If both copies of BubBasic's iCloud account metadata are unreadable, BubBasic hides all child histories, keeps widgets empty and blocks iCloud actions. Retry can reopen the histories only after a readable metadata copy is recovered. Erase Data on This iPhone removes all BubBasic data on that iPhone, including the unreadable metadata, and returns the app to onboarding; it does not delete iCloud data.

If Apple's encrypted keys are reset, an owner may keep the data local or rebuild iCloud from that iPhone. A participant needs a new invitation. BubBasic does not silently recreate a deleted zone.

Access and correction

You can view and correct care information directly in BubBasic, export it as CSV, or remove it with the in-app controls.

Because the developer cannot access your local or private or shared CloudKit records, an email request cannot retrieve, correct or erase those records on your behalf. Support can explain the controls but cannot perform a remote deletion.

Children's privacy

BubBasic is intended for parents and carers, not for use by children. A parent or carer chooses what information to enter about a child. That information is processed locally or through optional Apple CloudKit as described above; it is not sent to the developer.

Website visits

The BubBasic pages are static. They have no account or form, set no first-party cookie, and do not use browser storage to track you.

The production website on www.basicapps.com.au uses Cloudflare Web Analytics. It is cookieless, uses no browser storage and does not build a profile of your activity across other sites. It reports aggregate visits and page views rather than counts of unique or identifiable people. Protected preview versions exclude Cloudflare analytics.

The website is hosted on AWS Amplify. Serving a page creates routine access and security logs that can include an IP address, browser user agent, request time, and the requested path or query string. AWS retains those logs until the Amplify app is deleted. BasicApps does not export them for routine audience analytics; access is restricted to hosting, reliability, abuse-prevention or security needs, and a downloaded incident working copy is deleted when the incident is resolved.

Do not put a child's name, care information, sharing URL or another secret in a website path or query string. The BubBasic app does not do this.

Emailing support sends the information you choose through your email provider to the developer. Do not attach a CSV, recovery file, record identifier, sharing URL or unredacted screenshot unless you have deliberately removed personal details and support has specifically asked for the file.

The site-wide explanation is available in BasicApps website privacy.

Disclosure and overseas processing

The developer does not disclose care records. Apple, AWS, Cloudflare, your email provider and destinations you choose through the document picker or share sheet may process relevant service data in locations governed by their terms, privacy notices and your account settings.

The developer does not control Apple's storage locations and does not receive BubBasic care records from CloudKit.

Security and honest limits

BubBasic uses Apple platform storage, file coordination, CloudKit and encrypted-value APIs. No security mechanism is perfect. Device access, Apple Account security, participant access, backups and files you export remain under your control.

Use an iPhone passcode, protect your Apple Account, share only with people you trust and check the destination before exporting information.

Questions, complaints and changes

Send privacy questions or complaints to sjmeehan9@gmail.com. Information about privacy rights in Australia is available from the Office of the Australian Information Commissioner.

This notice will be updated before a release changes how BubBasic handles data. Material changes will use a new effective date and clear in-app or release wording.

The BubBasic terms of use also apply when you use the app.