क़ानूनी
UK Privacy Notice
Explains, for people in the United Kingdom, how Bebemo processes personal data, including health data about pregnancy and children, on what lawful bases, with whom it is shared and with what safeguards it is transferred, and your rights under the UK GDPR and the Data Protection Act 2018.
यह दस्तावेज़ फ़िलहाल अंग्रेज़ी और तुर्की में प्रकाशित है। English · Türkçe
विषय-सूची · 18 खंड
- 1. Purpose and Scope of This Notice
- 2. Controller and Contact
- 3. Our Role, Family Profiles and Purchases
- 3.1. Processing for Which We Are the Controller
- 3.2. Information About Your Child and Your Family
- 3.3. Purchases
- 4. Personal Data We Process and Where It Comes From
- 4.1. Categories of Personal Data
- 4.2. Sources
- 5. Purposes and Lawful Bases
- 5.1. Our Legitimate Interests
- 5.2. Consent
- 6. Is Providing Your Data Required?
- 7. Special Category Data and Health Data
- 8. Recipients
- 9. International Data Transfers
- 10. Retention
- 11. Your Rights
- 12. Automated Decision-Making
- 13. Cookies and Similar Technologies
- 14. Security
- 15. Children
- 16. Complaints
- 17. Changes to This Notice
- 18. Language of This Notice
This Notice is published in Turkish and English with the same content. If you are located outside Türkiye, the English version is the authoritative version for you (see Section 18).
1. Purpose and Scope of This Notice
This UK Privacy Notice (the "Notice") explains how Mobiza Teknoloji ("we" or "us"), which develops and operates Bebemo, a mobile app for tracking pregnancy and the first years of a child's life with a Memory Box (Anı Kutusu), processes the personal data of people located in the United Kingdom. It provides the information required by Articles 13 and 14 of the UK General Data Protection Regulation ("UK GDPR") and is based on the UK GDPR and the Data Protection Act 2018 ("DPA 2018"), as amended by the Data (Use and Access) Act 2025, and on the Privacy and Electronic Communications (EC Directive) Regulations 2003 ("PECR"). Applicability: The Bebemo app is not offered in the app stores (App Store and Google Play) in the United Kingdom, and we do not offer services directed at the United Kingdom. This Notice still applies to people in the United Kingdom who visit our website or join the "Notify me at launch" list, and to people who get the app with a store account from another country and use it in the United Kingdom; for processing relating to them, we follow the protection the UK GDPR provides where it applies.
This Notice covers the processing for which we are the controller, in particular when you:
- visit bebemo.com.tr,
- sign up on our website to be notified when Bebemo launches,
- create a Bebemo account with Sign in with Apple, Sign in with Google or your email address and a password and use the Bebemo app on iPhone or Android,
- enter information about your pregnancy, your child or your family in the app, or add memory texts, photos or videos to the Memory Box (photos and videos stay on your phone and are not sent to us),
- use the Bebemo Assistant, or ask questions and reply in the Community,
- join a family profile at a parent's invitation, for example as a partner, grandparent or babysitter, or receive such an invitation,
- buy a Bebemo Plus subscription through the App Store or Google Play, or your subscription renews, is cancelled or ends,
- buy a credit pack for the Bebemo Assistant or earn credits with a rewarded ad,
- contact us by email or through our support page,
- receive notifications or service messages from us or, if you have opted in, emails about Bebemo,
- see ads in the free version of the app, if you do not have a Bebemo Plus subscription, or choose to watch a rewarded ad, if you are a Bebemo Plus subscriber (Sections 5 and 8).
Information about children: Children never create Bebemo accounts. Information about a child is entered by a parent or legal guardian, or by family members they have invited. This Notice also explains how we process that information; the parent or legal guardian can exercise the child's rights on the child's behalf (Sections 3.2 and 11).
Relationship with other documents: This Notice complements the Privacy Policy, which describes our processing in more detail and applies to everyone who uses Bebemo. If you are located in the United Kingdom and this Notice differs from the Privacy Policy, this Notice prevails. The explicit consent you give in the app for health data is explained in the health data consent text. As a company established in Türkiye, we are also subject to Turkish Law No. 6698 on the Protection of Personal Data (KVKK), which is described in the KVKK Privacy Notice; this does not limit the rights you have under this Notice. People in the European Economic Area and Switzerland should read the GDPR Privacy Notice, and residents of the United States the US Privacy Notice.
2. Controller and Contact
The controller for the processing described in this Notice is Mobiza Teknoloji, established in Türkiye:
- Controller: Mobiza Teknoloji
- Address: Ovaakça Santral Mah. Ovaakça Fatih Sultan Mehmet Cad. No: 86, 16335 Osmangazi, Bursa, Türkiye
- Data protection contact: legal@mobiza.com.tr
- Customer support: info@mobiza.com.tr
- Phone: +90 850 307 90 23
We have no establishment in the United Kingdom, the European Economic Area or Switzerland. Because the app is not offered in the United Kingdom and we do not offer services directed at the United Kingdom, we have not appointed a representative under Article 27 UK GDPR; requests are made directly to our company.
You and the Information Commission, the UK data protection regulator (formerly the Information Commissioner's Office, "ICO"), can contact our company directly, at legal@mobiza.com.tr or at the postal address given above, on all matters relating to the processing of your personal data; we respond to requests within the periods set out in Section 11.
Please send questions about the processing of your personal data, requests to exercise your rights and complaints to legal@mobiza.com.tr; you can also send questions about your account or the app to info@mobiza.com.tr.
3. Our Role, Family Profiles and Purchases
3.1. Processing for Which We Are the Controller
We determine the purposes and means, and are therefore the controller, of the processing relating to our website and the launch notification list, Bebemo accounts, the data that you and your family members enter in the app (including health data and Memory Box texts), family sharing, the Bebemo Assistant, the Community, reminders and notifications, reports and exports, crash reports and usage statistics, the verification of in-app purchases, customer support, information security and compliance with the laws that apply to us.
3.2. Information About Your Child and Your Family
Keeping records about your own pregnancy, your child and your family in Bebemo is a purely personal or household activity for you. We are the controller of the data stored in Bebemo and are responsible for protecting it as described in this Notice.
- Children: The parent who creates a child profile is its owner. Everything about the child (for example the child's name, birth date, care logs, growth data and Memory Box entries) is entered by the owner or by the family members the owner has invited. The owner, or another person with parental responsibility for the child, can exercise the child's rights on the child's behalf.
- Pregnancy information: Pregnancy information relates to the person who is pregnant. If you are a partner or another family member, please enter or view pregnancy information only with that person's knowledge and agreement. The person who is pregnant can always exercise their rights directly with us.
- Family members: To invite a family member, you create an invite code in the app that gives the role you choose (parent or caregiver) and is valid for 7 days, and you share it with the person you want to invite yourself; we do not send anyone an email for an invitation and we do not receive the invited person's contact details. Members who join with the code can see the profile, add entries and see who logged each entry.
3.3. Purchases
Bebemo can be downloaded for free. Bebemo Plus is an optional subscription that renews automatically every month or every year and can be bought only within the app through the App Store or Google Play; it is tied to the family profile in which it was purchased, and the family members in that profile can also use the Plus features. The purchase and the payment are handled by Apple or Google, which process your payment data as independent controllers under their own privacy policies. We never receive your card details. To verify your subscription, turn Plus on in the family profile, keep track of the subscription's status and let you restore the purchase on a new device, we receive from the store only the transaction ID and signed transaction information, the plan (monthly or yearly), the subscription's status, the end date of the current period, whether auto-renewal is on, whether a free trial was used and whether the purchase was made in the test or the live environment. To tie the purchase to the family profile, the family profile's randomly generated ID (which does not contain your name or email address) is passed to the store as an account identifier at the time of purchase. We receive changes such as the subscription renewing, being cancelled or refunded, or a payment failing through the subscription notifications that the App Store and Google Play send to our servers. Credit packs for the Bebemo Assistant can also be bought only within the app, through the App Store or Google Play, as one-time (consumable) purchases. For credit pack purchases, to verify the purchase, add the credits to your family profile's shared credits and process refunds, we receive only the store transaction ID (the transaction ID on the App Store, the purchase token on Google Play), the product, the platform and the purchase status; to tie the purchase to your account, your account's randomly generated ID (a UUID that does not contain your name or email address) is passed to the store. Purchased credits are added to the shared credits of the family profile of the child profile open in the app at the time of purchase, can be used by everyone in that profile and never expire; the family profile the purchase was added to is also recorded in the credit ledger.
4. Personal Data We Process and Where It Comes From
4.1. Categories of Personal Data
Depending on how you use Bebemo, we process the following categories of personal data; a detailed list is given in the Privacy Policy:
- Website visitors: IP address, browser information (user agent), the requested page and the time of the request, recorded in our server logs. Our website uses no cookies, analytics or tracking pixels (Section 13).
- Launch notification sign-ups: email address, the website language you chose, your consent, the time of consent, the version of the consent text, IP address and user agent.
- Account data: the first and last name and email address received from Apple or Google or entered by you when you sign up with email (if you use Apple's Hide My Email feature, the private relay address created by Apple), your Apple or Google user identifier, for email sign-in an irreversible hash of your password and hashes of the email verification and password reset codes, your open sessions (device name, platform, last use), app language, the ready-made profile picture you chose (only its identifier; no photo is uploaded; visible to your family members and, on posts that are not anonymous, to other Community users) and your phone's time zone (sent automatically by the app with each request; not derived from your location; used so that your days, reminders, notifications and limits follow your own local time).
- Child profile: the child's name, date and time of birth, sex (used only to choose the colour theme; you can choose "surprise" instead and change it at any time), birth weight and length, the week of pregnancy at birth if the baby was born early, for twins, triplets and more the birth order and the link to siblings born together, the identifier of the ready-made picture chosen for the profile (no photo of the child is added), the due date or the first day of the last menstrual period, and during pregnancy the number of babies expected and each baby's sex.
- Pregnancy data: pregnancy week, doctor appointments, symptom and mood diary, weight and blood pressure, kick counter and contraction timer records.
- Baby care logs and growth data: breastfeeding (side and duration), bottle and breast pump entries, solid foods and allergy notes, sleep, diapers (wet or dirty, stool colour and consistency, gas and colic notes), bath, tummy time, fever, medicine and vitamin doses, vaccines, doctor visits, height, weight, head circumference, teeth and developmental milestones.
- Other app content: the hospital bag checklist and the baby names you save as favourites with the name finder (including those shared with your partner).
- Memory Box: the memory's title, note and date, any developmental milestone, who added the memory and whether it has a photo. The photos themselves (including ultrasound images) are kept on the phone of the person who added them and are not sent to our servers. Videos added to the Memory Box from the phone's gallery (up to 3 minutes and 200 MB; the app does not record video with the camera, and the microphone is not used for memory videos) also stay, without re-encoding and with location and personal metadata removed, only on the phone of the person who added them; videos and the cover frames extracted on the phone are never sent to our servers by any route, and we are not even told that a memory has a video. Videos are not included in the PDF memory book, the ZIP archive or slideshow videos. With the optional Sync at home, family phones paired once with a QR code send the photos and videos (up to 200 MB per video) directly to each other, end-to-end encrypted, while they are on the same Wi-Fi network; the photos and videos do not pass through our servers and the pairing key is kept only on the phones. So that each phone can show who is on the other phone, paired phones send each other, over the encrypted connection, only the device's model name (e.g., "iPhone 15 Pro"), its platform (iOS or Android) and the Bebemo user ID of the person signed in on that phone; the receiving phone matches this ID against the family members it knows and shows that person's name as it appears in the family and the ready-made profile picture they chose. This information is not broadcast openly on the local network and is not sent to us.
- Family sharing: family members' first and last names, roles, relationship to the family (e.g., mother, father, grandmother, caregiver; for the profile owner, chosen at setup) and, if they chose one, the label shown for them in the family, the invite codes created and who used them, the child profiles they can access and which member logged each entry.
- Bebemo Assistant: the messages you write to the assistant and the context passed to the AI service with each question (the profile stage with any multiple pregnancy or birth and preterm birth details, the selected country and its emergency number, the assistant's name, the screen that is open, a short summary of recent records), the date of your consent for the assistant and the credit ledger kept for AI credits (for each answer, the date, feature, model used, token counts, number of web searches and calls (each call is also recorded with its model, token counts, duration and cost), actual cost and credits deducted; the family profile each credit movement is linked to (the family account the credits for an AI operation were deducted from and the family profile a purchase was added to); rewarded ad, valid report reward, Bebemo gift and purchase movements, expired credits, the source of extra credits, who they belong to (the family profile or a person) and their last day of validity, and your credit balance). The chat history is kept only on your phone; messages are not stored on our servers and are not included in the credit ledger. If you use voice input in the assistant, your phone's own speech recognition is used (the first time, your phone asks for microphone and speech recognition permission); your voice does not reach us and is not recorded or stored, and only the resulting text is processed as a message (Section 8).
- Community: the questions and replies you write (including category, tags, an optional province and birth-month group), whether you chose to post anonymously, your "helpful" votes, the reactions you give to questions and replies (heart, like, haha, wow, sad, angry), the questions you save, the reports you send and the credits added for a report found to be valid, if you are a verified expert your field of expertise, whether you have Bebemo Plus (for the Plus mark and the daily question limit), the status of your posts in the Community (being checked, published, under review, not published because it broke a rule, removed for breaking the rules, or hidden because of reports) and the rule involved, and the record of the automated checks made on your posts and reports (the type of content checked, the decision, the rule involved, a short note for the moderators, whether the check failed for a technical reason, the AI model used, the duration and the date; the content itself is not kept in this record).
- Reminders and notifications: reminder and notification settings (including feeding intervals and the night shift setting), device push notification tokens (Firebase Cloud Messaging registration tokens) and the Firebase installation ID; the copy of each notification our servers send that is kept in the notification inbox (type, title and text, the screen it opens and the identifiers needed, the related family or child profile, when it was created and read; the text of feeding reminders may contain health data). Inbox entries for reminders set up on the phone are kept only on the phone.
- Device and technical data: device model, operating system, app version, IP address, and crash and diagnostic logs.
- Usage and operations records (regardless of consent to usage statistics): for each day you use the app while signed in, the day (UTC), the platform and the time of the first and last request that day (active days); for each AI call made for Bebemo Assistant answers and Community checks, the model used, token counts, duration and cost, linked to the account that caused the call; the number of push notifications sent to you each day and the total size of your images stored on the server; and, calculated every few hours from these, from your purchases (estimated at list price) and from ad revenue records, the estimated revenue and estimated cost per person, the net contribution, the number of active days and, if you have consented, the time you spend in the app. Which screens you open and the content of messages, answers and posts are not included in these records. Details are given in Section 4.17 of the Privacy Policy.
- Crash reports (only if you consent): device model, operating system and version, app version, the error and its stack trace, the generic name of the screen open at the time of the crash (pregnancy and health screens under a single name, "care_tools"), app language and the installation ID created by Firebase Crashlytics. Crash reports do not contain your user ID, name, email address, health entries, Memory Box content, photos or videos.
- Usage statistics (only with your consent): the generic names of the screens opened, which features are used (for example, that a feeding, sleep, diaper, solid food or growth entry was added, a vaccine was marked, a memory was added or the memory book was exported, a message was sent to the assistant, a family invite was created or a family was joined, a question or reply was written in the Community, an in-app purchase was started or verified, a notification was tapped (with the type of the notification and the generic name of the screen it opens), the intro tour was started and finished, the first entry was made in one of the profiles (only the type, and only for a care entry or a memory), a home screen widget was used, a tool was opened with a rewarded ad, the amount of credit the assistant used and the credit earned with a rewarded ad, a memory video was exported, a credit pack purchase was started, and the sign-in and sign-up method), revenue measurement (for in-app purchases the product, amount and currency, and for every ad shown the network, format, ad unit and estimated revenue in US dollars; the advertising ID, country, and user and family IDs are not sent, and trial and test purchases are not counted as revenue), as user properties the app language, the country chosen in the app, your Plus status (free, trial, paid or gift), your role in the family, the number of profiles (1, 2, or 3 or more), the number of people in the family (1, 2, 3, or 4 or more), the number of widgets on the home screen and your ad personalization choice (pregnancy or baby stage is not a user property), and the data that Firebase collects automatically (the app instance ID, session start and duration, first open, app and operating system version, device model, language and approximate location derived from the IP address: country, region, city; in-app purchase and, on Android through Google Play, subscription renewal, cancellation and refund events; Google Analytics does not store the IP address). Nothing is sent until you consent; the first-launch steps before the consent window are held only in the app's memory, are not written to your device, and are sent if you allow it and deleted if you do not. Revenue measurement is not linked to your account and is not used for ad targeting or personalization. The content of entries (for example, amounts, durations, temperature, medicine, symptoms, notes), your child's age, pregnancy and the week of pregnancy, whether you keep temperature, medicine or pregnancy entries, your name, email address, photos, videos and user, family or entry IDs are not sent, and Bebemo does not send a user ID (User ID) to Google Analytics. Details are given in Section 4.11 of the Privacy Policy.
- App sessions (only with the consent you give for usage statistics; Bebemo's servers): the time the session starts and how long the app stays open on screen, the generic names of the screens opened during the session (pregnancy and health screens under a single name, "care_tools"), the platform, the app language and the country selected in the app; linked to your account. The content of entries, health and pregnancy information, your name, email address and photos are not sent. If you have no connection, sessions wait on your phone for up to 30 days. Details are given in Section 4.11 of the Privacy Policy.
- Subscription data: the store transaction ID and signed transaction information, the plan (monthly or yearly), the subscription's status, the end date of the current period, whether auto-renewal is on, whether a free trial was used, the test or live environment and the family profile to which the subscription is tied; card details never reach us.
- Credit pack data: the store transaction ID, the product purchased, the platform, the purchase status, the credits added and the family profile they were added to, and the account ID passed to the store as an account identifier; card details never reach us.
- Support communications: your name, email address, the content of your messages, any attachments and the history of our correspondence.
- Advertising data (in the free version if you do not have a Bebemo Plus subscription, or only in rewarded ads you choose to watch if you are a Bebemo Plus subscriber): advertising ID (AAID on Android; on iPhone, the IDFA, only if you grant App Tracking Transparency permission), IP address and the coarse location derived from it, device and operating system information, app information, and ad impression and click data; this data is passed to the ad mediator and the advertising partners through the advertising software components (SDKs) in the app. Health and baby records, pregnancy information, Memory Box content, name, email address and user ID are never passed to advertising partners; advertising partners are not given a user ID or a user segment. Details are given in Section 21 of the Privacy Policy.
- Ad revenue records (app users who are signed in; for Bebemo Plus subscribers, only for rewarded ads they choose to watch): for each ad shown in the app, the ad format, the advertising partner that showed the ad, the ad unit and placement, the platform, the country reported by the ad mediator (two-letter country code), the impression time and the estimated revenue (US dollars), as reported to the app by the ad mediator (Unity LevelPlay); linked to your account and to your family that is active at the time of the impression. The advertising ID, device ID, IP address and health records are not included in these records; the records on our servers are not passed to advertising partners (the only exception: if you consented to usage statistics, the format, network, ad unit and estimated revenue of each impression also go to Google Analytics without being linked to your account).
- Brand stories (app users who are signed in): which brand stories you have seen (story ID, time seen), linked to your account; taps on a story's button are only added to a total count. The choice uses the country you selected, the app language and your family's Bebemo Plus status; health data, week of pregnancy and your baby's age are not used (your phone decides whether a story appears on the pregnancy or the baby page).
We treat pregnancy data, baby care logs and growth data (including the birth weight and length, the week of pregnancy at birth and the due date or last menstrual period in the child profile) as health data, that is, special category data (Section 7).
4.2. Sources
We collect personal data:
- directly from you, when you sign up on our website, use the app, enter information about your pregnancy, your child or your family, or write to us,
- from family members: from the person who invites you (the role your invite code gives you); entries about a child, from the parent or the invited family members who log them,
- from other users in the Community (for example, replies to your posts and reports),
- from Apple or Google, when you sign in with them (first and last name, email address or private relay address, user identifier) and when you subscribe to Bebemo Plus or buy a credit pack through the App Store or Google Play (transaction information and renewal, cancellation and refund notifications),
- automatically from your device when you use our website or the app (technical data, active day, AI call, notification and storage records, push notification tokens, crash and diagnostic logs, crash reports and, if you consent, usage statistics and app sessions); when ads are shown in the free version, ad data is passed directly from your device to the ad mediator and the advertising partners through the advertising software components in the app,
- from the impression and revenue information reported to the app by the ad mediator (Unity LevelPlay) when ads are shown in the app while you are signed in (ad revenue records).
5. Purposes and Lawful Bases
| Purpose | Main data | Lawful basis (Article 6(1) UK GDPR; for health data, also Article 9(2) UK GDPR) |
|---|---|---|
| Creating your account, signing in with Apple or Google or with email and password (including email verification and password reset), providing the app and its features, and syncing your data across your devices | account data, password hash, sessions, settings, the content you enter, technical data | Performance of a contract with you (b) |
| Keeping your child's profile and the information you enter about your child that is not health data, such as the child's name, birth date, theme and Memory Box entries | child profile, Memory Box content | Your and our legitimate interest in keeping the records you have asked us to keep about your child (f); we give particular weight to the child's interests (Section 5.1) |
| Storing and syncing health data about your pregnancy or your child, showing it to the family members you invite, generating reminders and reports from these records; exporting entries and reports as PDF and Excel files | pregnancy data, baby care logs, growth data | Your consent (a) and, because this is special category data, your explicit consent (Article 9(2)(a)); for a child's data, given by the parent or legal guardian (Section 7) |
| Family sharing: creating invite codes, giving access to the profile, syncing entries in real time and showing who logged each entry | first and last names, roles and labels of family members, invite codes, entry records | Performance of a contract (b) with you and with the members who have joined with an invite code |
| Bebemo Assistant: passing your messages and context information (the profile stage with any multiple pregnancy or birth and preterm birth details, the selected country and its emergency number, the assistant's name, the screen that is open, a summary of recent records) to the AI service provider Anthropic in the USA to generate answers, saving suggestions you confirm | messages, context information (which may include health data), consent date | The consent you give when turning on the assistant (a) and, for health data, your explicit consent (Article 9(2)(a)); this consent is separate from your consent for health data |
| Calculating, deducting and showing AI credits for the Bebemo Assistant; adding personal credits earned with rewarded ads and with valid reports in the Community; keeping the credit ledger and tracking AI costs | credit ledger: for each answer, the date, feature, model used, token counts, number of web searches and calls (each call is also recorded with its model, token counts, duration and cost), actual cost and credits deducted; the family profile the credit movement is linked to; rewarded ad, valid report reward, Bebemo gift and purchase movements, expired credits, the source of extra credits, who they belong to and their last day of validity, credit balance (no message content) | Performance of a contract (b); for tracking AI costs and preventing abuse of the credit system, also our legitimate interests (f) |
| Community: showing questions and replies to other users, search, saving, reactions and reply notifications; showing the Plus mark on posts by people who have Bebemo Plus and applying the daily question limit according to Bebemo Plus | questions, replies, first name with last-name initial and chosen profile picture (with expertise badge and Plus mark, if any) or anonymous display, category, tags, optional province, votes and reactions, whether you have Bebemo Plus | Performance of a contract (b) |
| Community safety: filtering inappropriate content and spam, daily question and reply limits, receiving reports, hiding posts that are found to break the rules or receive many reports and recording which account an anonymous post was made from | posts, reports, author account | Our legitimate interest in protecting the Community and its users against misuse (f) |
| Automated Community check: checking every question and reply in the background before it is published (while the check is running, the post is visible only to its author), and a reported post on its first report, against the Community rules through a word filter and the AI service provider Anthropic in the USA, having a moderator review posts the AI is not sure about or that could not be checked, not publishing posts that clearly break the rules, keeping check records and notifying the author of the outcome (Section 12) | the content checked (for a question, its title, text and category; for a reply, the text of the reply and the title of the question it answers; for a report, the reported post and the reason for the report; no account details are passed on), check record (decision, rule involved, short note, duration and date; without the content) | Our legitimate interest in protecting the Community and its users against harmful content and misuse (f); for health information you choose to write in posts, see Section 7 |
| Reward for valid reports: sending a thank-you notification and adding personal AI credits, valid for 7 days, to the person whose reported post is found to break the rules and removed | report, outcome of the report, credits added | Performance of a contract (b) |
| Sending the reminders and notifications you set up (feeding, medicine and vitamins, vaccines, appointments, diaper reminders, family activity; memory suggestion notifications are scheduled on your phone and are not processed by us) and showing the feeding timer on the lock screen | notification settings, push notification tokens, the related records | Performance of a contract (b); for reminders based on health data, also your explicit consent (Article 9(2)(a)) |
| Notification inbox: keeping a copy of each notification our servers send, even if your device is not registered or notification permission is turned off, and showing past notifications, the unread count and read status in the inbox opened from the bell button on the home screen (including notifications of Bebemo Plus and credits gifted by Bebemo; reminders set up on your phone are listed only on your phone) | type of notification, title and text, the screen it opens and identifiers, the related family or child profile, when it was created and read | Performance of a contract (b); for the text of feeding reminders, which contains health data, also your explicit consent (Article 9(2)(a)) |
| Exporting the Memory Box on your phone at your request as a ZIP archive (always free) or a PDF memory book (preview free; saving, printing and sending with Bebemo Plus) (videos are not included) | the content you export | Performance of a contract (b); for health data, your explicit consent (Article 9(2)(a)) |
| Verifying the Bebemo Plus subscription, turning Plus on in the family profile to which it is tied, updating the subscription's status (renewal, cancellation, refund, payment problem) from store notifications and restoring the purchase on new devices | store transaction ID and signed transaction information, plan, subscription status, end date of the current period, auto-renewal and trial information, test or live environment, purchasing user and family profile; the family profile ID passed to the store as an account identifier | Performance of a contract (b) |
| Verifying credit pack purchases, adding the credits to the family profile's shared credits and, following the store's refund notifications, taking back an amount equal to the credits added from the unspent part of the purchased credits | store transaction ID (the transaction ID on the App Store, the purchase token on Google Play), product, platform, purchase status, credits added and the family profile they were added to; the account ID passed to the store as an account identifier | Performance of a contract (b) |
| Keeping the accounting, tax and commercial records required by the laws of Türkiye, where we are established; keeping purchase records for 10 years, unlinked from you after your account is deleted (Turkish Commercial Code No. 6102 Art. 82, Tax Procedure Law No. 213 Arts. 253 and 254), and using them to defend against store refunds, chargebacks and disputes | subscription, purchase and transaction records; purchase records (store transaction number, product, amount and currency, transaction date, store, country, refund and, only if it came from an older version of the app, withdrawal consent information) | Our legitimate interest in complying with the laws that apply to us (f); because these obligations do not arise from UK law, we do not rely on Article 6(1)(c) for them |
| Answering support requests, questions and messages | name, contact details, message content | Performance of a contract (b); otherwise our legitimate interest in answering your questions (f); if we need to look at your health data to resolve a request, your explicit consent (Article 9(2)(a)), which we ask for first |
| Sending service messages about your account, security and changes to our terms | first and last name, email | Performance of a contract (b) and our legitimate interest in informing our users (f) |
| Information security, preventing fraud and misuse, and detecting and fixing errors and crashes | IP address, device information, server and security logs, crash and diagnostic logs | Our legitimate interest in keeping the service and its users secure and the service working properly (f) |
| Detecting and fixing app crashes and errors through crash reports sent via Firebase Crashlytics (Google LLC) | device model, operating system and app version, the error and its stack trace, generic screen name, app language, Crashlytics installation ID | Your consent (a); because an installation ID is stored on your device for crash reports, this is also based on your consent under regulation 6 of PECR. Crash reports are off by default; you are asked in the consent window as a separate option and can withdraw consent at any time with the Crash reports switch under Profile › Privacy |
| Usage statistics through Google Analytics for Firebase: understanding which features are used, finding problems in the sign-up and setup steps, improving the app and preparing aggregate usage and growth measurements that are not specific to any individual (for example, only aggregate numbers in investor and business reports) | generic screen names, feature usage events, revenue measurement (purchases and ad revenue), user properties, app instance ID, session and device information, approximate location (Section 4.1) | Your consent (a) and, because feature usage events can show that you use pregnancy and baby care features and may therefore count as health data, your explicit consent (Article 9(2)(a)); storing and accessing information on your device for this purpose is also based on your consent under regulation 6 of PECR |
| Storing app sessions on our servers linked to your account: measuring how much and which parts of the app are used, how much time is spent in the app and whether users come back to the app, and improving the app; besides aggregate numbers, our authorized staff can see the number of sessions and the time spent in the app for each person; sessions are not used for advertising and are not transferred to Google or any other third parties | session start time and duration, generic names of the screens opened during the session, platform, app language, country selected in the app, account ID (Section 4.1) | The consent you give for usage statistics (a); storing sessions that are waiting to be sent on your device is also based on your consent under regulation 6 of PECR |
| Showing personalized ads in the free version to users who do not have a Bebemo Plus subscription, and to Bebemo Plus subscribers only in rewarded ads they choose to watch, and measuring ads, through Unity LevelPlay and the advertising partners | advertising ID (on iPhone, only with App Tracking Transparency permission), IP address and coarse location, device, operating system and app information, ad impression and click data (Section 4.1) | The consent you give in Google's consent form (User Messaging Platform; IAB TCF) (a); storing and accessing information on your device is also based on this consent under Regulation 6 of PECR; on iPhone, your tracking permission is also required |
| Showing non-personalized (contextual) ads in the free version where you have not consented, and measuring ads | IP address and coarse location, device, operating system and app information, ad impression and click data | Our legitimate interest in offering the free version with ads (f) |
| Showing and measuring, where you have not consented, non-personalized rewarded ads that you choose to watch as a Bebemo Plus subscriber | IP address and coarse location, device, operating system and app information, ad impression and click data | Performance of a contract (b): you request the reward (extra credits) yourself, and the ad is given in return for that request |
| Keeping ad revenue records linked to your account: analysing how much revenue which users, families, ad formats and advertising partners generate, making decisions about the free version, ad frequency and pricing, and reconciling with the ad mediator's daily reports; the records are not used to show you ads or to target you | ad format, advertising partner, ad unit and placement, platform, the country reported by the ad mediator, impression time, estimated revenue, account and family ID (Section 4.1) | Our legitimate interest in analysing our business and keeping the free version sustainable (f); you can object to this processing by turning off the Profile › Privacy › Ad revenue records switch in the app or by writing to us (Section 11). After you object, records are no longer linked to your account; the link between your existing records and your account and family is removed within 30 days at the latest |
| Showing the brand stories (sponsored content, always labelled) on the home page, remembering on all your phones which stories you have seen, and keeping total view and tap counts per story | IDs and times of stories seen, the country you selected, the app language, the family's Bebemo Plus status | Performance of the contract (b) and our legitimate interest in keeping the free version sustainable through partnerships (f). Health data, week of pregnancy and your baby's age are not used; no profile is built about you and no personal data is passed to advertisers (ads are clearly labelled) |
| Keeping usage and operations records: measurements such as the number of active users, retention and growth; keeping track of infrastructure and AI costs; business analysis of pricing and of the sustainability of the free version and the credit system; detecting abuse of the credit system and the service; the records and the summary are seen only by our authorized staff, are not used to make automated decisions about you, to show you ads or to target you, are not combined with health data and are not transferred to third parties | active days (day, platform, first and last request time), AI calls (model, token counts, duration, cost), per-person notification and storage counters, estimated revenue and cost summary per person, account ID (Section 4.1) | Our legitimate interest in running the service and analysing our business (f); you can object to this processing (Section 11) |
| Sending the launch announcement to people who signed up on our website | email address, language, consent record | Your consent (a), which is also the consent required for marketing emails under regulation 22 of PECR; we keep a record of your consent so that we can demonstrate it (Article 7(1) UK GDPR) |
| Sending push notifications about campaigns, discounts and announcements from Bebemo and its partners | device notification token, language, consent record (date, time, text version) | Your consent (a), which is also the consent required for electronic marketing messages under regulation 22 of PECR. The consent is separate, off by default and can be withdrawn at any time under Profile › Family and notifications; your device's notification permission does not replace it; we keep a record of your consent so that we can demonstrate it (Article 7(1) UK GDPR) |
| Sending news and announcements about Bebemo to app users who have separately opted in | name, email address, communication preferences | Your consent (a) and regulation 22 of PECR |
| Establishing, exercising or defending legal claims and responding to requests from public authorities | relevant records | Legal obligation under UK law (c), where one applies; for disclosures necessary for a recognised legitimate interest listed in Annex 1 to the UK GDPR, such as responding to a request from a public authority, national security, emergencies or the prevention and detection of crime, Article 6(1)(ea); otherwise our legitimate interest in protecting our rights (f); for health data, Article 9(2)(f) |
5.1. Our Legitimate Interests
Where we rely on legitimate interests, our interests are: providing a secure and reliable service, preventing fraud and misuse and fixing errors; protecting the Community against harmful content and checking posts automatically before they are published; enabling parents to keep the records they want to keep about their children and to share them with their family; offering the free version of Bebemo with non-personalized (contextual) ads and keeping it sustainable by analysing ad revenue at account level; running the service, measuring usage and growth, keeping track of infrastructure and AI costs and analysing pricing and sustainability; answering inquiries and keeping our users informed; complying with the laws that apply to us as a company established in Türkiye; ensuring the continuity of the service in a merger, acquisition or similar transaction; and establishing, exercising or defending legal claims. We use only the data needed for these interests and weigh them against your interests and fundamental rights and freedoms. Where the data relates to a child, we give particular weight to the child's interests: child profiles are private by default and visible only to the family members the parent invites, they are never made public, a child's health data and Memory Box content are never used for advertising or marketing profiling and are not passed to advertising partners, ads are shown to the parent using the app rather than to the child and no profile of the child is built, and the parent can delete the profile at any time. You can ask us for information about this balancing test, and you can object to processing based on legitimate interests at any time (Section 11).
5.2. Consent
Where we rely on your consent, giving it is voluntary, and you can withdraw it at any time with effect for the future: your explicit consent for health data in the app settings, your consent for the Bebemo Assistant with "Withdraw permission" in the assistant menu, your consent to usage statistics with the Usage statistics switch under Profile › Privacy (collection then stops, the app instance ID and unsent events are deleted from your device and your app sessions on our servers are deleted too), your consent to personalized ads by reopening Google's consent form under Profile › Privacy › Ad preferences (and, on iPhone, the tracking permission under Settings › Privacy & Security › Tracking), and your consent to launch and news emails through the unsubscribe link included in every email or by writing to legal@mobiza.com.tr. If you withdraw your explicit consent for health data, health records can no longer be stored or synced and your existing health records are deleted; before withdrawing, you can export them free of charge. Withdrawing consent does not affect the lawfulness of processing carried out before the withdrawal. You can also turn off reminders in the app and push notifications in your device settings at any time.
6. Is Providing Your Data Required?
You are not under a statutory obligation to provide personal data to us. However, to create an account you need to sign in with Apple, Google or your email address and a password; without this data, we cannot create your account or provide the app. Giving explicit consent for health data is optional, but without it you cannot use the features that store health data, such as pregnancy tracking, baby care logs, growth data and reports. You do not have to tell us your baby's sex (you can choose the "surprise" theme instead), and whether you add photos or videos to the Memory Box, or use the Bebemo Assistant and the Community, is entirely up to you. Signing up for the launch announcement and for news emails is entirely optional, and not doing so has no effect on your use of Bebemo. Consent to usage statistics is also entirely optional, and not giving it does not restrict any feature. Consent to personalized ads is also optional; if you do not give it, ads in the free version are shown without personalization. Bebemo Plus subscribers are not shown ads on their own; watching rewarded ads is optional.
7. Special Category Data and Health Data
What we treat as health data: We treat pregnancy data (including the due date or last menstrual period), baby care logs and growth data (including birth weight and length and the week of pregnancy at birth) as data concerning health within the meaning of Article 9 UK GDPR, that is, special category data, and protect it accordingly, even where a single entry may not reveal anything about health on its own. Feature usage events in usage statistics (for example, "feeding entry added") are treated the same way because they can show that you use pregnancy and baby care features, and they rely on your explicit consent (Article 9(2)(a)), requested in a separate window.
Explicit consent: Before any health data is stored, the app asks for your separate explicit consent (Article 9(2)(a) UK GDPR); the scope of this consent is explained in the health data consent text. Consent for a child's health data is given by the parent or legal guardian on the child's behalf, and the family members you invite add entries within the profile for which you have given consent.
Bebemo is not a health service: Bebemo is a tracking and information app. It does not diagnose or treat, and it does not replace advice from your doctor, midwife or health visitor. We therefore do not process health data on the basis of Article 9(2)(h) UK GDPR or the conditions in section 10 of and Schedule 1 to the DPA 2018 (such as health or social care purposes); we rely on your explicit consent. In the exceptional cases where health data is needed to establish, exercise or defend legal claims, we rely on Article 9(2)(f) UK GDPR. In an emergency, call 999 or 112.
Additional safeguards: We do not sell health data, we never use health data or Memory Box content for advertising or marketing profiling, we do not pass it to advertising partners, and we never make it public; health data is never processed for advertising purposes in any way. Health data is visible only to you and the family members you invite. Our staff can access it only where strictly necessary, for example to resolve a support request with your permission or to keep the service secure. You alone decide whether to share the files you export (for example, a PDF or Excel file of your entries), and with whom. The content of health entries is not included in crash reports, usage statistics or app sessions; pregnancy and health screens are reported only under a single generic name, and whether you keep temperature, medicine or pregnancy entries is not sent to usage statistics.
Withdrawing consent: You can withdraw your explicit consent in the app settings at any time; the effects are described in Section 5.2.
The Bebemo Assistant and the Community: The messages you write to the assistant and the record summary passed with each question may contain health data and are passed to the AI service provider in the USA; this relies on the explicit consent you give when turning on the assistant (Article 9(2)(a) UK GDPR), separately from your consent for health data, and does not happen if you do not use the assistant. Health information you choose to write in the Community is visible to other users. In addition, for the safety of the Community, every question and reply is checked automatically in the background before it is published (while the check is running, the post is visible only to you), and a reported post on its first report; for this purpose the text of the post, including any health information you write in it, is passed to our processor, the AI service provider in the USA; your account details are not passed on. Unlike the Bebemo Assistant, this check does not depend on a separate consent and applies to the posts of everyone who writes in the Community; using the Community is optional. We recommend that you do not share detailed health information in the Community.
Support messages: Please do not include health information in your support messages unless it is needed. If we need to look at your health records to resolve your request, we ask for your explicit permission first.
8. Recipients
We disclose personal data only to the extent necessary for the purposes above, to the following categories of recipients (see also the Privacy Policy):
- service providers acting as our processors: Pentech Bilişim Teknolojileri Sanayi ve Ticaret Limited Şirketi (PenDC data center) for the data center and server infrastructure where our servers are located, Firebase Crashlytics (Google LLC) for crash reporting, Google for push notifications (Firebase Cloud Messaging), only if you consent, for usage statistics (Google Analytics for Firebase), and for transmitting and storing your correspondence with our support and data protection addresses, the emails you send and our replies (Google Workspace), Cloudflare, Inc. (Cloudflare R2; data is stored in the EU) for storing images that are kept on the server and an encrypted copy of our database backups and server access logs, and the AI service provider Anthropic in the USA (only if you use the Bebemo Assistant, for generating answers, and if you use the Community, for the automated check of posts); these providers process data only on our instructions,
- Apple and Google: for Sign in with Apple and Sign in with Google and for Bebemo Plus subscriptions and credit packs bought through the App Store and Google Play (the family profile's random ID is passed to the store at the time of purchase to tie a subscription to your family profile, and your account's random ID to tie a credit pack to your account), as independent controllers for their own processing; Apple also delivers to iPhones, through the Apple Push Notification service, the push notifications passed on by Firebase Cloud Messaging,
- your phone's speech recognition service: for voice input in the assistant, we do not receive your voice and do not disclose it to anyone; if your phone cannot turn speech into text on the device in your language, your voice may be processed by your phone's speech recognition service (Apple on iPhone, Google on Android) under that company's own terms. This processing depends on your phone's settings; you can turn the permissions off at any time in your phone's settings,
- the family members you invite: they can see the child profile, entries and memory texts you share with them, and your name next to the entries you log; photos and videos stay on the phone of the person who added them and are transferred directly only to family phones paired with Sync at home (paired phones also see each other's model name and platform),
- other people who use the Community: they can see the questions and replies you write in the Community, with your first name, the initial of your last name and the profile picture you chose (with your expertise badge and, if you have Bebemo Plus, the Plus mark) or anonymously,
- people you choose to share with: when you export your data (for example, as a PDF or Excel file) and share it, the recipients you choose; we are not responsible for how they use it,
- ad mediator and advertising partners: for showing and measuring ads in the free version if you do not have a Bebemo Plus subscription, or only in rewarded ads you choose to watch if you are a Bebemo Plus subscriber, the ad mediator Unity LevelPlay (Unity Technologies) and the advertising partners working on a bidding basis, Unity Ads and ironSource Ads (Unity Technologies), Google AdMob (Google LLC), Meta Audience Network (Meta Platforms Ireland / Meta Platforms Inc.), and Pangle (Bytedance Pte. Ltd., Singapore); these companies process and keep the data passed to them under their own privacy policies: Unity, Google, Meta, Pangle,
- professional advisers: lawyers, auditors and accountants who are bound by confidentiality,
- a successor: in a merger, acquisition or transfer of all or part of our business, the acquirer, which will continue to use the data in line with the commitments in this Notice,
- public authorities: competent authorities and courts, where we are legally required to disclose data or where disclosure is necessary to establish, exercise or defend legal claims.
We send email verification and password reset codes, the launch announcement and service emails without using an email service provider, through our own mail server (in Pentech Bilişim's PenDC data center in Bursa, Türkiye).
We do not sell your personal data. We never use health data or Memory Box content for advertising or marketing profiling. Crash reports and usage statistics are not used for advertising either. Only the ad data listed in Section 4.1 is passed to advertising partners.
9. International Data Transfers
We are established in Türkiye, and there are no UK adequacy regulations for Türkiye. Personal data that you send us directly when you use Bebemo or our website is collected by us as a controller established in Türkiye and stored on the servers of our hosting provider (Pentech Bilişim Teknolojileri Sanayi ve Ticaret Limited Şirketi (PenDC data center)), located in Türkiye (Bursa). Such direct collection from you is not in itself a restricted transfer under the UK GDPR; the UK GDPR nevertheless applies to our processing, and we protect your data with the measures described in Section 14.
When we pass personal data that is subject to the UK GDPR on to another organisation located outside the United Kingdom, such as our hosting provider or the other service providers listed in Section 8, we rely on:
- UK adequacy regulations for the recipient's country (for example, for the countries of the European Economic Area) and, for recipients in the United States that are certified under the UK Extension to the EU-U.S. Data Privacy Framework, the Data Protection (Adequacy) (United States of America) Regulations 2023,
- where no adequacy regulations cover the transfer, the International Data Transfer Agreement (IDTA) or the International Data Transfer Addendum to the European Commission's standard contractual clauses (UK Addendum), issued under section 119A of the DPA 2018, together with supplementary measures where necessary.
If you choose to use the Bebemo Assistant, your messages and record summary, and if you use the Community, the text of the questions and replies you write and of reported content for the automated check, are passed to Anthropic in the USA; for these transfers, we rely on the standard contractual clauses and the UK Addendum incorporated into Anthropic's Data Processing Addendum. Images stored on the server and the copy of our database backups and server access logs, which is encrypted on our servers, are kept in Cloudflare R2, in data centers in the European Union; if Cloudflare, Inc., which is based in the USA, needs to access this data to provide the service, we rely on the adequacy regulations above, because Cloudflare, Inc. is certified under the UK Extension to the Data Privacy Framework, and, should that certification lapse for any reason, on the standard contractual clauses and the UK Addendum in Cloudflare's data processing agreement. Push notifications sent from our servers do not carry health details (the time since the last feeding and the breastfeeding side in a feeding reminder, and the text of a Community reply or a question title, are not included; they are shown in the notification inbox in the app). Crash reports and usage statistics (only if you consent) and push notifications are processed by Google LLC, which may process this data in the USA; Google LLC is certified under the UK Extension to the EU-U.S. Data Privacy Framework, so we rely on the adequacy regulations above for these transfers and, in addition, on the standard contractual clauses incorporated into Google's data processing terms for Firebase and Google Analytics, as they apply to transfers from the United Kingdom. Your correspondence with our support and data protection addresses is stored in Google Workspace and may be processed by Google in Google's data centers, including in the USA; for this transfer we likewise rely on the same adequacy regulations and on the standard contractual clauses in the Google Workspace data processing terms, as they apply to transfers from the United Kingdom. Because our hosting provider and our own mail server are located in Türkiye, storing data with them does not involve a separate transfer outside Türkiye. Data passed to the ad mediator and the advertising partners for ads (if you are a Bebemo Plus subscriber, only in rewarded ads you choose to watch) may be processed in the USA, Ireland and Singapore. The UK has no adequacy regulations for Singapore. This data is collected directly from your device by the advertising partners' software components; the safeguards the partners rely on for these transfers are described in their privacy policies linked in Section 8. The data that Apple and Google collect directly from you for Sign in with Apple, Sign in with Google, the App Store and Google Play is subject to their own privacy policies and transfer safeguards. You can request a copy of the safeguards we use at legal@mobiza.com.tr.
10. Retention
We keep personal data only for as long as necessary for the purposes for which it is processed. To determine retention periods, we use the following criteria: the duration of your account; the time needed to handle your request, complaint or support case; the retention periods for accounting and commercial records under Turkish law; the limitation periods for possible legal claims; and the time for which we must be able to prove consents and opt-outs. The main periods are:
- Account and app data (including child profiles, pregnancy data, care logs, growth data, Memory Box texts and Community posts): for as long as your account is active. When you delete your account in the app, this data is deleted immediately, or within 30 days at the latest of the verification of your identity for requests made by email, and backup copies are deleted within the backup cycle (30 days). The family you are the Family admin of is deleted for everyone, even if it has other members (the admin role cannot be handed over); if you are a member of a family whose admin is someone else, the child profiles and their entries belong to the family and stay with the other members.
- Individual entries, memories, child profiles and Community posts you delete in the app: removed from the app immediately; marked as deleted on our servers and permanently deleted within 31 days.
- Community posts that were not published because they broke a rule: visible only to their author; permanently deleted automatically if not edited and resubmitted within 30 days.
- Photos, memory videos and the assistant chat history: not stored on our servers; they stay on your phone until you delete them, delete your account on that phone (for photos and videos) or uninstall the app. Memory videos are also deleted from that phone when the memory is deleted, when you leave the family or when the family is deleted. Photos and videos received through Sync at home are also deleted the next time Sync at home is opened on that phone after the memory is deleted or you leave the family.
- Bebemo Assistant and AI credits: messages are not stored on our servers; the credit ledger (including credit pack purchase, rewarded ad, valid report reward and Bebemo gift movements), personal extra credits and the consent date are kept while your account exists and are deleted when you delete your account; the family profile's shared credit account, purchased credits added to the family profile and credits Bebemo gives to the family profile as a gift are kept while the family profile exists, and purchased credits stay with it even if the buyer's account is deleted; when the family profile is deleted, unspent purchased credits move to the buyer's account as personal credits (if the buyer's account has been deleted, they are deleted together with the family profile), while credits gifted to the family profile are deleted together with it. Retention period at Anthropic: inputs and outputs are deleted from Anthropic's systems within 30 days at the latest of being received or generated; content flagged by Anthropic's automated trust and safety systems as possibly violating its Usage Policy may be kept for up to 2 years, and the related trust and safety classification scores for up to 7 years; Anthropic may keep data longer where a legal obligation requires it and does not use this data to train its models.
- Reported assistant replies (the reply, the last question that led to it, reason, note, language, model; our team sees them under a pseudonym): 180 days; deleted immediately when you delete your account.
- Community check records (decision, rule involved, short note, duration and date; without the content): deleted after 90 days, or immediately when you delete your account. For the content passed to Anthropic for the check, retention period at Anthropic: inputs and outputs are deleted from Anthropic's systems within 30 days at the latest of being received or generated; content flagged by Anthropic's automated trust and safety systems as possibly violating its Usage Policy may be kept for up to 2 years, and the related trust and safety classification scores for up to 7 years; Anthropic may keep data longer where a legal obligation requires it and does not use this data to train its models.
- Community moderator decisions and history of restrictions (action, administrator, date, rule, short note): 365 days; the previous text of an edited post 30 days; when you delete your account the decisions are unlinked from it, and the previous text and the history of restrictions are deleted immediately.
- Notification inbox: copies of the notifications our servers send are permanently deleted automatically 90 days after they are created, or immediately when you delete your account; notifications linked to a child profile or family are also deleted when that profile is permanently deleted or the family is deleted, and feeding reminder notifications are deleted when you withdraw your explicit consent to health data. Inbox entries for reminders set up on the phone are kept only on your phone for 90 days and are deleted from the phone when you sign out, when you delete your account and when the related family or profile is deleted.
- Health data after you withdraw consent: deleted without undue delay; backup copies are deleted within the backup cycle.
- Entries you made in the profile of a family with other members: if you delete your account, these entries remain in that family's records without your name. The text of your Community posts, however, is deleted, and the posts are no longer linked to you; the check records kept for your posts and reports are also deleted.
- Purchase records (store transaction number, product, amount and currency, transaction date, store, country, refund and, only if it came from an older version of the app, withdrawal consent information): 10 years from the end of the calendar year in which the purchase was made (Turkish Commercial Code No. 6102 Art. 82, Tax Procedure Law No. 213 Arts. 253 and 254), then deleted automatically. When you delete your account, these records are not deleted; they are unlinked from your account and family, and your name, email address and device information are not kept. If you ask for erasure, these records are kept to the extent necessary for the establishment, exercise or defence of legal claims (Article 17(3)(e) UK GDPR). An unlinked record cannot be matched to you (Article 11); it can be found if you give us the store transaction number.
- Subscription and credit ledger records and other records we must keep by law: the subscription status record and the credit ledger are deleted together with your account; other records are kept for the periods in tax and accounting law (up to 10 years).
- Server and security logs: 2 years.
- Access and action logs of the administration tool: 2 years.
- Crash reports: for the retention period Firebase applies to crash reports (currently 90 days); unsent reports on your device are deleted when you withdraw your consent to crash reports.
- Usage statistics: event-level and user-level data is deleted in Google Analytics after 14 months; when you withdraw your consent, collection stops and the app instance ID and unsent events are deleted from your device. Because crash reports and the usage statistics in Google Analytics are not linked to your account, they cannot be matched to your account and deleted when you delete it.
- App sessions: deleted on our servers after 14 months, or immediately when you withdraw your consent or delete your account. Sessions not yet sent wait on your phone for up to 30 days.
- Usage and operations records: active days, AI calls and per-person notification and storage counters are deleted after 14 months; the revenue and cost summary per person is kept up to date for as long as your account exists. When you delete your account, your active days, counters and summary are deleted immediately; the link between AI calls and your account is removed, and these rows stay for cost tracking, not linked to anyone, until the 14-month period ends. Daily totals that are not linked to anyone (for example, that day's number of active users or total cost) contain no personal data and are kept.
- Launch notification sign-ups: your email address is kept for no longer than 12 months after Bebemo is released in the app stores, or until you withdraw your consent, whichever is earlier; it is deleted immediately when you leave the list, and a one-way digest that cannot be reversed is kept in its place to prove the consent record. The consent record (time of consent, IP address and version of the consent text) is kept for 3 years from the date the consent ceases to be valid (when the consent is withdrawn or the email address is deleted at the end of its retention period), then deleted automatically, as required by Article 13(2) of the Turkish Regulation on Commercial Communications and Commercial Electronic Messages.
- Support correspondence: 2 years after the request is closed.
- Advertising data: data passed to the ad mediator and the advertising partners is kept for the periods stated in the partners' privacy policies linked in Section 8. Your ad preference and the information about the tool or music unlocked by a rewarded ad are kept only on your phone until you change your preference or uninstall the app. Because this data is not linked to your account, it cannot be deleted together with your account. Credits earned with a rewarded ad, however, are added as extra credits that only the person who watched the ad can use and that are valid for 7 days; they are recorded in the credit ledger and kept with it.
- Ad revenue records: 24 months from the impression date, then deleted. When you delete your account, the records' link to your account and your family is removed immediately; the remaining records are kept as anonymous revenue figures that cannot be linked to anyone until the end of this period. Impressions not yet sent wait on your phone for at most 30 days; in the United Kingdom, impressions are held on your phone only if you have given ad consent, and waiting impressions are deleted when you withdraw it. If you object to ad revenue records, later records are not linked to your account and the link of your existing records is removed within 30 days at the latest.
- Brand stories you have seen: deleted 30 days after the campaign ends or is unpublished, in any case no later than 180 days; deleted immediately when you delete your account. Total counts contain no personal data.
At the end of these periods, data is deleted or anonymised. Details of account deletion are given on the Account and Data Deletion page.
11. Your Rights
Subject to the conditions and exceptions in the UK GDPR and the DPA 2018, you have the right:
- to obtain confirmation as to whether we process your personal data, and to access the data and information about the processing (Article 15),
- to have inaccurate data rectified and incomplete data completed (Article 16),
- to have your data erased (Article 17),
- to have processing restricted (Article 18),
- to receive the data you have provided to us, where it is processed by automated means on the basis of your consent or a contract, in a structured, commonly used and machine-readable format, and to have it transmitted to another controller (Article 20),
- to object at any time, on grounds relating to your particular situation, to processing based on our legitimate interests, and to object at any time and without giving reasons to the use of your data for direct marketing (Article 21),
- to withdraw your consent at any time, without affecting the lawfulness of processing before the withdrawal (Article 7(3)),
- to complain to us and to the Information Commission (Section 16).
How to exercise your rights: Send your request to legal@mobiza.com.tr, preferably from the email address registered to your Bebemo account; if you use Apple's Hide My Email feature, we may ask for additional information reasonably needed to confirm your identity. In the app, you can view and correct much of your data, export your Memory Box free of charge as a ZIP archive (the PDF memory book is part of Bebemo Plus; videos are not included in these files), withdraw your consent for health data and for the Bebemo Assistant, withdraw your consent to usage statistics and object to crash reports with the switches under Profile › Privacy, withdraw your consent to personalized ads under Profile › Privacy › Ad preferences, delete your Community posts, and delete your account under Profile › Account › Delete account (see Account and Data Deletion). Requests are free of charge. We respond without undue delay and in any case within one month of receiving your request or, if later, of receiving the information we need to confirm your identity; where necessary, taking into account the complexity and number of requests, we may extend this period by two further months, in which case we tell you within the first month and explain why. If we process a large amount of information about you and reasonably need you to specify the information or processing activities your request relates to, we may ask you to do so, and the time limit is paused until you reply. For access requests, we carry out reasonable and proportionate searches. We ask only for the information reasonably necessary to verify your identity; we do not ask for a Turkish national ID number, a passport number or a handwritten signed letter. Where a request is manifestly unfounded or excessive, we may charge a reasonable fee or refuse to act on it, as permitted by the UK GDPR. We inform the recipients to whom your data has been disclosed of any rectification, erasure or restriction, unless this proves impossible or involves disproportionate effort (Article 19).
Your child's data and family profiles: A child has rights over their own personal data. Until the child is mature enough to exercise these rights themselves, the parent or legal guardian who owns the child profile, or another person with parental responsibility for the child, can exercise them on the child's behalf and in the child's best interests. If you are an invited family member, you can exercise your rights over your own data; requests concerning a child's data should be made by the owner of the child profile or by a person with parental responsibility for the child. When responding to requests, we take the rights of other family members into account, for example where a record also contains information about them.
12. Automated Decision-Making
We do not take significant decisions about you based solely on automated processing, that is, decisions that produce legal effects concerning you or similarly significantly affect you (Articles 22A to 22D UK GDPR). Bebemo automatically calculates reminders, summaries and reports from the records you enter, for example the next feeding time, a reminder that no dirty diaper has been logged for three days, or weekly sleep and feeding summaries. These are only information for you: they do not produce legal effects, do not similarly significantly affect you and are not medical assessments. The Bebemo Assistant's answers are also automatically generated general information; the records it suggests are saved only when you confirm them. Every question and reply you write in the Community is checked automatically in the background against the Community rules by a word filter and an AI service before it is published (while the check is running, the post is visible only to you); a reported post is also checked automatically once more on its first report and is hidden if it is found to break the rules. This check is automated, but it is not a decision that produces legal effects concerning you or similarly significantly affects you: a moderator looks at posts the AI is not sure about, you can edit and resubmit a post that was not published because it clearly broke the rules, and to appeal a check decision you can write to legal@mobiza.com.tr and ask for the decision to be reviewed by a person. A post reported by three different users is also hidden automatically until a moderator reviews it. We never use your health data or Memory Box content for advertising or marketing profiling. If you consent, advertising partners may build an advertising profile to personalize ads; this is not a decision that produces legal effects concerning you or similarly significantly affects you. No profile of your child is built. Usage and operations records and the revenue and cost summary per person are not used to make automated decisions about you either. Automated security controls may temporarily limit requests; if you believe that such a control has affected you wrongly, contact us and a member of our team will look into it.
13. Cookies and Similar Technologies
Website: bebemo.com.tr uses no cookies, no local storage, no analytics tools and no tracking pixels. Fonts are loaded from our own server, so visiting the site does not send requests to font services such as Google Fonts. Our website therefore does not store information on your device, or access information stored on it, in a way that would require consent under regulation 6 of PECR. The server logs kept for security are stored on our servers, not on your device.
App: Apart from usage statistics and advertising technologies, the Bebemo app stores and accesses information on your device only where this is strictly necessary to provide the app and the features you use, for example to keep you signed in, save your settings, deliver the notifications you have switched on (push notification token), keep the Memory Box photos and videos and assistant chat history that exist only on your phone and, if you turn on Sync at home, the pairing key, and keep the app secure. Under regulation 6 of PECR, this does not require consent. Detecting crashes and technical faults through Firebase Crashlytics (Google LLC), which stores an installation ID on your device, happens only with your consent; crash reports are off by default, and you can withdraw your consent at any time under Profile › Privacy. For usage statistics, the app stores and accesses information on your device (the Google Analytics for Firebase app instance ID and events not yet sent, and app sessions not yet sent) only with your consent under regulation 6 of PECR; until you consent, collection is completely off. If you do not have a Bebemo Plus subscription, the app uses the software components of the ad mediator and the advertising partners and the advertising identifier for the ads in the free version; if you are a Bebemo Plus subscriber, these components and the consent form below are started only when you first tap the rewarded ad button. Google's consent form (User Messaging Platform; IAB TCF) is shown for this; the advertising partners' storing of and access to information on your device and the personalization of ads are subject to the consent you give in this form, and if you do not consent, ads are shown without personalization (contextually). On iPhone, the advertising identifier (IDFA) is accessed only if you grant App Tracking Transparency permission; this permission is requested only if you have consented to personalized ads in Google's form. By default, ads are not personalized; without your consent, a signal that you have not given consent is sent to the ad mediator. You can change your choice under Profile › Privacy › Ad preferences (Sections 5 and 8). If we ever want to use another technology that requires consent under PECR, we will ask for your consent first and update this Notice. Device permissions such as camera, photo library, local network and notifications are requested only when you use a feature that needs them, and you can withdraw them in your device settings at any time.
Further details are given in the Cookie Policy.
14. Security
We implement appropriate technical and organisational measures to protect personal data, including encrypted transmission (TLS) on all connections, access controls that make each family profile accessible only to its members, never sending photos and videos to our servers, end-to-end encryption of photo and video transfers between family phones (Sync at home) and not storing assistant messages, storing email sign-in passwords as salted scrypt hashes and refusing passwords known to have been breached (with Apple and Google sign-in, the passwords of those accounts are not passed to us), limiting our staff's access to health data and Memory Box content to what is strictly necessary; our employees can see only account-level data, mostly masked and according to role-based permissions, in an administration tool that requires two-step verification and logs every access, and health data, children's information, entries, memories and assistant conversations are never shown in that tool (its logs are kept for 2 years), logging, and regular backups. If a personal data breach occurs, we notify the Information Commission and the people affected where the UK GDPR requires it. Please remember that notifications and the feeding timer on the lock screen can be seen by anyone who can see your device's screen; you can turn them off in the app or in your device settings.
15. Children
Bebemo is intended for adults. Only people aged 18 or over can create an account; children do not create accounts and do not use Bebemo themselves. Information about children aged 0 to 6 is entered by a parent or legal guardian or by the family members they invite, and the parent or legal guardian gives the explicit consent for the child's health data (Section 7).
Bebemo is not directed at children and is not designed to be used by them. However, because Bebemo holds information about children, we handle that information with the best interests of the child in mind, the principle on which the ICO's Age Appropriate Design Code (the "Children's Code") is also based: child profiles are private by default and visible only to the family members the parent invites; their content is never made public; children's health data and Memory Box content are never sold, used for advertising or marketing profiling or passed to advertising partners; the ads in the free version are shown to the parent using the app, ad networks are told that the app is not directed to children, and no profile of the child is built; and parents can export or delete this data at any time. If we learn that someone under 18 has created an account, we close the account and delete the related data.
16. Complaints
Complaining to us: Under section 164A of the DPA 2018, you have the right to complain to us if you are concerned about the way we process your personal data. You can send your complaint electronically to legal@mobiza.com.tr. We acknowledge receipt of your complaint within 30 days, take appropriate steps to respond to it without undue delay, including making enquiries into its subject matter to the extent appropriate, and inform you of the outcome without undue delay.
Complaining to the Information Commission: You also have the right to complain to the Information Commission (ICO), the UK data protection regulator, through its complaint page. The regulator generally expects you to raise your concern with us first and to give us the opportunity to respond. You also have the right to bring proceedings before the courts.
17. Changes to This Notice
We may update this Notice if the law, our services or our service providers change. The date of the current version is shown at the top of this page. For significant changes, we may also inform you in the app or by email; if a change requires your consent (for example, using health data for a new purpose), we will ask for your consent first.
18. Language of This Notice
This Notice is published in Turkish and English with the same content. For people located outside Türkiye, the English version is authoritative.
अन्य क़ानूनी दस्तावेज़
कंपनी की जानकारी
Bebemo, Mobiza Teknoloji द्वारा बनाया और चलाया जाने वाला प्रोडक्ट है।
- नाम
- Mobiza Teknoloji
- पता
- Ovaakça Santral Mah. Ovaakça Fatih Sultan Mehmet Cad. No: 86, 16335 Osmangazi, Bursa, Türkiye
- कर कार्यालय (vergi dairesi)
- कर पहचान संख्या
- 1280527561
- DUNS संख्या
- 751143161
- कंपनी की वेबसाइट
- mobiza.com.tr