Trainerrr uses outside services for account access and storage, hosting, food search, optional health connections, analytics, email, push notifications, and exercise visualization. Trainerrr uses them only to run and improve the app. Your data is never sold or used to target you.
| Provider | Why it is used | What it may process | What that means for users |
|---|---|---|---|
| Supabase | Authentication, database, and file storage | Email for account auth, optional profile data, workout and nutrition records, goals, health integration preferences, and imported health data | Supabase is the main service used to run sign-in, store app data, and keep profile files available |
| Cloudflare | Hosting for this website, the Trainerrr MCP server, and the service that sends notifications | Requests from a connected AI assistant, and the sign-in grant for each assistant connection, which holds the account identifier and email address | Requests from ChatGPT, Claude, or another connected assistant pass through Cloudflare on their way to your account |
| PostHog | Anonymous app usage counts, consented product analytics, and MCP connector tool-usage measurement | A short list of app usage events with no identifier attached; and, only after the user explicitly accepts analytics sharing, the remaining in-app events against the signed-in user identifier. Separately, for the MCP connector: the name of each tool a connected assistant calls, our own description of that tool, how long it took, whether it failed and in which category, which assistant application was connected, and a per-connection session identifier, against the signed-in user identifier. Also against that identifier, the rewards results Trainerrr's servers work out, such as streak weeks and achievements earned. No email address, name, body measurement, nutrition entry, or user-created content is ever sent, and the arguments and results of MCP tool calls are never sent | PostHog always receives enough to count which features are used. It can only recognise a returning person in the app once the user opts in, which they can do or undo at any time in Settings › Privacy. Connector tool-usage measurement is separate: it tells us which parts of the connector work, carries no workout, meal or journal content, and is not covered by that in-app toggle |
| Sentry | Crash and error reporting | The error and where in the code it happened, the app version, and the device model; and, only after the user accepts analytics sharing, the signed-in user identifier. Never a screenshot, a view hierarchy, a network request address, an IP address, an email address, a name, a body measurement, a nutrition entry, or user-created content | Crash reports are sent for every user so that faults get fixed for everyone, and are anonymous unless the user opts in to linking them. Retained for 30 days |
| Loops | Email: a one-time welcome email at sign-up and occasional product updates | For the welcome email, the email address and the account identifier. For product updates, the email address, the name the user gave Trainerrr or their Google or Apple account shared, and the account identifier. Never meals, workouts, body measurements, connected assistants, or activity dates | Product updates go to account holders who have not unsubscribed, never to a group picked by how people use the app. Every product update has an unsubscribe link |
| OneSignal | Push notifications | The account identifier, the device's push subscription and basic device details, and the text of each notification. Older versions of the app also sent the account's email address; the current version does not | Push notifications are sent only after the user allows them, and can be turned off in the app |
| Discord | Private alerts for the Trainerrr team | The account identifier of each new sign-up, and a daily summary of totals such as the number of new accounts | No email address, name, or app content is posted |
| Google and Apple | Optional sign-in | Confirmation of the user's identity, their email address, and their name if the provider shares it | Used only when the user chooses to sign in with Google or Apple |
| Tally | The support form on this website | What a person types into the form, such as their email address and a description of the problem | Only used when someone sends a support request through the form |
| Open Food Facts | Food search and nutrition reference data | Food search terms and the food records selected by the user | It supplies reference nutrition data; selected foods can then be saved in the user's Trainerrr account |
| Apple Health | Optional health data connection on iOS | Only the Body, Activity, Workouts, or Nutrition categories the user authorizes; background delivery is used only when enabled | Apple Health is a user-controlled source and, for opted-in nutrition export, destination. Trainerrr does not export workouts |
| Health Connect | Optional health data connection on supported Android devices | Only the Body, Activity, Workouts, or Nutrition categories the user authorizes; background reads are used only when enabled | Health Connect is a user-controlled source and, for opted-in nutrition export, destination. Availability depends on the Android device |
| RapidAPI muscle visualizer feature | Optional exercise visualization support when the build is configured with an API key | Visualization requests derived from selected muscle groups and rendering options such as color, gender, image size, and background | The feature is optional and does not send email addresses or full workout log entries in the current app version covered by this page |
Apple Health and Health Connect are device health stores, not Trainerrr's cloud database. You choose access by category on each device. Trainerrr requests nutrition access and background updates separately when those features are available in the installed release.
Trainerrr imports authorized body, activity, and workout information. It does not export workouts. Disconnecting stops future sync; removing imported history from Trainerrr is a separate action.
Trainerrr includes an optional muscle visualization integration that is only active when that feature is enabled in the app build. When active, it uses selected muscle groups and display settings to request visual output from the provider.
In the current version covered by this page, the optional visualization feature does not send email addresses or full workout log payloads.
