Privacy

Version: 22 October 2026. Effective date: 10 November 2026.

1. Who is responsible for your data

BeMomsy is operated by Gleb Malenkov (Malenkov Gleb), an independent developer in Israel registered as an esek patur. Postal address and applicable registration details: 6 Ze’ev Orlov St, Apt 76, Petah Tikva 4920206, Israel. For privacy questions and deletion requests, contact support@bemomsy.com.

Representatives in the European Economic Area and the United Kingdom, and a data protection contact where appointment is required: will be listed here once appointed; until then, write to support@bemomsy.com.

This policy covers the BeMomsy app, website and support. The app is intended for adults who keep a child-care journal. Children do not create accounts. Journal entries nevertheless contain their personal information, and this policy applies to that information.

2. The local journal and cloud features

Without cloud features, the contents of your personal journal are not synced to BeMomsy’s servers. Sign-in is required. Sign-in, account services, subscription checks and online actions you choose transmit the information needed for those actions. For example, checking or deleting a child’s profile may transmit the child’s technical identifier.

Cloud features transmit child profiles, records, notes and reminders for storage, recovery and sync. An invited adult receives shared records through the cloud even without their own BeMomsy+ subscription.

A child’s profile photo is stored in the app on the phone and is not included in ordinary profile sync. A photo you add to your own adult profile is uploaded to Supabase. Adding photos to events is unavailable in version 1.0. A backup file you create may include the child’s profile photo.

A device backup or a file you choose to save or share is separate from BeMomsy sync. App data may be included in an iPhone system backup, depending on device settings and the particular storage location. The absence of BeMomsy sync does not turn off Apple backups.

3. Information we receive

4. Purposes and legal grounds

We use account information to provide sign-in, check access, manage subscriptions and answer support requests. The cloud journal provides storage, recovery and sync. Family access lets adults maintain a shared journal. Assistant processes a message and permitted context to answer or propose an entry. A proposed entry is saved to the journal after your confirmation.

Technical information supports operation of the service, account security, abuse prevention, notifications and error correction. We do not use children’s journals for advertising, sell them or train our own models on them. We do not use Assistant to make solely automated decisions producing legal or similarly significant effects on you or a child. Anonymous usage statistics show where the app is hard to use so we can fix it; this relies on legitimate interests, and you can turn it off in Settings.

Where the GDPR or UK GDPR applies, processing of adult information necessary for the account and subscription is based on performance of the contract. Optional cloud processing of child information and its use by Assistant rely on consent. Processing health information also requires explicit consent from a person entitled to act for the child. Minimal processing for security relies on legitimate interests, taking adults’ and children’s rights into account. Mandatory records and legal claims require the specific grounds and periods identified in section 9.

In Israel and other applicable jurisdictions, processing must meet local requirements concerning notice, consent, security and individual rights. This policy does not replace separate consent where the law requires a particular form, and does not displace data-localisation or international-transfer requirements.

Acceptance of the Terms of Use, reading this policy, consent to a specific processing purpose and iOS system permissions serve different purposes. None automatically replaces the others.

5. Children and family access

Only add a child’s information if you are entitled to act for them or have the necessary permission. Family ownership and other adult roles are technical permissions within the app. They do not establish parenthood, guardianship or authority to consent to every use of the child’s information.

An invitation gives an adult access to all children in the family within the assigned role. If a new shared child is added, their records are also covered by family access. An adult who can read records can export a separate copy. Grant access only to a person to whom you are entitled to disclose this information. Private Assistant conversations do not become part of the shared family journal.

The family owner can end shared access. A member can leave the family. The server stops further access once the action is confirmed. An offline device learns of the change later. Files already saved outside BeMomsy are not automatically erased.

Data rights belong to the child. Contact support about access, correction, deletion or disputed authority. We may request necessary evidence of identity and authority. An app role does not resolve a dispute between lawful representatives or remove the child’s rights.

6. Assistant and voice

Where Assistant is available and you have accepted its separate consent, messages are processed through BeMomsy’s server. Anthropic’s Messages API provides text responses. OpenAI’s Responses API may act as a backup provider. Following a provider change, a later request may include part of the current conversation.

In a selected child’s chat, BeMomsy may add the child’s name, date of birth and calculated age, recent measurements, dates, times and relevant event details. Context may include temperature, symptoms, illnesses, medicines and recorded doses, vaccinations and food reactions. The general chat does not automatically receive a child’s profile or journal.

BeMomsy does not automatically add journal notes or photos to Assistant context. Text you send to the chat is transmitted as a message, including text copied from notes. Voice is transmitted for recognition before you send the transcript to the chat.

Voice input uses Apple Speech. Apple recognises speech on the device when supported. Otherwise, audio may be sent to Apple while recording. After recording ends, BeMomsy sends the audio file through its server to OpenAI’s Audio Transcriptions API. You can review and edit the transcript before sending it to the chat. Transmission for recognition takes place before the text message is sent. iOS microphone or speech-recognition permission does not replace information about the recipients.

Full chat history is stored on the current phone and is not synced between devices. Part of the conversation is still sent to the server and selected AI provider to produce a response. The separate temporary server response cache and technical records are described in section 9.

