BabyLinkPre-release version: the current test candidate works with two phones on the same Wi-Fi only. Remote services and purchases described below are not enabled in it; saving short sound clips on the phone is available and off by default. Support is handled through the contact address at the end of this page.
Effective 1 September 2026
Privacy policy
BabyLink is built to minimise data before it is collected. Core sound detection runs on the Baby Phone, and the BabyLink backend does not accept nursery audio or video.
Data kept on your phone
App settings, trusted-device records, monitoring events and optional short audio clips are stored in the app-private area of your phone. Clip retention is off by default.
Data used for local monitoring
Audio level measurement and sound-event detection happen on the Baby Phone. Raw microphone audio is not sent to BabyLink servers. Requested Live Audio travels over an encrypted WebRTC connection between the phones.
Optional remote services
If you enable remote alerts, BabyLink may process a device identifier, public key, family membership, push token, room name, event type and event time. Firebase or Apple may deliver the notification under their own terms. Audio is not included.
Purchases
The app stores subscription entitlement and transaction identifiers needed to verify a purchase. Payment details are handled by Google Play or Apple and are not received by BabyLink.
Deletion and retention
Delete all local data is available in the Privacy screen. Disabling remote alerts unregisters the push route when connectivity permits. Short-lived pairing and presence data expire automatically.
Children and sensitive data
BabyLink is a tool for adults supervising a child. It is not intended for a child to create an account, and it does not perform face, speech, emotion, health or sleep analysis.
Security and changes
Device authentication uses cryptographic keys stored by the operating system. No service can promise absolute security. Material policy changes will be dated on this page.