← Back to Home

Legal

Privacy Policy

Effective Date: April 2026

1. Introduction

Ergomi (“App,” “we,” “us,” or “our”) is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our mobile application and related services (the “Service”).

Please read this policy carefully. By downloading and using Ergomi, you consent to the practices described herein.

2. Information We Collect

2.1 Health & Fitness Data (On-Device)

When you use Ergomi to track workouts, we collect and store locally on your device:

  • Workout Metrics: Distance, duration, heart rate, power output, cadence, pace, calories burned
  • Session Timestamps: Start/stop times, intervals, workout type (Running, Cycling, Rowing, Skiing, etc.)
  • Biometric Preferences: Max heart rate, resting heart rate, FTP (Functional Threshold Power), weight, age
  • Interval Plans: Custom or template-based workout structures you create
  • Performance History: Past sessions stored in the app’s local database (Room)
  • Coach Memory Notes and Summaries: Short coaching notes and compact performance summaries generated after completed sessions and stored locally to personalize future coaching

Location Data: If you enable GPS tracking for outdoor activities, we collect and store GPS coordinates locally. This data is only used to calculate distance and create GPX/TCX files for export.

All health and fitness data is stored on your device by default. We do not transmit this data to our servers unless you explicitly opt in to cloud sync (if available).

2.2 Health Connect Integration

If you grant Ergomi permission to access Android Health Connect:

  • Daily Readiness Metrics: Resting heart rate, HRV (Heart Rate Variability), sleep duration from your connected wearables
  • Purpose: To provide personalized daily readiness scores and coaching guidance based on your recovery status
  • No Transmission: Health Connect data is read-only and used locally to inform coaching decisions. We do not send this data to external servers.

2.3 Hardware Connection Data

When you connect to fitness hardware (Concept2 rowing machines, smart trainers, Bluetooth HR sensors):

  • Device Identifiers: Bluetooth MAC addresses, device names
  • Real-Time Metrics: Power, cadence, stroke rate transmitted over Bluetooth
  • No Storage of Hardware IDs: We do not store device identifiers after the session ends.

2.4 Optional Connected Service Integrations

If you choose to connect third-party services:

  • Strava: Selected workout files (GPX/TCX/FIT) may be uploaded to Strava via HTTPS when you choose to export them
  • Concept2 Account Connectivity (when available): If a future production-approved build enables Concept2 account connectivity, any required account tokens are stored locally on your device
  • Authentication: You authenticate directly with the connected provider; we do not store your password
  • Our Role: We facilitate the connection or upload but do not retain your uploaded workout files on our servers

2.5 Voice Coaching

Ergomi delivers coaching audio using a mix of on-device playback paths:

  • Pre-rendered Voice Packs: Some coaching cues are played from bundled audio assets stored in the app
  • Android Text-to-Speech: When no bundled cue is available, Ergomi uses Android’s built-in text-to-speech engine on device
  • No Voice Text Submission: Ergomi does not submit your coaching text to an external voice synthesis provider as part of the current launch scope

2.6 Subscription & Billing Information

If you choose to purchase a subscription:

  • Google Play Billing: Subscription status, product identifiers, purchase tokens, expiry timing, and related billing state are processed through Google Play
  • Local Entitlement Cache: Ergomi stores a local, secure cache of your last verified subscription tier to support temporary offline use
  • Purpose: To unlock and verify Premium features such as additional coach styles, Coach Memory, and export features

We do not receive your full payment card details.

2.7 Device & System Information

  • Device Model & OS Version: Collected for crash reporting and app stability
  • App Version: Used to identify which version of the app you’re using
  • Crash Logs: If the app crashes, logs may be collected (locally or via your chosen crash reporter)

2.8 User-Provided Information

  • Profile Name & Photo: Optional — used only locally to personalize your dashboard
  • Preferences: Sport preferences, theme, language, measurement units (all stored locally)

3. How We Use Your Information

3.1 Primary Uses

  • Workout Tracking: Display and analyze your exercise data, calculate metrics
  • Coaching Guidance: Generate real-time feedback and post-workout summaries based on your performance
  • Daily Readiness: Compute daily readiness scores and training load (CTL/ATL/TSB)
  • History & Analytics: Show past sessions, trends, and performance charts
  • Export & Sharing: Create files (GPX/TCX/FIT) for export to third-party platforms
  • Subscription Verification: Confirm whether Premium features should be available on your device

3.2 Personalization

  • Your biometric preferences, past performance, Coach Memory notes, and compact local performance summaries inform coaching advice
  • Struggle state detection (Beast/Flow/Struggling/Wall) adjusts coaching tone in real time

3.3 App Improvement

  • Crash Reports: Help us identify and fix bugs
  • Product Improvement: We may review aggregated, non-identifying product signals in future versions if we introduce them and update this policy accordingly

We do not use your data for marketing, advertising, or selling to third parties.

