Trainerrr Privacy Policy

Overview

We use your data only to run Trainerrr and make it better. We never sell it, and we never use it to target you.

There are no ads, and no email goes to a group picked by how people use the app. We email you about your account, with a welcome email when you sign up, and we send occasional product updates about Trainerrr. You can unsubscribe from product updates with the link in any of them.

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 file storage.

This policy covers the current version of the app. Trainerrr will update this page if its features, services, or data uses change.

Information we collect

Category	Examples	Whether it is optional	Why it is used
Account data	Email address and authentication credentials handled through Supabase Auth. With Google or Apple sign-in, the name that provider shares, if any	Email is required to create and access an account	To register users, authenticate sessions, secure accounts, support password reset, and send account emails and occasional Trainerrr product updates
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, short notes, and saved-meal photos 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
Progress check-ins	Weekly bodyweight, a short note, and an optional progress photo when added by the user	Optional	To let users track their progress week by week
Connected health and fitness data	Weight, height, body-fat percentage, steps, active energy, workouts, the distance and heart-rate readings recorded during those 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
Notification settings	The device's push subscription, time zone, reminder times, and which notifications the user has turned on	Push notifications are sent only after the user allows them	To send meal and workout reminders and the daily summary the user chooses
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

How we use information

Trainerrr uses the information it collects only to provide the app's workout, food, goal, and planning features for your account, to find what is broken and improve the app, and to email you about your account and about Trainerrr. Trainerrr never sells user data, rents it, or shares it for advertising, never uses it to target you, and does not use it for academic or scientific research.

To create and manage user accounts.
To authenticate users and keep sessions secure.
To store profile data such as display name and avatar image.
To let users create workout plans, log workouts, log nutrition, and manage fitness goals.
To import the Apple Health or Health Connect categories a user enables and reconcile updates or source deletions.
To write food entries created in Trainerrr to the connected health platform only when nutrition export is available and the user enables it.
To complete requests sent through ChatGPT or another client connected to the Trainerrr MCP server.
To send one Android public launch notification to visitors who request it. This request is not a newsletter subscription.
To send a welcome email when an account is created, and occasional product update emails about Trainerrr, through Loops. Every product update email has an unsubscribe link. Product updates go to account holders who have not unsubscribed. Loops is not told what anyone does in the app.
To send the push notifications a user allows, such as meal and workout reminders and the daily summary, through OneSignal.
To provide exercise features, including optional muscle visualization support if enabled in the build.
To support account deletion and data cleanup when a user requests it from inside the app.
To count anonymous app, screen, workout and onboarding events in PostHog, so we can tell which features are used and which are broken. These counts carry no account identifier and are not retained across sessions.
To measure the remaining product usage and app error reports in PostHog against the account identifier, only after the user has explicitly consented to analytics sharing, so we can understand what breaks and make the app better.
To record, in PostHog, that a tool was called on the Trainerrr MCP server by a connected assistant: the tool's name and our own description of it, how long it took, whether it failed and in which category, which assistant application was connected, and a per-connection session identifier, all against the account identifier. What was passed to a tool and what it returned are never recorded, so workouts, meals, body measurements and journal text are not part of this. This measurement is how we tell which parts of the connector work, and it runs on our legitimate interest in operating and improving the service rather than on the in-app analytics consent toggle, which governs the app only.
To record, in PostHog against the account identifier, the rewards results our servers work out: how complete a day's food log was and whether its step target was met, training streak weeks, and achievements earned. These events carry no meal, workout, or body measurement details. Like the connector measurement above, they are recorded whether or not in-app analytics sharing is on.

Connected health data

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.

Body, Activity, Workouts, and Nutrition import are read permissions. Workouts remain import-only.
Workouts includes the distance and heart-rate readings recorded during a workout. Both are stored on the platform as their own records rather than inside the workout, so they are read alongside it to show a run's distance and its heart-rate curve. Neither is read outside the workouts a user has imported.
Nutrition export is a write permission used only to send meals created in Trainerrr to the selected platform.
Background health access is requested only after Background updates is enabled. Foreground synchronization remains available when background delivery is delayed or disabled.
Imported health records are stored in the user's Trainerrr account so they can appear in history, totals, statistics, nutrition calculations, and widgets.
When active energy is available from the health platform, Trainerrr uses it for exercise calories and does not add it to workout calorie estimates.
Imported records are read only in Trainerrr. Edit them in the source app.

Trainerrr does not use connected health data for advertising, data brokerage, credit decisions, employment decisions, insurance decisions, or medical diagnosis and treatment.

How information is shared or processed

Trainerrr does not use in-app advertising. In the app, it uses PostHog for two things: anonymous counts of a short list of app usage events, which are always on and carry no account identifier, and identified product analytics, which runs only after the user explicitly accepts analytics sharing and stops again if that consent is withdrawn.

