Your training data should not be a mystery.

Section 1

Overview

Dyne is a strength training product operated by FASHION ART 3.0 INC. The mobile app helps users create workouts, log sets, track recovery, monitor progress, manage subscriptions, receive weekly workout reports, optionally connect supported health platforms, and sync data across devices. This policy covers the Dyne marketing website and the Dyne mobile app, including optional nutrition features.

Dyne is a cloud-connected service. While the app may keep some information on the device for app performance, cached media, and active-session continuity, user account, profile, workout, template, preference, and related training data are generally synchronized to Dyne's remote backend services, including Supabase-backed infrastructure.

Dyne requires an online account and server storage for its core account, workout and synchronization features; it does not offer a local-only mode. Registration explains this storage. Optional health imports, selected-photo uploads and third-party AI meal analysis require separate permission. Account name and email are sign-in information, not access to your device Contacts.

Section 2

Information we collect

Account and sign-in information

We collect the information needed to create and secure your account, such as your email address and authentication credentials. If you choose Google or Apple sign-in, we may receive basic profile details associated with that provider, such as your name, email address, and profile image.

Training, health, and profile information

We collect information you enter to personalize the app and support workout generation, including your display name, sex, age or date of birth, height, weight, experience level, goals, workout frequency, preferred split, gym type, equipment inventory, training preferences, workout templates, and exercise preferences.

We also collect workout and progress records created through the app, such as sessions, exercise selections, sets, reps, weight, RPE, durations, workout history, body weight logs, body-fat entries, and body measurements.

Nutrition records, selected photos and optional AI analysis

If you use Nutrition, Dyne stores your nutrition goal, calorie and nutrient targets, dietary preferences, allergens, excluded foods, meal records, food quantities, saved meals and custom foods on its servers (Supabase). Records may include meal descriptions, analysis results and photos you choose to submit. Food searches and scanned product barcodes are sent to Dyne's food catalogue service to find products. Barcode search does not require sending a meal photograph to an AI provider.

If you explicitly allow AI meal analysis and request an analysis, your submitted meal photo or text description is uploaded to Dyne's servers and sent to Google Gemini to estimate foods, portions and nutrients. The request includes the response language; Dyne does not need to send your account email or complete workout history for this analysis. Your own photo or text can still contain personal information, so avoid including people, documents or unrelated private details.

Dyne stores the resulting food and nutrient estimates with your meal and may retain a result copy to avoid repeating the same analysis. You may decline AI and use manual entry or barcode search instead. The backend requires an explicit, versioned consent record; older automatic consent records do not authorize analysis. Google processes requests under the Gemini API terms, including applicable service-security and abuse-monitoring provisions. This notice does not promise zero retention by Google or other service providers.

App settings and feature preferences

We collect settings and preference data needed to run the app experience, such as units, language, notification preferences, timer audio and vibration preferences, keep-screen-on settings, adaptive replan and smarter workout analytics flags, weekly workout report settings, time zone, and delivery schedule preferences.

Subscription, referral, and device information

We collect subscription and entitlement status for Dyne Coach/Pro and Complete, workout and nutrition trial usage, purchase restoration and referral rewards. This can include product and transaction identifiers, referral activity, gym affiliate attribution tokens and device identifiers used to reduce abuse. Campaign links may provide campaign parameters and click identifiers (such as gclid, gbraid, wbraid or ttclid) used for attribution and campaign measurement with Firebase and RevenueCat. Enabled Android builds may send onboarding, paywall and purchase events to TikTok for campaign measurement. Dyne does not receive your full payment-card details from an app-store purchase.

Optional permissions and connected services

Dyne may request camera access to photograph meals or scan barcodes, and photo-library access to choose a meal or profile image. Only selected images are uploaded for the purpose explained in the app; Dyne does not upload your whole photo library. Uploaded profile photos are stored privately in Supabase and displayed across your devices. Notifications support reminders and workout/rest timers. Device permissions and permission to upload data are separate choices. Dyne does not request access to your device Contacts/address book.

