babybites

Privacy

Privacy Policy

Last updated October 13, 2026. First Baby Bites is designed for calm, lightweight tracking with clear choices about your data.

App Data

The First Baby Bites iOS app stores allergen rosters, bite logs, reactions, calendar plans, and notes on your device. When you create or sign in to an account, this data is also sent to First Baby Bites servers so it can be backed up and synced across your devices. Account data includes your email address and onboarding preferences. You can delete your account and synced data from the Profile tab. Recipe drafts, favourites, reports, and blocked creators are linked to your account and stored on our servers. Drafts are private. When you publish a community recipe, its contents and your chosen display name become public, including on its share page; your email and feeding history remain private. Making a recipe private or deleting it disables public access, but cannot recall copies others have saved. Deleting your account also removes your recipes, favourites, reports, and blocks.

Optional Email Updates

During onboarding, you can choose to receive occasional allergen-rotation tips, product updates, and reminders. If you opt in, we store the email address you provide, your consent status, and when you opted in. This is optional and does not affect access to your account or subscription. You can unsubscribe from any marketing email.

Website Waitlist

If you join the waitlist on this website, we collect the email address you submit so we can send launch updates and early access information. If a waitlist webhook is configured, that email may be processed by the connected waitlist or email tool.

Support Messages

If you contact us for support, we may receive your email address and anything you include in the message. Please avoid sending sensitive medical information in support requests.

Analytics and Tracking

Starting with version 1.1.7, the app sends limited usage events to First Baby Bites servers hosted on Railway to understand setup, subscription screens, purchase attempts, and feature activation. Events include screen and button names, subscription plan identifiers, outcomes, bounded diagnostic error codes and stages (not error messages), app version, event times, and randomly generated installation, setup-flow, and session identifiers. Analytics does not include your name, email address, baby’s name, individual foods, feeding history, reactions, notes, or account credentials. We do not use these product events for advertising or tracking across other companies’ apps and websites. When usage analytics is enabled, a random experiment identifier links onboarding events to subscription trial, payment, renewal and cancellation outcomes from RevenueCat. This lets us compare onboarding experiences. These experiment records contain no account names, emails, or feeding details.

You can turn off “Share usage analytics” in Profile. Turning it off clears events waiting to be sent and stops future collection. Events already received are retained for approximately 90 days, then deleted. Re-enabling analytics generates a new random identifier and does not reconnect your previous experiment measurements. A separate device-only experiment setting preserves your assigned experience and any used introductory bite allowance, including across ordinary reinstalls. It is not an advertising identifier. Development and TestFlight events are separated from production reporting. Hosting providers may process IP addresses in operational logs; IP addresses are not saved in our product-event records.

In builds using Superwall, Superwall delivers the subscription screen while RevenueCat continues to process purchases and confirm subscription access. Both services use the same randomly assigned or account subscription identifier. When “Share usage analytics” is enabled, Superwall receives subscription-screen interactions, purchase and restoration outcomes, and technical information such as app version and device information. Turning that preference off disables Superwall SDK usage-event collection; requests needed to deliver the subscription screen and manage purchases still occur. We do not send Superwall your name, email, baby profile, foods, feeding history, reactions, or notes. See Superwall’s privacy policy.

Starting with version 1.1.12, Apple’s SKAdNetwork may report anonymous ad-attributed app installations without sharing your identity or device advertising identifier. If you allow tracking when iOS asks, Meta’s app events SDK also measures app installs and opens using advertising identifiers and device information. The SDK may also send diagnostic and SDK usage information. Starting with version 1.1.30, if you allow tracking, RevenueCat may also send subscription trial starts, purchases, trial conversions, and renewals to Meta using the Meta SDK’s anonymous matching identifier and a hashed subscription-customer identifier. These events include the subscription product, event time, value, and currency, so we can measure which ads lead to subscriptions. The tracking prompt remains optional; events that occur before consent may not be attributed. We do not send account emails, baby profiles, allergens, feeding history, reactions, or notes to Meta. Declining tracking does not affect app access. You can change your tracking permission in iOS Settings.

We use Vercel Web Analytics to understand website visits, which App Store links visitors select, and use of the printable food log’s Print button. Download-click events include the public page path and button placement; print-button events include only the public page path. These events do not include names, email addresses, baby profiles, feeding records, or notes. Our integration removes query strings and fragments from page URLs before sending analytics. Vercel Web Analytics does not use tracking cookies. Learn more in Vercel’s analytics privacy documentation.

Hosting providers may also process basic technical information such as IP address, browser type, device type, and request logs to operate and secure the website.

Children's Privacy

First Baby Bites is intended for use by parents and caregivers. It is not intended for children to use directly.

Your Choices

  • You can turn usage analytics off in Profile.
  • You can clear app data from the Profile tab in the iOS app.
  • You can ask to be removed from the waitlist by contacting support.
  • You can unsubscribe from optional email updates using the link in an email.
  • You can delete your account and synced data from the Profile tab. Recipe drafts, favourites, reports, and blocked creators are linked to your account and stored on our servers. Drafts are private. When you publish a community recipe, its contents and your chosen display name become public, including on its share page; your email and feeding history remain private. Making a recipe private or deleting it disables public access, but cannot recall copies others have saved. Deleting your account also removes your recipes, favourites, reports, and blocks.
  • You can delete the app to remove locally stored app data from your device.

Contact

Questions about privacy? Visit Support.