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, and manage fitness goals. The app uses Supabase for authentication, database storage, and avatar file storage.
This policy reflects the current version of the app. If Trainerrr later adds new features, services, or data uses, this page will be updated to reflect those changes.
| 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 |
| 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 |
| Consented analytics data | PostHog analytics identifier, sign-in state, and limited app usage events after the user explicitly accepts analytics sharing | Optional and only enabled after explicit consent on the sign-in or sign-up flow | To understand whether core flows are working and improve app reliability and product decisions |
All information collected by Trainerrr is used exclusively to provide necessary personal workout, nutrition, goal, and planning features to the individual user who provided it. Trainerrr does not use user data for any commercial purpose, advertising, or academic and scientific research of any kind.
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.
The app includes an account deletion flow. In the current version, deleting an account removes the authenticated user and deletes user-linked workout plans, workout days, workout day exercises, workout logs, workout log entries, nutrition items, nutrition logs, user goals, and custom exercises. The app also attempts to remove the stored avatar file during account deletion.
Some backup or operational copies maintained by service providers may take additional time to expire or be overwritten.
Trainerrr uses account authentication and service-provider security controls to protect user data. No method of storage or transmission is perfectly secure, but reasonable steps are taken to reduce 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. When that happens, the “Last updated” date at the top of this page will also change.
For privacy questions or data requests, contact: privacy@trainerrr.xyz
