Privacy Policy

Watch+

Effective date: August 13, 2025

Owner & Data Controller: Krzysztof Rózga Mobile Apps

Thank you for using Watch+. This Privacy Policy explains what data the app collects, how and why it is used, and your choices. The app is developed and published by Krzysztof Rózga Mobile Apps (“we”, “us”, or “our”). We are based in the European Union, so the processing of personal data is carried out in accordance with the General Data Protection Regulation (GDPR).

This document is designed to satisfy Apple App Store requirements and to be clear and readable for users. It covers the services actually used in the app: Firebase (Messaging, Firestore, Analytics), RevenueCat, and Sentry.

Summary

  • No in‑app account creation. Subscriptions use RevenueCat Anonymous User IDs.
  • We store device push tokens in Firebase Firestore to deliver notifications.
  • We send notifications using Firebase Cloud Messaging (FCM) / Apple Push Notification service (APNs).
  • We measure usage with Firebase Analytics (aggregated usage data).
  • We collect crash and error diagnostics with Sentry.

Data We Process & Purposes

App identifiers

Examples: Anonymous RevenueCat App User ID; Firebase Instance ID

Purpose: Enable subscriptions, entitlement checks, and restore purchases without creating an in‑app account.

Legal basis (GDPR): Performance of a contract; Legitimate interests (operate app & prevent fraud)

Device & app data

Examples: Device model, OS version, app version, language, country, time zone

Purpose: App functionality, analytics, troubleshooting, and crash diagnostics.

Legal basis (GDPR): Legitimate interests

Push notification tokens

Examples: APNs/FCM device token stored in Firestore

Purpose: Send you opted‑in push notifications.

Legal basis (GDPR): Consent (you can disable anytime in iOS Settings)

Usage analytics

Examples: Screen views, events, app interactions (non‑sensitive)

Purpose: Understand feature usage and improve the app.

Legal basis (GDPR): Legitimate interests

Crash & diagnostics

Examples: Stack traces, error messages, device/app context at time of crash

Purpose: Find, reproduce, and fix bugs and performance issues.

Legal basis (GDPR): Legitimate interests

Purchase information

Examples: Product identifiers, transaction receipts, subscription status

Purpose: Provide premium features; manage entitlements and refunds.

Legal basis (GDPR): Performance of a contract; Legal obligation (tax/accounting)

We do not collect your name, email address, or other direct contact information in the app.

Third‑Party Services We Use

RevenueCat (Subscriptions)

We use RevenueCat to manage in‑app purchases and subscriptions. We do not create user accounts; RevenueCat assigns an anonymous App User ID that links your device’s purchases with your entitlements. Data processed may include product identifiers, transaction receipts, country, device/app metadata, and subscription status.

See RevenueCat’s privacy documentation and terms on their website.

Firebase Firestore (Token Registry)

We store your device’s push notification token in Firestore so the app can send notifications to your device. Firestore stores this identifier and minimal metadata required for routing notifications. You can opt out by disabling notifications in iOS Settings or within the app (where available).

Firebase Cloud Messaging (FCM) & APNs (Push Delivery)

With your permission, Watch+ uses FCM and Apple Push Notification service to deliver notifications to your device. FCM and APNs process device tokens and message routing data to deliver notifications.

Firebase Analytics (Measurement)

We use Firebase Analytics to collect aggregated, non‑sensitive usage metrics (e.g., screen views, feature usage). This helps us understand how the app is used and improve it. You can limit analytics collection in the app settings (where available) or via platform privacy controls.

Sentry (Crash Reporting)

We use Sentry to collect crash reports and diagnostics. This may include stack traces, device model, OS version, app version, timestamps, and limited breadcrumbs (recent events leading to the crash). We do not intentionally send personal content.

Cookies & Tracking

The app does not use cookies. Third‑party SDKs may generate device identifiers solely for the purposes described above (analytics, crash reporting, subscription management, and notifications).

Data Sharing & International Transfers

We do not sell your personal data. We share data only with the processors listed above to operate the app. Some processing may occur outside the EU/EEA (e.g., in the United States). When data is transferred internationally, we rely on appropriate safeguards such as Standard Contractual Clauses offered by the respective providers.

Retention

Your Rights (GDPR)

Depending on your location, you may have the right to request access, rectification, erasure, restriction, or portability of your personal data, and to object to processing based on legitimate interests. You also have the right to withdraw consent at any time (for example, by disabling notifications).

You can exercise these rights by contacting us (see Contact). You also have the right to lodge a complaint with your local supervisory authority. For Poland, this is the Urząd Ochrony Danych Osobowych (UODO).

Controls & Opt‑Out

Children’s Privacy

Watch+ is not directed to children under 13, and we do not knowingly collect personal data from children under 13. If you believe a child has provided us with personal data, please contact us so we can take appropriate action.

Security

We take reasonable technical and organizational measures to protect your data. However, no method of transmission or storage is 100% secure. We encourage you to keep your device updated and use device security features.

Contact

Data Controller: Krzysztof Rózga Mobile Apps.

Email: watchplus.app@gmail.com

Changes to This Policy

We may update this Privacy Policy from time to time. We will post the new version in‑app and update the “Effective date” above. Material changes will be highlighted in release notes or in‑app notices where appropriate.