Bloom Privacy Policy

Who operates the service

The service is operated by מעיין אברהם מלט, trading as Bloom. This policy covers the Bloom app and app.bloomfit.store. The store at bloomfit.store is a separate commerce service of the brand.

Account and sign-in

Sign-in is available with email and password, Google, and Apple on iOS. Firebase Authentication processes sign-in information and the account identifier. Your name and email, provided by you or the sign-in provider, may be stored in the Firebase profile for identification, access and sync.

The password is submitted to Firebase authentication, not stored as a pregnancy-profile field. If Apple supplies a relay email address, that may be the address associated with your account.

Pregnancy profile and records

The profile may include an estimated due date and its source, number of babies, names and nicknames, favourite names, whether this is a first pregnancy, and onboarding preferences. You can also enter mood, symptoms, appointments and movement records. These may be sensitive personal health and pregnancy data.

The information supports your weekly view, relevant content, organisation and tracking. The profile and supported records are stored on the device and synced to the account in Cloud Firestore. Not every app record is synced. Network connectivity and account access affect sync availability.

Preferences such as audio favourites, guide progress, preparation lists and a shopping cart are also stored in app storage on the device. Some records can remain on the device while offline. A local copy is not a guaranteed backup or medical record.

Nadia and transmission to OpenAI

Nadia uses artificial intelligence for general information. Opening the screen performs availability and entitlement checks with the Bloom server even before a question is sent. Some actions and safety replies are handled locally. After consent, a conversation request sends Bloom up to ten recent messages, up to 2,000 characters each, the computed pregnancy week and response language. The request is authenticated to the Bloom account for permission and entitlement checks.

After the consent check, the latest question may be sent to OpenAI moderation. Messages and the pregnancy week are sent to OpenAI with response instructions to generate a reply. The request does not attach name, email, estimated due date, baby names or account identifier as profile fields. However, personal or medical details you type into a message or that appear in conversation context will be transmitted as part of it. The conversation is therefore not anonymous; avoid information that is not needed for your question.

Requests use store:false, meaning they do not request storage of the response as a retrievable API resource. This is not a zero-retention promise: providers may process and retain information for security, abuse monitoring and legal requirements. OpenAI states that API data is not used for training by default unless the customer opts to share it. Retention at OpenAI depends on the service, applicable data controls and legal requirements, as described in its data policy.

Nadia notifications and the updates feed use a generic message that the answer is ready, without copying its content. An answer selected for reporting is stored separately as explained below. Usage and entitlement counters are stored on the server. Avoiding a new question does not delete data already transmitted.

Bloom asks for your consent before a conversation is sent to OpenAI, with Not now, a policy link and Agree and continue. Withdraw through Settings, Nadia AI consent, Withdraw consent. The choice and its version are stored on the device and in the Firebase account to enforce it. If a message says withdrawal did not sync to the server, do not assume it has already applied on another device. Reconnect and contact support if withdrawal cannot be completed. Withdrawal cannot recall data already sent and does not prevent use of the rest of Bloom.

Choose Report answer in Nadia and select a reason. The report sends Bloom the selected answer and reason, not the entire conversation. It is linked to the Firebase account and stored with handling status and creation/expiry times for safety and quality review. Each report is assigned an expiry date after 30 days. Cleanup of expired records is handled separately, so the expiry date is not confirmation of completed deletion. Contact us to check the status or request deletion. A reported answer may contain personal details from the conversation.

• OpenAI API data policy

Subscriptions, store and support

1. Bloom Plus: Apple or Google manage the subscription transaction. RevenueCat and the Bloom server process account and purchase identifiers, plan, status and entitlement validity for access, restoration and limits. The website does not request a card number to restore access.
2. Bloom store: the app integrates a catalogue and cart, with checkout in the Shopify-based store. Order, contact, shipping and payment details are provided through checkout under the store and payment providers’ policies. For shipment lookup, email and order number pass through the Bloom server to Shopify. Benefits may link an account identifier, benefit code and order; usage counters help prevent misuse.
3. Support: the sender address, submitted request and correspondence are stored in the email service to handle the enquiry. Clicking an email link only opens a draft; the website does not send the request.

