Privacy Policy

1. Controller

Exerlyze UG (haftungsbeschränkt), represented by the managing director Mr. Markus Kurbel Stresemannallee 63, 60596 Frankfurt am Main, Germany

Contact email: mail@exerlyze.com

2. Scope / Overview

This Privacy Policy applies to the mobile app Ringforge (iOS/Android).

For the website privacy policy, see exerlyze.com Privacy Policy.

Current setup:

No user accounts / no login
No cloud sync
Timer, workout history, streak, settings, and profile data are stored locally on your device
The app may show advertising through Google AdMob unless you have active ad-free access
The app offers a one-time ad-free in-app purchase through the Apple App Store or Google Play
The app uses Google consent tools, Firebase services, and RevenueCat as described below, including limited product analytics when analytics consent permits it

3. Local App Data

Ringforge stores timer, settings, profile, workout history, streak, badge, and monetization state data locally on your device. We do not automatically receive this local app data.

Locally stored monetization state may include whether ad-free access is active, the daily ad impression counter, and cached product information used to display purchase options.

Purpose: providing app functionality and remembering your settings. Legal basis: Art. 6(1)(b) GDPR (performance of contract / provision of app functionality). Deletion: you can delete local data by resetting the app data, using available in-app deletion options, or uninstalling the app.

4. Health and Fitness Data

Ringforge is a training timer app for combat sports such as boxing, Muay Thai, and MMA. As part of the app's functionality, the following fitness and activity data may be stored locally on your device:

Workout session data: date and time of the training session, duration, number of completed rounds, completion status
Training progress: workout streaks, weekly goals, total completed workouts, and total completed rounds
Gamification data: earned badges and personal records
Timer profiles: individual configurations for preparation, round, and rest intervals

We do not collect biometric or body-related data such as heart rate, steps, calories, weight, or body composition. Ringforge does not integrate with Apple HealthKit, Google Fit, or Health Connect.

Purpose: tracking personal training progress and motivation through streaks and badges. Storage: locally on your device. Detailed workout history, custom profile names, and full local training records are not automatically transmitted to us by Ringforge. If analytics consent permits it, Ringforge may send limited derived product analytics as described in section 7, such as timer configuration values, completed round counts, workout duration, progress percentage, streak counts, weekly goal progress, and achievement identifiers. Legal basis: Art. 6(1)(b) GDPR.

Ringforge may display banner ads using Google AdMob / Google Mobile Ads SDK. We use Google's User Messaging Platform (UMP) to request and manage privacy choices where required.

Depending on your platform, region, consent choices, and device settings, Google AdMob / Google Mobile Ads SDK may process:

IP address, which may be used to estimate approximate location
Advertising identifiers, such as Android Advertising ID where available and permitted
App interactions and ad interactions, such as app launches, taps, ad requests, and ad views
Device, app, and SDK diagnostic or performance information
Consent state and privacy preference information

Purpose: displaying ads, measuring ad delivery, frequency management, fraud prevention, security, and complying with consent and platform requirements. Legal basis: where required, your consent (Art. 6(1)(a) GDPR); otherwise our legitimate interests and Google's legitimate interests in ad delivery, fraud prevention, and app security (Art. 6(1)(f) GDPR), subject to your privacy choices and applicable law. Provider privacy information: policies.google.com/privacy, policies.google.com/technologies/partner-sites

You can manage available Google privacy choices in the app settings where the privacy options form is available. You can also control advertising identifiers through your iOS or Android system settings.

Ad-Free Purchase

If you buy ad-free access, Ringforge stops displaying banner ads in the app for your app store account while the entitlement is active. Advertising and consent services may still be initialized to manage consent state, privacy choices, analytics consent, and platform compliance.

6. In-App Purchases (Apple / Google / RevenueCat)

Ringforge offers a one-time ad-free purchase. Payments are processed by the Apple App Store or Google Play. We do not receive your full payment card details.

We use RevenueCat to manage purchase products, purchase status, entitlement state, and restore-purchase functionality.

RevenueCat, Apple, and Google may process:

Product IDs and purchase history
Purchase status, timestamps, and entitlement state
Store account and transaction identifiers provided by Apple or Google
Anonymous RevenueCat customer identifiers and technical request metadata

Purpose: showing purchase options, completing purchases, restoring purchases, unlocking ad-free access, support, fraud prevention, and compliance with tax/accounting obligations. Legal basis: Art. 6(1)(b) GDPR (purchase and app functionality), Art. 6(1)(c) GDPR where retention is legally required, and Art. 6(1)(f) GDPR for support and fraud prevention. Provider privacy information: revenuecat.com/privacy, apple.com/legal/privacy, policies.google.com/privacy

7. Firebase Analytics

Ringforge uses Firebase Analytics to understand app usage and monetization flows only when the app's consent state permits analytics storage.

Firebase Analytics may process:

App instance identifiers and Firebase installation identifiers
Screen views and app lifecycle events
Monetization events, such as paywall views, purchase start/success/failure, and restore events
Purchase event details such as product ID, product type, value, and currency where available
Onboarding and profile events, such as onboarding shown/skipped, selected profile type, profile creation/selection/deletion, and the source from which a workout was started
Timer and workout interaction events, such as timer start, pause, resume, completion, or abandonment
Derived timer and progress values, such as preparation/round/rest duration, total rounds, total planned duration, duration bucket, completed rounds, progress percentage, workout duration, prior/completed workout counts, workout count bucket, current streak, weekly goal progress, and achievement identifiers
Device, app, and approximate location information derived from technical request data

Ringforge does not send custom profile names, notes, or full workout-history records to Firebase Analytics as custom event parameters.

Purpose: understanding app usage, onboarding, profile and timer feature usage, training-progress feature engagement, measuring purchase flow reliability, improving the app, and debugging monetization behavior. Legal basis: where required, your consent (Art. 6(1)(a) GDPR). Provider privacy information: firebase.google.com/support/privacy

Firebase Analytics is not used by us to sell personal data. Analytics consent can be affected by your Google privacy choices in the app.

8. Crash Reporting (Firebase Crashlytics)

We use Firebase Crashlytics to analyze crashes and improve app stability. Crash diagnostics can be managed in the app settings.

Crashlytics may process:

Crash stack traces and diagnostic data
Relevant app state at the time of a crash
Device, operating system, and app version information
Crashlytics installation UUID and Firebase installation identifiers
Non-fatal error reports generated by the app

Purpose: detecting, diagnosing, and fixing crashes and errors. Legal basis: Art. 6(1)(f) GDPR (legitimate interests in maintaining a stable and secure app). Retention: Crashlytics generally retains crash data for a limited period, commonly around 90 days, subject to Firebase's current retention practices and configuration. Provider privacy information: firebase.google.com/support/privacy

9. Data Retention

Local timer, workout, streak, and settings data: retained on your device until you delete it, reset app data, or uninstall the app.
Ad-free entitlement and product cache: stored locally and refreshed through RevenueCat while purchase functionality is used.
Purchase records: retained by Apple, Google, RevenueCat, and us as needed for purchase restoration, support, fraud prevention, and legal retention obligations.
AdMob / Google consent and advertising data: retained according to Google's policies and your consent choices.
Firebase Analytics data: retained according to Firebase/Google Analytics settings and your consent choices.
Crashlytics data: retained according to Firebase Crashlytics retention practices and configuration.

10. Cookies and Tracking

The exerlyze.com website privacy policy applies to website cookies and website tracking.

In the Ringforge mobile app, Google AdMob, Google UMP, Firebase Analytics, Firebase Crashlytics, RevenueCat, Apple, and Google may use identifiers and similar technologies as described above. Advertising identifiers can be managed in your device settings, and available Google privacy choices can be managed in the app settings.

11. Minors

Our service is intended for individuals aged 16 and older. We do not knowingly process personal data of children under 16. If we become aware that such data has been processed, we will delete it as required by law.

12. Your Rights

Under the GDPR you have, in particular, the right to:

access (Art. 15)
rectification (Art. 16)
erasure (Art. 17)
restriction (Art. 18)
data portability (Art. 20)
object to processing based on legitimate interests (Art. 21)
withdraw consent (Art. 7(3)), where applicable
lodge a complaint with a supervisory authority (Art. 77)

To exercise your rights, contact us at mail@exerlyze.com. For data controlled directly by Apple, Google, or RevenueCat, we may need to direct you to the relevant provider or store account controls.

13. Changes to This Privacy Policy

We update this Privacy Policy if technologies or processing activities change.

Last updated: May 9, 2026