Privacy policy

1.1 Account Information

When you sign in with Apple, we may receive:

• Apple ID identifier (an opaque, app-specific user ID assigned by Apple)
• Full name (only if you choose to share it; provided on first sign-in only)
• Email address (only if you choose to share it; may be an Apple Private Relay address)

We store this information locally in the device Keychain. Your name and email are never sent to our servers.

1.2 Subscription Data

When you subscribe to CaddyGo Premium, your subscription is managed by RevenueCat, a third-party subscription management service. The following data is shared with RevenueCat:

• User identifier (your Supabase account ID, a UUID)
• Subscription status and entitlements (whether your subscription is active)

RevenueCat communicates directly with Apple to verify purchase receipts. We do not collect or store any payment or financial information. All billing is handled by Apple through the App Store.

1.3 Location Data

• iPhone: We request your approximate location (accuracy ~100 meters) to find golf courses near you. Location is obtained once per search and is not stored on our servers.
• Apple Watch: During a round, we continuously access your precise GPS location (best available accuracy, updated every 5 meters) to calculate distances to greens, hazards, and hole features. This data is processed on-device and is not sent to our servers.

We request location access only while using the App ("When In Use"). We do not access your location in the background.

1.4 Health and Fitness Data

On Apple Watch, CaddyGo records a golf workout via Apple HealthKit. With your authorization, we access the following data:

• Heart rate (read during the workout)
• Active calories burned (read and written to your workout)
• Distance walked (read and written to your workout, also measured via pedometer)
• Step count (measured via pedometer during the workout)

If you deny HealthKit authorization, the App will continue to function for GPS distances and scoring, but workout tracking will not be available.

1.5 Motion Data

On Apple Watch, we use device motion sensors (accelerometer, gyroscope, magnetometer) to determine your compass heading. This is used solely to orient the course map in your direction of play. Motion data is processed on-device in real time and is not stored or transmitted.

1.6 Scorecards

Your scorecards (course name, date, tee, par, and strokes per hole) are stored on your device and automatically synchronized across your devices via Apple iCloud (CloudKit). Your favorite courses are synchronized via iCloud Key-Value Store. This data is stored in your personal iCloud account, managed by Apple. It is never sent to our servers.

1.7 Usage Data

We collect usage events to understand how the App is used and improve it. These events include:

• App opened
• Round started (course name, number of holes)
• Round completed (course name, score, holes played, score vs. par)
• Subscription started or renewed (product identifier, price)
• Course sent to Apple Watch (course name)

Usage events are sent to Mixpanel and are associated with a random device identifier, not your Apple ID or name.

1.8 Crash and Diagnostic Data

We use Firebase Crashlytics to collect crash reports, which include device model, operating system version, and the state of the App at the time of the crash. This data helps us identify and fix bugs.

1.9 Apple Search Ads Attribution

On first launch, we check whether you installed the App through an Apple Search Ad. If so, we receive anonymized campaign attribution data from Apple's AdServices framework. This data is sent to Mixpanel to measure the effectiveness of our advertising. We do not request the Identifier for Advertisers (IDFA) and do not use App Tracking Transparency.