Service Providers Used by Trainerrr
Trainerrr relies on a small number of service providers to run core features such as authentication, storage, and optional 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 display name, optional avatar path and file, workout plans, workout logs, goals, and custom exercises | Supabase is the main service used to run sign-in, store app data, and keep profile files available |
| 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 reflected by this page |
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 reflected by this page, the optional visualization feature does not send email addresses or full workout-log payloads.
If this list changes later
- 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.