Private by design.

How PupWatch is used

You use two Apple devices: one as Puppy Station and one as Monitor. No PupWatch account is created.

Live audio and video are transmitted between those two devices for monitoring. PupWatch does not continuously store this media in a cloud archive.

Permissions

• Camera: Puppy Station video while monitoring is active.
• Microphone: puppy audio and two-way talk.
• Local network: finding and connecting the two devices on the same Wi-Fi network.
• Calendar: optional, and only after you confirm you want it. Calendar details are not required to monitor.

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

What stays on the device

Settings and role (Puppy Station or Monitor) stay on the device. Removing the app removes its local app data from that device.

Purchases

Apple processes subscriptions and payments through the App Store. PupWatch reads the entitlement needed to unlock Pro. It does not receive your payment-card details.

No advertising or tracking

PupWatch does not sell personal data and does not include an advertising SDK or cross-app tracking.

PupWatch is an indicator tool. It is not a safety or medical monitor. Always check your puppy directly when you are concerned.

Sent without analytics permission

These limited records are processed even when optional analytics is off, because they are needed to count installs and to understand purchases and cancellations. None of them contains a name, email address, advertising identifier, Apple Account details or a hardware device identifier, and the server does not log the IP address for these requests. The only identifier is a random installation number that PupWatch creates itself (described below); it is not linked to your identity and is not used for tracking.

• 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 product, 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). The code is not reused. From version 1.1.11 the app also sends its random installation number with it, so that PupWatch can show you one relevant offer or message if you later cancel.
• "Why are you stopping?" answer. If automatic renewal of your subscription is off, PupWatch 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.
• Product analytics. PupWatch sends first-party usage events to our own server at analytics.bumblly.com: first open, onboarding steps, paywall views and the paywall source, plan taps, trial start, purchase completed, cancellation-offer views and taps, and a successful live watch. Each event includes a random installation number that PupWatch creates on the device, the platform (iPhone or iPad), App Store country, app and iOS version. Events never include your name, email address, advertising identifier, audio, video or calendar contents. They are not shared with ad networks or data brokers and are not used across other companies' apps or websites. Reinstalling the app creates a new installation number.
• Apple Ads attribution. On first launch, PupWatch asks Apple's AdServices framework for an attribution token. If the install came from an Apple Ads campaign, the campaign, ad-group and keyword identifiers and country are sent once to our server with the random installation number, so we can see which campaigns lead to installs. No advertising identifier is used, and this is not tracking as defined by Apple's App Tracking Transparency.
• Cancellation offers. When you open the app, it may ask our server, using the random installation number, whether there is a message or offer for you after you switched off renewal or your subscription ended. Whether you saw, accepted or dismissed it is sent back with the same number. You can always continue without the offer, and cancelling stays in your Apple subscription settings.

These records are used only in aggregate to improve PupWatch.

Android: anonymous counters and the first-open choice

On first open, PupWatch 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 PupWatch 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; PupWatch never receives your card details.

Contact and changes

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

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