Last updated: July 14, 2026
This policy describes what information TrainerLinq ("we," "us," "the App") collects, why, and who we share it with. It's written to match exactly what the app actually does — not a generic template. If you have questions, contact us at support@trainerlinq.com.
TrainerLinq connects two kinds of users: clients (people tracking their fitness/nutrition and working with a coach) and trainers (coaches who manage clients, get paid for sessions, and sell affiliate-linked products). Both roles are covered by this policy.
Account information: name, email address, phone number (optional), your role (client or trainer), and a profile photo if you upload one.
Health and fitness data (only from clients and only what you choose to log): body weight, height, body measurements, progress photos, food and water logged each day, nutrition targets set by you or your coach, workouts completed, and exercise history. Progress photos are stored privately — only you and your actively-linked coach can ever see them; we do not use them for any purpose other than displaying them back to you and your coach.
Trainer business information: bio, certifications, specialties, hourly rate, gym locations, and public gallery photos — this is information you choose to publish to be discoverable by clients, and it is shown publicly in the marketplace.
Communications: messages you send to your coach or client through the in-app chat.
Payment information: when a client pays a trainer for a session or buys something in the store, payment is processed by Stripe. We never see or store your card number — we only store the amount, timestamps, and Stripe's own reference IDs for that transaction, so we can show you a receipt/history and handle refunds.
Device and usage information: a push-notification token (so we can notify you about messages, accepted requests, and payments), and basic product-analytics events (e.g. "logged a meal," "sent a coaching request") tied to your account, so we can understand which parts of the app are used and fix what's broken.
Crash and error reports: if the app crashes or hits an unexpected error, technical details (what screen you were on, the error message, device type) are sent to our crash-reporting tool so we can fix the bug. This is not used to build a profile of you.
We use a small number of service providers to run the app. Each only receives the data it needs to do its specific job:
| Provider | What they receive | Why |
|---|---|---|
| Supabase | All app data (it's our database, auth, and file storage host) | Hosting the entire backend |
| Stripe | Payment amounts, card details (directly, we never touch them), billing name | Processing payments and trainer payouts |
| USDA FoodData Central / Open Food Facts | The food name or barcode you search for (no account info) | Nutrition lookup |
| Expo | Your device's push token | Delivering push notifications |
| Sentry | Crash/error technical details | Fixing bugs |
| PostHog | Anonymized-where-possible usage events tied to your account ID | Understanding app usage |
We do not sell your data. We do not share your health/fitness data with advertisers. We do not use your data to train third-party AI models.
This is enforced at the database level (Postgres Row-Level Security), not just hidden in the app's UI — even a direct API request can't bypass it.
We keep your data as long as your account is active. If you delete your account, your personal data is deleted immediately, except where the law requires us to keep financial records longer (typically 7 years for payment records, kept by Stripe as the payment processor of record).
TrainerLinq is not directed at children under 16, and we don't knowingly collect data from them.
If we make a material change to this policy, we'll notify you in the app before it takes effect.
Trainerlinq 1332 S Windy Ridge Dr, Spanish Fork, UT 84660 support@trainerlinq.com