Privacy Policy

Last Updated: November 5, 2026

Your privacy at a glance

Baby Soma is operated by APPROVEX LLC. This policy covers our iOS and Android apps, babysoma.app, website registration, your account dashboard and subscriptions. We use the records you and your family add to provide the features you choose. Advertising measurement is separate from your child's diary. Details, exceptions and your rights are explained below.

  • -Website analytics and marketing are optional. Use Your privacy choices in the footer to refuse or withdraw them. A subscription does not require advertising consent.
  • -We do not send child profiles, diary entries, family messages or AI conversations to advertising partners. With the applicable permissions, those partners can receive device/account matching identifiers and general conversion events.
  • -You can request access, correction or deletion at support@babysoma.app. Shared family records, legally required payment records and protected backups have the limits explained below.
  • -Cancelling renewal and deleting an account are separate actions. Manage a website subscription in your account dashboard; manage an Apple or Google subscription through the store that sold it.

1. Who we are and what this policy covers

APPROVEX LLC operates Baby Soma and is responsible for the personal information described here. This policy covers our mobile apps, related watch and widget features, babysoma.app, account registration and dashboard, purchases, support and communications. References to the service include these features where available. Our contact details are in section 15.

Read this policy together with our Terms of Service and separate Consumer Health Data Privacy Policy. Accepting the Terms or continuing to use the service is not consent to optional advertising, optional diagnostics, or a new use of sensitive information. A device permission also does not replace a separate consent required by law.

2. Information you and your family provide

  • Accounts: email address or phone number, account identifier, sign-in method, profile information and account settings. If you choose Apple or Google sign-in, we receive the account information those services make available for that sign-in, such as your name, email or relay email and profile image.
  • Child profiles and care records: name, date of birth or due date, profile details and optional photo; sleep times, wake windows, notes, routines and schedules; feeding, pumping, milk, diaper, weight and height records and related preferences that you choose to enter.
  • Health information: optional temperatures, medicines and entered doses, vaccinations, reactions, illness periods, Sick mode, teething, notes and reminders. Sleep, feeding, growth and other records can also be health information when they reveal health status. Our separate health policy describes this processing.
  • AI and voice features: your questions, assistant replies, conversation context and relevant child/care summaries. This includes photos or other attachments you choose to send and audio or recognized text when you use a voice feature. Do not include information about someone else unless you have authority to provide it.
  • Family sharing: invitations, caregiver membership, messages, photos and voice messages, and records added by invited caregivers. Everyone authorized for a child profile may see and change the records available to that family.
  • Purchases and referrals: purchase channel, plan, order or transaction identifiers, subscription status, payment history, billing contact details available from the provider, referral codes and reward or commission records. Payment providers collect card or cryptocurrency payment details directly. We do not receive your full card number or card security code.
  • Support and communications: messages, contact details, feedback, attachments and the account or technical context needed to help you, plus your notification and email preferences.

3. Technical information, permissions and diagnostics

Operating the service produces technical information such as IP address, browser or device type, operating system and app version, account or installation identifiers, timestamps, errors, security logs and push-notification tokens. Providers may receive this information when your device connects to their service. We distinguish necessary service/security processing from optional analytics and advertising.

Camera, photo library, microphone and notification permissions support the features you request, such as family messages, profile photos, vaccination recognition, voice commands and reminders. You can change device permissions in operating-system settings. Connected watch features, widgets and live activities may display the records or status you choose on that device. Consider who can see your device and lock screen.

Optional technical activity journal: this is off by default and requires a separate choice in Settings. It records technical screen codes, named actions, timing, errors and responsiveness, app/OS versions and an installation identifier linked to your account for authorized support staff. It excludes typed text, screenshots, photos, diary amounts and notes, message contents, payment details and tokens. It is not session replay. A visible indicator shows when it is enabled. Withdrawal stops collection on that device immediately, including offline; the account-wide choice synchronizes when online. Reports have a 14-day availability limit, after which expiry and cleanup remove them. Protected backups can retain deleted records for up to 28 additional days. Minimal consent records are kept until account deletion is processed.

Crash reporting: Firebase Crashlytics separately processes technical crash, error and freeze reports with app/device information and an account identifier. Current release settings enable reporting by default; you can turn it off in Settings - Data and diagnostics. Some SDK changes take full effect after restarting the app. Firebase describes a 90-day retention period before removal from live and backup systems begins. We do not use Microsoft Clarity session replay.

