Privacy Policy for Gym Progress

Last updated: 17 September 2026

This Privacy Policy explains how personal data is processed when you use the Android application “Gym Progress”.

1. Data Controller

The controller responsible for the processing described in this Privacy Policy is:

RealityForge GbR
Biberacher Weg 3
12247 Berlin
Germany

Represented by its partners:
Patrick Bethke
Evgeni Melan

Email: realityforgeeu@gmail.com
Website: https://www.realityforge.eu

2. Scope and Overview

This Privacy Policy applies to the Android application “Gym Progress” with the package name:

eu.realityforge.gymprogress

Gym Progress is a workout-planning and training-progress application.

The App can be used without creating an account. RealityForge does not require users to provide a name, email address, telephone number, password or payment information in order to use the App.

Most workout-related information is stored only in the private application storage of the user’s device.

Gym Progress currently uses:

• local device storage for workout plans, exercise settings and workout history;
• Google Analytics for Firebase for optional product analytics, only after the user has consented;
• the YouTube embedded player in Privacy-Enhanced Mode for optional movement-guide videos.

Gym Progress does not currently use:

• user accounts;
• Firebase Authentication;
• Cloud Firestore or another cloud database for user workout data;
• cloud synchronisation of workout plans or workout history;
• Google AdMob or another advertising SDK;
• Firebase Crashlytics;
• Firebase Performance Monitoring;
• Firebase Cloud Messaging;
• in-app purchases or subscriptions;
• a RealityForge backend server for personal workout data.

Android cloud backup of the App’s private data is disabled.

RealityForge does not sell personal data and does not use App analytics for personalised advertising.

3. Data Stored Locally on the Device

Gym Progress stores workout-related information locally in the private application storage of the user’s device.

Depending on how the App is used, this may include:

• the selected App language;
• workout names entered by the user;
• exercises assigned to individual weekdays;
• the order of exercises within a workout;
• cardio warm-up, Zone 2 and cool-down durations;
• exercise weight settings;
• whether an exercise uses no external weight;
• number of sets;
• minimum and maximum repetitions;
• selected difficulty;
• exercise completion records;
• timestamps of recorded workouts;
• historical exercise settings associated with workout records;
• technical information required to maintain and migrate the local save format.

If a user previously used an earlier version of Gym Progress, the App may preserve a local backup of the original save file during migration to the native Android version.

This workout information is not uploaded to a RealityForge account or synchronised with a RealityForge server.

RealityForge cannot remotely access the workout file stored in the App’s private local storage.

Local workout information normally remains stored until:

• the user deletes the App’s data through Android settings;
• the user uninstalls the App;
• the data is otherwise deleted by the operating system;
• the App itself replaces or removes information as part of normal operation.

The local storage is necessary to provide the functionality requested by the user.

Where Article 6 GDPR applies, the legal basis for this processing is Article 6(1)(b) GDPR.

Where Section 25 of the German Telecommunications-Digital-Services Data Protection Act (TDDDG) applies, storage or access that is strictly necessary to provide functionality expressly requested by the user is based on Section 25(2) no. 2 TDDDG.

4. Google Analytics for Firebase

Gym Progress uses Google Analytics for Firebase to understand how the App is used and to improve its usability and functionality.

For users in the European Economic Area, the relevant Google entity is generally:

Google Ireland Limited
Gordon House
Barrow Street
Dublin 4
Ireland

Analytics collection is disabled by default.

Google Analytics for Firebase is enabled only after the user has expressly allowed usage analytics through the privacy choice shown in the App.

When Analytics is enabled, Google Analytics for Firebase may automatically process technical and usage information including:

• an App-instance identifier assigned to the installation;
• information about App launches and sessions;
• session duration and engagement information;
• App lifecycle events;
• device manufacturer and device model;
• Android and operating-system information;
• App version;
• language and regional settings;
• approximate geographic information derived from network information;
• technical SDK and diagnostic information.

According to Google, Google Analytics for Firebase uses an App-instance identifier to distinguish individual App installations.