Crash and error reports go to Sentry, and are sent for every user under legitimate interest rather than consent. They are anonymous unless the user has accepted analytics sharing, in which case they also carry the account identifier. A crash report can never contain a screenshot, a view hierarchy, a network request address, an IP address, or anything the user typed or recorded — those capture channels are switched off, not filtered afterwards.

User data is never sold, rented, shared for commercial gain, or shared for advertising, and it is not used for research. Information is processed by these service providers, each only for the purpose listed:

Supabase: used for account authentication, database storage, and storage of the images users add, such as avatars, progress photos, and saved-meal photos.
Cloudflare: hosts this website, the Trainerrr MCP server, and the service that sends notifications. Requests from a connected assistant pass through it, and it stores the sign-in grant for each assistant connection, which holds the account identifier and email address.
PostHog: used for anonymous app usage counts, and — after consent — for product analytics tied to the signed-in account identifier. It is also used to record which tools a connected assistant calls on the Trainerrr MCP server, and the rewards results described above, tied to the same identifier, without the contents of those calls. PostHog never receives a name, email address, body measurement, nutrition entry, or user-created content.
Sentry: used for crash and error reports from the app and from the Trainerrr MCP server. Sentry receives the error, where in the code it happened, the app version and the device model, and — only after consent — the signed-in account identifier. Reports from the MCP server carry no account identifier and nothing passed to or returned by a tool, but do include request timings and, during assistant sign-in, the browser's user agent. Sentry never receives a name, email address, body measurement, nutrition entry, or user-created content.
Loops: sends Trainerrr's emails to account holders, which are a one-time welcome email and occasional product updates. For the welcome email, Loops receives the email address and the account identifier. For product updates, Loops holds the email address, the name the user gave Trainerrr or their Google or Apple account shared, and the account identifier. Loops is never told what anyone does in the app: no meals, workouts, body measurements, connected assistants, or activity dates.
OneSignal: sends push notifications. It receives the signed-in user's account identifier, the device's push subscription and basic device details, and the text of each notification, which can name a workout plan or summarise the previous day. Older versions of the app also sent the account's email address. The current version does not, and Trainerrr does not send email through OneSignal.
Discord: when an account is created, its account identifier is posted to a private Discord channel so the Trainerrr team can see new sign-ups. No email address or name is posted. A daily summary posted to Discord carries only totals, such as the number of new accounts.
Tally: hosts the support form on this website. It receives what a person types into the form, such as their email address and a description of the problem.
Google and Apple: when a user signs in with Google or Apple, that provider confirms the user's identity and shares their email address with Trainerrr, and may share their name.
Open Food Facts: used when users search for food nutrition data. Its database is made available under the Open Database License (ODbL).
RapidAPI muscle visualizer feature: optional and only used if the app build is configured with a muscle visualizer API key.
Apple Health and Health Connect: user-controlled platform stores that provide or receive only the categories authorized on that device.

Trainerrr does not authorize any of these providers to use that information for their own commercial or research purposes.

An AI assistant you connect, such as ChatGPT or Claude, is not one of these providers. It sends Trainerrr the details you ask it to act on, and it receives what Trainerrr returns, such as your logged meals, workouts, or targets. The assistant's provider handles that data under its own privacy policy.

Retention and deletion

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. It also removes the avatar, progress photos, and meal photos stored for the account, and the account is not deleted until they are gone.

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.

Deleting an account does not automatically remove the contact held by Loops, the push profile held by OneSignal, or the sign-in grant Cloudflare stores for a connected assistant. To have them removed, email privacy@trainerrr.xyz. The Discord sign-up message carries only the account identifier, which no longer points to anyone once the account is deleted.

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.

User controls

Users can update their password from inside the app.
Users can update their display name and avatar.
Users can delete workout and nutrition content they create.
Users can enable or disable connected-health categories independently for the current device.
Users can sync manually, open system settings, disconnect the current device, or separately remove imported health data.
Users can revoke Apple Health or Health Connect permissions in the device's system settings.
Users can request full account deletion through the in-app account deletion flow.
Users can turn analytics sharing on or off at any time in Settings › Privacy.
Users can unsubscribe from product update emails with the link in any of them.
Users can turn push notifications on or off inside the app.
Users can erase the analytics data recorded for their account at any time from Settings › Privacy, without deleting the account.
People who requested the Android notice can withdraw before launch by emailing support@trainerrr.xyz.

Security

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.

Children

Trainerrr is designed for a general fitness audience and is not intended for young children.

Changes to this policy

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.

Contact

For privacy questions or data requests, contact: privacy@trainerrr.xyz