App privacy policy

Who is responsible

The data controller for the Dr. Baby mobile app is Alican Efe. Privacy and support contact: alican84627@gmail.com. This policy concerns the mobile app. The separate website policy describes the browser tools.

Who the app is for

Dr. Baby helps parents and authorized caregivers record a child’s growth, feeding and sleep. It is not a service directed to children, a medical diagnosis or treatment service, or a medical research study. Use it for a child whose data you are authorized to manage. No HealthKit access is requested. Health guidance and Lumi responses can be incomplete or wrong; consult a clinician when making health decisions.

Records on your device

You enter child names, birth dates, reference sex, gestational age, birth measurements, subsequent weight/height measurements, feeding, sleep, diaper logs and optional notes. These records stay on your device unless you choose the AI feature or export a report. In the iOS release, health records are kept in an Apple Data Protection file excluded from device backups. Previous app-preference records are migrated only after a successful file write. Existing backups made before this change cannot be remotely erased. There is no automatic cloud sync or recovery; keep exports you need securely.

Optional Lumi AI: what is sent and why

Before the first AI request, the app explains the sharing and asks for your explicit permission. For each question, the app sends the active child’s age in days, reference sex, gestational age, birth weight, up to 12 recent measurements and their WHO weight/height percentiles calculated on the server, up to seven days of feeding/sleep summaries, selected topic, language, units, your question and a limited recent conversation history through Google Firebase to OpenAI. Child names, exact birth dates, record IDs and notes are not automatically sent. Do not add identifying details to your questions. Removing names does not make health information necessarily anonymous.

These data are used to answer your question, not for advertising. Premium AI access is verified by linking your anonymous Firebase account ID to your Adapty subscription profile. Only that identifier and subscription status are used for this check; child records are not sent to Adapty. Deleting your Lumi account also requests deletion of its linked Adapty profile, without cancelling your store subscription. Consent is remembered on this device, can be withdrawn in Family → Privacy and data, and is requested again if the disclosed scope changes. Declining AI sharing leaves local tracking available. The app does not send a question just because consent is remembered. Withdrawing stops future AI requests; it cannot recall data already sent.

Recipients and security processing

Google Firebase/Google Cloud provides the server function, anonymous authentication, App Check and quota storage. Firebase creates an anonymous account identifier; device/app verification, network and diagnostic metadata may be processed to protect the service. Firestore stores only request counters and timing against that identifier, not child profiles or conversations. The counter/function region is europe-west1; this is not a promise that every provider service or subprocessor operates only in Europe.

Firebase privacy information explains its processing. OpenAI processes AI inputs and outputs. Dr. Baby sends requests with store:false and does not use a server-side conversation archive. This does not guarantee zero retention: OpenAI describes safety logs generally retained for up to 30 days, with legal/safety exceptions, and model-dependent prompt caching. API data are not used for training by default unless the API account opts in. See OpenAI’s data controls. The app does not claim that special zero-retention or regional-processing agreements have been enabled.

Subscriptions

When you open the subscription screen, plans load automatically. Apple and Adapty process products, purchase/subscription status, transaction identifiers and technical device information to provide and restore Premium. Dr. Baby does not send child records or AI messages to Adapty. Advertising identifier collection, attribution and optional paywall-view analytics are disabled in our SDK configuration. Network services necessarily receive connection information; this is different from advertising tracking. After your first store connection, the app may refresh subscription status on later launches. This does not send child records or start an AI request. Payment-card details are handled by Apple, not entered in Dr. Baby. Apple’s terms and retention obligations apply to purchases. See Adapty privacy and Apple privacy.

Retention and deletion

• Local child records remain until you delete them or remove the app. Family → Privacy and data offers deletion of all local child records. Individual profiles/entries can also be removed. Device backups predating the protected storage migration and your exported copies must be managed separately.
• The in-app conversation is cleared when you leave the assistant. Dr. Baby does not persist conversation content in Firestore or application logs. Infrastructure security/diagnostic records may still be retained by providers.
• Quota records expire 48 hours after the latest use and are then removed asynchronously by Firestore TTL; deletion is not instantaneous at the 48-hour boundary.
• Delete Lumi account requests deletion of its linked Adapty profile, then removes its Firebase anonymous identity and associated quota record. Consent is withdrawn. Local child records are a separate deletion option. A new AI account is created only after renewed consent and a later request.
• Apple/Adapty transaction and subscription data may be retained for operation, fraud prevention or legal obligations. Contact the controller about deletion or access to subscription-related data. Deleting records, the app or Lumi does not cancel a subscription; manage it in Apple subscription settings.
• When you export a PDF or send a support message, the recipient you choose receives it. We do not automatically attach health records to support messages. Delete exported copies wherever you saved/shared them.

Purposes, legal bases and international transfers

Local tracking and requested subscription functions serve the service you request. Optional transmission of child health data for AI is based on your explicit, separate consent. Necessary authentication, abuse prevention and legal recordkeeping serve security and applicable legal obligations; the appropriate legal basis depends on your jurisdiction. Providers may process data outside your country, including the United States. Applicable processing agreements, lawful transfer safeguards and special-category/children’s-data conditions must be in place for the markets where the service is offered. Contact us for information about the safeguards applicable to your data. This policy does not itself establish a transfer safeguard or grant permission beyond your separate AI choice.

Support requests

If you email us, we receive your email address, your message and any attachments you choose to send. We use them to respond and handle privacy requests. Email is processed by our email provider, Google Gmail. We keep correspondence only as needed to resolve your request and meet applicable legal obligations; you can request deletion. Please avoid unnecessary child or health information.

Your rights and choices

Depending on the applicable law, you may request information, access, correction, deletion, restriction, portability or objection, withdraw consent without affecting prior lawful processing, and complain to a data protection authority. Turkish users have the rights under Article 11 of Law No. 6698 (KVKK); other applicable rights remain available. Contact alican84627@gmail.com. Explain your request without attaching unnecessary child records. Reasonable identity/authority verification may be required. The app does not sell child health information or use it for advertising.

Changes

The version and date above identify this policy. Material changes to AI recipients or data shared require a new in-app permission. Continued use alone is not treated as permission for a new AI-sharing scope.