Privacy Policy

1. Information we collect

We collect information that you provide or that is needed to operate, secure, and support the Service:

• Account, contact, family, and caregiver information: your email address, family-visible display name, family membership, caregiver role, relationship label, invitations, and the caregivers you choose to invite.
• Child profile information: information you provide about a child, such as a name, sex, birth date, due date, adjusted-age preference, and other profile details made available through the Service.
• Care and child-related records: information you choose to record through available features, including care activities, growth or developmental observations, preferences, optional notes, and information you choose to import. The Service may derive summaries, trends, achievements, and skill marks from these records.
• Communications: waitlist and product-news email addresses, support requests, feedback, and our correspondence with you.
• Technical, account-security, and legal information: information reasonably necessary to provide, secure, diagnose, update, and administer the Service, such as app version, platform and operating-system version, network requests, authentication and synchronization status, and records of your acceptance of our legal documents. When you send feedback, its automatic context is limited to app version, platform, and operating-system version. You may choose to include limited technical sync details to help us investigate a sync issue. Those details can include aggregated activity types and counts, but never names, notes, measurements, identifiers, raw errors, or activity details. Feedback does not automatically include child or family information, care activities, screenshots, device identifiers, or care summaries.
• Limited diagnostics and app-usage data: if the in-app setting remains enabled after you accept this Policy, we receive a pseudonymous installation identifier, app version and build, operating-system version, coarse device manufacturer and model, selected app screens, and whether a limited set of core actions succeeded. We also receive limited crash diagnostics: error type and a scrubbed code-location stack trace. We do not send account, family, child, activity, note, quantity, timestamp, email, name, token, database identifier, free-text, URL, request, or raw-error content in these diagnostics or usage events.

The Service is not designed for children to create accounts. If you add or share a child’s information, you confirm that you are authorized to do so and to share it with the caregivers you invite.

2. How we use information

We use information to provide, authenticate, secure, maintain, and improve the Service; save and synchronize information between your signed-in devices; show shared family information to invited caregivers; import information you choose; calculate and display summaries, trends, achievements, and other in-app views; send account, security, invitation, and service messages; respond to support requests; administer the beta; comply with legal obligations; and enforce our agreements.

We may use your confirmed waitlist email for beta invitations, feedback requests, and future Baby Unlocked product news. You can unsubscribe from marketing email at any time. Account, security, invitation, and deletion messages are operational messages and may still be sent when needed.

3. Local storage, sync, and notifications

The app saves information first in a local SQLite database on your device so common caregiving actions can work without a connection. When you are signed in and connected, it synchronizes shared information with our cloud service. Local storage is protected primarily by your device and operating system security. We do not claim that the local database is encrypted.

The current beta can show an optional local notification while a breastfeeding timer is active. This notification stays on your device, may be visible according to your device settings including on a lock screen, and does not obtain or send a remote push-notification token. You control notification permissions through your device settings and can turn breastfeeding timer notifications on or off in the app’s Preferences. If you import a file, it is selected by you through your device’s picker and processed to create the records you choose; the original file is not retained solely for import recovery.

4. How we share information

We share information only as follows:

• with the caregivers in your family whom you invite or join;
• with an app, service, or recipient you choose when you explicitly export and save or send care data;
• with the service providers described below that process it for us to provide the Service;
• when reasonably necessary to comply with law, protect rights or safety, or address fraud or security; and
• as part of a corporate transaction, if one occurs, subject to this Policy or notice of materially different practices.

We do not sell, rent, or use your information for targeted advertising or cross-context behavioral advertising.

5. Service providers

We use service providers for limited operational purposes, including:

• Supabase for cloud authentication, database, access control, synchronization, and server functions;
• Kit for optional waitlist and product-news email signups;
• GitHub Pages for website hosting; and
• Expo for app delivery and update services; and
• PostHog for the limited diagnostics and app-usage data described above. We configure this service for U.S. processing and disable IP-based geolocation, session replay, touch autocapture, feature flags, push-notification capture, and person profiles.

