RTC
FITNESS

Privacy Policy

RTC Fitness · Last updated: 23 October 2026

1. Who we are

RTC Fitness is a fitness coaching app (workouts, meals and progress tracking) operated by RTC Fitness (“we”, “us”), an independent business based in France. For the purposes of the EU GDPR and UK GDPR, we are the data controller for the personal data described below.

Contact: Richardstrim89@gmail.com

2. The short version

3. What we collect

3.1 Data you enter

CategoryExamplesSpecial category?
ProfileName, age, sex, height, weight, body fat %, injuries or areas of pain you flag, equipment you haveYes: health data
GoalsFitness goals, target weight or body fat %, timeframe, experience level, food preferences and allergiesYes: health data
TrainingPlans, logged sessions, sets, reps, weights, effort ratings, personal records, session feedback, rehab comfort ratings, an unfinished workout (kept so you can resume it), and, if you tell us, why a session was stoppedYes: health data
CardioActivity type, duration, distance, estimated calories, heart rate (only when you tap the heart on the cardio clock)Yes: health data
NutritionLogged meals, calories, macros, favourites and foods you create, small meal-photo thumbnails (240 px) attached to favourites and logged meals, meal plansYes: health data
Wellbeing and progressSleep, steps, weigh-ins with body fat %, flexibility, badges, dumbbells and streak-style rewardsYes: health data
Progress photosPhotos you take or choose in Progress, stored with a date and weightYes: health data, kept on your phone only
Body measurementsMeasurements you enter (Pro)Yes: health data, kept on your phone only

We process this to provide the service you asked for: building your plans, calculating targets and tracking progress. Our lawful basis is your explicit consent (GDPR Art. 9(2)(a)), which you give by entering the data and can withdraw at any time by deleting your account.

3.2 Account and sign-in data

If you create an account you can sign in with email and password, with Google, or (on iPhone) with Apple. We receive a Firebase user ID, your email address, your display name and the sign-in method. With Sign in with Apple you may choose to hide your email, in which case Apple gives us a private relay address. We never see or store your password.

The app also stores a short description of your device (the first 100 characters of its browser user-agent) with your cloud copy, to show which device last synced.

3.3 Subscriptions

Pro subscriptions are sold by Google Play or the Apple App Store. We never see your card details. We use RevenueCat to check your subscription status. RevenueCat receives your store purchase information and an app user ID (your Firebase user ID once you are signed in, or an anonymous RevenueCat ID before that). Offer codes such as RTCLAUNCH are redeemed in Google’s or Apple’s own screens; the app does not receive the code.

3.4 Refer a friend (Android only)

If you are signed in, the app creates a referral code (REF-XXXXXX) linked to your account. If a new user enters your code, we store a referral record with your code, both account IDs, the new user’s first name, the dates and whether they have completed their first full week. The app works out that result on their device; only the outcome is stored, not their training or nutrition details. When a referral qualifies you receive a free week of Pro (a “Guest Pass”), and the reward code assigned to you is stored against your account ID. Deleting your account does not yet remove these small records (codes, account IDs and dates, no health data). Email us and we will delete them within 30 days.

3.5 Preferences

We store your app settings (theme, timer sounds, meal preferences, which tips you have seen, and similar) so the app behaves the way you set it. Language and some display preferences stay on your device only.

3.6 Data we do not collect

We do not collect your precise location, contacts, call logs, SMS or browsing history. The app asks for camera access only when you use Snap, Scan barcode, Make a meal or progress photos, and for photo library access only when you choose to pick a photo or save a share card. The app has no crash-reporting service, and sends no push notifications (see 4.10).

4. Where your data goes

4.1 On your device

All app data is stored on your device (local storage, and an on-device database for progress photos). If you never sign in, this is the only place it exists and we have no access to it.

4.2 Google Firebase (sign-in and cloud sync)

If you sign in, your app data is synchronised to Google Firebase (Authentication and Cloud Firestore). This covers your profile, injuries, goals, plans, training and nutrition logs, favourites, sleep, steps and weigh-ins, cardio, referral and reward information, and your Pro entitlement. Pro users sync automatically. Free signed-in users sync when they sign in or out, save their profile, shift a plan, press Sync Now, and when the app closes. Progress photos and body measurements are not synced. Google acts as our data processor. Data may be stored outside the UK/EEA, and Google relies on Standard Contractual Clauses for those transfers. The Firebase code library is loaded from Google’s servers (www.gstatic.com), so Google sees your IP address when the app starts. Google’s privacy policy: policies.google.com/privacy

4.3 Health Connect (Android) and Apple Health (iPhone): read only

If you choose to connect them, and only after you grant permission on your phone, RTC Fitness reads the following. It never writes anything to Health Connect or Apple Health.

