This Privacy Policy explains what information Trainerrr uses, why it is needed, how long it is kept, and what controls users have inside the app.
Trainerrr is a workout, nutrition, and goal logging application. Users can create an account, sign in, upload an optional avatar, create workout plans, log workout sessions, log food intake, manage fitness goals, and optionally connect Apple Health or Health Connect. The app uses Supabase for authentication, database storage, and avatar file storage.
This policy covers the current version of the app. Trainerrr will update this page if its features, services, or data uses change.
| Category | Examples | Whether it is optional | Why it is used |
|---|---|---|---|
| Account data | Email address and authentication credentials handled through Supabase Auth | Email is required to create and access an account | To register users, authenticate sessions, secure accounts, and support password reset |
| Profile data | Optional display name and optional avatar image | Optional | To personalize the user profile and show profile information inside the app |
| Workout plans | Plan names, descriptions, workout days, exercise selections, sets, reps, and rest timers | Optional, but required to use planning features | To let users build and manage workout programs |
| Workout logs and goals | Workout start and completion times, exercise entries, reps, weight, completion state, calories burned, weekly targets, and calorie targets | Optional, but required to use workout logging features | To let users log completed workouts and maintain necessary goal history |
| Nutrition logs | Food names, ingredient or recipe labels, serving details, calories, macros, fiber, sugar, and short notes when added by the user | Optional, but required to use nutrition logging features | To let users track food intake, daily nutrition totals, and active streaks |
| Connected health and fitness data | Weight, height, body-fat percentage, steps, active energy, workouts, workout source details, and nutrition samples when that feature is available and enabled | Optional. Each category is enabled separately on each device | To import the selected data into the user's Trainerrr account, show consistent activity and calorie totals, and synchronize nutrition only when the user chooses that feature |
| Conversation-based MCP requests | Workout, food, target, journal, progress check-in, and image reference details users choose to send through ChatGPT or another MCP client | Optional and only used when a user connects the MCP server | To complete the requested Trainerrr action for the signed-in account |
| User-created exercise content | Custom exercise names, descriptions, instructions, and media links when added by the user | Optional | To support custom exercise creation and search |
| Android launch requests | The email address a visitor chooses to send from or include in an Android public launch notification request | Optional and separate from a Trainerrr account | To send one email when Trainerrr becomes publicly available on Android |
| Anonymous usage counts | A short list of events recording that the app was opened, a screen was viewed, a workout was started or finished, or onboarding was completed. No account identifier, no name, no email, no body measurements, no nutrition data, and no content the user created. Location is not derived from the IP address, and the identifier used is discarded when the app closes, so these counts cannot be linked to a person or followed between sessions | Always on. This is the minimum needed to see whether the app works | To count how often the core features are used, so broken or unused parts of the app can be found |
| Consented analytics data | The same usage events, plus the remaining in-app events and app error reports, linked to the account identifier so they can be recognised as one person over time. Still no name, email, body measurements, nutrition data, or user-created content | Optional and only enabled after explicit consent, which can be given or withdrawn at any time in Settings › Privacy | To understand whether core flows are working, identify what breaks, and make the app better |
Trainerrr uses the information it collects to provide workout, food, goal, and planning features for your account. Trainerrr does not use user data for advertising, commercial purposes, or academic and scientific research.
Apple Health and Health Connect access is optional. Trainerrr groups permissions into Body, Activity, Workouts, Nutrition import, Nutrition export, and Background updates. Core read categories may be offered during onboarding, but the user chooses whether to connect them. Nutrition and background access require a separate action from Profile and may not appear in every release.
Trainerrr does not use connected health data for advertising, data brokerage, credit decisions, employment decisions, insurance decisions, or medical diagnosis and treatment.
Account and app data are retained for the lifetime of the account unless the user deletes entries, deletes their account, or the data is no longer needed to operate the service.
Disconnecting the current device stops future health synchronization and revokes access where the platform supports it. Previously imported records remain in the Trainerrr account. A separate Remove imported health data action removes health-sourced workouts and meals from Trainerrr without deleting the originals from Apple Health or Health Connect.
The app also includes an account deletion flow. In the current version, deleting an account removes the authenticated user and user-linked workout plans, workout logs, nutrition data, health integration records, imported health data, goals, and custom exercises. The app also attempts to remove the stored avatar file during account deletion.
Deleting an account also deletes the analytics profile held for it, together with the events recorded against it. The same erasure can be requested on its own from Settings › Privacy without deleting the account. Anonymous usage counts carry no account identifier, so there is nothing in them to trace back and erase. Analytics deletion is processed asynchronously and can take some time to complete.
Android launch-notification requests are kept until the public launch notice is sent and removed within 30 days afterward, unless the requester withdraws earlier. To withdraw, email support@trainerrr.xyz with "Remove my Android launch request." Trainerrr does not add these addresses to a general newsletter.
Some backup or operational copies maintained by service providers may take additional time to expire or be overwritten.
Trainerrr uses account authentication and its providers' security controls to protect user data. No storage or transmission method is perfectly secure, but these controls reduce the risk of unauthorized access, loss, misuse, or alteration.
Trainerrr is designed for a general fitness audience and is not intended for young children.
This policy may be updated when the app's features, service providers, or data practices change. The "Last updated" date at the top of the page will change at the same time.
For privacy questions or data requests, contact: privacy@trainerrr.xyz