Under their published commercial terms, Anthropic and OpenAI do not train models on API data by default. This does not mean there is no retention. Rules can differ by product, model, voluntary feedback and account settings.

Anthropic and OpenAI process this data under their data processing terms with BeMomsy, which require the same or equal protection of personal data as this policy.

Anthropic’s standard API input and output retention is up to 30 days. Published periods for material flagged for policy enforcement are up to two years, safety scores up to seven years, and separately submitted feedback up to five years. Certain models may have different terms. OpenAI Responses abuse-monitoring logs are generally kept for up to 30 days; disabling storage of the response object does not remove that period. A separate encrypted technical cache may persist for up to 24 hours. For Audio Transcriptions, the published table separately states no content retention in application state or abuse-monitoring logs. Technical caches, legally required retention and special contractual arrangements are considered separately.

Provider information: Anthropic organisational data retention, OpenAI API data controls. Deleting a BeMomsy chat does not immediately erase these providers’ logs.

7. Support and error reports

A support request transmits its subject, message, reply address, app version and device information. Attaching an error report is enabled by default. You can turn it off before sending. You can send a request without a report.

The automatic report contains technical information and errors from the previous 72 hours. Its defined contents exclude saved journal entries, notes, children’s names and photos. The request itself is not anonymous: you provide a reply address and may describe personal circumstances. Do not send passwords, sign-in codes or unnecessary information about a child.

The request is stored in Supabase and the report in separate private storage. Cloudflare forwards the request and attached report to the support Gmail account. Further replies take place by email. Deleting a Supabase row or file does not itself erase the Gmail message or attachment. Separate retention periods are addressed in section 9.

8. Recipients and international transfers

For certain operations, Apple and Google independently determine processing purposes, including for their own accounts and purchases. Other providers’ roles depend on the service and applicable agreement. Provider legal entities and contractual safeguards: available on request at support@bemomsy.com.

A main database in Germany does not mean that all processing occurs within the EU. Information may be processed in Israel, the United States and other provider infrastructure locations. AI processing cannot be described as exclusively US-based. Specific countries, applicable international-transfer safeguards and how to obtain a copy of them: available on request at support@bemomsy.com.

9. Retention periods

Removal from the interface, termination of access and physical cleanup are separate steps. An iPhone system backup, a doctor’s file or an export in an app you selected is not automatically deleted with the BeMomsy account.

10. Controls, withdrawal and deletion

Cloud processing. To request withdrawal of consent to cloud processing, write to support@bemomsy.com. You can delete your account in Profile. The current version has no separate cloud-consent withdrawal action in Settings. A support request is not an immediate command to stop every device; its outcome and next steps are communicated when the request is handled.

Assistant. You can withdraw consent in Assistant Settings. The app clears local chat on this phone and sends the withdrawal to the server. If there is no connection or the request does not complete, withdrawal remains pending and can be retried. Other devices apply the change after receiving the server state. A request already in progress and information previously sent to a provider do not disappear retroactively.

Voice. You can choose not to use voice input and disable microphone and speech-recognition permissions in iOS Settings. BeMomsy currently has no separate action to withdraw consent only for voice. Withdrawal of Assistant consent also applies to further use of its voice features.

Children and family access. Deleting a cloud child ends access to that child’s shared records. It does not erase other adults’ own journals. Leaving a family or removing a member ends their access, without deleting the owner’s child journal. A request concerning the child’s rights is considered separately from the requester’s technical app role.

Account. You can export data before deletion. Deleting the owner’s account ends shared access to their cloud children and family. The journal on this iPhone is deleted with the account, so download a copy first. Account deletion does not mean that every associated record has already been physically erased; section 9 explains periods and exceptions.

Withdrawal does not affect earlier lawful processing. Deleting the app or account, withdrawing consent or leaving a family does not cancel an Apple subscription. Renewal management and refund requests are separate and follow Apple’s rules and applicable law.

11. Your rights

Depending on applicable law, you may request access and a copy, correction, deletion, restriction, portability, withdrawal of consent and objection to legitimate-interest processing. The child’s rights may be exercised by a person with the necessary authority and, where the law provides, by the child.

Write to support@bemomsy.com. We may request only information necessary to verify identity and authority. Journal export does not replace a request for account, support or technical information.

Requests are handled within the applicable legal period. Where an extension is permitted, we explain the reason within the required time. If a request is refused, we explain the grounds and available complaint route. You may complain to the competent data protection authority: in the EEA, including where you normally live or work; in the United Kingdom, the ICO; in Israel, the Privacy Protection Authority; and in Russia, Roskomnadzor where Russian law applies to the processing. Applicable local requirements for request format and procedure: available on request at support@bemomsy.com.

12. Security and policy changes

The app and server restrict access according to account, family role and granted permissions. We do not claim end-to-end encryption of all information: BeMomsy’s server and the providers used process content to deliver selected functions.

A child’s name and reminder or active-event details may appear on the lock screen. Notification previews are controlled in iOS. An offline device may display a previously scheduled notification before receiving changes.

We publish updated policies with a date. A change in wording does not replace consent required for a new purpose or recipient. Such changes must be disclosed before the corresponding processing, with the permission required by law. For questions, contact support@bemomsy.com.