Effective date: 23 July 2026 · Last updated: 11 October 2026
Dozeling turns two phones into a private baby monitor: one phone stays by the crib (the baby unit, an Android phone or an iPhone) and streams sound to the other phone (the parent unit — Android or iPhone), which alerts you when your baby cries.
This policy explains, in plain language, what data Dozeling handles and what it deliberately does not. Our guiding principle: your baby's sound is yours. It streams directly between your two phones and is never stored on, or listened to by, our servers. The only recording is five seconds of sound around an alert, kept on your phones (section 1).
Dozeling is an independent app. For any privacy question or request, contact us at [email protected].
The baby phone captures microphone audio and streams it to the parent phone over an encrypted peer-to-peer connection (WebRTC, DTLS-SRTP). The audio goes directly between your two devices. It is not sent to us, and the live stream is not recorded.
The one recording: five seconds around an alert. The picture from the camera is never recorded. The only recording Dozeling makes is the five seconds of sound around an alert, so you can hear what set it off. The baby phone saves it and sends it to the parent phone over the same encrypted phone-to-phone link as the live sound. Each phone keeps only the last five clips, in the app's private storage, and every new alert deletes the oldest. Clips are never sent to us — not to our servers, not to Firebase, not to our alert service. They are deleted when you uninstall Dozeling or clear its data. The clips are excluded from device backups on both iPhone and Android. Android versions before 2.37.0 could include them in your phone's own Google backup, which belongs to your Google account and which we never receive — updating the app stops that.
When the two phones cannot reach each other directly (for example behind certain home routers), the encrypted stream may be relayed through a TURN server so the connection can be established. The relay only forwards encrypted packets — it cannot decrypt, listen to, or store the audio, and we do not keep the relayed content.
To link your phones, the baby phone generates a short one-time pairing code (a session id and a random secret). This is stored temporarily in our signaling backend (Google Firebase Firestore) so the parent phone can find and confirm the pairing. Pairing records are short-lived and are removed when pairing completes or expires.
To open the peer-to-peer audio link, the phones briefly exchange technical connection details (WebRTC "SDP" offers/answers and network "ICE" candidates) through the same signaling backend. This is transient technical data used only to connect the call; it contains no audio and no personal profile information.
So a cry can wake the parent phone even if the app was closed by the system, the parent phone registers a push token (Firebase Cloud Messaging) that is stored with your pairing. When the baby phone detects noise, a small signal (no audio) is sent — via our alert service — to wake the parent phone and prompt you to listen.
Each install signs in with anonymous Firebase Authentication. This gives the device an anonymous id used only to secure your pairing on the backend. It is not an account: there is no email, password, name, or profile, and we cannot use it to identify you personally.
Premium follows the Google account that bought it, so if your two phones use the same Google account, everything works and you never meet this section.
If they use different ones — a partner's phone, an old handset still signed in to somebody else — the phone by the cot has no way to know you paid. Signing in to a Dozeling account on both phones is the way to tell it.
You can sign in with Google or with Sign in with Apple. If you create an account, we store the email address the sign-in provider gives us (with Apple's Hide My Email that is the private relay address Apple creates for you, of the form [email protected] — we never see your real address), the display name the provider shares, if any, and the fact that you have an active subscription. Nothing else. No phone number, no profile, and nothing about your baby or your nights.
Deliberately smaller than the alternative: signing your Google account into a phone that lives in a nursery would give that phone your mail, your photos and your contacts. A Dozeling account gives it Dozeling.
You can delete the account and everything in it at any time.
Google Play or the App Store handles the payment; we never see your card. To let the phone by the cot know that premium is active, the phone that bought it sends our server proof of the purchase — on Android the purchase token Play issued, which our server checks with Google; on iPhone the transaction Apple signed, whose signature our server checks against Apple's certificate. We keep the answer — active or not, and until when — and nothing else about the transaction.
A baby monitor that dies at 3 a.m. and leaves no trace is the failure we most need to see, so Dozeling reports its own crashes.
What is sent, and when. Only when the app actually crashes. The report describes the failure: the stack trace (where in our code it broke), your phone model, your Android or iOS version, the app version, and how long the app had been running. No crash report is sent while the app is working normally.
What is never in it. The sound from the room. Your baby's name or the names you gave your phones. Any recording, clip, or video. Your email address, your pairing secret, or your session history. A crash report describes a failure, not how you use the app; what we learn about use comes only from the usage statistics in section 8.
Who processes it. Google Firebase Crashlytics, acting as a processor on our behalf, under the same terms as the rest of our Firebase use (see Where your data is processed).
Turning it off. Settings → Diagnostics — the same switch that turns off the usage statistics in section 8. See section 8 for how it works and on which phone it is.
Crash reports tell us when the app breaks. They cannot tell us whether a night of monitoring happened at all, whether the sound reached the parent phone, or whether anyone comes back the next evening. For that, Dozeling sends a short, fixed list of named events to Google Firebase Analytics.
What is sent. Only events from this list — the app has no way to send any other:
What comes with each event. Firebase Analytics attaches a random app-instance identifier, created when the app is installed and different on every install, together with basic technical context: phone model, operating-system version, app version, language, and an approximate country or region that Google derives from the network address (Google Analytics does not keep the address itself). The library also records a few events of its own — the first time the app is opened, the start of a session and how long the app was in use, app and system updates. We have switched off its automatic screen tracking.
Not anonymous, and not used to identify you. Because the identifier belongs to your install, these statistics are linked to that install, and we describe them that way in the App Store and Google Play. We never attach your name, email address, account, or anything about your baby to them, and we do not use them to work out who you are.
What is never in it. The room's sound or any picture from the camera. Any recording or clip. Your baby's name or the names you gave your phones. Your email address, your pairing code, or your session history. Your precise location. Any advertising identifier: on Android the advertising-ID permission is removed from the app, and on iPhone we use the edition of Firebase Analytics that does not include the advertising identifier (IDFA).
Why. To learn whether Dozeling works through the night for real families — whether pairing succeeds, how long the sound takes to arrive, whether monitoring lasts until morning — whether people come back to it, and whether the Premium offer makes sense to anyone. Not for advertising, not to profile you, and never sold or shared.
Who processes it. Google Firebase Analytics, acting as a processor on our behalf, under the same terms as the rest of our Firebase use.
How long it is kept. Google Analytics deletes individual events after the retention period set on our account, which is never longer than 14 months. What remains after that are totals (for example, “nights monitored last week”) that do not point to any install.
Turning it off. Settings → Diagnostics, on the parent phone and on the phone by the cot — each phone has its own switch and keeps its own choice. It is one switch for both crash reports and usage statistics, and it is on unless you turn it off. The app starts with collection off and switches it on only after reading your choice, so a phone where you turned it off sends nothing even at start-up. Switching it off takes effect immediately, not at the next restart, and it stays off until you turn it back on. In versions before 2.37.0 the phone by the cot has no such switch and sends crash reports and the start and end of monitoring; updating the app adds it.
| Permission | Why |
|---|---|
| Microphone (baby phone) | To capture and stream the room's sound. You start monitoring yourself each time; the app never turns on the microphone by itself. |
| Microphone (parent phone) | Only while you hold Talk, so your voice reaches the baby phone. Nothing is recorded, and outside that moment the parent phone's microphone stays off — on iPhone the microphone indicator shows you exactly when it is on. |
| Camera (parent phone) | Only to scan the pairing QR code. Processed on-device, never uploaded. You can skip it and type the code instead. |
| Camera (baby phone) | Optional, for the video preview (Premium). The camera is used only while you are looking into the room from the paired parent phone; the picture goes straight to your phone over the same encrypted phone-to-phone link as the sound, and is never recorded or sent to us. Monitor without video and Dozeling does not touch the camera. |
| Notifications | To alert you when your baby cries — on Android also by waking the screen; on iPhone as a normal or, if you turn it on, a Time Sensitive notification. |
| Local network (iPhone) | So the two phones can connect directly over your home Wi-Fi. Optional: without it the encrypted stream still works, through the relay. |
| Background audio (iPhone) | To keep the room's sound playing with the screen locked. It is the live room audio, not silence; if the link drops and cannot be restored within two minutes, monitoring stops and you are notified. |
| Run without battery restrictions (Android) | So monitoring survives the whole night instead of being shut down to save power. Optional. |
| Internet | To connect your two phones over the network. |
Dozeling uses a small number of infrastructure providers that process data on our behalf:
We do not transfer your data to any other third parties.
To erase your data: un-pair your devices in the app and/or uninstall Dozeling. To request deletion of any pairing data still held on our backend, email [email protected] — we will delete it promptly.
Dozeling is a tool for parents and caregivers (adults). It is not directed to children and is not intended for use by children under 13 (or the equivalent minimum age in your country). Although the app monitors a room where a baby may be present, that audio is treated as sensitive: it is processed on-device and streamed end-to-end encrypted directly between your own phones, and is never collected by us. We do not knowingly collect personal information from children.
No method of transmission or storage is 100% secure, but we design Dozeling to keep the most sensitive data — your baby's sound — off our servers entirely.
We may update this policy as the app evolves. Material changes will be reflected here with a new "Last updated" date.
Questions or requests about your privacy: [email protected]