BabyOnboarding
Privacy policy
Last updated: October 12, 2026
This policy describes data used by BabyOnboarding: Baby Simulator, published by 4LLs. The app can work locally; some rehearsal and purchase features use external services when available.
Data stored on your device
The app saves information it needs on this device, including your initial answers — journey stage, pregnancy week if provided and interest in rehearsing with another person —, names you enter, feeding preference, baby visual tone, individual lesson progress, access status and rehearsal data, including responses waiting for a connection. Journey stage and pregnancy week stay on this device and are not sent to connected services. Individual lesson progress also stays on this device and is not synced between people. Optional night alarms are scheduled by the device operating system; alarm content is not sent to a notification service. Drafts for the 90-day Network also stay on this device until published.
Email account and sign-in
The demo without an account stays on this device and does not create a remote account. A verified email account is required for a connected rehearsal or to buy/restore purchases. When email delivery is configured and available, sign-in uses a six-digit code that expires after 10 minutes; you remain signed in for up to 30 days. A request can fail when email delivery is unavailable. We use your email and IP address to limit code requests and help prevent abuse. Cloudflare services process your verified email, an account identifier, your language and, if provided, your display name to maintain the account and provide access. Cloudflare Email Service receives the destination address and message contents, including the code, when email sending is configured and available. The family also signs in to publish the 90-day Network; helpers using the link do not need an account.
When you use connected services
Cloudflare services store the account identifier, language and display name if provided, rehearsal setup, chosen names, invitations and partner link, responses, times, pauses and access status needed to operate the feature. Your partner can see the shared rehearsal data; they do not receive your personal lesson progress. An installation used only locally does not create a remote account by itself. If the connection fails, pending actions may stay on this device until it returns.
90-day Network
The network is free and helps people organize requests for help. Drafts stay on this device. The family signs in to publish. We store the short label chosen for the network (up to 40 characters), the responsible account identifier, the time zone and requests: task, day, time window and status. We also store the identifiers and times needed to operate the network, its link, permission granted to a partner and offers. Helpers provide only a first name (up to 24 characters), without an account, email or phone number. The name is what the person entered; it is not verified. To learn whether the network is useful, we keep unidentified daily counts (for example, how many requests were created and how many times links were opened). These counts include no names, IP addresses or request content.
Anyone with the link can see the short network label, requests, days, time windows and availability, as well as the time zone and expiry. The page does not show helpers’ names or the family’s account details. The family sees the helper’s entered first name in the app; its partner can also see it if the family allows access. Share the link only with people you want to invite: it can be forwarded to others. The family can pause the network or change the link to stop that access.
The network does not ask for health data or access or collect health records. There are no fields for a baby’s name or birth date, address, photos, phone number or free-form notes. Do not enter health data, children’s names, an address or contact details in the network label or first-name field. Arrange the details directly with people.
In a helper’s browser, we save the language choice and a random key to recognize and undo that browser’s own offer. The key stays in that browser’s local storage; only its cryptographic digest is stored on the server. Clearing browser storage may prevent Undo from working, but does not delete the server-side offer. If the browser cannot save the key, it may last only while the page remains open. To limit abuse, we store cryptographic digests of IP addresses in temporary counters, rather than plain IP addresses in those counters. Hosting providers may retain technical records under their own practices.
The network expires 120 days after creation. Renewal sets a new expiry 120 days from renewal. After expiry the link stops working, and the records become eligible for deletion 30 days later through daily cleanup. Deleting the network or its responsible account deletes active network and offer records. Undoing an offer, or the family declining it or removing an active request, immediately removes the first name from that offer. An offer awaiting confirmation loses the name after 48 hours or the end of the request’s day, whichever comes first, when the system updates its status. Completed help retains the first name while network records exist. The network may mark help completed after its day passes; this does not prove the help took place.
You can request access, correction or deletion of your data and ask how it is used, even without an account. For an active offer, open the same link in the same browser and use Undo. If you lost the key, the link no longer works or the help is completed, ask the family or write to support@babyonboarding.app. The family can decline active offers or delete the network; the family can delete a completed or canceled record in the app, removing the request and helper name. Provide only what is needed to locate the network and request, without sending the full link or your key. We may request proportionate confirmation to avoid disclosing or deleting another person’s data.
We use family data to provide the service requested when the family publishes the network. We use your first name and offer to organize the help you chose to offer and let the family follow it; you can withdraw an active offer. We use temporary security controls to prevent abuse. We do not use network data for advertising, selling data or medical guidance. The family can delete the network; helpers can withdraw an active offer or ask support to delete their data.
In the browser, keys without an active request are removed when the page successfully refreshes the list; the key for an undone offer is removed when the action succeeds. The language choice may remain until you clear site storage. Deleting active records does not erase copies others saved, calendar files you saved, or providers’ technical records and copies; the limits already stated in “Deletion and retention” apply.
You can also report a problem using the “Report a problem” link; the family can individually delete completed or canceled requests, removing the request and helper name, and name fields accept only letters and permitted punctuation.
Notifications
If you allow notifications and use a connected rehearsal with a verified account, an identifier used to deliver notifications to your device may be sent to Cloudflare services and Expo for daytime rehearsal nudges. Night alarms are local to the device. You can revoke notification permission in system settings. The network may send the family a generic notice that someone offered to help, using an already registered notification identifier. The notice contains no names, requests or dates. Helpers receive no reminders or notifications from the network.
Purchases
When purchases are available, RevenueCat helps the app check purchases and access and receives your verified account identifier and the purchase/subscription information needed for that purpose. RevenueCat also analyzes purchase and subscription history for its analytics and reporting features. This purchase analytics is separate from optional PostHog app-usage analytics, which sends events only in builds compiled with an analytics key. The App Store or Google Play processes billing and keeps transaction records under its own practices. The app does not receive your card number. Deleting the app account does not erase records held by the store or RevenueCat and does not cancel a subscription.
Optional app-usage analytics
Only app builds compiled with an analytics key can send predefined app-usage events to PostHog. Events use event names, closed categories, boolean states and counts; they do not include names you enter, typed text or audio. Session replay is disabled. You can turn analytics off in app settings; without a configured key or after opting out, events are not sent. The provider may process technical metadata needed to provide the service under its own policy.
Sensitive data and content
The app stores your journey stage and, if provided, pregnancy week locally. These data are not sent to connected services or included in the analytics events described below. Display names and baby names may be sent to operate a connected rehearsal, but are not included in those analytics events. The analytics events do not include names, typed text or audio. Avoid including personal information in display names.
Deletion and retention
Choose “Delete account” in app settings. Remote deletion happens first and requires an internet connection: it removes the account and email, sign-in sessions, pending codes and code-request controls associated with that email, notification identifiers, partner links, the app’s access record and rehearsals you created. If you joined someone else’s rehearsal, your participation is removed, but its creator may keep the remaining data. If remote deletion fails, the app reports an error and does not clear local data. After it succeeds, the app clears local data and progress on this device and asks the device system to cancel alarms; cancellation can fail, so check alarms on the device. Local progress on another device is not synced or erased by this request.
Deletion through the app does not erase purchase records held by the App Store, Google Play or RevenueCat, cancel or refund a subscription, or remove technical records held by email, hosting or notification services. Cancel a subscription in the store where you bought it. We do not publish a fixed removal period for technical records or copies held by these services. The network you created and its offer records are also removed.
Website and questions
This website includes informational pages and the 90-day Network page, where people with a link can offer or undo help. We do not use first-party analytics scripts on these pages. Hosting services receive technical requests to deliver them, and the network page queries our API. For questions or requests about your data, write to support@babyonboarding.app.
Publisher
The publisher identified for this app is 4LLs.
Contact us
Support email: support@babyonboarding.app