If the feature is enabled for your account and supported on your device, Dyne can also connect to Apple Health on iPhone or Health Connect on Android. If you choose to connect one of those services, Dyne may import height, weight, and body-fat data and may export completed workouts; on Android, the current code can also export calories-burned data with the workout record. If you allow imports and server uploads, imported height, weight and body-fat metrics are stored in your Dyne profile/body logs on Supabase for synchronization and workout personalization. Imports can run in the background while connected. A connected heart-rate monitor can also supply heart-rate information for your workout.

Website and support information

If you contact Dyne by email, we receive your email address and the contents of your message. If you use the in-app support chat when it is available, Dyne and the support-chat provider may receive your support messages and account-support metadata such as your display name, email address, user ID, subscription tier, app version and build, platform, locale, time zone, account creation date, member since value, and referral code.

When you visit the website, infrastructure providers may process standard technical information such as IP address, browser details, and device information needed to deliver the site. The reviewed website code does not currently show third-party advertising SDKs or a dedicated web analytics tracker.

Usage, diagnostic and security information

Firebase Analytics records app interactions and events such as onboarding, feature use, paywall views and purchases, together with relevant app-instance/device and campaign information. Some events include training setup or nutrition goal/rate settings to understand use of those features. Sentry records errors and performance information. We do not describe this collection as anonymous merely because a name is absent; identifiers and event context may make information linkable to an account or device.

The reviewed mobile app code includes Sentry integration for error and performance monitoring. In addition, some protected Android backend requests use Google Play Integrity checks to help validate the request and reduce abuse. These flows may involve limited diagnostic, device, or request-integrity information needed to monitor reliability and protect the service.

Section 3

How we use information

• To create accounts, authenticate users, and keep accounts secure.
• To personalize workout plans based on your profile, gym inventory, preferences, and training history.
• To log sessions, calculate progress signals, recovery status, streaks, and other in-app insights.
• To store, synchronize, and process data in Dyne's remote backend systems.
• To calculate nutrition targets, keep meal records and provide optional AI food/nutrient estimates.
• To understand feature use, subscriptions and campaign performance through analytics and attribution.
• To process subscriptions, free-workout trial access, referrals, and entitlement changes.
• To generate weekly workout reports and deliver them in-app or by email when you enable those options.
• To operate optional health integrations, including importing supported body metrics and exporting completed workouts.
• To provide support, respond to requests, troubleshoot issues, and improve reliability.
• To monitor app reliability, investigate errors, and help protect the service against abuse.
• To enforce terms, prevent abuse, and comply with legal obligations.

In the current app architecture, workout generation may involve sending your training history, profile, and gym setup to Dyne's backend function so it can generate a tailored workout plan.

Section 4

Sharing and service providers

We do not sell your personal information. We may share information with service providers that help us operate Dyne, subject to contractual or operational controls appropriate to the service involved.

Service providers and optional integrations

• Supabase for authentication, database and private photo storage, synchronization and backend functions.
• Google Gemini for meal photos or descriptions submitted for optional AI analysis.
• Google Firebase Analytics for usage, purchase and campaign measurement.
• TikTok for campaign-event measurement in Android builds where that integration is enabled.
• Google and Apple when you choose their sign-in flows.
• RevenueCat, Apple App Store, and Google Play for subscriptions, purchase validation, and entitlements.
• Sentry for mobile error and performance monitoring.
• Zoho Mail for weekly workout report email delivery when you enable that feature.
• Tawk for support chat you choose to open; native builds may also include Crisp support integration where enabled.
• Apple Health and Android Health Connect if you connect those services in eligible app builds and accounts.
• Google Play Integrity on supported Android protected requests to help validate requests and reduce abuse.
• GitHub Pages and website infrastructure providers, including Google Fonts, when the website loads in your browser.

We may also disclose information if needed to comply with law, protect users or Dyne, investigate fraud or abuse, or as part of a business transfer such as a merger, acquisition, or asset sale.

