Privacy Policy

Effective date: 23 July 2026 · Last updated: 23 July 2026

Dozeling turns two phones into a private baby monitor: one phone stays by the crib (the baby unit) and streams sound to the other phone (the parent unit), 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 short version

🔒 Live audio is end-to-end encrypted and peer-to-peer. It travels directly between your two phones (DTLS-SRTP). We never receive, record, or store it.
🧠 Cry detection runs entirely on the baby phone. No sound leaves the device to decide whether your baby is crying.
🙅 No accounts, no ads, no tracking, no data selling. We don't ask for your name, email, or phone number, and we run no advertising or profiling SDKs.
🗑️ You can erase your data at any time by un-pairing the phones or uninstalling the app.

Who we are

Dozeling is an independent app. For any privacy question or request, contact us at molczykappz@gmail.com.

What data Dozeling handles, and why

1. Live room audio — not collected by us

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, not recorded, and not stored anywhere by Dozeling.

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.

2. Pairing information — to connect your two phones

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.

3. Connection setup data — transient

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.

4. A wake-up token (FCM) — to alert you

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.

5. An anonymous device identifier

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.

6. On-device only — never leaves your phone

Cry / noise detection is computed locally on the baby phone.
The "Last night" report (monitoring duration, alerts, reconnects, battery) is stored only on the baby phone.
Camera use (scanning the pairing QR code) is processed on-device and never uploaded.

What we do not do

We do not record or store your baby's audio.
We do not listen to your stream — it is encrypted and peer-to-peer.
We do not sell or rent your data to anyone.
We do not show ads or use advertising identifiers.
We do not collect your name, email address, phone number, contacts, or precise location.

Permissions and why they're needed

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.
Camera (parent phone)	Only to scan the pairing QR code. Processed on-device, never uploaded. You can skip it and type the code instead.
Notifications	To alert you — including waking the screen — when your baby cries.
Run without battery restrictions	So monitoring survives the whole night instead of being shut down to save power. Optional.
Internet	To connect your two phones over the network.

Where your data is processed

Dozeling uses a small number of infrastructure providers that process data on our behalf:

Google Firebase (Firestore, Authentication, Cloud Messaging) — pairing, connection setup, anonymous device id, and wake-up push.
A TURN relay provider — relays encrypted audio packets only when a direct phone-to-phone connection isn't possible.
Cloudflare — hosts our lightweight alert service that forwards a cry signal (no audio) to wake the parent phone.

We do not transfer your data to any other third parties.

Data retention and deletion

Live audio: never stored.
Pairing / connection data: short-lived; removed when pairing completes, expires, or when you un-pair.
Wake-up token & anonymous device id: kept while your devices are paired so alerts can reach you.
On-device data (reports, settings): removed when you uninstall the app or clear its data.

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 molczykappz@gmail.com — we will delete it promptly.

Children's privacy

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.

Security

Live audio is encrypted end-to-end (DTLS-SRTP) between your phones.
Backend access is scoped by your pairing secret and an anonymous, per-device identity.
We minimize what we handle: no accounts, no audio storage, no profiling.

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.

Changes to this policy

We may update this policy as the app evolves. Material changes will be reflected here with a new "Last updated" date.

Contact

Questions or requests about your privacy: molczykappz@gmail.com