4. Purposes and legal grounds

  • Provide the service you request: register and authenticate your account; synchronize records; provide schedules, tracking, family sharing, AI answers, reminders, exports and purchased access. For ordinary account and contract administration, the basis is performance of our contract or steps you request before entering it.
  • Consent where required: optional website analytics and advertising, optional technical activity journals, marketing communications where consent is required, and processing or disclosure of health or other sensitive information where the applicable law requires consent. Health information requires an additional lawful condition under laws such as GDPR, commonly explicit consent. An ordinary contract basis alone does not remove that requirement.
  • Legitimate interests where permitted: maintaining security, preventing fraud, resolving support issues, keeping limited operational records and improving reliability. These interests must be balanced against your rights and cannot override a required consent or a special protection for health or children's information. You can object to processing based on legitimate interests.
  • Legal obligations and claims: accounting, taxes, lawful requests, disputes and protecting legal rights. We retain only information needed for the applicable obligation or claim.

We use service messages for account, security and subscription matters. Promotional messages are separate and include an unsubscribe option. Unsubscribing from promotions does not prevent necessary service messages. We do not make decisions with legal or similarly significant effects solely through automated processing; sleep schedules and AI suggestions are informational and are not medical decisions.

5. AI processing and model improvement

AI features send your request and relevant context to OpenAI or Anthropic (Claude), depending on the feature and routing. We currently use their hosted APIs for AI responses and no longer operate a separately rented GPU service. Context can include child profile details, sleep/care summaries and previous messages. A health-diary summary is included only when you separately enable the diary option for the assistant. The diary summary excludes medicine doses, free-text diary notes and entry authors; information you type directly into a message is still part of that message.

Vaccination recognition sends the photo you choose to Anthropic for recognition. We do not retain that source photo or the extracted text as a vaccination document; the entries you review and save become diary records. This does not promise that the provider retains no temporary processing or security copy. Other photos sent to chat or family sharing follow the retention rules for those features. OpenAI may also process audio for transcription and food descriptions for Soma Plate pictures where those features use it.

We retain server-side assistant questions and replies for a normal period of up to 90 days for conversation support, quality review and troubleshooting, with scheduled expiry and cleanup. Authorized staff may review necessary samples. Copies used in a separate improvement or evaluation workflow must have a documented purpose, retention period and lawful basis.

We have used questions, replies and sleep summaries with names, birth dates and contact details removed to evaluate and train our own model, including with Anthropic/OpenAI tools and rented GPU servers in the United States or European Union. Removing these fields is pseudonymization, not a guarantee of anonymity: free text can still identify someone or describe health. We must not treat such copies as unrestricted anonymous data. Further reuse of identifiable or pseudonymized conversations for training requires the legal grounds and any separate consent required for that use. Health-diary entries are not a training source. You can ask us to identify and delete personal information in improvement copies as well as account-linked logs.

AI providers and infrastructure operators process information under the settings and terms applicable to the service we use; provider retention and access can differ. We do not promise zero retention by every provider or that all data always stays in one country. Ask us about a particular feature or recipient before sending information you do not want processed there.

6. Recipients and disclosures

  • Google Cloud/Firebase: authentication, database, functions, file storage, push notifications, technical operations, analytics and Crashlytics as applicable.
  • Anthropic and OpenAI: AI processing described in section 5 through their hosted services.
  • Your authorized family: shared child records, messages and files. Removing someone's access does not erase copies they previously exported or saved.
  • Apple, Google Play and RevenueCat: app purchases, entitlement verification and subscription management. Website providers Stripe, NOWPayments and Coinbase Commerce handle their supported payment methods. These providers also process information for their own payment, fraud and legal responsibilities under their notices.
  • Support and email tools: our email services and private Telegram support group. A support request or summary, account email/sign-in method, subscription context and submitted attachments can be available there to authorized staff. Avoid sending unnecessary child or health information to support.
  • Google Analytics/Ads, Google AdMob and Meta Platforms: optional analytics, ads and conversion measurement subject to the choices and restrictions in section 7.
  • Referral partners: limited referral, reward or commission records needed to operate the program. They do not receive child diaries or AI/family conversations.
  • Professional advisers, authorities or a business successor: only as necessary for legal/accounting advice, a valid legal obligation, protection of rights or a business transaction with appropriate confidentiality and privacy protections. A new purpose still requires the notice and legal grounds applicable to it.