4. Data Sharing & Disclosure

4.1 No Sale or Rental

We do not sell, rent, lease, or otherwise disclose your personal health data to third parties for commercial purposes.

4.2 Third-Party Services (Optional)

  • Google Play: Used for subscription purchase and entitlement verification
  • Strava: You control whether to export workouts; we facilitate the transfer but do not retain files on our servers
  • Health Connect: We read data you’ve shared via Health Connect; data remains on your device
  • Concept2: If you link Concept2 services, account tokens are stored locally on your device and requests are sent directly to Concept2 APIs as needed
  • Firebase Crashlytics: In production builds, anonymized crash information may be sent to Firebase Crashlytics to help diagnose app stability issues

We may disclose information if required by law or court order to comply with legal obligations.

4.4 Future Services

If Ergomi introduces cloud sync or additional hosted services in the future:

  • We will update this policy before those features become generally available
  • We will describe what data is processed, where it is stored, and how you can control or delete it

5. Data Retention

5.1 Local Data

Health and fitness data stored on your device is retained until you manually delete it (via the app’s data management features or uninstalling the app).

Deleting a visible workout removes the detailed workout record from history. To keep coaching continuity, Ergomi may retain compact local Coach Memory summaries derived from completed workouts, such as date, sport, duration, distance, heart-rate, power, cadence, and training-load values. These summaries are stored on your device and are designed to be less detailed than the original workout. Clearing app storage or uninstalling Ergomi removes this local Coach Memory data. A dedicated in-app control for clearing Coach Memory separately is planned.

5.2 Exported Data

Exported files (GPX/TCX/FIT) are retained on your device or third-party services per your control. We do not store copies.

5.3 Crash Logs

Crash logs are retained for 30 days for debugging purposes, then deleted.

5.4 Future Cloud Features

If future versions introduce cloud storage or sync, retention details will be added to this policy before launch.

6. Data Security

6.1 On-Device Storage & Encryption

Ergomi stores workout history in a local Room database on your device. Sensitive tokens and secure entitlement data are stored using Android Keystore-backed encrypted storage where available. Your device’s built-in encryption also helps protect data at rest.

6.2 Network Security

  • HTTPS/TLS is used for all external API calls (Strava, Health Connect, and other enabled integrations)
  • Certificates are validated to prevent man-in-the-middle attacks
  • OAuth tokens and secure entitlement cache data are stored using encrypted local storage where available

6.3 Limitations

No security system is 100% secure. We implement industry-standard practices but cannot guarantee absolute protection against determined attackers.

7. Your Privacy Rights

7.1 Access & Control

  • Data Access: You can view all your workout history and metrics within the app
  • Data Export: You can export your workouts as GPX/TCX/FIT files at any time
  • Data Deletion: You can delete individual sessions or clear your local app data. Detailed workout history and compact Coach Memory summaries may have separate controls as Ergomi evolves; until a dedicated Coach Memory control is available, clearing app storage or uninstalling the app removes the local Coach Memory data.
  • Connected Accounts: You can disconnect supported third-party services from the app

7.2 Permissions Management

  • You can revoke Health Connect access anytime via Android Settings
  • You can disconnect Strava at any time (future workouts won’t be exported)
  • You can disable voice packs and rely on Android system TTS where supported
  • You can manage or cancel subscriptions through Google Play

7.3 Location Data

If you use GPS tracking, you can disable it anytime. Previously recorded GPS data can be deleted per your control.

8. Children & COPPA

Ergomi is not intended for children under 13. We do not knowingly collect data from children under 13. If we discover that a child under 13 has provided information, we will delete it immediately. Parents who believe their child has provided data should contact us.

Ergomi may link to external services such as Google Play, Strava, Android Health Connect, Concept2, and Zwift. This Privacy Policy does not cover those services’ practices. We encourage you to review their privacy policies.

10. Contact & Data Requests

If you have questions about this Privacy Policy, or wish to request access, correction, or deletion of your data, contact us at:

Email: support@ergomi.app
Website: https://ergomi.app

11. Changes to This Policy

We may update this Privacy Policy periodically. Changes will be posted here with an updated effective date. Continued use of the app constitutes acceptance of the updated policy.

12. Regional Compliance

12.1 GDPR (EU)

If you are in the EU, you have the right to:

  • Access your personal data
  • Rectify inaccurate data
  • Erase your data (right to be forgotten)
  • Data portability
  • Restrict processing
  • Lodge complaints with your local data protection authority

All requests can be submitted via the contact method above.

12.2 CCPA (California)

If you are a California resident, you have the right to:

  • Know what personal information is collected
  • Know whether it’s sold or disclosed
  • Delete personal information
  • Opt out of the sale/sharing of personal information

As stated, Ergomi does not sell personal information. To exercise your rights, contact us at the address above.

Last Updated: April 2026