Privacy Policy

FlexForce X provides training, nutrition, recovery, and wellness guidance. This policy explains how we collect, use, disclose, retain, export, and delete information in the web app, iOS app, Android app, and support systems.

FlexForce X is not a medical service. Readiness, movement-caution, recovery, nutrition, and training-load signals are wellness and performance signals. They are not diagnoses, treatments, injury predictions, or substitutes for professional medical advice.

We may collect account details, profile and onboarding answers, training history, workouts, nutrition entries, check-ins, wearable data and Apple Health or Google Health data you choose to connect, location context you permit, device identifiers, billing entitlement state, support requests, consent records, and app usage or error diagnostics.

Some information can be sensitive, including health, fitness, genetic, body-composition, nutrition, psychology, location, and calendar-context data. Optional integrations remain optional and can be disconnected where the app provides that control.

We collect information directly when you create an account, answer onboarding questions, enter workouts, meals, check-ins, measurements, messages, support requests, or payment choices, and when you change consent or privacy settings.

We also collect information automatically when you use the app, including app events, device and build details, crash diagnostics, security records, and service logs. With your separate permission, we receive data from device capabilities and connected services such as Apple Health, Google Health, calendars, wearables, location services, camera capture, app stores, and payment providers.

In the iOS and Android apps, FlexForce X may process native app data such as push notification tokens, device tokens used for secure mobile sync, app version/build details, crash and error diagnostics, trial or support tickets, subscription entitlement records, and app settings. Push tokens are used to deliver reminders, nudges, and account or product notifications. We do not use push notification tokens for advertising.

On iOS, Apple may process App Store, StoreKit, Apple Push Notification service, and user-controlled HealthKit permission flows. On Android, Google Play and Firebase Cloud Messaging may process app distribution, billing, purchase verification, push delivery, and related device or entitlement metadata.

Optional voice input can be used to dictate workout, meal, supplement, journal, and other notes. Depending on the device and speech-recognition service, the audio may be processed on the device or transmitted to the operating-system or browser speech-recognition provider, including Apple or Google, for real-time or ephemeral transcription. FlexForce X receives the resulting transcript when you save it. You can always type instead.

Normal voice-to-text features do not intentionally retain the original audio in FlexForce X. If the optional support-ticket capture feature is enabled and you affirmatively attach a voice recording, that recording is uploaded to the disclosed support system and retained with the support request under this policy.

Optional connected accounts can include Apple Health/HealthKit, Google Health, Google Calendar, Oura, and WHOOP. These integrations are used only after you connect them or grant the relevant permission. They may provide sleep, readiness, heart-rate, HRV, resting-heart-rate, strain, activity, body-measurement, workout, recovery, and calendar-context records, depending on the provider and permission you approve.

FlexForce X encrypts stored OAuth connection tokens where applicable. Disconnecting an optional integration stops future sync and removes the stored connection. Existing product records derived from an integration are handled through the export, deletion, retention, billing, security, and backup limits described in this policy.

We use information to create and adapt training plans, nutrition guidance, recovery guidance, reminders, safety constraints, account controls, billing access, support workflows, abuse prevention, reliability monitoring, and legally required privacy operations such as export and deletion.

AI systems may process minimized training, nutrition, recovery, and wellness context to generate app guidance. User-authored free text and coach context can still contain personal information even when direct identifiers are removed where practical. FlexForce X may use genuinely de-identified information for internal analysis, testing, and model development. We will seek separate express consent before using identifiable sensitive information for research or model development beyond what is necessary to provide the service.

Health-prediction functions that are still in internal research are not displayed to customers and do not change customer plans. We do not permit third-party general-purpose AI providers to train their base models on FlexForce X user data unless a separate reviewed agreement and user-facing disclosure expressly allow it.

If you grant location consent, FlexForce X may collect and store precise latitude and longitude records to create location context, identify routine or travel patterns, and support nearby food, movement, or supplement suggestions. Location consent is optional and is separate from the device permission.

