Service providers used by Trainerrr
Trainerrr uses outside services for account access and storage, food search, optional health connections, analytics, and exercise visualization.
Current service providers
| 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 |
| PostHog | Anonymous app usage counts, consented product analytics and error reporting, 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 and app error reports 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. 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 |
| 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 |
About connected health platforms
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.
Current scope
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.
About the optional visualization feature
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.
Current scope
In the current version covered by this page, the optional visualization feature does not send email addresses or full workout log payloads.
Updates to this list
- If Trainerrr starts using additional providers, this page will be updated.
- If a provider handles new categories of user information, the privacy policy will be updated as well.
- If a feature becomes optional or is removed, this page will be adjusted to match the live app version.