Bimbi Privacy Policy
Effective date: September 17, 2026
This Privacy Policy explains how Bimbi’s creator, operating the project under the name Bimbi Labs (“Bimbi Labs,” “Bimbi,” “we,” “us,” or “our”), collects, uses, discloses, and protects personal information when you use getbimbi.com, the Bimbi iOS app, the Bimbi web beta, Nana, our website demo, and related support and beta services (collectively, the “Services”).
The short version: We do not sell personal information, serve behavioural advertising, or use your family’s information to train public AI models. The native iOS app keeps its tracking database and saved history on your iPhone. Nana sends conversation content and selected family context to OpenAI to respond. In iOS versions that offer Shared learning, you may separately review and send limited structured child-profile and outcome data to Bimbi to help us understand patterns across families. This is optional and does not authorize AI model training. The web beta stores account, child, tracking, plan, and conversation information on Bimbi’s systems so it can work across browser sessions. You can request a copy of your information or delete it.
1. Who we are
Bimbi is an independent project operated by its creator under the project name Bimbi Labs. It provides voice-first parenting tracking, education, and coaching for adult parents and caregivers. Bimbi is not directed to children.
For privacy questions or requests, contact our Privacy Lead at [email protected]. General support is available at [email protected], and safety concerns can be sent to [email protected].
2. Information we collect
The information we collect depends on which Services you use, your app version, and the choices you make. Supported versions offer the simplified personalized-Nana setup and Manage data navigation described below. Earlier versions show separate AI-processing and personalization switches and may call these screens Privacy center and Shared learning. Existing choices remain valid for their original scope; installing an update does not grant a new permission. Shared learning data is collected only in a supported version after a separate opt-in and your explicit review and submission.
Account and contact information
We may collect:
- your Sign in with Apple identifier and, if Apple provides it, your name or email address, including an Apple private-relay address;
- for the limited web beta, your name, email address, password hash, language, consent timestamp, and session information;
- language, time zone, account status, trial status, and preferences;
- waitlist information, support messages, privacy requests, safety reports, and beta feedback; and
- any contact information or attachments you choose to include when contacting us.
We do not receive your Apple Account password.
Child, caregiving, and tracking information
You may choose to provide information about a child and your family’s routines, including:
- the child’s name, date of birth, age, prematurity or adjusted-age information, and whether solids have started;
- optional reported sex, health status, and coded known conditions, including whether you report a clinician diagnosis; these are caregiver reports, not verified medical records;
- sleep, nap, waking, feeding, mood, schedule, bedtime, plan, and routine information;
- sleep setting, sleep challenges, caregiver responses, goals, method preferences, and comfort with different approaches;
- notes, summaries, plan progress, guides, and facts you ask Nana to remember; and
- information you type, say, or confirm while using Nana or tracking features.
This information can reveal health, development, and family-routine details. We treat it as sensitive personal information and, where applicable, consumer health data.
Conversations, voice, and AI information
When you start a Nana voice or chat session, the Services may process:
- microphone audio and speech transcriptions;
- typed messages and Nana’s responses;
- the child’s name, age, prematurity, feeding and sleep context, recent tracking history, active plan, language, time zone, summaries, and relevant facts; and
- tool actions needed to log an event, update a plan, create a guide, or complete another request you make.
In the iOS app, raw voice audio is streamed for real-time processing and is not stored by Bimbi Labs. Partial captions are discarded. Finalized conversation text is stored on your iPhone only if you enable conversation history; summaries may be stored locally so you can review prior sessions. The Bimbi iOS backend is designed not to store raw audio, typed chat content, transcripts, or summaries.
The separate web beta stores typed messages and finalized voice transcript lines, summaries, guides, and plan information on Bimbi’s systems so the beta experience can persist between browser sessions. The web beta never stores raw audio.
Optional Shared learning in supported iOS versions
Shared learning lets an adult caregiver explicitly review and contribute structured observations about a completed coaching outcome. Contributions can include:
- age in months, adjusted age, weeks born early, reported sex or a not-shared value, and an optional coded health report frozen when the outcome was evaluated;
- a profile revision, report and evaluation dates, and whether a condition was parent-reported or reported as a clinician diagnosis;
- the method and goal codes, an outcome such as improved, unchanged, worse, or insufficient data, aggregate baseline and follow-up sleep measures, adherence, coded factors that may affect the observation, and the evaluation policy/version; and
- account-linked pseudonymous child and outcome identifiers used to avoid duplicates, apply corrections, and honor deletion.
This submission excludes names, dates of birth, private notes, free text, raw sleep logs, audio, and conversation transcripts. The optional structured health fields include asthma, eczema, reflux, food allergy, sleep apnea, or an “other” code without a diagnosis description. You may leave sex or health information unshared. Contributions remain linked to your Bimbi account; hashing identifiers does not make this data anonymous.
Changing a profile does not silently add today’s health information to an older outcome. Editing an outcome invalidates its older contribution when the app can reach Bimbi; you must explicitly review and submit a corrected outcome to share it again. There is no automatic retrospective upload.
Purchase and subscription information
Apple processes App Store purchases. We may receive product identifiers, transaction and original-transaction identifiers, subscription state, expiration or revocation status, storefront or environment information, and an app-account token used to associate an entitlement with your Bimbi account. We do not receive or store your full payment-card number.
Device, usage, and operational information
We may collect limited technical and operational information, including:
- app version, build number, operating-system version, device model, language, time zone, and timestamps;
- a pseudonymous or hashed account identifier;
- session start and end times, model tier, duration, token counts, estimated or measured service cost, trial usage, and rate-limit counters;
- content-free product events, counts, timings, and short categorical values if you opt in to app analytics; and
- IP address, browser type, security signals, essential session cookies, and approximate region inferred from IP when you use the website, web beta, waitlist, or demo.
Optional in-app analytics contain account-linked counts, timings and short feature categories, not message text, transcripts or private notes. They are not anonymous. Essential service usage and security records are separate from optional analytics. The private operations dashboard displays usage, reliability, cost, subscriptions, consented product events, and feedback and optional reply email you submit. Authorized personnel may separately access contributions you explicitly share to operate Shared learning, examine patterns, and honor correction or deletion; this does not provide remote access to your iPhone tracking database.
Information we do not currently collect
The current native app does not request access to contacts, HealthKit, the photo library, camera, Bluetooth data, precise device location, advertising identifiers, voiceprints, or biometric identifiers. This does not exclude attachments you deliberately send in a support request outside the app. Nana does not perform cry detection, speaker identification, emotion recognition, or voiceprint analysis. A child’s voice or other background sound may be incidentally captured during a Nana voice session; avoid starting a session when others should not be recorded.
3. Where information is stored
Native iOS app
Child profiles, optional learning profiles, tracking history, local plans, evaluations, plan preferences, decision comparisons and responses, frozen displayed sleep predictions, Nana summaries, optional finalized conversation history, and local notes are stored on the iPhone using Apple’s device protections. Bimbi Labs cannot remotely read that local database. Depending on your Apple settings, local app data may be included in a device backup controlled by Apple.
The native app sends selected context off-device when needed to authenticate, verify subscriptions, operate Nana, generate a recap, extract a fact, submit feedback, send analytics you have enabled, or submit Shared learning observations you explicitly reviewed. Supported Shared learning contributions are stored in an account-linked Bimbi database hosted by Cloudflare, separate from the local tracking database.
Web beta
The web beta stores account, child profile, tracking, plan, guide, conversation, consent, and product-event information in Bimbi’s Cloudflare-hosted database. This architecture is separate from the native iOS app.
Website and demo
The public Nana demo does not require an account. Bimbi does not store demo audio or transcripts. We use transient IP-based controls and security services to enforce session and spending limits. Waitlist submissions are stored so we can contact you about Bimbi.
4. How we use information
We use information to:
- create and secure accounts and authenticate sign-ins;
- provide tracking, schedules, reminders, summaries, plans, guides, and Nana conversations;
- personalize the Services using the child and family context available to the selected product;
- process subscriptions, trials, restores, and entitlements;
- respond to support, privacy, safety, and beta-feedback requests;
- prevent abuse, fraud, and unauthorized access and enforce usage limits;
- measure reliability, service cost, and product performance;
- troubleshoot and improve the Services using content-free analytics and feedback you intentionally submit;
- where you separately choose Shared learning, examine patterns in reported profiles and coaching outcomes to improve the product and evaluate future changes;
- comply with law, enforce our Terms, and protect users, children, Bimbi Labs, and others; and
- communicate material service, safety, legal, or account changes.
We never use child information or the personal information you provide through the native app and Nana for marketing, advertising, or sale. We do not add native-app accounts or family information to marketing audiences. A separate website waitlist or newsletter submission is used only to send the communications you requested through that form; it is not combined with family or coaching records. We do not use customer content to train or fine-tune our own or a third party’s general-purpose model unless we first offer a separate, explicit opt-in. Shared learning does not grant permission to train or fine-tune a general-purpose model. It is observational product learning, not clinical research, proof that a method caused an improvement, diagnosis, or automatic treatment. There is no automatic model training from these contributions. Small-group patterns can be misleading; aggregate reports suppress groups with fewer than ten distinct children and ten accounts.
5. Consent and processing choices
In Build 24, Enable personalized Nana is one affirmative action that permits the disclosed core coaching uses: external AI processing and relevant family-history personalization. The setup identifies OpenAI, the information sent, the purposes, and provider retention before activation. These permissions are saved as separate, versioned records together. Nana uses relevant history, plans, preferences and observed outcomes automatically while personalized Nana is enabled. It also saves decision and prediction records on the iPhone so the app can explain and evaluate its coaching.
You can choose Continue with tracking without enabling Nana. Under More → Privacy → Manage Nana, you can review the processing explanation or turn Nana off. Turning it off stops active Nana sessions, future AI requests and new local learning records, and erases saved plan preferences. Other stored history and learning records remain available until you erase them. Withdrawal cannot undo processing that has already occurred. A failed save is reported rather than treated as a completed change.
An update preserves earlier permissions and refusals. An earlier AI-only or personalization-only permission does not become permission for both. You must explicitly activate the combined experience if you want to change those choices. A changed purpose or expanded data-sharing scope requires a new disclosure and permission where applicable.
These optional choices remain separate from personalized Nana:
- Optional child details: you choose whether Nana may use selected sex and health categories. Private health notes are excluded from structured AI context.
- Help improve Nana: the current Shared Learning V1 flow requires explicit review and submission of each outcome. Enabling Nana, agreeing to terms, or permitting analytics does not enroll you. It does not permit automatic contribution uploads or model training.
- Optional usage statistics: off by default. In Build 24, sending statistics also requires a current account-specific server permission record. Older local permission flags do not grant this new permission. Turning statistics off stops collection and clears pending events immediately; the app requests erasure of stored optional statistics and shows when server cleanup is pending. Minimal permission/retry records enforce withdrawal.
- Save conversation history: off by default; this controls future copies of finalized conversation text stored on the iPhone. Turning it off does not erase previously saved copies or change a processor’s retention.
Optional sharing and usage statistics are not required for personalized coaching. Permissions can be changed in Privacy. Accepting our Terms does not replace the specific choices described here.
6. AI and voice processing
Nana uses OpenAI’s API services. During a Nana session, microphone audio may travel directly from the device to OpenAI over an encrypted real-time connection, while Bimbi’s backend handles authentication, safety instructions, selected context, tools, and connection signalling. Typed conversations and recap or fact-extraction requests pass through Bimbi’s backend to OpenAI. Knowledge searches may send the search text to OpenAI to create a search embedding. Optional Apple speech dictation is a separate feature: recognition runs on the iPhone when supported; otherwise Apple processes the dictation audio under its speech-service terms and permission prompt.
OpenAI states that API customer content is not used to train its models unless the API customer opts in. Under OpenAI’s default API controls, abuse-monitoring logs may contain prompts, responses, audio, transcriptions, and related metadata and may be retained for up to 30 days, unless law requires longer retention. Bimbi Labs has not authorized OpenAI to train models on Bimbi customer content. We do not promise zero provider retention. See OpenAI’s API data controls for endpoint-specific policies.
Bimbi personnel do not routinely listen to or read native iOS Nana conversations because Bimbi does not store them. Access to web-beta conversation content, support messages, safety reports, or feedback is limited to authorized personnel who need it to provide support, investigate a reported problem, protect safety or security, or comply with law.
AI can be inaccurate or incomplete. Nana is an educational and coaching feature, not a healthcare professional or emergency service. See our Safety page and Terms of Service.
7. When we disclose information
We disclose personal information only as described here:
- OpenAI: real-time voice, transcription, chat, recap, fact extraction, and related AI processing;
- Cloudflare: website, web-beta, backend, database, security, logs, rate limiting, and content delivery;
- Apple: Sign in with Apple, App Store subscriptions, optional speech recognition, notifications, device services, and any Apple-controlled backups;
- Plausible: cookieless website analytics configured without advertising profiles;
- Support and communications providers: email delivery and the tools we use to answer messages; and
- Professional advisers and authorities: where reasonably necessary for legal, security, accounting, insurance, safety, or compliance purposes.
We may disclose information when you direct us to, when required by valid legal process, or when reasonably necessary to protect a person from serious harm, investigate fraud or abuse, or protect legal rights. If Bimbi Labs is involved in a financing, merger, acquisition, reorganization, or sale of assets, information may be transferred subject to confidentiality and applicable law.
We do not sell personal information, share it for cross-context behavioural advertising, or allow third-party advertising trackers in the native app. We do not knowingly sell or share consumer health data.
8. Cookies and website analytics
The public website uses Plausible for aggregate, cookieless analytics and Cloudflare for security. The web beta uses an essential secure session cookie to keep you signed in. Cloudflare Turnstile may process technical and security signals when you use protected forms. We do not use advertising cookies or respond differently to browser “Do Not Track” signals because we do not track users across unrelated services for advertising.
9. Retention and deletion
We retain information for the period reasonably needed to provide the Services, meet the purposes described above, resolve disputes, maintain security, and comply with legal obligations.
- Native device data: remains on the iPhone until you delete individual records, use More → Privacy → Manage data to delete a baby or your account, or remove the app or its data. Apple-controlled device backups may follow Apple’s retention settings.
- Native account and operational records: account, authentication, trial, subscription-entitlement, usage, consent, feedback, and optional analytics records remain while the account is active or until you delete your account, which also deletes active Shared learning contributions and their consent/retraction records, subject to legal, fraud-prevention, and backup requirements.
- Optional usage statistics: active event records are erased when you withdraw this permission in Build 24 or delete your account; offline withdrawal is queued until the server can acknowledge it. Minimal consent operation records remain to prevent stale requests from restoring permission until account deletion.
- Shared learning: retained while you choose to share it. Withdrawing in Help improve Nana deletes all active contributions across your account and records the withdrawal to prevent stale requests from restoring them. Individual child/outcome deletion and correction controls remove or invalidate the applicable contribution. Minimal account-linked consent/retraction records remain to enforce these choices until account deletion. If offline, removal from Bimbi completes after the queued request reaches the server; the app shows pending removal.
- Web-beta data: remains until you delete the web-beta account, we retire the beta, or it is no longer needed for the beta. Account deletion cascades through the associated child, tracking, plan, guide, and conversation records in the active database.
- OpenAI API content: under the default API configuration, eligible content may remain in abuse-monitoring logs for up to 30 days, unless legal or security obligations require longer retention.
- Website demo and security data: transient rate-limit data and ordinary infrastructure logs are retained for short operational and security periods controlled by Bimbi or its providers.
- Waitlist and support records: remain until they are no longer needed for the request, relationship, or legal record, or until you request deletion where applicable.
- Transaction records: Apple and Bimbi may retain entitlement and transaction records as needed for billing, fraud prevention, tax, accounting, and legal compliance.
Deletion from Bimbi does not automatically cancel an App Store subscription. Cancel the subscription separately in your Apple subscription settings. Providers such as Apple and OpenAI may retain information under their own legal obligations and retention schedules. Residual copies may remain temporarily in protected backups until those backups cycle out.
10. Your privacy rights and choices
Depending on where you live, you may have rights to:
- know whether we process your personal information and obtain access to it;
- request a portable copy;
- correct inaccurate information;
- delete information;
- withdraw consent or object to certain processing;
- opt out of sale, targeted advertising, or certain sharing—although Bimbi does not engage in those practices;
- appeal a denied privacy request; and
- make a complaint to the privacy or data-protection authority where you live.
In Build 24, use More → Privacy → Manage data to export, delete one baby’s data, or delete your account and all family data. Deleting one child preserves other profiles and queues removal of that child’s shared contributions. Account deletion removes all family profiles and active account records. Server cleanup may require a connection; the app distinguishes completed local erasure from pending server work. Earlier supported iOS releases expose these controls in the baby-profile editor and Privacy center. The web beta provides its own export and deletion controls. You can also email [email protected]. We may need to verify your identity and authority before completing a request. An authorized agent may submit a request where permitted by law, but we may ask for proof of authorization and may verify the request directly with you. We will not discriminate against you for exercising a privacy right.
11. Children and caregiver authority
The Services are for adults. You must be at least 18 or the age of legal majority where you live. Children may not create an account or intentionally use Nana.
By providing information about a child, you confirm that you are the child’s parent or legal guardian or are otherwise authorized by the parent or guardian to provide the information and use the Services for that child. Babysitters and other caregivers must have the parent’s or guardian’s permission.
We do not knowingly solicit personal information directly from children. If you believe a child has created an account, intentionally spoken to Nana without adult involvement, or provided personal information without appropriate authorization, contact [email protected]. We will investigate and delete information where required.
12. Security
We use administrative, technical, and organizational safeguards designed to protect personal information, including encrypted network connections, Apple platform protections, access controls, pseudonymous account identifiers in the native backend, and data-minimization rules for analytics. No service can guarantee absolute security. Keep your device, Apple account, web-beta credentials, and email account secure, and contact us if you suspect unauthorized access.
13. International processing
Bimbi Labs and its providers may process information in Canada, the United States, and other countries where our providers operate. Those countries may have privacy laws different from the laws where you live. Where required, we use contractual and other safeguards intended to protect information transferred across borders.
14. Third-party services and links
The Services may link to Apple, healthcare, crisis, educational, or other third-party resources. Their privacy practices apply to information you provide directly to them. This Policy does not govern third-party services that Bimbi Labs does not control.
15. Changes to this Policy
We may update this Policy as the Services, vendors, or law change. We will post the revised Policy with a new effective date. If a change materially affects how we use sensitive information, we will provide additional notice in the app, by email, or through another reasonable channel before the change takes effect where required.
16. Contact us
Questions, requests, or complaints may be sent to:
Bimbi Labs — Privacy Lead
For general support: [email protected]
For urgent product-safety concerns: [email protected]