Napwatch Privacy Policy

Napwatch turns two Apple devices into a baby monitor: one stays in the nursery as the camera, the other stays with you as the parent unit. This page explains what happens to data. The short version: the picture and sound of your home travel only between your own two devices, over your own Wi-Fi. There is no account and no Napwatch server.

1. Camera and microphone

On the device you put in the nursery, Napwatch uses the camera and the microphone, with your permission. The live picture and room sound are sent directly to the parent unit you paired, over your local network. They are encrypted end to end between the two devices (a key agreed during pairing, then ChaCha20-Poly1305). They never pass through a server of ours or anyone else's, and we cannot see or hear them.

The camera device also analyses the picture and the sound level on the device itself to decide when to alert you about movement or sound. Nothing about that analysis is sent anywhere except the alert to your own parent unit.

2. Local network

iOS asks for permission to use your local network. Napwatch needs it so the two devices can find each other on the same Wi-Fi (Bonjour) and connect. Napwatch does not scan for or connect to any other device on your network.

3. Clips, alerts and pairings

• Clips— if you turn on clip saving, short clips are stored on the camera device only. The parent unit can play them, and you can choose to save or share a clip with the iOS share sheet; that is your action, and Napwatch does not upload anything itself.
• Alert history— a list of recent movement and sound alerts is kept on the device.
• Pairings— the keys that let your devices recognise each other are stored in the iOS Keychain on each device.
• Notifications are local notifications created on your parent unit. No push server is involved.

Deleting Napwatch from a device removes its clips, alert history and settings.

4. Purchases and RevenueCat

Napwatch Plus is sold through Apple In-App Purchase. Apple handles the payment; we never see your payment details. To confirm what you have bought, the app uses the RevenueCat SDK. RevenueCat receives an anonymous identifier created by the app, together with App Store transaction data. If you arrived from an Apple Search Ads campaign, Apple's attribution token (AdServices) is also passed to RevenueCat so we can see which campaign led to a purchase; this does not involve tracking across other companies' apps and does not identify you. RevenueCat gives us aggregated purchase statistics. None of this includes video, sound, clips or alerts. See RevenueCat's privacy policy.

5. No analytics, no ads, no tracking

Napwatch contains no analytics SDK, no advertising, no crash-reporting service and no third-party trackers. We do not build a profile of you and we do not sell or share data.

6. Children

Napwatch is made for parents and carers. It is not directed at children, and it collects no personal information from anyone. Video and sound of your child stay on your own devices and your own network.

7. Changes and contact

If this policy changes, the new version will be posted here with a new date. Questions: [email protected]. Because we hold no account or recordings, there is nothing on our side to look up, export or delete.