法律
GDPR Privacy Notice (European Economic Area and Switzerland)
Explains, for people in the European Economic Area and Switzerland, how Bebemo processes personal data, including health data, and on what legal bases, with whom it is shared, with what safeguards it is transferred, and your rights under the GDPR and the Swiss Federal Act on Data Protection.
目录 · 共 20 节
- Data Controller Information
- 1. Purpose and Scope of This Notice
- 2. Controller, Representative and Contact
- 3. Our Role, Family Sharing and Purchases
- 3.1. Processing for Which We Are the Controller
- 3.2. Family Sharing and Information About Your Family
- 3.3. Purchases (App Store and Google Play)
- 4. Personal Data We Process and Where It Comes From
- 4.1. Categories of Personal Data
- 4.2. Sources
- 5. Purposes and Legal Bases
- 5.1. Our Legitimate Interests
- 5.2. Consent
- 6. Is Providing Your Data Required?
- 7. Special Categories of Personal 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. Right to Lodge a Complaint
- 17. Additional Information for People in Switzerland
- 17.1. Applicable Law and Contact
- 17.2. Disclosure Abroad
- 17.3. Your Rights in Switzerland
- 18. Changes to This Notice
- 19. Language of This Notice
This Notice is published in Turkish and English with the same content. If you are located outside Türkiye, this English version is the authoritative version for you (see Section 19).
Data Controller Information
- Data controller: Mobiza Teknoloji
- Brand / service: Bebemo
- Data protection contact: legal@mobiza.com.tr
- Customer support: info@mobiza.com.tr
- Phone: +90 850 307 90 23
- Address: Ovaakça Santral Mah. Ovaakça Fatih Sultan Mehmet Cad. No: 86, 16335 Osmangazi, Bursa, Türkiye
- Website: bebemo.com.tr
- Representative in the European Union (Article 27 GDPR): Enes Babekoglu, Zlatoustovo village, Madzharovo municipality, Haskovo province, 6484, Bulgaria (in Bulgarian: с. Златоустово, общ. Маджарово, обл. Хасково, 6484, България), email: legal@mobiza.com.tr
1. Purpose and Scope of This Notice
This GDPR Privacy Notice (the "Notice") explains how Mobiza Teknoloji ("we" or "us"), which develops and operates the pregnancy and baby tracking app Bebemo, processes the personal data of people located in the European Economic Area ("EEA": the member states of the European Union, Iceland, Liechtenstein and Norway) and in Switzerland. It provides the information required by Articles 13 and 14 of Regulation (EU) 2016/679 (General Data Protection Regulation, "GDPR") and, for Switzerland, by Article 19 of the Federal Act on Data Protection of 25 September 2020 ("FADP"). Because we offer Bebemo to people in the EEA, the GDPR applies to the processing described in this Notice (Article 3(2)(a) GDPR).
This Notice covers the processing for which we are the controller, in particular when you:
- visit the bebemo.com.tr website,
- leave your email address on our website to be notified when Bebemo launches,
- create an account in the Bebemo app using Sign in with Apple, Sign in with Google or your email address and a password, and use the app's features, including pregnancy tracking, baby care logs, reminders, reports, the Memory Box, the Bebemo Assistant and the Community,
- are invited to a family by a parent as a partner, grandparent or caregiver and use the family profile with your own Bebemo account,
- buy a Bebemo Plus subscription through the App Store or Google Play, your subscription renews, is cancelled or ends, or you restore your purchase on a new device,
- 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 service messages and push notifications from us or, if you consent, the launch announcement and news emails,
- 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).
Data about your child: Children do not create accounts in Bebemo. Information about your child is entered by you, as the child's parent or legal guardian, or by family members you invite. This Notice also explains how we process your child's personal data; your child's rights are exercised on the child's behalf by their parent or legal guardian (Sections 11 and 15).
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 EEA or Switzerland and this Notice differs from the Privacy Policy, this Notice prevails. The scope of the explicit consent you give to the processing of your and your child's health data is set out in the Explicit Consent for Health Data. 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 United Kingdom should read the UK Privacy Notice, and residents of the United States the US Privacy Notice.
2. Controller, Representative and Contact
The controller for the processing described in this Notice is Mobiza Teknoloji, established in Türkiye, whose contact details are given at the beginning of this Notice. We have no establishment in the EEA, the United Kingdom or Switzerland.
Our representative in the European Union under Article 27 GDPR is: Enes Babekoglu, Zlatoustovo village, Madzharovo municipality, Haskovo province, 6484, Bulgaria (in Bulgarian: с. Златоустово, общ. Маджарово, обл. Хасково, 6484, България), email: legal@mobiza.com.tr. People in the European Economic Area and supervisory authorities can contact our representative, in addition to or instead of us, on all matters relating to the processing of personal data in connection with Bebemo; our representative also keeps the records of our processing activities under Article 30 GDPR and provides them to supervisory authorities on request.
Information concerning Switzerland is given in Section 17.1.
Please send questions about the processing of your or your child's personal data, and requests to exercise your rights, to legal@mobiza.com.tr; you can also send questions about your account, the app or your purchase to info@mobiza.com.tr.
3. Our Role, Family Sharing 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 announcement list, Bebemo accounts, pregnancy and baby tracking logs, the Memory Box, family sharing, the Bebemo Assistant, the Community, reminders and push notifications, reports and exports, crash reports and usage statistics, verification of in-app purchases, customer support, information security and compliance with the laws that apply to us. In Bebemo, we do not act as a processor on behalf of any other company or organization.
3.2. Family Sharing and Information About Your Family
The person who creates a pregnancy or child profile in Bebemo (the "profile owner"; "Family admin" in the app; usually a parent, and sometimes a grandparent or caregiver when the family does not use Bebemo yet), or another parent in the family, can invite the mother, a partner, a grandparent or a caregiver to the family with an invite code, valid for 7 days, that they create in the app and share themselves; we do not send anyone an email for an invitation. Family members who accept the invitation can see the entries in the family profile and add new ones; entries sync in real time, and each entry shows who logged it. A family can have more than one child profile. Because the people you invite can access the entries in the family profile, including health data, we recommend that you invite only people you trust.
When you enter information about yourself, your child and your family for your family's own purposes, this is, as a rule, a purely personal or household activity within the meaning of Article 2(2)(c) GDPR. This does not affect our obligations: as the controller that processes this data in our systems, we comply with the GDPR (Recital 18 GDPR). Please enter information about your partner or another adult, such as the health information of the person who is pregnant, only with that person's knowledge and agreement.
3.3. Purchases (App Store and Google Play)
Bebemo is free to download. Bebemo Plus is an optional subscription that renews automatically every month or every year, and it can be bought only within the app through the App Store or Google Play. The subscription 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 payment is processed entirely by Apple or Google, which process your payment data as independent controllers under their own privacy policies. We never receive your card or other payment details. To verify the subscription, turn Plus on in the family profile, keep track of the subscription's status and restore the purchase on new devices, we receive only 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 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. Cancellations and refund requests are made through Apple or Google under their policies. 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 interact with Bebemo, we process the following categories of personal data; a detailed list is given in the Privacy Policy:
- Website visitors: server logs containing the IP address, browser and operating system information (user agent), the address of the page visited and the time of access. Our website does not use cookies, analytics tools or tracking pixels.
- People who sign up for the launch announcement: email address, the site language you chose, the fact that you ticked the consent box, the time of consent, the version of the consent text, IP address and browser information (user agent).
- Account holders (parents and invited family members): first and last name, email address (with Sign in with Apple, this may be a private relay address created by Apple), Apple or Google user ID, for email sign-in an irreversible hash of the password and hashes of the email verification and password reset codes, open sessions (device name, platform, last use), language preference, the chosen ready-made profile picture (only its identifier; no photo is uploaded; visible to family members and, on posts that are not anonymous, to other Community users) and the phone's time zone (sent automatically by the app with each request; not derived from location; used so that days, reminders, notifications and limits follow the person's own local time), role in the family, reminder and notification settings (including the setting that sends night-time notifications only to the chosen parent), device tokens for push notifications 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 model, operating system and app version, IP address, crash and diagnostic logs.
- App users who consent to crash reports: 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.
- App users who consent to usage statistics: 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 (app users who consent to 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.
- Pregnancy data: due date or the date of the last menstrual period, doctor appointments, symptom and mood diary, weight and blood pressure readings, kick counts, contraction timings, hospital bag checklist and favorite baby names.
- Data about your child: the child profile (name, date and time of birth, sex, which is asked only to choose the color theme and can be changed at any time, birth weight and length, the week of pregnancy at birth if the baby was born early, the birth order and the link to siblings born together for twins and triplets, the identifier of the ready-made picture chosen for the profile; no photo of the child is added); logs of breastfeeding, bottle feeding and pumping, solid foods and allergy notes, sleep, diapers (including stool color and consistency, and gas and colic notes), baths, tummy time, fever, medicine and vitamin doses, vaccines, doctor visits, height, weight and head circumference, teeth and developmental milestones.
- Memory Box content: 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; we therefore do not process them. 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.
- Data about family members: 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, and who logged which entry.
- People who use the Bebemo Assistant: the messages written 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 and a short summary of recent records), the date of 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 the credit balance). The chat history is kept only on the 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).
- People who use the Community: the questions and replies they write (including category, tags, an optional province and birth-month group), whether they chose to post anonymously, "helpful" votes, reactions to questions and replies, saved questions, reports sent and the credits added for a report found to be valid, for verified experts their field of expertise, whether they have Bebemo Plus (for the Plus mark and the daily question limit), the status of their 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 their 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).
- Bebemo Plus subscribers: 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, received from the App Store or Google Play; we do not receive card details (Section 3.3).
- People who buy credit packs: the store transaction ID, the product purchased, the platform, the purchase status, the credits added and the family profile they were added to, received from the App Store or Google Play, and the account ID passed to the store as an account identifier; we do not receive card details (Section 3.3).
- People who contact us: name, email address, the content of your messages and support requests, attachments and correspondence history.
- App users who see ads (in the free version if they do not have a Bebemo Plus subscription, or only in rewarded ads they choose to watch if they 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).
- Usage and operations records (app users who are signed in; 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.
Much of the pregnancy data and the care logs about your child is health data, a special category of personal data; we process this data as described in Section 7.
4.2. Sources
We collect personal data:
- directly from you, when you fill in forms, use the app, log entries, upload content or write to us,
- for data about your child, from you as the child's parent or legal guardian and from the family members you invite,
- from other family members who log entries in the same family profile (for example, who logged which entry),
- from the person who invites you to the family (the role your invite code gives you),
- from Apple or Google, when you use Sign in with Apple or Sign in with Google (your first and last name, email address and user ID); directly from you when you sign up with email,
- from other users in the Community (for example, replies to your posts and reports),
- from Apple or Google in connection with your Bebemo Plus subscription and credit pack purchases (purchase verification and renewal, cancellation and refund notifications),
- automatically from your device and browser when you use our website and the app (server logs, active day, AI call, notification and storage records, device information, 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 Legal Bases
| Purpose | Main data | Legal basis (Article 6(1) GDPR; for health data, also Article 9(2)) |
|---|---|---|
| Creating your account, Sign in with Apple, Sign in with Google or email and password sign-in (including email verification and password reset), providing the app and syncing your data across your devices | first and last name, email, Apple or Google user ID, password hash, hashes of verification codes, sessions, language and time zone, child profile | Performance of a contract with you (b) |
| Storing pregnancy and baby health logs, syncing them across your devices and with your family members, sending reminders based on these logs, preparing reports and exporting entries as PDF and Excel files (longer-term statistics, the monthly summary and exporting entries are part of Bebemo Plus) | your and your child's health data (Section 7) | Your explicit consent (a and Article 9(2)(a)); for your child's data, the explicit consent you give on your child's behalf as the child's parent or legal guardian |
| Providing the Memory Box: storing memory texts and showing them to family members (photos and videos are kept on phones and are not sent to us) | the memory's title, note, date, milestone and whether it has a photo | Performance of a contract (b); for health information you add to memory texts, your explicit consent (Article 9(2)(a)) |
| Family sharing: creating invite codes, giving family members access to the profile and showing who logged each entry | invite code and role, family members' first and last names, roles and labels, entry details | Performance of a contract with the users who send and accept the invitation (b) |
| 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) |
| Providing reminders and push notifications (feeding, medicine and vitamin, vaccine, appointment and family activity reminders; memory suggestion notifications are scheduled on your phone and are not processed by us) and the live feeding timer on the lock screen | reminder and notification settings, device tokens, relevant logs | Performance of a contract (b); for reminders based on health logs, 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 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 choose to 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 EU or Member State law, we do not rely on Article 6(1)(c) for them |
| Answering support requests, questions and messages | name, email, message content | Performance of a contract (b) where your request concerns your account, the app or your purchase; otherwise our legitimate interest in answering your questions (f) |
| Sending service messages about your account, security, purchases 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, authentication, logging, preventing fraud and misuse, and fixing errors using crash and diagnostic logs | IP address, device and app 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 Article 5(3) of the ePrivacy Directive and the national laws implementing it. 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 Article 5(3) of the ePrivacy Directive and the national laws implementing it |
| 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 Article 5(3) of the ePrivacy Directive and the national laws implementing it |
| 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 Article 5(3) of the ePrivacy Directive and the national laws implementing it; 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: analyzing 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 analyzing 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 (EU Digital Services Act, Art. 26) |
| 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 analyzing our business (f); you can object to this processing (Section 11) |
| Providing and securing our website | IP address, browser information, page address, time of access | Our legitimate interest in providing our website securely (f) |
| Sending the launch announcement and, if you consent, news and announcements about Bebemo by email | email, site or app language | Your consent (a); sending commercial electronic messages is also based on your prior consent under Article 13 of the ePrivacy Directive (2002/58/EC) and the national laws implementing it, and under Turkish Law No. 6563 on the Regulation of Electronic Commerce |
| 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); sending commercial electronic messages is also based on your prior consent under Article 13 of the ePrivacy Directive (2002/58/EC) and the national laws implementing it, and under Turkish Law No. 6563. 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 |
| Proving the consents and opt-outs you have given | time of consent, version of the consent text, IP address, browser information | Our legitimate interest in being able to demonstrate your consent (f; Article 7(1) GDPR) |
| Establishing, exercising or defending legal claims and responding to requests from public authorities | relevant records | Legal obligation under EU or Member State law (c), where one applies; otherwise our legitimate interest in protecting our rights (f); for health data, also Article 9(2)(f) |
5.1. Our Legitimate Interests
Where we rely on legitimate interests, our interests are: providing a secure and reliable service, fixing errors and preventing fraud and misuse; protecting the Community against harmful content and checking posts automatically before they are published; enabling family sharing; offering the free version of Bebemo with non-personalized (contextual) ads and keeping it sustainable by analyzing ad revenue at account level; running the service, measuring usage and growth, keeping track of infrastructure and AI costs and analyzing pricing and sustainability; answering inquiries and keeping our users informed about the service; being able to demonstrate the consents given; complying with the laws that apply to us as a company established in Türkiye; and establishing, exercising or defending legal claims. We use only the data needed for these interests and weigh them against your and your child's interests and fundamental rights and freedoms. 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: for health data, in the app's settings (Section 7); for the Bebemo Assistant, with "Withdraw permission" in the assistant menu; for usage statistics, with the Usage statistics switch under Profile › Privacy, after which collection stops, the app instance ID and unsent events are deleted from your device and your app sessions on our servers are deleted too; for personalized ads, by reopening Google's consent form under Profile › Privacy › Ad preferences (and, on iPhone, the tracking permission under Settings › Privacy & Security › Tracking); for promotion and partner notifications, with the Promotion and partner notifications switch under Profile › Family and notifications (one tap; these notifications are off by default and are not sent without this separate consent); for the launch announcement and news emails, through the unsubscribe link included in each email or by writing to legal@mobiza.com.tr. Withdrawing consent does not affect the lawfulness of processing carried out before the withdrawal.
6. Is Providing Your Data Required?
You are not under a statutory obligation to provide personal data to us. However, a sign-in method (your Apple or Google account ID, or your email address and a password) and your email address are necessary to conclude and perform the contract with you: without them, we cannot open an account for you or provide the service. Using the Bebemo Assistant and the Community is entirely optional. Consent to usage statistics is 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. To turn Bebemo Plus on, the subscription must be verified with the store's transaction information. Giving explicit consent to the processing of health data is optional; if you do not consent, you cannot use the features that let you keep pregnancy and baby health logs, but you can continue to use the features that do not require this data. Consent to the launch announcement and news emails is entirely optional and has no effect on your use of Bebemo. You decide what information about your child and your family you enter.
7. Special Categories of Personal Data and Health Data
The pregnancy data you enter in Bebemo (for example, symptoms and mood, weight and blood pressure readings, doctor appointments, kick counts and contraction logs) and the logs about your child's health and care (for example, feeding, sleep, diaper, fever, medicine and vitamin, vaccine, allergy, doctor visit, growth and development logs) are health data within the meaning of Article 9 GDPR. Where we are unsure whether an entry is health data, we choose to protect it as health data.
Explicit consent: Apart from establishing, exercising or defending legal claims (Article 9(2)(f) GDPR), we process health data only on the basis of your explicit consent (Article 9(2)(a) GDPR). Before storing entries that contain health data, the app asks for your explicit consent separately from the terms of use and any other consents; the scope of the consent is explained in the Explicit Consent for Health Data. Giving explicit consent is optional, and not giving it does not prevent you from using the features that do not require health data. Because feature usage events in usage statistics (for example, "feeding entry added") can show that you use pregnancy and baby care features, these events also rely on your explicit consent (Article 9(2)(a)), requested in a separate window (Section 5).
Your child's health data: For health data about your child, you give the explicit consent on your child's behalf, as the person with parental authority or parental responsibility for the child. Health entries that the family members you invite log in the same profile are also processed under this consent.
Withdrawing consent: You can withdraw your explicit consent at any time in the app's settings. Once you withdraw it, health logs can no longer be stored or synced, and existing health logs are deleted. Before it is deleted, you can request a copy of your data held on our servers free of charge by writing to legal@mobiza.com.tr, and if you have a Bebemo Plus subscription you can also export your entries from the app as PDF or Excel files. Withdrawal does not affect the lawfulness of processing carried out before it.
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) 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.
Additional safeguards: We do not sell your health data or your Memory Box content, we never use them for advertising or for marketing profiling, and we do not pass them to advertising partners; health data is never processed for advertising purposes in any way. We store this data so that only you and the family members you invite can see it; access by our staff and service providers is limited to what is necessary to provide and secure the service and to handle your requests (Section 14). 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. Please do not include health data in support requests unless it is needed to answer your request.
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 (Google Analytics for Firebase) for usage statistics, only if you consent, Google (Google Workspace) for transmitting and storing your correspondence with our support and data protection addresses (the emails you send and our replies), Google (Firebase Cloud Messaging) and, on iPhone, also Apple (Apple Push Notification service) for delivering push notifications, 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 the data only on our instructions and under contracts that comply with Article 28 GDPR,
- sign-in providers: Apple and Google, if you use Sign in with Apple or Sign in with Google; these companies act as independent controllers for the sign-in process,
- 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,
- app stores: Apple, which operates the App Store, and Google, which operates Google Play, for Bebemo Plus subscriptions and credit packs; 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; these companies act as independent controllers for the purchase, subscription and payment process,
- family members: the family members you invite, or who invited you, can see the entries in the family profile, memory texts and who logged them; 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); Memory Box content is never shared publicly,
- 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,
- 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: accounting, legal and audit service providers,
- 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,
- corporate transactions: in the event of a merger, acquisition, demerger or sale of assets, a successor company that will continue to process the data in line with the safeguards in this Notice; we will inform you if this happens.
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 your health data or your Memory Box content for advertising or for marketing profiling, and we do not share them with third parties for these purposes. 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 the European Commission has not adopted an adequacy decision for Türkiye. Personal data that you send us directly when you use Bebemo is collected and processed by us. According to the European Data Protection Board (Guidelines 05/2021), such direct collection from you is not a transfer within the meaning of Chapter V GDPR; the GDPR nevertheless applies to our processing, and we protect your data with the measures described in Section 14.
Bebemo data is hosted on Pentech Bilişim Teknolojileri Sanayi ve Ticaret Limited Şirketi (PenDC data center) infrastructure, on servers located in Türkiye (Bursa). When your personal data is passed on to servers or service providers in a country not covered by an adequacy decision, or is transferred from a service provider in the EEA to our team in Türkiye, we rely on:
- an adequacy decision of the European Commission for the recipient's country (for example, for the EEA countries and the United Kingdom) and, for recipients in the United States that are certified under the EU-U.S. Data Privacy Framework, Commission Implementing Decision (EU) 2023/1795,
- where no adequacy decision covers the transfer, the appropriate module of the standard contractual clauses adopted by the European Commission in Implementing Decision (EU) 2021/914, together with supplementary measures such as encryption and access restrictions 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 (Modules Two and Three) incorporated into Anthropic's Data Processing Addendum.
Images stored on the server (for example, images created in the app at your request) and the copy of our database backups and server access logs, which is encrypted on our servers, are kept in Cloudflare R2, in a storage area restricted to the European Union jurisdiction, in data centers in the EU. If Cloudflare, Inc., which is based in the USA, needs to access this data to provide the service, we rely on the adequacy decision above, because Cloudflare, Inc. is certified under the EU-U.S. Data Privacy Framework, and, should that certification lapse for any reason, on the Standard Contractual Clauses in Cloudflare's data processing agreement. Memory Box photos and videos are not sent to Cloudflare.
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. 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). Google LLC is certified under the EU-U.S. Data Privacy Framework, so we rely on the adequacy decision above for these transfers; in addition, we rely on the Standard Contractual Clauses incorporated into Google's data processing terms for Firebase and Google Analytics. Your correspondence with our support and data protection addresses (info@mobiza.com.tr, legal@mobiza.com.tr) 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 decision and on the Standard Contractual Clauses in the Google Workspace data processing terms.
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. Ireland is in the EEA; the European Commission has not adopted an adequacy decision 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.
Apple and Google collect the data needed for sign-in and purchases directly from you as independent controllers and rely on their own transfer safeguards for that data. Transfers concerning people in Switzerland are described in Section 17.2. 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 or support case; the retention periods for accounting, tax 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. On this basis:
- Account and app data (including pregnancy and baby logs, Memory Box texts, Community posts, family, reminder and notification settings, sessions and device tokens): kept while your account is active. When you delete your account in the app, it is deleted immediately; for requests made by email, within 30 days at the latest of the verification of your identity; copies in backups are deleted within the backup cycle, within 30 days.
- 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: when you withdraw your explicit consent, existing health logs are deleted (Section 7).
- 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 defense of legal claims (Article 17(3)(e) GDPR). An unlinked record cannot be matched to you (Article 11 GDPR); it can be found if you give us the store transaction number.
- Subscription and credit ledger records and other records that the law requires us to keep: the subscription status record and the credit ledger are deleted together with your account; other records required by law are kept for the periods in Turkish 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 announcement list: your email address is kept for no longer than 12 months after Bebemo is released in the app stores, or until you leave the list (withdraw your consent), if earlier; it is deleted immediately when you leave. In its place, a one-way digest of your address that cannot be reversed is kept to prove the consent record. The records needed to prove your consent (time of consent, IP address and version of the consent text) are 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.
- "Advertise" applications: 1 year from the application.
- 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 EEA, 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.
Data whose retention period has ended is deleted or anonymized. When you delete your account, the child profiles of families of which you are the Family admin and of families of which you are the only member are deleted for everyone together with all their logs and Memory Box texts; because the admin role cannot be handed over, the other members of these families are removed from them. If you are a member of a family whose admin is someone else, the child profiles and their logs belong to the family and stay with the other members, and the entries you logged remain in that family's records, shown without your name. The text of your Community posts is deleted, and the posts are no longer linked to you; the check records kept for your posts and reports are also deleted. Details are given on the Account and Data Deletion page.
11. Your Rights
Subject to the conditions and exceptions in the GDPR, 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 lodge a complaint with a supervisory authority (Article 77; Section 16).
How to exercise your rights: Send your request to legal@mobiza.com.tr, preferably from the email address linked to your Bebemo account. You can also view and correct much of your data in the app, export your Memory Box free of charge at any time as a ZIP archive (and, with Bebemo Plus, as a PDF memory book; videos are not included in these files), delete your Community posts, withdraw your consent to usage statistics and object to crash reports with the Usage statistics and Crash reports switches under Profile › Privacy, withdraw your consent to personalized ads under Profile › Privacy › Ad preferences, and delete your account under Profile › Account › Delete account. Because photos, memory videos and the assistant chat history exist only on your phone, access and portability requests cover the data on our servers. Requests are free of charge. We respond without undue delay and in any case within one month of receipt; 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. We ask only for the information reasonably necessary to verify your identity; for example, we may ask you to send your request from the email address linked to your account or to sign in again in the app. 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 Article 12(5) 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).
Rights relating to your child: For data about your child, you exercise these rights on your child's behalf as the child's parent or legal guardian. As a rule, we handle requests concerning a child profile together with the profile owner, and we also take into account the rights of any other parent or legal guardian who uses the profile.
12. Automated Decision-Making
We do not make decisions about you or your child based solely on automated processing, including profiling, that produce legal effects concerning you or similarly significantly affect you (Article 22 GDPR). The reminders that the app generates automatically from your entries (for example, that a feed is due, or that no dirty diaper has been logged for three days), the weekly and monthly reports and the PDF and Excel files you export are information for you and your family members only. Bebemo is a tracking and information app; it does not diagnose, does not recommend treatment and does not make medical decisions about you. The Bebemo Assistant's answers are also automatically generated general information; they are not decisions about you, and 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. 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 intended to prevent misuse 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
The bebemo.com.tr website does not use cookies, analytics tools, tracking pixels or similar technologies, and it does not store information in your browser's local storage (for example, localStorage). Fonts are served from our own server, so no requests are sent to third-party services such as Google Fonts when you visit the site. Only server logs are kept, to provide and secure the site (Section 10).
The Bebemo app stores and reads on your device the information needed for the app to work, for example to keep you signed in, to remember your settings, to hold the device token for push notifications, to 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, to keep the pairing key. Under Article 5(3) of the ePrivacy Directive and the national laws implementing it, these operations, which are strictly necessary to provide the service you have explicitly requested, do not require consent. Crash reports sent through Firebase Crashlytics (Google LLC) to detect errors in the app, and the installation ID stored on your device for them, are used only with your consent under Article 5(3) of the ePrivacy Directive; crash reports are off by default, and you can withdraw your consent at any time under Profile › Privacy (Sections 5 and 8). Information is stored on and read from your device for usage statistics (the Google Analytics for Firebase app instance ID and events not yet sent, and app sessions not yet sent) only with your consent, as required by Article 5(3) of the ePrivacy Directive; 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. In the EEA and Switzerland, 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). Details are given in the Cookie Policy.
14. Security
We implement appropriate technical and organizational measures to protect personal data, including encrypted transmission (TLS) on all connections, encryption of data stored on our servers, 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, the passwords of Apple and Google accounts never being passed to us with Sign in with Apple and Sign in with Google, separation of family profiles so that only invited family members can access them, limiting access by our staff and service providers to what is 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, misuse detection and regular backups. We review these measures regularly, taking into account the risks posed by special categories of data such as health data. If a personal data breach occurs, we notify the competent supervisory authority and the people affected where the GDPR requires it (Articles 33 and 34 GDPR).
Push notifications may appear on your device's lock screen; you can choose in your device settings whether notification content is shown on the lock screen.
15. Children
Bebemo is intended for parents and families. Accounts are only for people aged 18 or over (adults), and children cannot create accounts; because we do not offer Bebemo directly to children, the consent rules in Article 8 GDPR for information society services offered directly to children do not apply. Data about children is entered by a parent or legal guardian or by family members they invite; you give the explicit consent for health data about your child (Section 7) and exercise your child's rights on their behalf (Section 11). Once your child becomes an adult, they can also exercise their rights concerning data about them themselves. 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 your child is built. If we learn that a minor has created an account, we delete the account and the related data; if you become aware of such a case, please let us know at legal@mobiza.com.tr.
16. Right to Lodge a Complaint
If you believe that we process your or your child's personal data in breach of the GDPR, you can lodge a complaint with the supervisory authority of the EEA country of your habitual residence, your place of work or the place of the alleged infringement. The contact details of all EEA supervisory authorities are available in the list of members of the European Data Protection Board. You also have the right to an effective judicial remedy (Article 79 GDPR). We would welcome the chance for us or our representative in the European Union (Section 2) to address your concern first, so please feel free to contact us at legal@mobiza.com.tr; this is not a precondition for a complaint.
17. Additional Information for People in Switzerland
17.1. Applicable Law and Contact
For people in Switzerland, our processing is subject to the FADP, in force since 1 September 2023, and to the Data Protection Ordinance ("DPO"). This Notice provides the information required by Article 19 FADP; the sections above also apply to you, with the additions in this section. We process your personal data in accordance with the principles in Article 6 FADP (lawfulness, good faith, proportionality, purpose limitation and transparency). Where a justification is required, we rely on your consent, on our overriding private interests, which correspond to the legitimate interests described in Section 5.1, or on the law (Article 31 FADP). Your and your child's health data is sensitive personal data within the meaning of Article 5(c) FADP; we process it on the basis of your express consent in accordance with Article 6(7) FADP (Section 7). Storing information on your device and reading it is also subject to Article 45c of the Telecommunications Act (Section 13).
Article 14 FADP requires controllers established abroad that offer goods or services to people in Switzerland or monitor their behavior to designate a representative in Switzerland where certain conditions are met cumulatively. The Bebemo app is not offered in the app stores in Switzerland and we do not offer services directed at Switzerland; for this reason no representative has been designated in Switzerland. This Notice still applies to people who visit our website, or who get the app with a store account from another country and use it in Switzerland. If the conditions are met in the future, we will publish the contact details of the representative we designate in this section. You can contact us directly about any matter concerning your personal data at legal@mobiza.com.tr.
17.2. Disclosure Abroad
Your personal data is processed in Türkiye, where we are established, is hosted on servers located in Türkiye (Bursa), and may be disclosed to our service providers listed in Section 8. Türkiye is not on the list of states with an adequate level of data protection in Annex 1 to the DPO; the EEA states and the United Kingdom are. For disclosures to recipients in states without an adequate level of protection, we rely, for certified recipients in the United States, on the Swiss-U.S. Data Privacy Framework, recognized by the Federal Council with effect from 15 September 2024, and otherwise on the standard contractual clauses of the European Commission recognized by the Federal Data Protection and Information Commissioner ("FDPIC"), with the adaptations required for Switzerland (Article 16(2)(d) FADP). Transfers of data passed to advertising partners for the ads in the free version are described in Section 9; Singapore is not on the list in Annex 1 to the DPO either. You can request a copy of these safeguards at legal@mobiza.com.tr.
17.3. Your Rights in Switzerland
Under the FADP, you have the right:
- to request information on whether we process personal data about you and, if so, which data (Article 25 FADP); we provide this information free of charge, as a rule within 30 days, and if we cannot do so within 30 days, we tell you within that period when you will receive it,
- to receive the personal data you have disclosed to us in a commonly used electronic format, or to have it transferred to another controller (Article 28 FADP),
- to request the rectification of inaccurate personal data (Article 32(1) FADP), and to request that processing be stopped, that data not be disclosed to third parties, or that data be deleted or destroyed (Article 32(2) FADP),
- to withdraw your consent at any time with effect for the future.
For data about your child, you exercise these rights on your child's behalf as the child's parent or legal guardian.
We do not take automated individual decisions within the meaning of Article 21 FADP; the automated check of Community posts is not such a decision either, and you can ask for a check decision to be reviewed by a person (Section 12). If you believe that we process your personal data unlawfully, you can report this to the FDPIC, which can open an investigation (Article 49 FADP), and you can bring your claims before the civil courts (Article 32 FADP). We would welcome the chance to address your concern first at legal@mobiza.com.tr.
18. Changes to This Notice
We may update this Notice if the law, our app 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 by an in-app notification or by email. If a change extends the scope of processing based on your consent, we will ask for your consent again for that processing.
19. 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