The current app code includes Sentry for error and performance monitoring and configures default personally identifying information sending as disabled. Some protected Android backend actions also use Google Play Integrity checks as part of Dyne's service-protection flow.

The reviewed mobile app code includes an optional Apple Health and Android Health Connect integration path behind an account feature flag. In supported builds, connected providers can be used to import height, weight, and body-fat data and to export completed workouts; the current Android path can also write calories-burned data with those workout exports.

Section 5

Retention and security

Dyne keeps information for as long as needed to provide the service, maintain account continuity, meet security needs, resolve disputes, and satisfy legal obligations.

In the current app implementation, much of your Dyne account and training data is synchronized to remote backend systems. Signing out clears local app data stored on the device, including local database content and locally saved profile media, but signing out does not by itself delete remotely stored account or workout data associated with your account.

Meal data, selected images and AI results remain stored while needed for the feature until removed through applicable deletion processes. Deleting a meal or all Nutrition data removes it from normal app access through synchronization; that is not a promise that every analysis-result copy, operational record or backup is immediately erased. Disabling AI or disconnecting Health stops future processing described by that control, but does not delete historical records. For complete account deletion or help removing retained data, use Profile > Delete Account or contact support.

Account deletion removes the account and associated primary app records and requests cleanup of private profile and meal images. Billing-provider records, support correspondence, security records and backups may follow separate retention processes. We do not publish a fixed additional retention period for all such records. Contact us for information about a specific deletion request. Data may be processed in countries where our providers operate, under the applicable service arrangements and legal requirements.

We use private photo buckets and account-scoped database access controls. No method of storage or transmission is completely secure.

Section 6

Your choices and rights

The updated privacy controls are being rolled out with the next app update. If a control described below is not present in your installed version, avoid the optional upload feature, manage device permissions, or contact support for help. Existing account deletion remains available in Profile.

• You can update much of your profile, gym, workout, and body-log data inside the app.
• Decline uploads: cancel the separate health, profile-photo or AI-analysis confirmation. Declining optional uploads does not require deleting your account.
• Health imports: use Profile > Integrations > Disconnect to stop future imports on that device. Disconnect each connected device; previously imported Dyne records and records in Apple Health/Health Connect are not erased by disconnecting.
• AI meal analysis: turn it off in Nutrition Settings > Privacy. Manual entry and barcode search remain available. Withdrawal must synchronize to reach other devices; it does not delete earlier meals or results.
• Profile photo: use Profile > Remove uploaded profile photo to remove the uploaded image. A photo supplied by Google or Apple sign-in may still be displayed.
• Nutrition data: delete individual meals or use Delete all nutrition data in Nutrition Settings. See the retention section for the difference between removing app records and complete erasure.
• Account and server storage: use Profile > Delete Account, type DELETE and confirm, or request help by email. Signing out alone does not delete server data. Account deletion does not cancel store subscriptions.
• You can manage notification, photo-library, and connected health-data permissions in your device settings.
• You can manage weekly workout report delivery, supported health integrations, and related feature settings inside the app where available.
• You can manage paid subscriptions through the relevant app store account.
• You can sign out to remove local app data from your device, but that does not delete remotely stored account data.
• You can contact Dyne to request access, correction, deletion, or other privacy help, subject to applicable law.

To make a privacy request, email support@dyne.fitness.

For Dyne account deletion instructions and a summary of what data is deleted or kept, see the Account Deletion page.

Section 7

Children's privacy

Dyne is not intended for children under 16. The current app setup flow also enforces a minimum signup age of 16. If you believe a child has provided personal information to Dyne, contact us and we will review the request.

Section 8

Contact and updates

If you have questions about this Privacy Policy or want to make a privacy request, contact Dyne at support@dyne.fitness.

Dyne is operated by FASHION ART 3.0 INC, 1680 Michigan Ave Ste 910, Miami Beach, Florida 33139-2550, United States.

We may update this Privacy Policy from time to time. When we do, we will update the date at the top of this page.