Private by design.

Data Naptara processes

Optional product analytics

Naptara asks an adult for permission before sending first-party product analytics. The choice can be changed under Privacy & safety. Declining does not reduce monitoring functionality.

When enabled, allowlisted events may include app and feature use, pairing outcome, connection reliability, first live connection, reconnect outcome, Early Stir feedback, paywall source, purchase outcome, review-prompt eligibility, app version, operating-system version, device class, role, language, store or system country, and transport type.

A random installation identifier and a temporary session identifier are included to calculate unique-install counts, reliability funnels and repeated-failure rates. They are not advertising identifiers, are not linked to a name, email address or Naptara account, and are not used across other companies' apps or websites.

If the app crashed, the next launch may send a crash report containing only the name of the crashing module and the code offset; no memory contents, logs or personal data.

With analytics enabled, the Apple Ads attribution above is also linked to your installation identifier.

Analytics never includes audio, video, snapshots, baby or caregiver names, pairing codes, session media keys, advertising identifiers or the contents of monitoring sessions. Accepted reports are converted to aggregate counters. The installation and session identifiers are converted to keyed hashes before they are saved for unique counts. The analytics store does not retain raw event rows or the original identifiers.

Sent without analytics permission

Three limited, non-identifying purchase records, plus two anonymous counters described below, are processed even when optional product analytics is off. The purchase records are needed because they are needed to understand purchases and cancellations. None of them contains a name, email address, device identifier, installation identifier, advertising identifier or Apple Account details, and the server does not log the IP address for these requests.

• Subscription status from Apple. Apple sends signed App Store Server Notifications when a trial starts, a purchase or renewal happens, or automatic renewal is switched on or off. We store the notification type and subtype, product, App Store country, auto-renew status, expiration reason, offer type and times rounded to the hour. Apple's original transaction ID is stored only as a keyed hash.
• Purchase context from the app. When you buy, the app creates a new random code for that purchase only and gives it to Apple with the purchase. The app sends the same code with the app version, chosen plan, paywall variant, App Store country and a rough time-since-install range (0 days, 1–3, 4–7, 8–30 or more than 30 days). This lets us see which paywall and plan lead to purchases. The code is not reused and is not linked to your device or to analytics.
• "Why are you stopping?" answer. If automatic renewal is off, the app may ask once why you are stopping. Only if you tap an answer, the app sends that answer (too expensive, not working, only needed briefly, by accident, or other) with the app version, App Store country and the date. Ignoring the question sends nothing.
• Consent counter. When the analytics question is shown and answered, the app sends an anonymous count of the step (shown, allowed or declined) with only the platform and app version. It contains no installation or session identifier, country or language.
• Apple Ads attribution. For App Store installs, the app asks Apple's AdServices framework once for attribution and sends the campaign, ad-group, keyword and ad identifiers anonymously with only the platform and app version, without an installation or session identifier, country or language. No advertising identifier is used, and this is not tracking as defined by Apple's App Tracking Transparency.

These records are used only in aggregate to improve Naptara.

Permissions

• Camera: Baby Station video.
• Microphone: baby audio and two-way talk.
• Local network: finding and connecting devices on the same Wi-Fi network.
• Notifications: optional local monitoring alerts.

Permissions are requested when the related feature is selected and can be changed in iOS Settings or Android settings.

Retention, deletion and security

You can clear the local timeline from inside Naptara. Removing the app removes its local app data. Product analytics keeps aggregate counters and pseudonymous keys for unique-install and session counts. These keys can link usage within Naptara, but are not mapped to a name, email address or Naptara account. The analytics store keeps its most recent 180 daily summaries; this limit is applied as new reports arrive. For privacy questions or requests, contact privacy@bumblly.com.

Remote media uses session-specific encrypted transport. The service is configured not to log pairing codes, media keys or media content. An IP address may be used transiently in server memory for security and rate limiting, but is not stored in the product-analytics aggregate.

Naptara is intended for use by adult caregivers. It is not a medical device and does not replace responsible adult supervision or certified medical equipment.

Service providers and international processing

Apple processes App Store purchases under Apple's own terms. Google processes Google Play purchases under Google Play's terms. Remote monitoring uses LiveKit-based real-time media infrastructure operated for Naptara. Depending on where you use the app, encrypted network traffic may be routed across countries in order to provide the connection.

Naptara does not sell personal data and does not share data with advertising networks.

Android and Google Play

Update dated: 30 August 2026

Naptara is also available on Android via Google Play. The same privacy rules apply: no advertising, no Naptara account and no continuous cloud recording. Pro purchases on Android are handled by Google Play Billing. Naptara receives entitlement status, not your payment-card details. Camera, microphone, notifications and nearby-device or local-network permissions can be changed in Android settings. This update does not change how iPhone and iPad purchases are processed by Apple StoreKit.

Android: anonymous counters and the first-open choice

On first open, Naptara for Android asks whether you allow usage statistics. Before you answer, and also after you tap Not now, the app sends only anonymous counters to our own server at analytics.bumblly.com: app opened (cold start and return to the app), first open, onboarding step, paywall shown, plan tapped, purchase started, purchase completed or failed (closing the Google Play payment sheet yourself is not counted as a failure), restore, and the install source (Google Play referrer campaign fields only). Each counter carries only the event name, app version, platform, language and store country. It contains no installation ID, session ID, advertising ID, name or email address, and the server does not log the IP address.

Only if you tap Allow are these events sent with a random installation number that Naptara creates on the device, so we can count unique installs and sessions. You can change this choice in the app settings at any time. Payments are handled by Google Play Billing; Naptara never receives your card details.

Contact and changes

For privacy questions, contact privacy@bumblly.com. For product support, visit Naptara Support.

This page will be updated when Naptara's data practices materially change. The effective date at the top shows the latest revision.