Privacy policy

In short: sound and picture from the nursery are end-to-end encrypted; we can neither see nor hear them, and none of it is stored on a server. The website sets no cookies and has no tracking. So that the app can alert you, our server processes some data about your devices and about when a monitor is listening. Which data, is listed below.

Controller

This website

Visiting the pages

When you visit babyfino.eu, the servers involved process technically necessary data: your IP address, the time, the address requested, your browser’s identifier and the amount of data transferred. We use it to deliver the pages, find errors and fend off attacks – also automatically. Access logs are kept only as long as that requires and are not combined with other data. The legal basis is our legitimate interest in a secure, working website (Art. 6(1)(f) GDPR).

No cookies, no tracking

The website sets no cookies, uses no analytics or advertising services and loads nothing from other servers – fonts and images come from babyfino.eu itself. We see how often our pages appear in Google search in Google Search Console; no data is collected on this website for that.

The Babyfino app

Babyfino needs no account, no e-mail address and no adult’s name on our server. Each device signs in with a key it creates itself.

What our server stores

• Devices: an identifier, the public key, the platform (iOS or Android), the role (baby monitor, parent or babysitter), the family, the language for notifications, whether the end of monitoring wakes a parent’s phone like an alarm and, where it happened, the time a device was removed from the family. A babysitter’s phone is removed this way as soon as the evening ends, after 24 hours at the latest.
• Memberships: which devices belong to a family, with the keys they confirmed it with, for a babysitter with the end of the access.
• Push token: the address through which Apple or Google deliver notifications to your device. Deleted as soon as the platform reports it is no longer valid.
• Active monitoring: when a monitor started listening, its last sign of life, whether it failed, when it last alarmed for a noise and which phone said “I’m going”. Deleted as soon as the listening ends.
• Active sleep companion: who is with which child, how often it checks in, the last answer and since when it is missing. Deleted as soon as the sleep companion ends.
• Live Activity on iPhone: which parent phone shows which child’s state on the lock screen, with the token for it. Deleted when the display ends.
• Encrypted content: your children’s names and whether alarms reach your phones, encrypted for each receiving device. Our server cannot read them.
• Notification jobs: which kind of notification goes to which device. Deleted after they are sent.
• Sign-in attempts: a one-time challenge to sign. Deleted one hour after it expires.

Devices and memberships are kept as long as they belong to your family. Write to [email protected] if you want us to delete them.

What our server never receives

Sound and picture, excerpts of them and anything derived from them travel end-to-end encrypted directly between your devices or through a relay (TURN) that forwards only encrypted packets. The relay sees the devices’ IP addresses and how much data flows, not the content. Your evening’s history and the loudness in the room stay on your phones and in no backup – for one, seven or 30 days as set, on the baby’s phone for seven days. Your alarm threshold, and whether it follows the room, stays on your devices too.

To hear it again, the baby’s phone keeps the sound of each noise alarm, as long as your history, and the last 30 minutes in memory while it listens – on the baby’s phone only and in no backup. Your phones fetch both end-to-end encrypted directly from there, play them and keep nothing; an iPhone keeps only the four seconds up to the last alarm that its notification plays, until the next alarm. When the baby’s phone is removed from the family or set up anew, it deletes every recording.

Notifications through Apple and Google

Our server sends alarms and notices through the Apple Push Notification service (Apple Inc., USA) and Firebase Cloud Messaging (Google LLC, USA). These services receive the push token, a generic notification text and technical identifiers, but never your child’s name – our server doesn’t know it either.

Legal basis

We process this data to provide the app you use (Art. 6(1)(b) GDPR) and to run it securely (Art. 6(1)(f) GDPR).

Service providers

• Hetzner Online GmbH (Gunzenhausen, Germany) runs the servers for the website, the app server, the database and the relay, in data centres in the EU.
• Cloudflare, Inc. (USA) forwards the connections to the website and the app server and protects them against attacks. In doing so, Cloudflare decrypts the connection to the app server and sees the control data: which devices form a family, when a monitor starts and stops listening, and when an alarm happens. Sound and picture never pass through Cloudflare. Cloudflare is certified under the EU-US Data Privacy Framework.
• Apple Inc. and Google LLC (USA) deliver notifications as described above and distribute the app through their stores under their own privacy policies.

When you write to us

We use your e-mail address and message only to answer you (Art. 6(1)(f) GDPR) and delete them when they are no longer needed for that.

Your rights

You have the right to access, rectify and erase your data, to restrict processing, to object and to data portability. You can also lodge a complaint with a supervisory authority, for example the one responsible for us: Die Landesbeauftragte für den Datenschutz Niedersachsen, Prinzenstraße 5, 30159 Hannover, Germany.