We do not sell child records or health information or disclose their contents to advertisers. We do not exchange personal information for money. Some consented advertising disclosures can count as a sale, sharing or targeted advertising under a particular US privacy law even without money changing hands; you can opt out as described below. Our separate health policy governs consumer health information.

7. Cookies, advertising and your choices

Website

Necessary storage supports sign-in, security, checkout and saving your privacy choices. Optional categories are off until you choose them. Analytics permits website usage measurement; marketing permits advertising measurement and matching. You can accept, refuse or choose categories with the banner and reopen Your privacy choices in the footer at any time. Refusing does not prevent registration, purchases or core service access.

We load Google Analytics only with analytics permission and Google Ads or Meta Pixel only with marketing permission. Private account, support and invitation pages and payment success pages are excluded from these browser measurement tools. We do not queue pre-consent advertising events for later sending. On withdrawal, we stop optional browser measurement and remove relevant first-party measurement cookies where we can. A page reload may be needed to unload an already running third-party script.

With marketing permission, Meta may receive general page/offer views, checkout, trial and purchase events, amount/currency, browser/device information, IP address, _fbp/_fbc cookies and matching identifiers. Email, phone, name, city, region, postcode, country and the server-side account identifier are hashed before server transmission when available. Cookie values, IP address and user agent are not hashed. Hashing is matching/pseudonymization, not anonymization; Meta can associate a hash with a person. Browser advanced matching processes the account details you supply for that purpose.

Google may receive page/usage events and, with the relevant choices, advertising click identifiers and conversions. Server-side purchase analytics use a Google Analytics client identifier, transaction identifier, amount and currency. Advertising use and personalization are separately denied when marketing is refused. We do not send child profiles, care/health diary entries, family messages, uploaded child files or AI conversations as advertising event data.

Our server checks a privacy receipt both at checkout and when a later conversion is sent. Missing, expired or withdrawn permission suppresses the corresponding event, including for legacy subscriptions without proof. Payment and access are processed independently. Website choices normally expire after 180 days. The preference receipt uses a random token separate from advertising identifiers; the server stores its hash and the choices. When you are signed in on the website, we also record refusals against that account so a known account's later server events respect them. A new explicit choice can change these settings.

We honor Global Privacy Control (GPC) as a refusal of website marketing and advertising sharing. It does not automatically reject all unrelated analytics. If you withdraw while offline, the browser choice is saved immediately and the server update is retried when online; until it reaches us, a previously authorized server event may already have been processed. The settings show when synchronization is pending. Contact us if you need an account-wide opt-out and cannot use the settings. Other devices, signed-out browsers and app permissions have their own controls until we can associate the request with your account.

We may keep aggregate first-party page/store-link counts without persistent visitor identifiers when no optional analytics choice has been made. An explicit analytics refusal stops these optional counters. Identifiable visitor/session attribution requires analytics permission. Necessary access/security logs are separate.

iOS and Android apps

The apps have separate analytics/advertising settings. iOS App Tracking Transparency permission is also required for tracking covered by Apple's rules; Android and AdMob use their applicable privacy/consent controls. ATT permission alone is not a substitute for every consent required by law. Depending on your permissions, SDKs can process app/device identifiers, general app events and account matching details such as email, phone and a hashed account identifier to measure installs, trials and purchases. We do not attach child or diary content to those advertising events.

Where available, AdMob rewarded ads support free features. Ads and their personalization depend on applicable consent and platform settings; non-personalized ads can still involve technical data. Manage app privacy choices in Settings, iOS tracking permission in system settings, and Android advertising permissions in device settings. A website opt-in does not by itself grant app tracking permission.

8. Retention, account deletion and family records

Account and child/care records are generally kept while needed for the account and chosen features, until you delete them or request deletion. Shared records can remain available to the family owner when a caregiver leaves or deletes their own account. Deleting an owner's child profile schedules deletion of that profile, its records and stored files. Ownership and other caregivers' rights matter; deleting one caregiver does not automatically delete everyone else's child history.

We aim to process routine account-deletion requests within 7 days. This is not a promise that every backup, provider copy and legally required record disappears immediately. Authentication/profile data, owned child data and account-linked AI history enter their applicable deletion workflows; failures may require retries. Support requests and associated attachments are kept while needed to resolve the issue and any related claim, then reviewed for deletion. Separate AI and diagnostic retention periods are in sections 3 and 5.

