FWB Training Privacy Policy

Who this policy covers

FWB Training is a client service operated by Fitness with Benjamin. It is available to authorized coaching clients through the iOS app and Fitness with Benjamin web portal. This policy explains how information is handled when a client uses either experience.

Information we process

Depending on the features a client chooses to use, FWB Training may process:

• Account information: email address, account identifier, and the name or profile information connected to the coaching account.
• Fitness questionnaire information: the name and email address supplied with the questionnaire, contact and scheduling details, fitness goals, training history, lifestyle information, readiness answers, and health, pain, injury, or surgery information a person chooses to provide.
• Training and fitness information: assigned programs, saved generated workout plans, planned workout dates, custom workouts, exercise names, sets, repetitions, weight, effort, timers, cardio entries, workout history, and personal records.
• Health and progress information: readiness and weekly check-ins, pain or limitation notes, body weight, body-fat percentage, muscle mass, DEXA lean mass, body measurements, progress notes, and calorie or macro targets.
• User content: DEXA scan reports, food barcodes and food-label photos a client chooses to scan or upload, profile photos, progress photos, form-check photos or videos, workout notes, form-check notes, private workout comments exchanged with the coach, and optional gym reviews and photos.
• Notification information: notification preferences and an app-specific device token used to deliver notifications.

How information is used

Information is used to authenticate clients, display assigned coaching programs, save and synchronize workouts and planned workout details across signed-in devices, show planned workouts to the authorized coach, recover unfinished workouts, calculate and show progress, propose measurements from an uploaded DEXA report for client review, retrieve nutrition facts from an optional food barcode or food-label photo, provide readiness and macro features, deliver requested notifications, support coach feedback, maintain app security, and respond to support or privacy requests. It is not used for third-party advertising or cross-app tracking.

Storage and service providers

Authentication, coaching records, synchronized workout data, private media, uploaded DEXA reports, notifications, and authenticated client copies of fitness questionnaires are handled through the Fitness with Benjamin Supabase project. Supabase acts as a service provider for database, authentication, private file storage, and related infrastructure. Questionnaire submissions are also sent through Google Apps Script to a restricted Google Sheet used by Fitness with Benjamin to review responses and connect them to the correct coaching client. A questionnaire is linked to a signed-in client profile only when its email address exactly matches the verified account email. Limited preferences and unfinished workout data may also be stored on the client’s device for settings, timers, offline recovery, and synchronization.

When a questionnaire is linked to a client account, selected answers may be used to fill profile fields that are still blank, such as name, phone number, fitness goal, or available home equipment. Existing client or coach-entered profile information is not replaced automatically.

If a client chooses automatic DEXA import, the uploaded report is sent to OpenAI to extract a proposed scan date, body weight, body-fat percentage, and lean mass. OpenAI processes the report as a service provider under its applicable API terms and data-retention practices. Automatic extraction can be wrong, so the proposed values are shown to the client for review and editing before they are saved to the progress profile. The feature is optional; clients may enter measurements manually instead.

If a client chooses food-label scanning, the selected photo is sent to OpenAI to propose the product name, serving, calories, protein, carbohydrates, and fat. The photo is processed transiently and is not retained in the food library. Automatic extraction can be wrong, so the values are shown for review and editing before the food log is saved. After confirmation, the reviewed food details—not the photo—are added to a shared food-label library available to authenticated clients.

If a client chooses barcode scanning, the barcode number is checked against the shared food library and may be sent to Open Food Facts to retrieve product and nutrition details. Open Food Facts provides its database under the Open Database License (ODbL). The retrieved values are shown for review and editing before the food log is saved. After confirmation, the reviewed barcode and food details may be added to the shared food library for other authenticated clients.

Profile photos are stored privately and shared between the web and iOS apps for the same account. DEXA reports, progress media, and form-check media are stored in private storage and accessed through time-limited links. Exercise demonstration links may open YouTube outside the app; use of YouTube is governed by Google and YouTube’s own terms and privacy practices.

Clients can import workout-history CSV files exported from Fitbod or Hevy. The selected file is parsed on the client’s device; the file itself is not uploaded. The client reviews the set count before saving. Imported exercise names, dates, sets, repetitions, weights, and optional notes are saved to the FWB account and are available to the client and authorized coach like other workout logs. Imports do not create gym check-ins or Community posts.

