Public App PagesBabyTracker: Words & Food

BabyTracker: Words & Food

AI Growth Insights for Parents

Privacy Policy

BabyTracker: Words & Food

Effective date: 2026-08-05

This page explains how the current version of BabyTracker: Words & Food handles event data, reminder settings, local permissions, and user controls. It is intended to serve as the public privacy policy URL for App Store submission and for end users who want a plain-language overview.

Plain-Language Summary

  • BabyTracker is local-first: language records, food records, profile details, settings, and conversation history are stored on the device by default.
  • No registration, login, child account, or cloud-sync account is required.
  • After a parent enables AI data use, only a compact relevant summary for the once-daily Today insight, the minimum summary and question for an initiated chat, or a separately confirmed food photo is sent for processing.
  • A random installation identifier, subscription entitlement, and limited quota metadata are processed to protect AI usage and purchases without creating an account.
  • The app does not include an advertising SDK or third-party analytics SDK and does not sell personal data.
  • AI output is informational and may be inaccurate. It is not medical, developmental, nutrition-treatment, or allergy advice.

Data Handled On Device

  • Baby nickname, birth date or age-month information, primary language, and optional local avatar
  • Language-record text, notes, categories, mastery levels, scenes, dates, and favorite state
  • Food-record dish name, ingredients, preparation notes, remarks, preference, date, and local image URI
  • Local AI questions, answers, common questions, and conversation history
  • The compact record summary used for the optional once-daily Today insight, or the minimum relevant summary and question submitted for optional chat AI processing
  • The food photo explicitly selected for optional AI recognition
  • A random installation identifier and short-lived signed session token
  • Apple product, purchase, and subscription entitlement status synchronized through RevenueCat
  • AI scenario, quota window, request status, model identifier, token estimate, cost estimate, and latency metadata
  • Feedback text, 1-to-5 rating, optional contact information, app version, platform, source, and request identifier when feedback is submitted
  • Camera and photo-library permission state
  • Local app settings and feature-consent state

Storage and Collection

  • Parent-confirmed language and food records, profile details, settings, and conversation history are stored locally using the app framework's device storage.
  • BabyTracker does not provide cloud sync and does not maintain a parent or child account database.
  • AI input is sent only after AI data use is enabled: at most once per day when Today requests a compact insight, or for a chat or food-photo request the parent initiates. The developer gateway forwards that input for processing rather than storing raw prompts, food photos, or full AI answers in quota records.
  • Anonymous installation, entitlement, quota, request status, and cost-control metadata may be stored on developer-controlled infrastructure to operate and protect the AI service.
  • Feedback content and optional contact details are stored only when the user chooses to submit feedback.
  • Deleting individual records or uninstalling the app removes local data according to iOS storage behavior. Server-side metadata or submitted feedback can be handled through a support request.

Permissions

  • Camera permission is requested only when the parent chooses to photograph a food record.
  • Photo-library permission is requested only when the parent chooses an avatar, food-record image, or optional chat background.
  • An avatar or chat background stays local. A selected food photo is sent for AI recognition only after explicit action and consent.
  • The app does not require microphone, contacts, location, or HealthKit permissions. Denying camera or photo access does not block manual language or food recording.

Framework and Third Parties

  • Apple processes in-app purchases and subscription billing. BabyTracker does not receive full payment-card details.
  • RevenueCat receives an anonymous app user identifier and purchase or entitlement information to synchronize Pro access across purchase and restore flows.
  • Text and food-photo AI requests are routed through the developer's protected gateway to configured third-party model services.
  • AI providers process submitted content to generate the requested result under their service and privacy terms. BabyTracker limits text submissions to the consented once-daily Today insight and parent-initiated chats, and limits food-photo submissions to separately confirmed requests.
  • AI processing may occur outside your country or region and is governed by the applicable third-party model service terms.
  • For supported third-party model channels, BabyTracker applies privacy controls such as zero-data-retention routing where available, disabled provider data collection, and no unmanaged provider fallback. Production settings must also be confirmed before release.
  • The app is built with Expo and React Native and uses AsyncStorage for local app data. It does not include advertising or third-party analytics SDKs.

Sensitive Use Boundaries

  • BabyTracker is parent-facing and is not designed as a child-directed quiz, social network, or public community.
  • The app does not provide medical diagnosis, developmental screening, treatment, therapy, clinical scoring, individualized medical nutrition, or allergy decisions.
  • AI output can be inaccurate, incomplete, or inappropriate for a particular child and must be reviewed by a parent.
  • Do not use BabyTracker for emergency, medical, developmental, nutrition-treatment, allergy, or feeding-safety decisions. Consult a qualified professional when concerned.
  • The app does not rank children against other children or make eligibility decisions.

User Controls

  • You can create, review, edit, and delete language and food records before or after saving.
  • AI is optional. You can continue using manual local records without sending text or photos to an AI provider.
  • You can deny camera or photo-library permission and still use manual recording features.
  • You can restore purchases from the membership page and manage or cancel an Apple subscription through your Apple ID subscription settings.
  • You can remove locally stored app data by deleting records or uninstalling the app according to iOS storage behavior.
  • You may contact support to request help with submitted feedback or server-side installation, entitlement, and quota metadata. Verification may be required to avoid deleting another installation's data.

Questions or Updates

If a future version changes data collection, account handling, analytics usage, or cloud features, this page should be updated before the related App Store version is submitted.

Privacy Contact

For privacy questions or requests concerning submitted feedback or server-side service metadata, use the public support mailbox or feedback form. Include a reachable contact only when follow-up is needed.