Payment, subscription, tax, fraud, dispute and audit records can be retained after account closure for the applicable legal period or a necessary legal claim. They can still contain personal identifiers; removing a profile does not make every retained record anonymous. Minimal opt-out records can remain necessary to honor your refusal. We restrict retained information to the relevant purpose instead of using it for advertising.

Deletion from active systems is distinct from backup expiry and deletion by independent payment providers. Protected backups are not used for normal service and are removed through their retention cycle; consumer health deletion is handled under the separate health policy, including the applicable backup deadline. If a backup must be restored, deletion requests must be reapplied. An export or attachment already saved by you or another family member is outside our server deletion process.

Cancel subscription renewal separately in the website dashboard or the selling app store. Account deletion does not guarantee cancellation of a subscription managed by Apple or Google, and cancellation does not automatically erase your records. See the Terms for purchases, cancellations and refunds.

9. Access, deletion and other rights

Depending on your location and the applicable law, you can request confirmation of processing, access and a copy, correction, deletion, restriction, portability, information about recipients, withdrawal of consent, objection to legitimate-interest processing, and refusal of targeted advertising or sale/sharing. You can exercise applicable rights through an authorized agent or a parent/guardian where permitted. We do not unlawfully discriminate against you for exercising them.

Email support@babysoma.app with your request and enough information to locate the account. We verify identity and authority proportionately, without asking for unnecessary sensitive documents. We do not ask you to email a password, authentication token or full payment-card details. Rights can have legal exceptions, which we explain when relevant.

We respond within the applicable deadline: normally one month for GDPR/UK requests or 45 days under relevant US privacy laws. A lawful extension requires timely notice and reasons. Requests are normally free; any permitted fee or refusal for abusive/excessive requests follows the applicable law. If we decline, you can ask for an internal review by replying with the subject Privacy appeal. We explain the outcome and applicable external complaint options. You can complain to your local data-protection authority, the UK ICO or the relevant US state authority; the health policy includes the Washington complaint route. Consent withdrawal does not undo lawful processing before withdrawal.

10. Security and access

We use access controls, authentication, encrypted transport and provider security measures to protect information. Access is limited according to role, family membership and operational need. No system is completely secure. Download or invitation links can give access to the person holding them; keep them private, revoke family access when appropriate and avoid sharing sensitive exports publicly.

11. International processing

APPROVEX LLC is in the United States. Firebase/Google, AI providers, payments and support tools may process information in the United States, European Union or other countries in their service chain. Protections and government-access rules can differ. A European-language website does not mean all processing occurs in Europe.

Where GDPR/UK or other transfer restrictions apply, a transfer needs an applicable adequacy decision, approved contractual safeguards or another valid legal mechanism, together with any required assessment and additional protections. Simply using the service or accepting our Terms is not blanket consent to an international transfer. Contact us for information about the safeguards and locations applicable to your processing.

12. Children and parental authority

Baby Soma is a service for adults, including parents and lawful guardians, not an app inviting children to register independently. Child records are supplied by adults with authority to do so. We do not use child diary information for targeted advertising. If a child has registered independently or you believe information was supplied without authority, contact us so we can investigate and take the required action.

13. Google sign-in information

Google sign-in requests basic identity/profile information needed to create and authenticate your account, such as name, email and profile picture. We do not request access to your Gmail messages, Drive documents or calendar for this sign-in. Firebase Authentication and the account service process the returned identity information. Optional advertising matching can use account contact details only under the separately applicable permissions described above; signing in is not advertising consent.

You can remove Google access through your Google account and request deletion of your Baby Soma account. Revoking Google access alone does not erase records already held in Baby Soma. Our use and transfer of information received from Google APIs must comply with the Google API Services User Data Policy, including Limited Use requirements where those requirements apply to the data/scopes involved.

14. Changes

We publish changes here with an updated date. We give appropriate notice of material changes through the service or email and obtain a new consent when required before a new consent-based use. A revised policy does not retroactively authorize processing that lacked a lawful basis.

15. Contact

APPROVEX LLC
5830 East 2nd Street
Ste 7000 #18761
Casper, Wyoming 82609
United States

Email: support@babysoma.app. For account and subscription help, visit Support or your account dashboard.

© 2026 · Baby Soma · All rights reserved.