Precise coordinates may be sent to Google Places for nearby-place searches and processed in the United States. Withdrawing location consent stops future consent-gated collection; existing location records remain subject to the export, deletion, retention, security, and backup limits described in this policy.

If you accept a coach or trainer assignment, FlexForce X may share only the data scopes you approve for that workspace. Depending on your choices, this can include profile, training, nutrition, recovery, check-in, progress, message, appointment, form, and media-review information, plus consented AI-generated coaching context. Coaches can add programs, tasks, forms, appointments, messages, and plan-adjustment proposals to your workspace.

You can review or withdraw coach-sharing consent in the app. Withdrawal stops new access through FlexForce X, but does not automatically erase records a coach must retain for completed services, payment, dispute, security, or legal obligations. The applicable offer or checkout should identify who provides a paid trainer service and any additional service terms.

We share data with service providers only for product operation, security, support, billing, communication, and reliability. Current active or optional processors include: Anthropic, Apple, Edamam, ExerciseDB (Zylalabs / RapidAPI), Firebase Cloud Messaging, Google AI (Gemini), Google Calendar API, Google Health API, Google Places API, Google Play, OpenAI, Oura, Pinecone, Resend, Sentry, Spoonacular, Stripe, Supabase, Twilio, Upstash, Vercel, WHOOP, YouTube Data API v3.

In particular, Supabase stores account and app data; Vercel hosts the application; Upstash supports rate limiting and background job coordination; Pinecone stores vector indexes; OpenAI may process minimized AI prompts and embeddings; Anthropic and Google AI (Gemini) may process the same relevant prompt context when selected for a model request; Resend processes transactional and lifecycle email; Sentry processes minimized error and crash diagnostics; Stripe processes web billing, eligible trainer-service payments, and connected-account payouts; Apple and Google Play process app-store purchases and entitlement notifications; Firebase Cloud Messaging and Apple Push Notification service deliver native push notifications; Google APIs process optional Google Health and Google Calendar connections; Google AI processes guided body-scan captures and body context only after the separate Body Scan permission; and Oura and WHOOP process data only when those optional wearable integrations are connected.

Payment card details are handled by Apple or Google Play for native in-app purchases and by Stripe for web billing or eligible external trainer services. FlexForce X stores transaction references and entitlement records such as product IDs, purchase tokens, checkout or subscription IDs, subscription state, and renewal periods, not full payment card details.

Some features use AI prompts, embeddings, retrieval indexes, and structured decision logs to generate user-facing guidance and keep recommendations consistent. We minimize direct identifiers where practical and exclude raw provider secrets, OAuth token ciphertexts, push-token secrets, and admin-only operational payloads from account exports.

AI and vector-memory features are consent-gated in the app where sensitive health, training, nutrition, recovery, psychology, wearable, or overseas processing context is involved. FlexForce X does not sell personal information or use health data for advertising.

The optional Google-assisted body scan sends two or three temporary full-body image captures together with height, weight, pose, and calibration context to Google AI (Gemini) to estimate measurements. Body images are inherently identifying and sensitive. FlexForce X does not intentionally save those captures after processing; confirmed measurement results and operational usage records may be retained under this policy. You can use manual measurement entry instead.

Before personalised AI processing begins, the app presents this information and records your express choice. The core categories that can be sent are: Training goals, history, schedule, equipment and workout preferences; nutrition preferences, allergies, meal and hydration details; sleep, recovery, activity and wearable signals; body measurements; injury, medication and medical-safety context; mood and wellbeing information you choose to provide; and free text you enter. We remove standard account fields such as your email and name where practical, but free text can still identify you.