• Restore Bloom Plus
• Bloom store and purchase policies

Technical data and notifications

Firebase/Google provide authentication, database and server functions. Infrastructure and SDKs may process installation and account identifiers, device and app details, IP addresses, request times and errors for operation, security and diagnostics. The information processed depends on the feature used, app version and provider configuration.

Local notifications and reminders use device permissions and in-app preferences. They may contain weekly information or a generic notice that a Nadia answer is ready. Review lock-screen preview settings. Turning notifications off does not delete the local feed. Notifications are not medical monitoring or a promise of delivery at a particular time.

Website delivery and security infrastructure, including Cloudflare, can process browser-request information and logs to serve and secure pages. The website source does not integrate marketing pixels or analytics tools. Infrastructure providers separately process operational and security information as described on the cookies page.

• Website cookies and storage
• Firebase privacy and security

Providers and processing outside Israel

Recipients depend on the feature: Firebase/Google for infrastructure and identity, OpenAI for Nadia and safety checks, RevenueCat for subscription entitlement, Apple/Google for sign-in and billing, Shopify for commerce, website hosting/delivery providers including Cloudflare, and the support email service. Data can be processed in other countries. A server function located in Europe does not guarantee that all information or copies remain in Europe or Israel.

We use providers for the purposes described in this policy, including delivering the service, security, handling enquiries and meeting legal obligations. Contact us with questions about data recipients, international transfers and rights that apply to your information. No system can guarantee absolute protection against unauthorised access or data loss.

• RevenueCat privacy
• Shopify privacy

Retention and deletion

Account data and cloud records are intended to be retained to provide the service while the account is active and included in handling a deletion request. Local records depend on the device and app-data cleanup. Provider records, backups, logs and correspondence are not necessarily deleted by the same action or at the same time.

Transaction records or limited information may need to be retained for a documented lawful reason, such as accounting obligations or a dispute. Retention is limited to information needed for the obligation or dispute and the period required for that purpose. You can request details of the information retained, the reason and the retention period applicable to your case. Deletion from devices, backups and provider services may take place at different times.

Bloom keeps a separate Firebase operational record linked to the account identifier, with deletion status and request/completion times. It blocks access during deletion and supports retry after failure; it contains no profile, transcript or payment details. The record is assigned an expiry date 30 days after deletion completes and is included in expired-record cleanup. While a request is pending, the record is retained to complete processing. A pending status does not confirm that data has been erased; contact us to check its status.

If an error or pending-deletion message appears, do not assume the process completed. Contact support to clarify the status. A deletion bug is not a permitted retention exception.

• Delete account and data

Requests about your information

You can contact us for access, correction, a copy or deletion of information. Additional rights, such as restriction, objection, portability or withdrawal of consent, depend on applicable law and the processing involved. A request does not guarantee erasure of records that must legally be retained, but you can ask for an explanation of a refusal or limitation.

For an initial request, provide your account email if known, sign-in method and a brief description. Do not send passwords, verification codes, identity documents, card details or medical information. If ownership verification is needed, we will request only information proportionate to the request.

You can choose not to enter an optional record or send questions to Nadia. These choices do not delete data already provided. Device notification settings are separate from transmission to Nadia and website cookies.

• What you can manage and where

Medical information and policy changes

Bloom provides general information and tools for pregnancy organisation and wellbeing. It is not a medical service or medical device and is not intended to diagnose, treat, cure or prevent any medical condition, or provide emergency monitoring. Contact your healthcare team about medical concerns. In an emergency, contact local emergency services immediately; do not wait for an app or email response.

We will update this policy when the service, providers or use of information changes. For material changes, we will provide notice and seek consent where required by applicable law. Linking to this policy or continuing to browse is not a substitute for explicit permission to transmit data when required.