Baby Cam Live
Privacy policy
Last updated: October 10, 2026
Baby Cam Live lets you use one phone as a Camera and other phones as Viewers. This policy explains what data the app uses, why, where it goes, and what happens when you delete your account.
What data we use
• Account: an anonymous or Google-linked account identifier; if you choose Google sign-in, the app receives the email address and name from your Google profile. Sign-in is anonymous or through Google; the app does not offer email-and-password sign-in. • Profile: your display name and, optionally, a profile-photo URL from Google or a photo uploaded from Settings. • Devices: the app's device identifier on the phone, phone name, platform, role (Camera or Viewer), online status and, for a Camera, battery level and state. • Pairing and operation: pairing links and requests, live-session status and timestamps, and access-change events. • Security: the IP address of pairing attempts, used to limit abuse.
Video and sound
Live video and audio travel between a Camera and an authorized Viewer over WebRTC, protected by DTLS-SRTP. If a TURN relay server is used, it forwards encrypted packets; the app does not store the live stream on its servers. On Android 10 or later, a Viewer can save a snapshot and an MP4 recording that may include the selected Camera audio played on the phone. If Viewer audio is muted, the clip has no sound. Recordings and snapshots are saved only locally in the gallery and are not uploaded by the app. On Android 9 and earlier, the app currently does not offer these save controls. The phone gallery may be synced by the user or operating system to photo services; that sync is controlled by the phone and the relevant service. Deleting the account does not delete files saved on the phone or synced copies. Cry recognition runs only on the phone used as the Camera, in the app's temporary memory. The samples and scores are not saved or sent by this analysis; live audio may still be streamed to connected Viewers as part of the monitoring feature.
Why we use data
We use data for sign-in, device registration, pairing and approving Viewers, showing Camera status, connecting the live stream and protecting the service against abuse. Alerts are local notifications on the Viewer phone: battery and Camera-offline alerts work only while the Viewer app is running, and sound alerts only while the Viewer is connected to the Camera. For sound alerts, the Camera sends connected, authorized Viewers, through the real-time signaling service (Supabase Realtime), only the alert state and its type (loud sound or crying); audio samples and analysis scores are not sent. There are no push notifications when the app is closed.
Where data is stored and who processes it
Supabase hosts the account and operational data. A profile photo received from Google is used as the address from the Google profile. A photo uploaded in Settings is stored privately at Supabase, in a space only your account can access; the app shows it through temporary links valid for one hour. Google provides Google sign-in. To set up a direct connection, the app contacts Google’s public STUN server, which sees the phone’s public IP address and port at connection time but never receives the image or sound. If a direct connection is not possible, DTLS-SRTP-encrypted media is relayed through the operator’s TURN server and is not stored.
How long we keep data
Account data and registered devices are kept while the account exists. Pairing attempts and their associated IP addresses are targeted for deletion after 7 days. Expired pairing requests, ended or expired sessions and inactive access events are targeted for deletion after 30 days. Automatic cleanup runs daily, so these thresholds may be exceeded by about one day. Active Cameras may keep session records until the Camera has not been seen for 30 days, followed by the next cleanup run. These are thresholds for the app's database records; providers have separate rules for their own technical logs and backups, which the app does not control. Signaling messages between the Camera and the Viewer (connection setup, including IP addresses and ports, Camera, battery and sound-alert status) go through Supabase Realtime, which keeps them automatically for 3 to 4 days and then deletes them; they never contain the image or sound. Deleting the account does not remove them immediately: they disappear automatically within that period.
Deleting data and your rights
You can start deleting your account from Settings → Delete account permanently. The server first marks the account as being deleted (no new photos are accepted), deletes all uploaded profile photos, verifies the deletion and only then deletes the account together with its devices, pairings and sessions. If a step fails, the account is not deleted and the deletion can be retried. Deleting the account does not remove snapshots, recordings or synced copies on the phone. Under the GDPR you have the right of access, rectification, erasure, restriction, portability and objection, and the right to lodge a complaint with a data protection authority (in Romania, ANSPDCP).
Children
The app is intended for adults monitoring a space. A Camera can transmit images and sound from the monitored area, including images or sound of children; the adult user controls Camera placement and Viewer access. The app does not store the live stream on its servers, and recordings saved by a Viewer may include audio from the selected Camera played on the phone.
Security
Connections to services use HTTPS/TLS, and live media is protected by WebRTC DTLS-SRTP. An account — anonymous or Google-linked — owns the devices registered to it. A Viewer signed into the same account can access that account's Cameras without individual approval; a Viewer on another account must send a pairing request that the Camera approves. Unpairing removes the Camera–Viewer pairing and access based on it, but devices on the same account keep owner access. Removing a device deletes its registration and pairings; if the app on that phone remains signed in and is used, the phone may register again. After a Viewer signs out or is removed, the Camera closes the connection at its next check, about 30 seconds later; if the service cannot be reached at all, an already authorized connection can continue for up to about 5 minutes.
Changes
If this policy changes, the new version appears in the app with its update date.
Contact
For questions about your data or to exercise your rights, write to contact@asapps.eu.
Who is responsible
The operator is the publisher named on the Baby Cam Live Google Play page: asapps.