Nearby gym search is optional and requests location permission only when the client searches. The search sends a rounded location to OpenStreetMap’s Overpass service to retrieve public gym and hotel-gym place data; a rounded search area is cached for up to 24 hours. The exact device search location is not saved. If a client chooses to add a missing place at their current location, that place’s coordinates and name become visible to signed-in clients. Gym reviews and uploaded gym photos are visible to signed-in FWB clients with the author’s Community nickname and avatar, without displaying their email or invite code. Photos are re-encoded before upload and stored in private storage with time-limited links. Clients can edit or delete their own review and photos.

Apple Health

Apple Health integration is optional. If a client grants permission, FWB Training writes completed workout type, start and end time, duration, and any distance or calories the client entered. Clients may separately allow FWB to read selected workouts (type, dates, duration, active calories, distance and average heart rate), daily steps, sleep duration, resting heart rate, heart-rate variability and body weight. Readings are shown on the iPhone. A separate, initially off choice for each category allows the last 30 days of selected records, dates, source app and record identifiers to sync to the existing FWB account service, where the client and authorized coach can view them on the web. Turning off a sharing category deletes its imported FWB data without changing Apple Health records or manual FWB logs. Sync runs when FWB is open or active. Clients can optionally enable automatic workout import, which lets Apple Health notify FWB of completed workouts in the background and refresh selected readings. iOS controls delivery and may delay it; opening FWB retries unfinished syncs. Imported workouts appear in Logs with their source, and account or coach sharing still requires the separate category choice. Clients can separately enable on-device workout detection alerts. The notification uses generic text without workout measurements; FWB stores per-account notification preferences, the opt-in time and workout identifiers on the device to avoid repeat alerts. This does not detect exercise from raw motion or provide continuous background monitoring. The Watch can optionally display live heart rate; its measurement session is discarded to avoid duplicating the workout saved by the iPhone. Health data is never used for advertising, marketing, or data mining, and is not sold or shared with data brokers. Apple Health access can be changed at any time in iPhone Settings.

Google Health, Fitbit, and Pixel Watch

Google Health connectivity is optional and requires the client’s consent in Settings. When enabled, FWB Training reads available exercise records from the connected Google Health account, including Fitbit and Pixel Watch workouts. These records can include activity type, workout date, start and end times, duration, total calories, distance, and average heart rate. The records are stored in the Fitness with Benjamin Supabase project and displayed in Saved Logs to the client and their authorized coach. FWB Training does not send workouts back to Google through this connection.

Automatic sync checks the most recent 30 days of exercise records approximately every 15 minutes. Clients can pause automatic sync, sync on demand, or disconnect in Settings. Disconnecting stops future imports and removes FWB’s stored connection credentials; previously imported workout records remain in Saved Logs unless deletion is requested. OAuth credentials are stored server-side and are not exposed in the client app. Google may require the client to reconnect if consent expires or is revoked.

Google Health data is not used for advertising, marketing, credit decisions, data mining, or training AI models, and is not sold or shared with data brokers. FWB Training’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. A client can also revoke access from the security settings of the connected Google Account or contact us to request deletion.

Retention and deletion

Coaching records are retained while needed to provide the service, maintain legitimate business records, resolve disputes, and meet legal obligations. Retention may vary by record type. A client may request access, correction, export, or deletion of their account and associated personal data by emailing fwb@benjaminbenz.com. We may verify the request before completing it. Data that must be retained for legal, security, or fraud-prevention reasons may be kept only for the required period.

Security and choices

We use reasonable administrative and technical safeguards designed to protect client information. No method of storage or transmission is completely secure. Clients can decline Apple Health access, pause or disconnect Google Health in Settings, disable notifications, choose manual entry instead of automatic DEXA or food-label extraction, change or remove their profile photo in Settings, remove uploaded progress photos within the app where available, sign out, or contact us about their information.

Children

FWB Training is not directed to children under 13. If information from a child under 13 was provided without appropriate authorization, contact us so it can be reviewed and removed.

Changes and contact

We may update this policy as the app or legal requirements change. The effective date above will be updated when material changes are published. Questions or privacy requests can be sent to fwb@benjaminbenz.com.

FWB Training is not an emergency or medical service. For immediate danger or urgent medical concerns, contact the appropriate local emergency or medical service.