Gym Progress does not assign or transmit its own user ID to Google Analytics.

Collection of the Android Advertising ID is disabled in the App’s configuration. The Android Advertising ID and Android AdServices advertising and attribution permissions are removed from the final App manifest.

Advertising storage, advertising user data and advertising personalisation consent remain disabled even if the user allows usage analytics.

Automatic screen reporting by Firebase Analytics is also disabled.

5. Custom Analytics Events

When the user has allowed Analytics, Gym Progress sends a limited set of custom product-usage events.

These events are deliberately designed to avoid transmitting detailed workout-performance information.

The App may report the following types of events:

• opening a workout day, including the weekday and number of exercises;
• opening the exercise library;
• selecting an exercise category;
• using the exercise search;
• opening an exercise preview;
• adding an exercise;
• removing an exercise;
• undoing the removal of an exercise;
• completing an exercise reorder operation;
• saving exercise settings;
• recording an exercise as completed;
• completing a workout;
• opening a movement guide;
• changing the App language.

Depending on the event, the transmitted parameters may include:

• a fixed weekday identifier;
• the number of exercises in a workout;
• a fixed exercise-category identifier;
• a static exercise identifier from the exercise catalogue;
• the source from which an exercise was added;
• the length of a search query;
• the number of search results;
• the selected App language.

The App does not intentionally transmit the actual exercise-library search text.

The App also does not intentionally transmit to Firebase Analytics:

• workout names;
• body weight;
• training weights;
• repetition counts;
• repetition ranges;
• number of sets;
• difficulty settings;
• cardio minutes;
• complete workout histories;
• personal notes;
• names;
• email addresses;
• telephone numbers;
• payment information;
• free-text content entered by the user.

Static exercise identifiers and category identifiers identify exercises included in the App’s own catalogue and are not user-created identifiers.

Gym Progress does not currently report whether an embedded YouTube video actually started playing. Opening a movement guide may be reported, but the YouTube playback itself is not used as a custom Firebase playback event.

6. Purposes of Analytics Processing

RealityForge uses Google Analytics for Firebase for purposes including:

• measuring how frequently core App features are used;
• understanding how users navigate between workout planning, the exercise library and exercise details;
• determining which exercise categories and catalogue functions are useful;
• evaluating the usefulness of exercise search;
• measuring whether exercise previews are used before exercises are added;
• understanding whether movement guides are opened;
• measuring successful workout and exercise workflows;
• identifying usability problems;
• prioritising improvements to the App.

Analytics data is not used by RealityForge to evaluate individual users’ athletic performance.

Analytics data is not used by RealityForge for personalised advertising.

7. Analytics Consent and Privacy Settings

Analytics collection is disabled when the App is first installed or started without a previous Analytics choice.

The user is presented with a choice to allow or refuse usage analytics.

Refusing Analytics does not prevent the user from using Gym Progress.

If the user allows Analytics:

• Analytics storage is permitted;
• Firebase Analytics collection is enabled.

Advertising-related consent remains denied.

The user can later change the Analytics choice through the App’s Privacy settings.

If Analytics permission is withdrawn:

• Firebase Analytics collection is disabled;
• Analytics storage consent is denied;
• locally held Firebase Analytics data is reset by the App.

Changing or withdrawing consent affects future processing.

Withdrawing consent does not automatically delete Analytics information that Google already received before the withdrawal.

Analytics events that occurred while Analytics collection was disabled are not intentionally stored by Gym Progress for later retroactive transmission.

The legal basis for optional Analytics processing is the user’s consent pursuant to Article 6(1)(a) GDPR.

Where the storing of or access to information on the user’s device requires consent under Section 25 TDDDG, the legal basis is Section 25(1) TDDDG.

Consent may be withdrawn at any time with effect for the future.

8. YouTube Movement Guides

Gym Progress provides optional movement-guide videos hosted on YouTube.

These videos are embedded using YouTube’s Privacy-Enhanced Mode through:

https://www.youtube-nocookie.com

The embedded player runs inside an Android WebView.

Simply using the workout planner, browsing the exercise library or editing a workout does not require a YouTube connection.

A connection to YouTube is initiated when the user deliberately opens a movement guide containing an embedded video.

When a YouTube movement guide is loaded, Google and YouTube may receive or process technical information including:

• the user’s IP address;
• device and operating-system information;
• WebView or browser-related technical information;
• the requested video identifier;
• the time of the request;
• interaction information associated with the embedded player;
• information necessary to deliver, secure and operate the video service.

The embedded player may use cookies, local storage or comparable browser technologies as part of providing the YouTube service.

Privacy-Enhanced Mode reduces the use of embedded-video viewing activity for personalisation.

According to YouTube, views of videos in Privacy-Enhanced Mode are not used to personalise the viewer’s YouTube browsing experience or advertising shown outside the embedded player.

If YouTube displays advertisements within a video shown in Privacy-Enhanced Mode, YouTube states that such advertisements are non-personalised.

RealityForge does not receive the user’s YouTube account credentials or a detailed YouTube viewing history through the embedded player.

Loading a movement guide is separate from the user’s Firebase Analytics choice. A user who has disabled Firebase Analytics can still choose to load an embedded YouTube movement guide.

The movement-guide video is loaded only after the user requests this external content.

To the extent that processing and access to information on the device are strictly necessary to provide the video functionality expressly requested by the user, the processing is based on Article 6(1)(b) GDPR and Section 25(2) no. 2 TDDDG.

Google and YouTube may process information under their own responsibility for purposes determined by them.

Further information is available at:

https://policies.google.com/privacy
https://www.youtube.com/t/terms
https://support.google.com/youtube/answer/171780

9. Android Permissions

Gym Progress currently requires Internet access for:

• optional Firebase Analytics after consent;
• optional YouTube movement-guide videos.

The App does not request Android permissions for:

• precise location;
• contacts;
• microphone;
• telephone calls;
• SMS messages;
• calendar access;
• photos or videos;
• general file storage;
• the Android Advertising ID.

The App does not require these permissions for its workout-tracking functions.

10. No Advertising or Advertising Profiles

Gym Progress does not integrate Google AdMob or another advertising SDK.

RealityForge does not use Firebase Analytics data for advertising personalisation.

Gym Progress does not create an advertising profile based on workout activity.

The YouTube embedded player is a separate Google service and may display non-personalised advertising as described above.

11. Service Providers and Recipients

Personal or pseudonymous data may be processed by the following recipients where the corresponding feature is used:

• Google Ireland Limited;
• Google LLC and affiliated Google companies involved in providing Firebase Analytics or YouTube;
• technical service providers engaged by Google;
• public authorities where disclosure is required by law.

For Google Analytics for Firebase, Google may act as a processor for certain processing carried out on behalf of RealityForge.

For certain service-operation, security and other purposes, Google may also process information under its own responsibility.

RealityForge does not operate a server that receives or stores users’ complete workout plans or workout histories.

Further information about Firebase privacy and data processing is available at:

https://firebase.google.com/support/privacy

Google’s Privacy Policy is available at:

https://policies.google.com/privacy

12. International Data Transfers

Google operates infrastructure in multiple countries.

Personal or pseudonymous information processed through Firebase Analytics or YouTube may therefore be processed outside the European Economic Area, including in the United States.

Google states that it relies on recognised legal mechanisms for international transfers, including:

• adequacy decisions;
• the EU-U.S. Data Privacy Framework where applicable;
• Standard Contractual Clauses where required.

Further information about Google’s international data-transfer mechanisms is available at:

https://policies.google.com/privacy/frameworks

13. Data Retention

Local workout information remains on the user’s device until it is deleted through normal App operation, the App’s storage is cleared, the App is uninstalled or the data is otherwise removed by the operating system.

The locally stored Analytics consent choice remains until it is changed, the App’s storage is cleared or the App is uninstalled.

