FLEX Privacy Policy
Effective October 29, 2026
FLEX is a workout tracking app for saving routines, workout history, body metrics, and optional AI-generated workout plans. This policy explains what data FLEX handles, why it is used, and how deletion works.
Data We Collect
- Account data: email address, account identifier, display name, authentication provider, password hash for password accounts, and session tokens.
- Workout data: routines, templates, custom exercises, workout logs, sets, reps, weights, time, notes, and sync timestamps.
- Body metrics: body weight, body fat percentage, metric dates, and related notes you enter.
- AI data: guided workout preferences, optional notes and refinement requests, compact exercise catalog data, generated plans, import status, and daily AI usage counts.
- Sharing data: shared routine and program snapshots, sender identity, share codes and their expiration or revocation status, recipient delivery and saved-copy records, lookup attempts, and content reports and moderation decisions.
- Bug reports: the message, optional steps, and optional images you submit, plus your account email, user ID, app version, current app page, user agent, submission time, triage status, and email delivery status. Unless you turn off Include device details, a report also includes device and browser type, operating system version, screen and window size, language and time zone, network status, theme and unit settings, plan status, whether a workout was active, and the screens, controls, and errors from your current session.
- Subscription data: FLEX Pro product, entitlement status, purchase platform, renewal and expiration status, anonymous transaction identifiers, and promotion-code redemption status. FLEX does not receive your full payment-card details.
- Optional analytics data: after you turn on Product Analytics, FLEX collects a random app-install identifier, app interactions such as screens viewed and workout actions, session identifier, platform, app version, event time, and your account ID when signed in.
- Local preferences: theme, avatar choice, weight units, onboarding status, and sync server URL preferences stored on your device.
How We Use Data
FLEX uses your data to authenticate your account, sync your workout history across devices, restore backups, display progress, import workout files, generate workout plans when you request AI assistance, and investigate bug reports you choose to submit.
Sync And Third-Party AI Sharing
When sync is enabled, your workout logs, routines, custom exercises, body metrics, and sync metadata are sent to the FLEX sync server. Before your first AI workout request, FLEX asks for your permission to send your typed or dictated description, selected goals and training preferences, optional notes, and compact exercise catalog through a Supabase Edge Function to OpenRouter and its AI model providers, such as OpenAI. Refinements also include your current plan and requested changes. Permission covers workout generation and refinement for this account on this device. You can withdraw it using Reset permission in Data & Privacy; FLEX will ask again before your next AI request. Canceling the permission prompt sends no AI request. Do not include sensitive medical information in your request. You can continue using the rest of FLEX without AI.
Routine And Program Sharing
When you choose Share, FLEX stores a snapshot of your routine or program and creates a five-character code and a QR link. Anyone with the active code or link who signs in with a verified FLEX account can preview the snapshot and choose to save it. Share codes only with people you intend to give access; they can forward a code or link to others. There is no public feed or browsable user directory, and copying a code does not send a notification or automatically add the content to another person's library.
The snapshot includes your sender identity, the routine or program name, exercise definitions, training targets, warm-ups, supersets, rest timers, and HIIT settings. Personal notes, saved weights, workout history, body measurements, and private media URLs are excluded. FLEX stores code and delivery records, saved-copy status, and lookup-attempt counts to provide sharing, prevent duplicate imports, and limit abuse.
Codes expire after seven days, and Stop sharing prevents further lookups using that code. Expiration or revocation does not erase stored delivery records or independent copies already saved by recipients. Saved copies can remain after you change the original or delete your account. Earlier app versions used email or username delivery; existing delivery records, sharing usernames, and blocked-sender preferences remain for compatibility. Deleted accounts' former usernames remain reserved without their account identifier to prevent impersonation.
Shared Content Reports
When you choose Report content and confirm a report, FLEX stores the shared copy, sender identity, your account identifier, report reason, and any details you provide in a private moderation queue. Reports are accessible to authorized FLEX administrators, not to the reported user or other app users. Reporting hides that delivery without deleting independent library copies. Reports about code imports do not block the sender or prevent you from opening their other codes. Reports about older direct deliveries retain their original sender-blocking behavior. Associated reports are removed if either account is deleted. Moderation decisions and sharing suspensions are stored to enforce the community rules; administrators can remove shared content, revoke its codes, or suspend a sender's sharing access.
Bug Reports And Email Delivery
When you submit a bug report, FLEX sends it through a Supabase Edge Function, stores it in the FLEX database, and emails it through Resend to FLEX support, including your account email and user ID so support can reply. Before you send a report, Report a Bug shows the device details it will include, and you can turn them off. Device details are collected on your device during the current session and are not sent anywhere unless you include them in a report. To investigate and fix reported problems, FLEX uses an automated assistant from Anthropic: the report message, steps, images, and device details, but not your name, email, or user ID, are processed by Anthropic’s Claude models under Anthropic’s commercial terms. Fixes are reviewed by FLEX before release. When a fix ships, FLEX may email you once to let you know.
Optional Product Analytics
FLEX does not create an analytics identifier or collect product-analytics events unless you turn on Product Analytics in Profile > Data & Privacy. It is off by default, and FLEX does not show a prompt asking you to enable it. If turned on, FLEX uses the analytics data listed above to understand feature use, diagnose product issues, and improve the app. FLEX does not use this information for advertising or to track you across other companies’ apps or websites. You can turn it on or off at any time in Profile > Data & Privacy. Turning it off stops future collection and removes the queued events and analytics identifier stored on that device. Analytics already received by FLEX is retained until account deletion or an applicable deletion request.
Payments And FLEX Pro
Apple processes iOS purchases, and RevenueCat processes subscription entitlement information for iOS and web purchases. FLEX receives entitlement and transaction status needed to unlock Pro, restore purchases, prevent fraud, and provide support. Payment providers handle payment credentials under their own privacy policies. Tester codes are stored as one-way hashes; FLEX records the account that redeemed a code and the resulting access expiration date.
Retention
Server sync and linked analytics data are retained while your account remains active. Local data remains on your device until you delete it, uninstall the app, clear browser storage, or delete your account from inside FLEX. Stored bug reports, including their images and device details, are deleted from the FLEX database 90 days after submission. Copies emailed to support are retained in the support mailbox and by the email delivery provider as needed to investigate and respond to the report.
Account Deletion
You can delete your account in FLEX from Profile > Data & Privacy > Delete Account. Deletion removes your server user row, stored sync payload, active sessions, linked provider records, auth rate-limit records, AI usage records, linked analytics events and identifiers, RevenueCat customer profile when configured, and stored bug reports with their images and device details. The app also removes local workouts, body metrics, routines, templates, custom exercises, AI history, analytics identifiers, and profile preferences for the signed-in account on that device. Deleting a RevenueCat customer does not cancel an Apple subscription; manage or cancel the subscription in your Apple Account. Deleting an account does not automatically delete bug reports already delivered to the support mailbox.
Fitness And Health Notice
FLEX is for general fitness tracking and workout planning. Body metrics and AI-generated plans are not medical advice. Use your judgment and consult a qualified professional before making medical, injury, nutrition, or treatment decisions.
Security
FLEX uses HTTPS for hosted services, password hashing for password accounts, session tokens for authenticated requests, CORS allowlists, request size limits, and rate limits for authentication and AI usage. No internet-connected service can be guaranteed completely secure.
Contact
For privacy questions, support, or deletion help, contact support@duffyadams.com.