How Trainerrr handles your data
This page explains what information Trainerrr uses, what the app does not access, and which controls you have.
This page explains what information Trainerrr uses, what the app does not access, and which controls you have.
| Type of information | Examples in the app | Required? | How it is used |
|---|---|---|---|
| Account information | Account email used for sign-up, sign-in, and password reset | Required to create and access an account | Lets you sign in, protect your account, and reset your password |
| Profile details | Optional display name stored in user metadata | Optional | Shows your chosen name on your profile |
| Profile image | Optional avatar image uploaded by the user | Optional | Shows your avatar in the app |
| Workout, nutrition, and goal data | Workout plans, workout logs, goals, exercise selections, reps, weights, calories burned, food names, servings, calories, macros, fiber, and sugar | Used only when these features are used | Provides workout planning, logging, food tracking, and progress history |
| Connected health and fitness data | Selected body measurements, steps, active energy, workouts, source details, and optional nutrition samples from Apple Health or Health Connect | Optional and controlled by category on each device | Provides activity, workout, food, progress, calorie, and widget features |
| MCP and ChatGPT app requests | Workout, food, target, journal, progress check-in, and image reference details users choose to send through the connected MCP client | Optional | Completes the requested Trainerrr action for the signed-in account |
| User-created exercise content | Custom exercise entries created by the user | Optional | Adds the exercise to your personal library and search results |
| Anonymous usage counts | That the app was opened, a screen was viewed, a workout was started or finished, or onboarding was completed. No identifier, no location, and nothing about you or your training | Always on | Counts which features are used, so broken or unused parts of the app can be found. The identifier is discarded when the app closes, so these counts cannot be linked to you or joined up between sessions |
| Consented analytics data | The same usage events plus the remaining in-app events and app error reports, linked to your account identifier | Optional, on or off any time in Settings › Privacy | Helps Trainerrr check whether app flows work and investigate errors |
Food search uses Open Food Facts nutrition data. Selected foods are saved to the user’s account so they can be reused in future logs. MCP clients only receive the tool results needed for the request the user made.
Trainerrr includes an account deletion flow. In the current version, deleting an account removes the authenticated user and deletes user-linked workout data, nutrition data, goals, and custom exercises. The app also attempts to remove the stored avatar file during deletion.
Deleting an account also deletes the analytics profile held for it and the events recorded against it.
Users can also update profile details, change passwords, turn analytics sharing on or off at any time in Settings › Privacy, erase the analytics data recorded for their account without deleting the account, and manage workout and nutrition content inside the app.
For connected health, users can manage each category in Profile, disconnect the current device while keeping imported history, or use the separate removal action to delete health-sourced workouts and meals from Trainerrr. System permissions can also be revoked in Apple Health, iOS Settings, or Health Connect.