Privacy Policy
Last updated: November 18, 2026
This Privacy Policy applies to the mobile application published by Abdulkadir Aktaş, trading as ProtonMob, under the store name Baby Lullabies & White Noise and localized names including Bebek Ninnileri (internetsiz) and Nanas para bebés (the “App”). It explains what information is collected when you use the App, how it is used, and the choices you have.
1. Who we are
The App is developed and published by Abdulkadir Aktaş (trading as ProtonMob; “we”, “us”) — the developer named on the App’s store listings. It is distributed as:
- Google Play — Bebek Ninnileri (internetsiz),
package
com.erbasaran.bebekninnileri, developer Abdulkadir Aktaş. - App Store — bundle identifier
info.Bebek-Ninnileri, seller Abdulkadir Aktaş.
If you have any questions about this policy or your data, contact us at [email protected].
2. Information we collect
The App does not require an account, and we do not ask for your email address, phone number or any other contact details. The App collects a limited amount of information, described below, through the third-party services listed in section 4:
- Setup answers — when you set the App up it asks a few questions to personalise it: your child’s gender and first name, your relationship to the child, your own first name, and your age range. The names can be left empty. These answers are stored on your device, and they are also sent to our analytics providers (Google Firebase, and Amplitude where it is running) as usage properties, so we can understand who uses the App.
- Usage and diagnostics data — anonymous app events (for example which sounds are played), device model, operating system version, app version, language, country, and crash reports. Collected via Google Firebase (Analytics, Crashlytics, Remote Config).
- Purchase information — if you buy a subscription, an anonymous user identifier and store receipt information are processed by RevenueCat to manage your subscription. Payment itself is handled entirely by the app store you purchased from; we never see your payment details.
- Advertising data — on iPhone and iPad the free version of the App shows ads served by Google AdMob. AdMob may process device information and, only if you allow it through Apple’s App Tracking Transparency prompt, the device advertising identifier (IDFA). If you decline, you will still see ads, but they will not be personalized using cross-app tracking. The Android app shows no ads and does not collect the Android advertising ID.
- Ad measurement data (Meta) — we advertise the App on Facebook and Instagram, and the App includes Meta’s SDK so we can tell whether those ads lead to installs and subscriptions. When the App is opened, the SDK tells Meta that the App was installed and opened, together with an anonymous identifier the SDK creates, the device model, operating system and app version, language, time zone and IP address. If you start a trial or a subscription, RevenueCat reports that event to Meta with the same anonymous identifier. On iPhone and iPad the device advertising identifier (IDFA) is shared with Meta only if you allow tracking in Apple’s App Tracking Transparency prompt. The Android app never collects or sends the Android advertising ID, and on Android the Meta SDK is not started at all unless the age answer described in section 5 indicates an adult (18 or older).
3. How we use information
- To operate the App and deliver its content (lullabies, white noise, sleep sounds).
- To manage subscriptions and unlock premium features you have purchased.
- To understand how the App is used so we can improve it.
- To find and fix crashes and technical problems.
- To show ads in the free version on iPhone and iPad.
- To personalise the App with the names and answers you give during setup.
- To measure whether our ads on Facebook and Instagram lead to installs and subscriptions.
We do not sell your personal information, and we do not use it for any purpose other than those listed above.
4. Third-party services
The services below process data on our behalf. Their own privacy policies apply to the data they handle:
- Google Firebase & AdMob — policies.google.com/privacy
- RevenueCat — revenuecat.com/privacy
- Amplitude — amplitude.com/privacy
- Meta (Facebook SDK) — facebook.com/privacy/policy
- Apple App Store — apple.com/legal/privacy
- Google Play — policies.google.com/privacy
5. Children’s privacy
The App plays lullabies and sleep sounds and is offered to a general audience that includes children. It is normally operated by a parent or caregiver, but we do not assume that, so on Android the App asks for an age during setup, before any ad measurement starts.
The age question (Android)
During setup the Android app asks for your age range; installs that skipped setup see a screen that asks for the year you were born instead. No answer is pre-selected and no answer unlocks more of the App. The answer is stored on your device. The age range chosen during setup is also sent to our analytics providers as a usage property, as described in section 2; a birth year entered on the separate screen stays on your device. The answer decides which analytics and ad-measurement behaviour applies to that device.
If the answer indicates a child under 13
For that device we treat the session as child-directed under the U.S. Children’s Online Privacy Protection Act (COPPA) and Google Play’s Families policy. In that mode:
- The Android app shows no ads, so no ad request is made.
- The device advertising identifier is not collected or transmitted, and no advertising consent signals are granted.
- Our product-analytics provider (Amplitude) is not started at all, so no behavioural analytics and no device identifiers are sent to it.
- Meta’s SDK is not started at all, so nothing is sent to Meta.
- We keep only crash diagnostics, basic app events and the setup answers described in section 2, sent to Google Firebase with a random installation identifier we generate ourselves — not an advertising identifier.
The App is set up by a parent or caregiver. Beyond the setup answers described above, we do not ask for an email address, photo, location, or any other contact detail, and the App has no social features, no messaging, and no user-generated content.
If the answer indicates a person under 18
Meta’s SDK is not started and no advertising identifiers are used. Where the EU General Data Protection Regulation (GDPR) applies, the age of digital consent ranges from 13 to 16 depending on the country; treating everyone under 18 this way covers the highest of these.
Parents and guardians
If you believe a child has provided us with personal information, or you want the answer on a device changed or erased, contact us at [email protected] and we will act on it. Clearing the App’s data in your device settings also erases the stored answer, and the App will ask again the next time it opens.
6. Data retention and security
Analytics and diagnostics data are retained by the services above for limited periods defined by their policies and are stored on secure infrastructure. We only have access to aggregated or pseudonymous data; we cannot directly identify you from it.
7. Your choices and rights
- Tracking — on iPhone and iPad you can allow or deny tracking at any time under Settings > Privacy & Security > Tracking. The Android app does not use the advertising ID.
- Personalized ads — you can limit ad personalization in your device settings.
- Deletion — you can request deletion of data associated with your device by contacting us at the email address below.
Depending on where you live (for example the EU/EEA, UK, or California), you may have additional rights such as access, correction, and objection. To exercise them, contact us.
8. Changes to this policy
We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated date above.
9. Contact
Abdulkadir Aktaş (ProtonMob) — [email protected]