Activ.run Mobile Application Privacy Policy
This Privacy Policy describes how Activ.run ("we," "us," or "our") collects, uses, and shares information related to your use of the Activ.run mobile fitness application and workout tracker.
1. Data we collect
Account and profile information
We may collect name, email address, internal user identifiers, securely hashed passwords, and profile information such as gender, height, and weight. We use this data for account management and App functionality.
Health and fitness data
We collect workout logs, sets, reps, weight, total volume, rest times, bodyweight entries, and related health and fitness information. We use this data for App functionality, analytics, and personalization.
If you connect Google Health Connect on Android, activ.run may also read bodyweight data from Health Connect and store it locally on your device and in your activ.run account to display your bodyweight history alongside manually logged entries and provide first-party, user-facing health and fitness analytics, such as trends, summaries, and progress insights. activ.run currently reads only bodyweight data from Health Connect. Health Connect data is not used for advertising, third-party analytics, machine learning model training, resale, or data brokering. You can revoke Health Connect access at any time from Android settings or the Health Connect app.
Usage and diagnostics
We may collect app interactions, taps, views, in-app search history, crash logs, diagnostics, API speed, memory, and other performance data. We use this data for analytics, fraud prevention, security, compliance, and App functionality.
Device information
We may collect device identifiers, advertising identifiers, device make and model, and operating system version. We use this data for analytics, advertising or marketing attribution, fraud prevention, security, and compliance.
Location
We may collect approximate location, such as country or region derived from IP address or similar non-precise methods, for App functionality, analytics, and marketing.
2. How we use your data
We use your data to create and manage your account, secure your session, display workout history, track progress and streaks, monitor app stability, diagnose bugs, analyze usage patterns, improve performance, measure marketing attribution, and detect or prevent unauthorized access and policy violations.
3. How we share your data
We do not sell your personal data. We share data only when necessary with service providers that help us operate the App, including PostHog for product analytics and Sentry for crash reporting and error monitoring.
To help us improve our apps and user experience, we share your email address with PostHog (posthog.com), a third-party product analytics platform. This data is used solely for analytics to understand usage patterns and identify internal testers. You may opt out of this data sharing at any time by toggling off "Share usage data" in the Profile section of the app.
We may share advertising identifiers and related usage data with advertising networks and marketing platforms to measure campaign performance and serve relevant advertisements. We may also disclose information if required by law or in response to a valid legal request.
Health Connect data is never shared with third parties, including service providers, analytics platforms, or advertising networks.
4. Your rights and data deletion
You can view, edit, or delete most personal information, bodyweight entries, and workout logs directly within the App's Profile section.
You may delete your account and associated data by navigating to the Profile menu in the App and selecting "Delete Account." This permanently removes personal information, workout logs, and bodyweight history, subject to retention and legal compliance obligations.
You can reset your Advertising ID or opt out of personalized ads through your iOS or Android device settings.
5. Data security
We implement security measures including secure API wrappers, token-based authentication, encryption in transit via HTTPS, and secure session storage on device to protect your data from unauthorized access, alteration, disclosure, or destruction.
7. Health Connect
activ.run integrates with the Android Health Connect platform to read health and fitness data from compatible apps and devices you choose to connect. The following applies specifically to data obtained through Health Connect.
What we read
activ.run currently requests permission to read bodyweight data only (android.permission.health.READ_WEIGHT).
How we use it
Health Connect bodyweight data is used only within activ.run to display your bodyweight history and provide first-party, user-facing health and fitness analytics, such as trends, summaries, and progress insights.
What we do not do
activ.run does not sell, license, transfer, or share Health Connect data with advertisers, data brokers, third-party analytics providers, or other third parties. activ.run does not use Health Connect data for advertising, artificial intelligence or machine learning model training, resale, data brokering, or unrelated purposes.
Writing data
activ.run does not write data back to Health Connect.
Revoking access
You can revoke activ.run's Health Connect access at any time through Android settings or through the Health Connect app's app permissions screen. Revoking access stops activ.run from reading new Health Connect data.
Retention
Bodyweight entries already synced to activ.run remain in your activ.run account and local app storage until you delete individual entries or delete your account.
Deleting your data
You can delete individual bodyweight entries in activ.run, or delete your entire account and all associated activ.run data from Profile → Delete Account. Deleting a Health Connect-sourced entry from activ.run does not delete the original record from Health Connect or the source app. For deletion requests, contact support@activ.run.
Compliance
activ.run's use of Health Connect data complies with the Health Connect Permissions Policy: developer.android.com/health-and-fitness/health-connect/core-topics/privacy-policy-requirements