You can turn off limited diagnostics and app-usage data in Preferences at any time. Turning it off stops future collection, clears queued telemetry on that phone, and resets its pseudonymous analytics identifier. This choice does not affect caregiving features, local storage, synchronization, or account access.

Service providers may process information needed for these limited operational purposes in the places where they and their subprocessors operate. We do not make a data-residency promise in this beta.

Live app requests to Supabase authentication, database, synchronization, and server functions, and to Expo update services, use HTTPS/TLS encryption in transit. This does not change the local-storage disclosure above or make an encryption-at-rest promise for local SQLite data or email.

6. Retention

We keep live account and family information while the account or family remains active. We keep a confirmed waitlist or product-news email until you unsubscribe, then remove it from active marketing within 30 days while retaining only the minimum record needed to honor that opt-out. We keep support and feedback messages for no more than 24 months after we receive them, and delete them sooner when the associated account is deleted or when required by a valid privacy request. We retain limited diagnostics and app-usage data for no more than 90 days.

We do not make a backup-retention promise in this beta because we have not established and verified a separate backup and restoration policy.

7. Your choices and privacy requests

All U.S. beta users may request access to, correction of, or deletion of their personal information by contacting us. We may verify your identity before acting. We will respond within 45 days, or explain if more time is reasonably necessary.

You can correct much of your information in the app. You can unsubscribe from marketing email using the link in that email.

A Primary Caregiver can export one CSV containing the family care data saved on their device, including hidden children, activities, pumping, saved milestones, and notes. The export includes saved local changes; changes from other devices may be missing until they sync. When changes need review, the export uses the device’s saved versions. It excludes account and caregiver fields, personal preferences, derived achievements, deleted information, and unsaved drafts. Notes are included as entered and may identify other people. This care-data export does not replace a request for access to other personal information through our privacy contact.

Export files contain sensitive child and health information. You choose the destination through your device’s share menu, and that destination’s own practices apply. We keep a temporary copy in the app’s private cache for sharing and attempt to remove copies older than 24 hours when the app starts or returns to the foreground. Copies you save or send elsewhere remain outside our control and are not removed when information, a family, or an account is deleted from Baby Unlocked.

8. Account and family deletion

Primary Caregivers share equal authority to manage family access and permanently delete shared family information and activities. Caregiver relationship labels do not grant permissions. Personal account deletion leaves the family and preserves its shared information for other caregivers. The last Primary Caregiver must first establish another active Primary Caregiver or separately confirm permanent family deletion. Family deletion is a separate confirmed action and leaves the personal account intact. These permanent deletion actions cannot be undone. When a family is retained, shared activities and the caregiver names used for their attribution remain with that family. Personal account deletion removes your sign-in account and private Quick Action preferences.

After an online, confirmed in-app deletion is processed, we delete the account and any affected family information from the live cloud service and clear Baby Unlocked information from the requesting device. Temporary CSV export copies follow the cache-cleanup schedule in section 7, including after deletion; copies saved or sent elsewhere remain outside our control. An offline device held by another caregiver may retain its cached shared copy only until it reconnects and receives the deletion state, or until its app data is cleared. That cached copy cannot restore information that was deleted from the shared Service.

If you cannot access the app, visit our account deletion page to submit an external deletion request.

9. Security

We use reasonable technical and organizational safeguards designed to protect information, including authenticated access controls and family-scoped permissions. No method of storage or transmission is completely secure, and the Service is not a backup service.

10. Children

The Service is for adult parents, guardians, and other adult caregivers, not for children to use directly. We collect child-related information only when an adult caregiver provides it. If you believe a child has created an account or provided us information directly, contact us.

11. Changes to this Policy

We may update this Policy as the beta evolves. We will post the updated version with a new effective date and, for a material change, give active beta users notice in the app and by email before it takes effect. We may ask you to acknowledge a new version before you continue using shared-service features.

12. Contact us

Chase Ricketts
California, United States
privacy@mail.babyunlocked.com