What this policy covers
This policy applies to BabyLog marketing pages, the logged-in app, and related support interactions. It covers information you provide directly, information collected automatically when you use the service, and information processed by trusted third-party providers acting on our behalf.
BabyLog is built as a local-first baby tracking app. That means some information is stored on your device immediately and then synchronised to our servers so authorised caregivers can stay in sync.
Information you provide to us
When you use BabyLog, you may provide account and profile information such as your name, email address, Clerk account identifiers, and settings preferences.
You may also provide baby-related information, including baby names, birth dates, sex, caregiver labels, sharing details, invite information, and care records you choose to log.
- Feeds, sleep, nappies, solids, pumping, bath, play, medication, temperature, growth, notes, timers, and similar activity records.
- Custom food types, medication types, import files, export files, and AI-summary or prompt content you choose to generate from your logs.
- Messages or details you send to us when requesting support or reporting an issue.
Information collected automatically
Like most web apps, BabyLog also collects technical and usage information automatically so the service can function, stay secure, and improve over time.
- Device, browser, IP, app version, timestamps, and page or route information needed to deliver the service and troubleshoot problems.
- Local browser storage and cache data, including IndexedDB, localStorage, sessionStorage, and service-worker or PWA caches used for local-first behaviour and offline access.
- PostHog pageview analytics. Our current implementation is limited to pageview-style product analytics and does not enable PostHog session recording.
- Sentry diagnostics, performance telemetry, console logs, and sampled session replay used to investigate crashes, regressions, and reliability issues. Depending on the event, this may include personal information visible in the app at the time of the error.
- Arcjet security and abuse-prevention signals used to protect sensitive routes such as sync, bootstrap, and account-related APIs.
How we use information
We use information to operate BabyLog, provide local-first syncing, show the correct baby data to the right caregivers, and support the features you choose to use.
- Authenticate users, manage accounts, and keep sessions secure.
- Save, display, sync, back up, import, export, and restore baby records across authorised caregivers and devices.
- Provide reports, trend views, WHO growth-chart references, and text summaries based on your logs.
- Detect bugs, investigate incidents, monitor performance, prevent abuse, and improve the product.
- Communicate with you about account, safety, legal, or product matters.
Local storage, sync, and retention
Because BabyLog is local-first, data may be stored on your device before it finishes syncing to the server. Clearing browser data, uninstalling the PWA, or resetting the device can remove the local copy from that device.
Server-side copies and copies already synced to other authorised caregivers may continue to exist until they are deleted, expire from backups, or are otherwise removed under our retention practices.
- Import sessions and recovery state may be stored locally so interrupted imports can be resumed safely.
- Unsynchronised changes may remain queued locally until you reconnect or manually sync.
- We keep information for as long as reasonably needed to provide the service, resolve disputes, protect the service, and meet legal obligations.
Your choices and controls
You can review and update much of your information inside the app. Current controls vary by role and feature.
- Update baby information, edit logs, or manage caregiver access inside the app where those controls are available.
- Export a baby profile as CSV if you are the owner of that baby profile.
- Delete a baby profile, archive it, or delete all history for a baby where those controls are available to your role.
- Use browser controls to clear cookies, cached files, or local storage, noting that this may remove offline copies from that device only.
- Contact us at hello@babylog.com.au if you need help with account or data questions.
Children's privacy
BabyLog is intended for parents, carers, and other authorised adult caregivers. It is not designed for independent use by children.
You should only upload information about a child when you are authorised to do so and comfortable sharing that information with the caregivers you invite.
Changes to this policy
We may update this Privacy Policy from time to time as BabyLog evolves, new providers are added, or legal requirements change. If we make material changes, we will update the date above and may provide additional notice inside the product or on the website.
Questions about this policy can be sent to hello@babylog.com.au.