Effective and last updated 5 August 2026
FitnX Privacy Policy
Version 1.0
This Policy applies worldwide. Additional rights may apply under the law where you live; mandatory local rights are not limited by this Policy.
1. Controller and contact details
Data controller: Gellért Dániel individual entrepreneur (Gellért Dániel e.v.)
Registered office: 2336 Dunavarsány, Erkel Ferenc utca 24., Hungary
Individual entrepreneur registration number: 59642088
Tax number: 90449813-1-33
Privacy and support email: support@fitnx.app
Data Protection Officer or EU representative: Not appointed; not currently required for this operation.
This Privacy Policy explains how FitnX collects, uses, stores and shares personal data when you use the FitnX mobile, Apple Watch or Wear OS applications, the FitnX website, support features and related services (the Service).
2. Scope and roles
This Policy covers personal data controlled by FitnX. Apple, Google and other third parties may separately control data collected through their stores, sign-in services, health platforms, operating systems or websites. Their notices also apply to that processing.
FitnX is not a health-care provider and is generally not subject to HIPAA. Certain fitness information may nevertheless be protected as health data, special-category data or consumer health data under applicable laws.
3. Personal data we process
Account and identity data
When you sign in with Google or Apple, we may receive a provider identifier, email address, name, profile image and authentication metadata. We create an internal FitnX user identifier and record registration information.
Profile and preferences
This may include birth date, selected gender, height, weight and weight history, measurement system, language, theme, feature-guide state, privacy choices, health-integration choices and app settings.
Workout, activity and fitness data
This may include workouts, exercise definitions, custom exercises, sets, repetitions, resistance or weight, durations, timestamps, notes, body measurements, activity history, statistics and comparisons. Tracked activities may include heart rate, energy, distance, speed, pace, cadence, elevation, laps, sensor samples and similar metrics.
Location and route data
If you start an eligible route-tracked activity and grant permission, FitnX may process precise location points, timestamps, altitude, accuracy, speed, distance and a derived route. Background location is used only while an eligible activity is being recorded or restored after interruption. You can continue without a route when permission or location data is unavailable.
Apple Health and Android Health Connect
With permission, FitnX can read supported profile or measurement data from Apple Health/HealthKit or Android Health Connect, such as birth date, biological sex where supported, height and weight. FitnX may receive workouts and sensor data recorded by a paired watch. If export is enabled, FitnX can write supported workouts, metrics and routes to those platforms.
Imported data may be synchronized to the FitnX cloud and retained like equivalent manually entered data. Revoking a platform permission stops future access but does not delete data already imported into FitnX. Delete that data in FitnX or request erasure.
FitnX does not sell health or fitness data or use it for advertising, data brokerage, credit, insurance or employment decisions.
Subscription information
Apple App Store or Google Play processes payment details. FitnX and RevenueCat receive limited purchase and entitlement information, which may include the FitnX user ID, store, product, purchase and expiry status, transaction or receipt identifiers, country/region and subscription events. FitnX does not receive full payment-card details.
Optional Analytics and Crashlytics
Firebase Analytics and Firebase Crashlytics start disabled and operate only after separate opt-in. Analytics may record limited events concerning onboarding, general feature use, activity outcomes, purchase outcomes, search and privacy actions. Crashlytics may receive sanitized error information, stack traces, app version, device/OS information, timestamps and pseudonymous installation identifiers.
FitnX does not intentionally attach workout or exercise names, notes, measurements, precise routes, email addresses or birth dates to telemetry. Analytics and crash data may nevertheless be pseudonymous rather than anonymous. Consent can be withdrawn independently in the app.
Support data
Support submissions may include the FitnX user ID, contact email, category, title, description, status, timestamps, optional screenshots and limited diagnostics. Do not include unnecessary health or sensitive information.
Device and local data
FitnX stores information locally for offline use and active-activity recovery. This can include settings, privacy choices, health-export state, pending phone/watch state, drafts and an account-scoped SQLite history mirror. Paired watches exchange the state, results, sensor metrics and routes required for companion recording.
Website data
The static website does not currently use analytics, advertising pixels or a contact form. It stores theme and language choices in local storage and, after a language selection, a fitnx-locale preference cookie for up to one year. These strictly functional choices can be removed in browser settings.
Firebase Hosting and network providers necessarily process ordinary request information such as IP address, time, requested URL, browser information and security logs under their applicable terms and operational retention schedules.
4. Purposes and legal bases
For EEA, UK and Swiss users, the principal legal bases are:
| Purpose | Data | Legal basis |
|---|---|---|
| Accounts, synchronization, history, statistics and requested features | Account, profile, settings, activity and device data | Contract; requested pre-contract steps |
| Pro access and purchase restoration | Account and entitlement data | Contract; legal obligations where applicable |
| Import, storage, analysis or export of health data | Profile, measurements, workouts, sensors and routes | Contract plus explicit consent under GDPR Article 9(2)(a), where applicable |
| Route recording | Precise location and derived fitness data | Requested service; consent/permission where required |
| Support | Contact, ticket, attachment and diagnostics | Contract; legitimate interests; explicit consent if special-category data is voluntarily supplied |
| Security, abuse prevention and legal records | Account, technical, support and transaction records | Legitimate interests; legal obligations; legal claims |
| Analytics and Crashlytics | Limited usage and technical data | Consent |
| Website language/theme | Preference data | User-requested functionality and applicable device-storage rules |
Location, health-platform access and telemetry are optional. Features dependent on those inputs cannot operate without them.
5. Sharing and service providers
We do not sell personal data or share it for cross-context behavioural advertising. We disclose data only as needed to:
- Google Ireland Limited, Google LLC and relevant Google affiliates: Firebase Authentication, Firestore, Cloud Storage, Cloud Functions, Firebase Hosting, optional Analytics and optional Crashlytics; Google Sign-In, Google Play and Health Connect. Firebase generally acts as processor/service provider for customer data; some store, sign-in or platform processing is independently controlled by Google.
- Apple Distribution International Limited, Apple Inc. and relevant Apple affiliates: Sign in with Apple, App Store, HealthKit and watchOS platform functions, generally as independent platform controllers.
- RevenueCat, Inc., 1032 E Brandon Blvd #3003, Brandon, Florida 33511, USA: purchase validation and entitlement management as processor/service provider.
- MapTiler AG, Zugerstrasse 22, 6314 Unterägeri, Switzerland: map tiles and related network requests. Tile coordinates can reveal the approximate displayed area. FitnX does not send the saved raw route as a separate MapTiler payload.
- authorized advisers or personnel who require access for support, security, accounting, legal or compliance work; and
- authorities, rights-holders or transaction participants when required by law, needed to protect rights or safety, or involved in a properly notified business transfer.
Provider details and subprocessors may change. Current provider information is available in the providers’ own notices and contractual terms.
6. International transfers
Some providers and subprocessors operate outside your country. Firebase Authentication is operated from US data centres; other Firebase services may use global infrastructure or configured regions. Where European transfer rules apply, transfers rely as appropriate on adequacy decisions, the EU-US Data Privacy Framework for certified recipients, Standard Contractual Clauses, the UK Addendum or another lawful mechanism, with supplementary measures where appropriate. RevenueCat’s DPA incorporates Standard Contractual Clauses. Switzerland benefits from an EU adequacy decision.
Contact us for information about safeguards relevant to your data.
7. Retention
We retain data only as long as necessary for the stated purpose, applicable provider operation and legal obligations.
| Data | Retention rule |
|---|---|
| Free activity history, related statistics and measurement history | Accessible for the current calendar month plus the previous five months; stored on a rolling 365-day basis. Locked data may remain until its storage period ends. |
| Active Pro history | No time-based history deletion while Pro remains active. |
| History after Pro expires | Free access resumes immediately. Older history is protected for 365 days after expiry; after that, data outside the rolling Free window may be deleted. Resubscribing before cleanup cancels the scheduled cleanup. |
| Account/profile, settings, workouts and exercises | While the account is active and needed to provide the Service. Inactive Free accounts are not currently deleted automatically. |
| Support tickets and screenshots | While needed to resolve and document the request; removed with account deletion unless a complaint, security or legal record must be retained. Hungarian consumer complaint records and responses are retained for three years where that rule applies. |
| Firebase Analytics, if enabled | According to the configured Google Analytics retention period, up to 14 months for user-level and event data; certain aggregate reports or provider-controlled data may remain longer. |
| Firebase Crashlytics, if enabled | Google retains crash stack traces, minidumps and associated identifiers for 90 days before removal begins. |
| RevenueCat and store transaction data | While needed to validate entitlements and until account/provider deletion, subject to provider, store, tax and legal records that may remain separately. |
| Accounting and tax records | For the period required by law; Hungarian accounting records may need to be retained for eight years. |
| Security, privacy-request and legal-claim records | Only as needed to demonstrate compliance, prevent abuse or establish claims, normally no longer than the applicable limitation or mandatory retention period. |
| Account deletion | RevenueCat erasure is requested before Firebase Authentication deletion. App-owned active data is then deleted without undue delay; provider-driven deletion may complete asynchronously. Verified privacy requests are answered within applicable statutory periods. |
| Backups | May remain temporarily in isolated disaster-recovery copies until overwritten under provider schedules; they are not restored to normal use except for disaster recovery. |
| Device copies | Until cleared by the relevant control, successful account deletion, uninstall or operating-system cleanup. |
8. Your choices and rights
In the app, go to Profile > Account > Data & Privacy to manage telemetry, health export, offline history, export information and account deletion. Device settings control location, HealthKit and Health Connect permissions.
Depending on your location, you may have rights to know/access, correct, delete, restrict processing, receive a portable copy, object, withdraw consent, opt out of sale/sharing/targeted advertising, appeal a refusal and complain to a regulator. We do not discriminate for exercising applicable privacy rights. FitnX does not currently sell personal data, use it for targeted advertising or make solely automated decisions producing legal or similarly significant effects.
EEA/UK/Swiss requests are normally answered within one month, subject to lawful extensions. In Hungary, complaints may be made to the National Authority for Data Protection and Freedom of Information (NAIH). Users elsewhere may contact their local privacy regulator.
California and other US-state residents may exercise any applicable access, correction, deletion, portability and opt-out rights. FitnX does not offer a sale or targeted-advertising opt-out because it does not conduct those activities. Washington and Nevada consumer health rights are described in the separate Consumer Health Data Privacy Policy.
Brazilian users may exercise applicable LGPD rights; Canadian, Australian and other users may exercise rights under their applicable privacy laws. Mandatory local rights remain available even if not listed individually here.
Send requests to support@fitnx.app. We may request proportionate information to verify identity. Authorized-agent requests must include authority and allow verification.
9. Account deletion
Delete an account in Profile > Account > Data & Privacy > Delete account. If you cannot access the app, follow Account and Data Deletion.
Deleting FitnX does not cancel an Apple App Store or Google Play subscription. Cancel it separately in the relevant store. Deleting a RevenueCat record also does not cancel a store subscription.
10. Security and breach response
Measures include authenticated access, owner-scoped database/storage rules, encrypted transport supplied by platform providers, least-privilege access, bounded operational processes and separation of optional telemetry from workout content. No system is completely secure. We assess incidents and notify affected people and authorities when required by applicable law.
11. Children
FitnX is not directed to children under 16 and does not permit them to create an account. We do not provide a parental-consent account workflow. If you believe a child under 16 supplied data, contact us so we can investigate and delete it as appropriate.
12. Changes
We may update this Policy when the Service, providers or law changes. We will post the updated date and provide additional notice or obtain new consent where required. Materially new health-data uses or optional tracking will not be introduced merely through a silent policy change.
13. Contact
Gellért Dániel individual entrepreneur
2336 Dunavarsány, Erkel Ferenc utca 24., Hungary
support@fitnx.app