Firebase Analytics information is retained according to the retention settings and policies applicable to the associated Google Analytics property.

Google Analytics distinguishes between user- and event-level data and aggregated reporting data. The retention controls for user- and event-level data do not necessarily determine how long aggregated reports remain available.

RealityForge uses Analytics information only for as long as it is required for the product-analysis purposes described in this Privacy Policy, subject to the technical retention controls made available by Google.

Information processed independently by Google or YouTube is retained in accordance with the applicable Google policies and retention rules.

14. Contact by Email

If you contact RealityForge by email, we process the information contained in your message.

This may include:

• your name;
• your email address;
• the contents of your message;
• attachments;
• date and time of communication;
• other information voluntarily provided by you.

The information is processed to respond to the enquiry and manage further communication.

Where an enquiry concerns a contract or steps requested before entering into a contract, the legal basis is Article 6(1)(b) GDPR.

For other enquiries, the legal basis is Article 6(1)(f) GDPR. RealityForge’s legitimate interest is the proper handling of enquiries addressed to the business.

RealityForge currently uses Gmail for email communication. Google may therefore process technical and communication information when emails are transmitted or stored.

15. Data Security

RealityForge limits the data transmitted by Gym Progress to the information required for the functions described in this Privacy Policy.

Workout plans and detailed workout-performance information are stored in the App’s private local storage.

Android cloud backup is disabled.

Network connections to Firebase and YouTube use encrypted HTTPS/TLS connections.

No method of electronic transmission or storage can, however, guarantee absolute security.

16. Your Rights under the GDPR

Where the GDPR applies, you have, subject to the applicable legal requirements, the following rights:

• the right of access under Article 15 GDPR;
• the right to rectification under Article 16 GDPR;
• the right to erasure under Article 17 GDPR;
• the right to restriction of processing under Article 18 GDPR;
• the right to data portability under Article 20 GDPR;
• the right to object to processing based on Article 6(1)(e) or (f) GDPR under Article 21 GDPR;
• the right to withdraw consent at any time with effect for the future under Article 7(3) GDPR.

To exercise your rights, you can contact:

realityforgeeu@gmail.com

Because Gym Progress does not require an account and RealityForge does not link Firebase Analytics data to names or email addresses, RealityForge may not be able to locate a specific Analytics record using a person’s contact information alone.

Where additional technical information is necessary to identify data relating to a particular App installation, RealityForge may request information reasonably necessary to process the request.

RealityForge does not require users to provide additional identifying information solely for the purpose of maintaining an ability to identify otherwise pseudonymous Analytics data.

Where Google acts as an independent controller, data-protection rights may also be exercised directly against Google.

17. Right to Lodge a Complaint

You have the right to lodge a complaint with a data-protection supervisory authority.

The supervisory authority responsible for RealityForge in Berlin is:

Berliner Beauftragte für Datenschutz und Informationsfreiheit
Alt-Moabit 59-61
10555 Berlin
Germany

Email:
mailbox@datenschutz-berlin.de

Website:
https://www.datenschutz-berlin.de

You may also contact another competent supervisory authority where permitted by applicable law.

18. Children

Gym Progress is not specifically directed at children.

The App does not require users to provide names, email addresses, telephone numbers or other direct contact information.

Where a user is not legally able to provide valid consent to optional Analytics processing under applicable law, Analytics should not be enabled without any authorisation required from a parent or legal guardian.

If RealityForge becomes aware that personal data relating to a child has been processed without the consent or authorisation required by applicable law, RealityForge will take reasonable steps to address the situation.

19. No Medical Purpose

Gym Progress is a fitness and workout-planning application.

The App is not a medical device and is not intended to diagnose, prevent, monitor or treat any disease, injury or medical condition.

Workout records and exercise information are intended for personal fitness organisation and progress tracking.

20. Changes to This Privacy Policy

RealityForge may update this Privacy Policy where the App, its functions, the services used or applicable legal requirements change.

The date shown at the beginning of this Privacy Policy indicates when it was last updated.