1. About this policy
This Privacy Policy explains how Birth Companion (“we,” “our,” or “us”) treats information when you use our iOS mobile application, Apple Watch companion app, and related web pages. We believe your pregnancy and labor experience is deeply intimate, and we design our software to collect the minimum data necessary to provide a soothing, functional experience.
2. Local-first data architecture
The core information you generate in Birth Companion is stored locally on your Apple device using SwiftData for the journal and local storage for settings:
- Contraction (Wave) logs: Start timestamps, end timestamps, durations, and time elapsed between waves.
- Sensation & intensity ratings: Personal reflections on whether sensations felt light, medium, or strong, or notes on pressure points.
- Personal notes: Any text notes you attach to an individual contraction entry.
- App settings & preferences: Selected appearance (Light, Dark, System), breathing preferences and haptic feedback toggles.
We do not upload your contraction journal, recorded contraction times, durations, intensity ratings, or personal notes to our servers, RevenueCat, or Google Analytics. General usage events are described below and do not include those journal contents. Device backups may include local app data according to your Apple backup settings.
3. No account or email registration
Birth Companion does not require you to create an account, register an email address, provide your full name, or sign in with social media. No named app account is needed. Subscription processing uses an app user identifier, as described below.
4. Breathing guidance
The current version provides visual breathing guidance and optional haptic feedback. It does not offer AI chat, AI voice support, ambient soundscapes, microphone recording, or HealthKit integration. No conversation prompts or audio recordings are collected by these unavailable features.
5. Apple Watch & Live Activities
If you pair Birth Companion with an Apple Watch or use Lock Screen Live Activities, your contraction timing state is shared securely across your own devices using Apple's native WatchConnectivity and ActivityKit frameworks. WatchConnectivity transfers timing records and access status between your paired devices. Delivery may be delayed when devices are disconnected. Live Activities can display timing information on your Lock Screen; you control their visibility in iOS settings.
6. In-App purchases & third-party service providers
We rely on trusted industry infrastructure to deliver specific app capabilities:
- Apple In-App Purchases (StoreKit): Apple processes all payments, renewals, and refunds. The app receives purchase and subscription status needed to unlock paid features. We never receive or store your credit card or bank details.
- RevenueCat: We use RevenueCat to validate purchases and manage subscription access. It processes an app user identifier, purchase history and transaction information, and technical app/device information needed to provide this service. An app user identifier is a pseudonymous identifier, not a guarantee of anonymity. RevenueCat’s purchase SDK can include Apple’s identifier for vendor (IDFV), when available, in technical request headers used to operate the subscription service. This is separate from Firebase Analytics and its app-instance identifier. Disabling usage analytics does not disable the purchase processing needed for your subscription. We do not send contraction records or personal notes to RevenueCat. See RevenueCat’s Privacy Policy for its processing and retention practices.
- Google Analytics for Firebase: In versions that include usage analytics, we use Google Analytics for Firebase to understand general app usage, feature and screen interactions, and paywall and purchase outcomes. Analytics receives a pseudonymous app-instance identifier, app and device information, and approximate country and region derived from network information. The SDK records event timestamps and may automatically measure app sessions and StoreKit purchase or subscription events, including product identifier, name, and price. These records can be associated with the same app installation; they are not a named app account. See Google Analytics data-disclosure information and Google Analytics terms.
We do not send your contraction journal, recorded contraction start or end times, durations or intervals, intensity ratings, pressure or sensation details, personal notes, care-contact details, or exported PDF records to Analytics. The app does not request GPS or Apple Location Services for analytics. Our custom analytics events use limited categorical values rather than journal contents or medical measurements. General app interactions and their SDK event timestamps may still reveal when the app was used.
We use Analytics to improve the app, not for cross-app advertising or sharing data with data brokers. In the Firebase Analytics integration, we do not set a named user ID, and IDFA and identifier-for-vendor collection are disabled. Firebase’s pseudonymous app-instance identifier remains in use while usage analytics is on. These Analytics controls do not disable the technical identifiers used by RevenueCat to operate your subscription. Google Analytics processing is governed by its applicable terms and privacy safeguards. Providers receiving personal information must protect it consistently with this policy and their applicable data-protection commitments.
7. Data export & your choices
You can manage your local journal:
- Exporting records: You can generate a PDF summary in the app at any time to share directly with your midwife, obstetrician, or partner.
- Deleting records: Open a record in the Log tab to edit or delete it. The journal, including PDF export and individual deletion, remains available without a subscription. When settings are accessible, the gear button on the Timer screen also offers Clear Personal Log.
- Free-recording counter: The app retains completed-record identifiers separately from journal entries to count the ten free recordings and avoid counting duplicate Watch deliveries. Deleting journal entries does not reset this counter.
- Shared copies: Deleting a local entry does not recall exported PDFs, backups, or copies already delivered to another device. You manage those copies separately.
- Usage analytics: Usage analytics is enabled by default in versions that include it. You can turn it off or on in the app’s privacy and analytics controls without changing your subscription or access to the local journal. Turning it off stops future Google Analytics for Firebase collection; RevenueCat subscription validation and related purchase reporting continue separately. It does not automatically erase records already received by a provider. Those records are subject to the provider’s applicable retention settings and terms. Deleting local journal entries or uninstalling the app does not recall existing Analytics records. Contact us about privacy requests using the address below.
- Support: If you email us, we receive the email address and information you choose to include and use them to respond to your request. Please avoid sending unnecessary health information.
8. Medical disclaimer
Birth Companion is not a medical device. It is designed solely for relaxation, informational support, and convenience timing. Nothing in the app or this policy creates a doctor-patient relationship. For any questions regarding the progression of your labor or your physical well-being, always contact your qualified healthcare provider.
9. Children’s privacy
Birth Companion is intended for expectant mothers and their adult birth partners. We do not knowingly collect personal information from children under 13 (or under 16 where required by local law).
10. Updates & Contact
We may update this Privacy Policy to reflect app improvements or regulatory updates. The revision date at the top indicates when modifications took effect. If you have any privacy questions or requests, please reach out to us: