Privacy Policy for Bike Analytics

Last Updated: January 10, 2025 | Effective Date: January 10, 2025

Introduction

Bike Analytics ("we," "our," or "the app") is committed to protecting your privacy. This Privacy Policy explains how our mobile applications (iOS and Android) access, use, and protect health data from your device.

Key Privacy Principle: Bike Analytics operates on a zero-server, local-only architecture. All health data accessed from Apple HealthKit (iOS) or Health Connect (Android) remains exclusively on your physical device and is never transmitted to external servers, cloud services, or third parties.

1. Health Data Access

Bike Analytics integrates with your device's native health platform to provide detailed cycling workout analysis:

1.1 iOS - Apple HealthKit Integration

On iOS devices, Bike Analytics integrates with Apple HealthKit to access cycling workout data. We request read-only access to:

  • Workout Sessions: Cycling exercise sessions with time and duration
  • Distance: Total cycling distances
  • Heart Rate: Heart rate data during workouts
  • Active Energy: Calories burned during cycling sessions
  • Cycling Power: Power data (watts) for performance analysis
  • Cycling Speed: Speed data for pace analysis

Apple HealthKit Compliance: Bike Analytics adheres to all Apple HealthKit guidelines. Your health data is processed entirely on your iOS device and never leaves it. We never share HealthKit data with third parties, advertising platforms, or data brokers.

1.2 Android - Health Connect Integration

Health Data Type Permission Purpose
Exercise Sessions READ_EXERCISE To identify and import cycling workout sessions from Health Connect
Distance Records READ_DISTANCE To display total distance per ride and calculate speed metrics
Heart Rate Records READ_HEART_RATE To display heart rate charts, calculate average and maximum heart rate
Speed Records READ_SPEED To calculate and display your cycling speed and pace zones
Power Records READ_POWER To analyze power output (Watts) and calculate FTP/TSS
Calories Burned READ_TOTAL_CALORIES_BURNED To provide overview of energy expenditure during rides

Android Permissions: These permissions are requested during the app's first launch. You can revoke these permissions at any time through Android Settings → Apps → Health Connect → Bike Analytics.

1.3 How We Use Health Data

All health data is used exclusively for the following purposes:

  • Workout Display: Show your cycling sessions with detailed metrics (distance, time, speed, heart rate, power)
  • Performance Analytics: Calculate power zones, FTP (Functional Threshold Power), and TSS (Training Stress Score)
  • Progress Tracking: Display performance trends, personal bests, and workout summaries
  • Data Export: Allow you to export your workout data to CSV format for personal use

1.4 Data Storage

🔒 CRITICAL PRIVACY GUARANTEE:

All health data remains exclusively on your physical device.

  • iOS: Data is stored using iOS Core Data and UserDefaults (on-device only)
  • Android: Data is stored using Android Room Database (on-device SQLite)
  • NO data is uploaded to external servers
  • NO data is transmitted over the internet
  • NO cloud synchronization or backup of health data
  • NO third-party access to your health data

The only time data leaves your device is when YOU explicitly choose to export your workouts to CSV format and share the file yourself.

2. Permissions Required

2.1 iOS Permissions

  • HealthKit Access: Read access to Workouts, Distance, Heart Rate, Active Energy, Cycling Speed, and Cycling Power
  • Photo Library (Optional): Only if you choose to save workout summaries as images

You can manage HealthKit permissions at any time in iOS Settings → Privacy & Security → Health → Bike Analytics.

2.2 Android Permissions

  • android.permission.health.READ_EXERCISE
  • android.permission.health.READ_DISTANCE
  • android.permission.health.READ_HEART_RATE
  • android.permission.health.READ_SPEED
  • android.permission.health.READ_POWER
  • android.permission.health.READ_TOTAL_CALORIES_BURNED
  • Internet Access (INTERNET): Used only for displaying static in-app content and accessing subscription management.

3. Data We Do NOT Collect

Bike Analytics does NOT collect, store, or transmit:

  • ❌ Personal identification information (name, email, phone number)
  • ❌ Device identifiers (IDFA on iOS, advertising ID on Android)
  • ❌ Location data or GPS coordinates
  • ❌ Usage analytics or app behavior tracking
  • ❌ Crash reports or diagnostic data to external servers
  • ❌ Any data through third-party SDKs or analytics services

4. In-App Purchases and Subscriptions

Bike Analytics offers optional in-app subscriptions managed through your device's native payment system (App Store or Google Play). We do not receive payment details, only subscription status.

5. Data Retention and Deletion

5.1 Data Retention

Health data is stored on your device indefinitely until manually deleted. You control your data retention.

5.2 Data Deletion

Delete individual workouts in-app, or clear all app data via system settings or uninstallation. Revoke health permissions at any time.

6. Data Security

We use device-level encryption (iOS Keychain, Android Sandbox). No data transmission occurs, eliminating network risks.

7. Data Sharing and Third Parties

Bike Analytics does NOT share your health data with any third parties. We do not sell data or use advertising SDKs.

8. Children's Privacy

Bike Analytics does not knowingly collect data from children under 13. Parents should supervise app usage.

11. Changes to This Privacy Policy

We may update this policy. Review it periodically. Continued use implies acceptance.

12. Contact Us

If you have questions:

Summary

In Simple Terms:

  • ✅ What we access: Cycling workout data from HealthKit (iOS) or Health Connect (Android)
  • ✅ Where it's stored: Only on YOUR device
  • ✅ Where it goes: Nowhere. It never leaves your device.
  • ✅ Who sees it: Only you.

Bike Analytics is built privacy-first.