• OpenAI: May receive the relevant text, structured wellness context and feature inputs to create personalised guidance; it also creates vector embeddings used for memory.
• Anthropic: May receive the same relevant text, structured wellness context and feature inputs when an Anthropic model is selected.
• Google AI (Gemini): May receive the same relevant text, structured wellness context and feature inputs when a Gemini model is selected. Full-body captures are sent only after the separate Body Scan permission described below.
• Pinecone: Stores the resulting profile text, vectors, related metadata and your internal account ID so FlexForce X can retrieve your memories and preferences.

Optional Google-assisted Body Scan: Google AI (Gemini) receives 2–3 full-body captures, height, weight, pose, calibration context and any fresh waist anchor only if you separately choose Google-assisted Body Scan and approve its capture disclosure. Manual measurement entry is available instead.

FlexForce X requires every AI or vector processor that receives personal data to process it only for the instructed service and to provide the same or equivalent privacy and security protection described in this policy. The production service checks the authoritative vendor register before a user-data transfer. A provider whose contract, DPA, privacy review, security review, and retained evidence are not approved is blocked from receiving user data.

OpenAI, Anthropic, or Google AI may be selected for a model request based on service availability and outages, capability, cost, or regulatory requirements. Providers that are not selected do not receive that request. Google AI receives body-scan images only after the separate Body Scan disclosure is approved. Pinecone has the distinct vector-memory role described above.

If you choose to connect Google Health, FlexForce X requests read-only Google Health API access to activity and fitness, health metrics and measurements, and sleep data. This can include steps, distance, energy, heart rate, resting heart rate, heart-rate variability, sleep sessions and stages, oxygen saturation, respiratory rate, weight, and body-fat data where those records are available in your Google account.

If you choose to connect Google Calendar, FlexForce X requests Google Calendar event access to read calendar commitments and create, update, or cancel FlexForce X workout events. Calendar data used for scheduling can include event title, start and end time, location, all-day status, reminder metadata, event links, and FlexForce X workout event identifiers.

Google-derived data is used only to provide user-facing FlexForce X features: wearable-informed readiness, recovery, sleep, training context, and calendar-aware scheduling. OAuth tokens are encrypted at rest, and Google-derived data is not sold, used for advertising, or used to train generalized AI models. We share Google user data only with service providers necessary to operate, secure, monitor, and support the product, or where required by law, and our use of Google user data is limited to the practices disclosed in this policy and Google API Services User Data Policy Limited Use requirements.

You can disconnect optional Google integrations in the app. Disconnecting stops future sync and removes the stored OAuth connection. Account export and deletion requests include Google-derived product records, subject to the retention, legal, billing, security, and backup limits described in this policy.

Some providers process information outside Australia. The primary FlexForce X Supabase database is hosted in Singapore, and providers including OpenAI, Anthropic when enabled, Pinecone, Stripe, Google, Vercel, Upstash, Resend, and Sentry may process information in the United States or other disclosed regions. We use contractual, security, minimisation, consent, and operational controls to manage overseas processing of personal and sensitive information. Binding processing terms, documented security controls, and retained governance evidence are required before a provider is authorised to receive personal data in production.

We retain information for as long as needed to operate the product, meet legal obligations, support safety and auditability, resolve disputes, and enforce agreements. Some derived or operational records may have shorter retention periods than account records.

You can request export or deletion in the app settings. Deletion removes or anonymizes account-linked product records and attempts to remove linked vector and storage data, subject to legal, billing, security, and backup limits.

You can also request account deletion from the web at flexforcex.fitness/account/delete.

Account exports are designed to include user-visible product records, consent records, mobile device state, notification records, connected-account status, wearable records, subscription entitlement records, support tickets, and message records where they relate to your account. Security secrets such as OAuth tokens, push tokens, raw provider payloads, and internal-only admin logs are excluded or redacted.

We use authentication, row-level access controls, encryption where appropriate, secret scanning, rate limiting, service-role isolation, monitoring, and data minimisation. No internet service can be guaranteed perfectly secure.

For privacy requests, export, deletion, correction, or complaints, contact privacy@flexforcex.fitness.