This page gives a plain-language summary of the information Trainerrr uses, what it does not access, and what controls are available inside the app.
| 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 | Used for account access, security, and password recovery |
| Profile details | Optional display name stored in user metadata | Optional | Used to personalize the profile experience inside the app |
| Profile image | Optional avatar image uploaded by the user | Optional | Used to display the user’s 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 | Used to power necessary planning, workout logging, nutrition logging, and progress history |
| User-created exercise content | Custom exercise entries created by the user | Optional | Used to support personal exercise libraries and search |
| Consented analytics data | PostHog identifier plus limited app usage data after the user accepts analytics sharing | Optional | Used to understand whether key app flows are working and to improve the product |
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.
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.
Users can also update profile details, change passwords, decide whether to accept analytics sharing during authentication, and manage workout and nutrition content inside the app.
