Polityka prywatności Babyphone

Ostatnia aktualizacja: 22 października 2026

Niniejsza polityka prywatności dotyczy aplikacji Babyphone wydanej przez MAVSAM LABS.

Data the app accesses or collects

Microphone: on the Baby phone, the microphone captures sound while a Parent phone is connected, to send it live to that Parent phone. On the Parent phone, the microphone is used only while "Talk to the baby" is on. Monitoring keeps running in the background through a foreground service, shown by a permanent notification with a Stop button.

Sound detection: the Baby phone measures the sound volume. When a sound stays above a threshold for at least half a second, it sends the Parent phone an alert containing only the time and the sound level. This is not cry recognition.

Camera, movement detection: on the Baby phone, if you grant the camera permission, Babyphone analyses camera images on the phone itself to detect movement. The detector works in memory on a reduced 32 × 24 brightness grid. Images are not sent to the Parent phone: a movement alert only contains the time of detection and an activity score.

Camera, live video (Premium): when the Parent phone has Premium, opens the video screen and taps Start, the rear camera of the Baby phone streams live video to the Parent phone, at 320 × 240, 640 × 480 or 1280 × 720 and 5, 10 or 15 frames per second. This video session carries no sound and stops when the Parent phone leaves the video screen.

Camera, pairing: on the Parent phone, the camera is used to scan the pairing QR code. The code is read on the phone by Google ML Kit, whose model is included in the app; camera images are not sent.

Battery: the Baby phone reads its battery level and sends the percentage to the Parent phone when it changes.

Local network: to build the pairing QR code, the Baby phone reads its local network addresses.

Babyphone does not ask for an account, a name, an email address, contacts or a location, and does not record audio or video.

Android permissions: microphone and audio settings (RECORD_AUDIO, MODIFY_AUDIO_SETTINGS) for listening and "Talk to the baby"; camera (CAMERA) for movement detection, live video and QR code scanning; network (INTERNET, ACCESS_NETWORK_STATE) for the connection between the phones, ads and purchases; notifications, foreground service, wake lock and vibration (POST_NOTIFICATIONS, FOREGROUND_SERVICE with the microphone, camera and media playback types, WAKE_LOCK, VIBRATE) to keep monitoring running in the background and show alerts; Google Play purchases (BILLING); Bluetooth (BLUETOOTH, Android 11 and earlier only), added by the WebRTC audio component for Bluetooth audio devices.

The Google Mobile Ads SDK adds the advertising ID permission (AD_ID) and access to Android's advertising APIs (ACCESS_ADSERVICES_AD_ID, ACCESS_ADSERVICES_ATTRIBUTION, ACCESS_ADSERVICES_TOPICS). You can reset or delete your advertising ID in Android's settings.

How the data is used

Sound is used only to let the Parent phone listen to the baby and, with "Talk to the baby", to let the baby hear the parent.

Camera images are used only to detect movement on the Baby phone and, during a Premium video session started from the Parent phone, to show live video on the Parent phone.

Alerts, battery level and monitoring status are used only to show information and local notifications on the Parent phone.

Ads: the Google Mobile Ads SDK shows a banner on the home screen and on the Parent phone's screens. No ad is shown on the Baby phone's monitoring screen.

From version 0.8.0, where required, for example in the European Economic Area, the United Kingdom and Switzerland, a Google consent form is shown before any ad is loaded. If you refuse personalised ads, Google shows non-personalised or limited ads instead; this never blocks monitoring. You can change your choice at any time with the "Ad privacy choices" button under the Premium offer, when this option is offered in your region.

The Premium purchase removes the ads and unlocks live video. With Premium, no ad and no consent form are shown.

Sharing with third parties and SDKs

Audio, video, alerts and battery level go directly between your two phones over your local network: the phones connect through local WebSocket signalling and WebRTC, with no server, ours or anyone else's, to relay or store them.

Ads are served by Google AdMob (Google Mobile Ads SDK), provided by Google LLC, which processes data under its own policies: https://policies.google.com/privacy and https://support.google.com/admob/answer/6128543.

The Premium purchase is processed by Google Play under the Google Play Terms of Service and Google's Privacy Policy. The app only receives the status of the purchase and never sees your payment details.

The QR code scanner uses Google ML Kit. ML Kit sends Google diagnostic and usage data (device and app information, performance metrics, error codes and a per-installation identifier), but not the camera images: https://developers.google.com/ml-kit/android-data-disclosure.

Apart from these Google components, Babyphone contains no analytics, crash reporting or Firebase SDK.

Bezpieczeństwo

Pairing uses a QR code holding a random 256-bit key. For the first connection the QR code expires after 10 minutes; once paired, the same key lets the two phones reconnect until monitoring is stopped.

The two phones prove they know this key without sending it over the network, and every control message is signed with it: altered or unsigned messages are rejected. Only one Parent phone can be connected at a time.

The audio and video exchanged between the two phones are encrypted (WebRTC, DTLS-SRTP).

Control messages (connection setup, alerts, battery level) are signed but not encrypted: another device on the same local network could read them. Use Babyphone on a network you trust.

Retention and deletion

Babyphone does not record or store sound, camera images or videos. When a video session ends, the camera is stopped and released.

While monitoring runs, the app keeps on the phone its role (Baby or Parent), the pairing information (key, local network addresses, expiry) and whether camera detection is on, so that monitoring can continue in the background. They are deleted when you stop monitoring from the app.

If monitoring ends another way (Stop button of the notification, app closed by the system, crash), some of this information can stay on the phone until the next monitoring session replaces it. It is not used outside a monitoring session.

Alerts, battery level and Premium status are not stored: the Premium status is checked again with Google Play each time the app starts. Uninstalling the app deletes all its data from the phone.

From version 0.8.0, the app's data is excluded from Android backup and from transfer to a new phone: it never leaves the phone that created it.

MAVSAM LABS runs no server and receives no data from the app. Data processed by Google is kept and deleted under Google's policies.

Children

Babyphone is intended for parents and other adults, not for children. It does not ask anyone, child or adult, for personal information.

Sound and movement near the baby are analysed on the Baby phone and shown only on the paired Parent phone.

Changes to this policy

We will update this page whenever the app's data practices change, and change the date of the last update shown at the top of this page.

← Babyphone

Kontakt

Pytania, współpraca lub prasa: napisz do nas.

mavsamlabs@free.fr