Privacy notice

How MyFitEra uses your information.

RCS Technologies Inc., based in Alberta, Canada, provides MyFitEra. For privacy questions or requests, contact info@rcstechnologiesinc.com.

Who MyFitEra is for

MyFitEra is intended for adults aged 18 and over. We do not collect date of birth during onboarding or verify each user's age. Contact us if you believe a child has supplied personal information.

Your account and training information

You can begin with a guest account. A guest account has a unique identifier and may synchronize records with our servers. It is not an anonymous, device-only mode. If you choose Apple or Google sign-in, we use the information supplied by that service, which can include your name and email address, to maintain your account.

We process training goals, equipment, experience, available training days, language, units and timezone; optional bodyweight; programs and exercises; workout dates, sets, repetitions, loads, timed exercises, duration and difficulty feedback; and progress records. Local records support offline logging. Account records synchronize when a connection is available. Losing guest-account access or reinstalling the app may affect access to guest or unsynchronized records.

If you use Coach or request an AI program, we process the preferences, messages and optional notes you submit, generated responses and proposals, and relevant training context. Notes can include health information you choose to share. Avoid including names, contact details or other information that is unnecessary for your training request.

Usage, diagnostics and subscriptions

We process feedback, subscription status, purchase-related identifiers, and technical information for security, diagnostics and service improvement. Usage events include feature interactions, training-preference categories, exercise identifiers, completed-set counts, workout duration, difficulty ratings and record counts. These can be linked to your account identifier. MyFitEra v2 does not send individual set repetitions, weights, hold times or total workout load to Analytics. Those records remain in account storage and may inform AI features you request.

Diagnostic reports can include device and app information, installation and account identifiers, training-preference attributes and error information. Server logs include account and request identifiers, outcomes, durations and AI-usage estimates. Infrastructure providers also process request metadata, including IP addresses, for delivery and security. Google Analytics derives approximate location, such as country and region, from masked IP addresses for usage measurement. Disabling granular location collection does not remove this general location processing. Subscription records can also include a transaction country or an approximate country derived from IP address. MyFitEra does not request precise device location. See Google Analytics data disclosures.

AI processing

Before sending information to OpenAI for an AI feature, MyFitEra asks for your explicit permission for the current account on this device. You can decline and continue using the free workout logger and ready-made programs. You can withdraw permission in Profile to stop future AI requests from this account on this device. This does not change permission on other devices or recall information already sent. Previously sent information remains subject to the retention and deletion practices described here.

We send relevant training information to OpenAI through our server when you request an AI feature. Depending on the request, this includes preferences, optional bodyweight and notes, recent messages, your current program, and limited summaries of recent workouts and exercise records. We do not deliberately add your account identifier or name to the model prompt, but your own text or workout names may contain personal details.

Our integration requests that responses are not saved for later API retrieval. Provider abuse monitoring and caching are separate, so this is not a promise of zero retention. OpenAI states that API content is not used to train its models unless the customer opts in. Its default abuse-monitoring retention can include prompts and responses for up to 30 days, with legal or safety exceptions. See OpenAI's data controls.

Providers and purposes

• Google Firebase and Google Cloud: authentication, synchronized storage, server processing and abuse protection.
• Google Analytics for Firebase and Crashlytics: usage measurement and reliability.
• OpenAI: training responses and program generation.
• RevenueCat and Apple: subscription verification and store purchases. MyFitEra does not receive your full payment-card details through App Store purchases.

We use these services to deliver features, maintain records, verify access, respond to support requests, prevent misuse and diagnose problems. MyFitEra v2 has no advertising network integration. Google signals, enhanced user-provided data and Analytics ads personalization are disabled in our configured property. Optional Google product/modeling/recommendation sharing is off; technical-support access remains on. Account-linked usage information is still personal data.

How long information is retained

• Saved programs, workouts, progress and Coach conversations stay while the account exists, and are handled by account deletion.
• We review and delete support feedback 90 days after resolution, unless a documented support, security or legal need requires longer retention. This is a manual process.
• Analytics user and event retention is set to 14 months, without restarting the period on new activity. Aggregate standard reports have separate handling.
• Our database recovery window is seven days. Standard project logs are retained for 30 days and required logs for 400 days.
• Short-lived AI retry records, which can contain generated results, and request counters have 24-hour expiry settings. Deletion-job and subscription-webhook delivery records have 30-day expiry settings. Database expiry is asynchronous, not an exact erasure deadline.

Provider copies have separate handling. Firebase states that Crashlytics retains crash data and associated identifiers for 90 days before removal begins, and deleted Authentication data can take up to 180 days to leave live and backup systems. RevenueCat customer deletion and app-store transaction retention are separate from deleting our database records. Legal, security or dispute-resolution needs may require some provider records to remain. See Firebase privacy information and RevenueCat's privacy policy.

Deletion and your choices

In the app, open Profile → Account → Delete account. The process can require another sign-in and a retry after an interruption. It removes app account records and feedback, requests RevenueCat customer deletion and removes Firebase sign-in. Device cleanup follows confirmation; the app provides recovery instructions if cleanup is incomplete. See account-deletion help.

Account deletion does not automatically erase historical Analytics, Crashlytics or server logs, recovery copies, or App Store transactions. Contact us for requests involving residual records. We assess what can be deleted, what a provider holds and any applicable retention requirement. Deleting the app or your MyFitEra account does not cancel a subscription. Manage subscriptions separately through Apple.

Reminders are optional local notifications with device permission. Schedules are stored on your device per account; notifications may show the workout name and estimated duration. Disable reminders in the app or change device notification settings. You can use workout logging without requesting AI features. Release builds collect the usage and diagnostic data described here; there is currently no in-app Analytics opt-out switch.

Security, international processing and requests

We use access controls and encrypted network connections, but no service can guarantee perfect security. Our backend runs in the United States and providers may process information in other countries. Depending on applicable law, you may have rights to access, correct, delete or obtain a copy of your information, object to or restrict processing, withdraw consent where relevant, and complain to a privacy authority. Contact us to discuss a request. We may need to verify that the information belongs to you; do not email passwords or verification codes.

This website

The v2 website pages do not add advertising trackers, analytics scripts, forms or third-party fonts. Hosting providers still process request metadata, including IP addresses, to deliver and protect the site. Links to app stores and social services lead to services with their own privacy practices.