Health data read this way is stored with your other app data: on your device, and in your cloud account if you are signed in. It is used only to provide these features. It is never sold, never shared with advertisers or used for advertising, and never used to decide eligibility for credit, insurance or employment. You can disconnect at any time in Health Connect’s or Apple Health’s own settings, and delete the data held by us by deleting your account.

The use of information received from Health Connect will adhere to the Health Connect Permissions policy, including the Limited Use requirements. On iPhone, data from HealthKit is not used for advertising or sold.

4.4 Google Gemini (AI meal recognition)

When you use Snap, Describe or Snap to fill in Make a meal, the photo (resized to at most 1280 px) or the text you typed, with the meal type and any note you add, is sent directly from your device to Google’s Gemini API to identify the food and estimate its nutrition. The result comes back to your device. We use Google’s paid Gemini API service, and under Google’s terms for paid services Google does not use this content to train its models. Google may keep it for a limited time for abuse and safety monitoring. We do not store the photos you send on our servers (small thumbnails you attach to a favourite or logged meal are described in 3.1).

4.5 Open Food Facts (barcodes and food search)

When you scan a barcode or search for a food that is not in the app’s own database, the barcode number or your search words are sent to Open Food Facts (openfoodfacts.org), an open food database, to find the product. Barcode scanning itself happens on your device. No account or health data is sent. Open Food Facts can see your IP address as part of answering.

4.6 Advertising (free version)

Free users may be shown banner ads, full-screen ads and optional rewarded videos through Google AdMob, with Unity Ads as one of the ad networks that can fill them. Pro subscribers see no ads. Before any ad is requested, Google’s consent form (where required by law) asks for your choice. On iPhone, Apple’s tracking prompt follows it. You can refuse without losing access to the app.

Never shared with advertisers, either way: your health, training, nutrition, weight, Health Connect or Apple Health data. You can review your ad choices in the app under Settings → Help → How RTC works → About. AdMob / Google Ads privacy: policies.google.com/technologies/ads

4.7 Firebase Analytics (app usage statistics)

We use Firebase Analytics to understand how the app is used. It records a few events (sign-up and the method used, which tab you view, workouts completed, meal days confirmed, Pro started, a meal added to favourites) and whether you are a Pro user, plus what the SDK collects automatically (installs, sessions, device model, app version, approximate country, purchases). None of the content of your workouts, meals or health data is sent to Analytics. On iPhone we use the version of Analytics that does not use the advertising identifier.

In this version of the app, once Google’s consent form has been answered, usage statistics are collected whichever personalised-ads choice you made; that choice controls ad personalisation. Pro subscribers in Europe are not measured. If you want your usage statistics removed, email us.

4.8 App stores (updates and reviews)

The app checks Google Play or the App Store for a newer version so it can offer the update. The Rate button opens the store’s review page; any review you write is handled by the store.

4.9 Problem reports and feedback

If you choose Report a problem or Send feedback, the app opens your own email app with a summary: device and app version, screen size, language, time zone, your Firebase user ID, Pro and billing status, ad-consent status, the size of your saved data, and a log of up to 500 recent lines of what the app did. Keys, tokens and email addresses are removed from the log, but a name you typed could still appear. Nothing is sent unless you press send in your email app, and you can edit it first.

4.10 Notifications

Reminders (training day, weigh-in, confirm day, rest finished and similar) are local notifications scheduled on your phone. We do not use push notifications, and no data is sent to a server to show them. You can switch them off in the app or in your phone’s settings.

4.11 Other content

Fonts and icons are built into the app and not loaded from other websites. Exercise help links open YouTube searches in your browser only if you tap them; no videos are embedded.

5. How long we keep it

6. Your rights

Under the EU and UK GDPR you have the right to:

To use any right, use the in-app controls or email Richardstrim89@gmail.com. We reply within one month. You may complain to your supervisory authority: the CNIL in France, the ICO in the UK, or your national authority elsewhere in the EU. To delete your account without the app, see how to delete your account or data.

7. Health information is guidance, not medical advice

RTC Fitness gives general fitness, nutrition and wellbeing guidance. It is not medical advice and is not a substitute for a doctor, registered dietitian or physiotherapist. Plans are generated by the app, not written for you by a qualified professional. Check with a doctor before starting if you have a medical condition or injury, are pregnant, take regular medication, or have a history of disordered eating. The app shows this on first use and keeps a copy in Settings.

8. Children

RTC Fitness is not intended for anyone under 15. We do not knowingly collect data from children under 15. If you believe a child has provided us data, contact us and we will delete it.

9. Security

Data in transit is encrypted with TLS. Cloud data is protected by Firebase security rules that limit each person’s data to their own account; referral records can only be changed in the ways the Refer a friend feature needs. No system is perfectly secure, and we cannot guarantee absolute security.

10. Changes

We will update this policy as the app changes and revise the date at the top. We will tell you in the app about material changes.

11. Contact

RTC Fitness, France
Email: Richardstrim89@gmail.com
Policy URL: rtcfitness.github.io/rtc-privacy