Last updated: September 12, 2026
Frova is a fitness-tracking app. This policy explains what data we collect, why we collect it, which service providers process it, and how to contact us about your information.
| Data | What it includes | Why |
|---|---|---|
| Email address | Your sign-up email | Authentication |
| Profile information | Your display name, optional profile image, fitness goals, training preferences, and app settings | Display and personalize your profile and experience |
| User ID | A unique ID assigned to your account | Links your data together |
| Fitness data | Workouts, exercises, sets, reps, weights, notes, dates, personal records, streaks, and XP, including workouts you choose to import from Apple Health | Core app functionality |
| Health data | Body weight, daily protein and water intake, and related goals you log | Fitness and nutritional goal tracking |
| Notification information | An Expo push notification token associated with your account when notification permission is granted | Notification registration; workout and streak reminders are scheduled on your device |
Apple Health import is optional. On iOS, with HealthKit read permission, Frova reads workouts from the last seven days, including activity names, start and end times, distance, and workout identifiers. Imported workouts are saved to your Frova account with their activity, date, duration, and source identifier. Duration and distance are used to calculate XP. This integration does not write data to Apple Health.
Account and fitness information, including imported workouts, is stored in Supabase. Profile images you select from your photo library are uploaded to Supabase storage and linked to your profile. These images have public URLs: anyone with the image URL can view the image without signing in. The URL includes your account ID, so choose an image you are comfortable making accessible this way.
We use the following services:
When configured in production, Google Analytics receives app-open and screen-view events, screen paths, event parameters, a generated client identifier stored on your device, a per-launch session identifier, and an engagement-time value to help us understand app usage. Screen paths may include identifiers for the records you view. Sentry receives JavaScript error reports, stack traces, diagnostic context, and your account ID to help us investigate failures. Diagnostic context can include error details and image-upload metadata such as file type, dimensions, and encoded size. Native crash reporting and performance tracing are currently disabled. These providers process the information sent to them to support analytics and troubleshooting.
You can, at any time:
Frova is not directed at children under 13. We do not knowingly collect data from anyone under 13. If you believe a child has provided us data, contact us to request its removal.
If we make material changes we will update the date at the top of this page. Please review this page for the current policy.