fitliftly — Privacy Policy

Effective from: 21 October 2026

1. Data Controller

The controller of personal data is:

Stelix holding s.r.o.
Company ID (IČO): 01443909, VAT ID (DIČ): CZ01443909
Registered seat: Ke stadionu 1953, 272 01 Kladno, Czech Republic
E-mail: info@stelixholding.cz

(hereinafter the "Controller" or "we")

In accordance with Art. 37 GDPR, the Controller has not appointed a Data Protection Officer (DPO), as it is not a public authority and its core activity does not consist of large-scale systematic monitoring of data subjects nor large-scale processing of special categories of data. The above contact e-mail will, however, fully address any data protection enquiries.

2. Who This Policy Applies To

This Policy applies to:

• registered Users of the fitliftly application (all roles — user, trainer, branch manager, venue owner (Partner), reception and moderator);
• Visitors of the website fitliftly.com without registration;
• persons who contact the Controller via e-mail or through the in-app feedback widget;
• persons who comment, message or review on our social media profiles and in the app stores (Section 3.10).

3. Categories of Personal Data Processed

3.1 Identification and contact data

• first name and surname
• username
• e-mail address
• phone number (optional)
• address (street, city, postal code — optional, used i.a. for invoicing)
• date of birth (optional)
• gender (optional)

3.2 Profile data

• profile picture (avatar)
• biography and other optional profile details
• privacy settings (public, friends, private)
• language and timezone

3.3 Social account data

If you sign in via Google, Apple or Facebook, we obtain from the identity provider:

• the user identifier with that provider
• the e-mail address
• the name (and possibly avatar)
• with Sign in with Apple, also a refresh token, which we keep encrypted until the account is deleted, solely so that we can revoke the App's access to your Apple ID at Apple when the account is deleted

3.4 Service usage data (operational)

• records of workouts created, completed and cancelled
• venue entry records (QR check-in/check-out)
• attendance confirmed by location — for a workout at a trainer's spot or at a venue that fitliftly does not manage, you can confirm your attendance with your device's location. The location is sent only at the moment you start the confirmation yourself; we compare it with the workout's place and neither store the coordinates nor write them to logs or error reports — we store only the attendance record and the rounded distance from the place. The trainer can also confirm your attendance at such a workout by scanning your QR code
• statistics (volume, streaks, XP, level)
• badges, challenges, leaderboards
• friend list, client–trainer relationships (being a trainer's client), followed venues
• trainers' invitations to become their client — who invited whom and when, until when the invitation is valid, whether it is waiting, accepted or withdrawn, and the client group the trainer will place you in once you accept, if any. A trainer can find you only by your name or username (never by e-mail), and only if you have not hidden from the people search (see Section 4), and we suggest to them people from their own workouts who are not their clients yet. You accept or decline it on the trainer's profile; we do not tell the trainer about a decline — they see the invitation as waiting until it expires after 30 days
• alerts about new workouts — which trainers whose client you are and which venues you follow have the bell turned on and since when, and which new workouts we told you about. You turn the bell on and off yourself at the trainer, the venue or in the notification settings; becoming a trainer's client or following a venue does not turn it on, and it ends when the client relationship or the follow ends. The trainer and the venue see only how many people have the bell on, not who they are. This also covers the alerts about the next dates of a workout that you turn on in its detail — we keep them as a saved search (venue, kind of workout, day of the week and time)
• watching full workouts — which workout you watch, the mode you chose (automatic booking or a notification, possibly paying with a MultiSport card), when you started watching (it sets the order) and when we last wrote to you. The trainer of the workout sees who is watching, in what order and in which mode; other users and the venue do not — they see only how many. We delete the record once the workout has taken place
• free perks from a venue — what a venue gives you for free (entry, classes, private sessions), until when, the reason the owner gave (employee, family, ambassador, or another with a note), who granted or ended the perk and when, and for entries and classes that they were free thanks to the perk. The venue owner grants the perk; you see what you have for free and until when, not the note. We also use the records to check that perks are not used to circumvent the commission (legitimate interest, Section 4), and keep them until the account is deleted
• chat messages, polymorphic comments, reactions
• uploaded photos of workouts and venues
• sport pass records (card type, number, validity)
• for MultiSport, a fingerprint of the identifier in the My MultiSport app QR code — an irreversible cryptographic fingerprint (the identifier itself is not stored), created when the front desk confirms at your entry that you use the MultiSport app and reads its QR code; it serves only to let the desk recognise you by that QR code next time and is deleted with your account
• for MultiSport set to “on request only”, your answer to the question “Use MultiSport today?” shown when you open your QR code — which venue and day it applies to and whether you chose MultiSport or credits; the desk enters your visit that day accordingly and we delete the record the following night

3.5 Payment and invoicing data

• records of credit wallet transactions
• Shared wallet (Article 7.12 of the Terms) — who invited whom and when, whether the invitation is waiting, accepted, declined or withdrawn, when a member joined, left or was removed, and the permissions the owner set for the member (entries and classes, front-desk purchases, monthly limit). For every payment from a shared wallet we record whom it was for; the owner sees it in their history with the date, place, service and amount, the member sees their own payments, at which venues the shared wallet pays for them and what is left of their limit (the owner's balance is not shown to them). Only friends and people of the same venue can be invited, and the owner is not told why someone cannot be invited. The front desk of a venue that allows sharing sees that a shared wallet paid an entry or purchase, and whose. A declined invitation is not reported to the owner
• invoices (number, IČO/DIČ, billing address) — for trainer/venue/partner roles
• payment card details are not stored in the App — card payments are processed via the Stripe gateway, which is an independent data controller; the App records only the amount, variable symbol and top-up status

3.6 Technical data

• IP address
• device type, operating system, browser version
• last-seen timestamp
• cookies and similar technologies (see Section 8)
• push notification token
• crash and technical error reports of the App (device model, operating system and App version, technical description of the error — no name or e-mail)
• a record of your use of artificial intelligence features (Sections 3.11, 3.12) — which feature you used and when, the model, the number of tokens processed, the estimated price and whether the request succeeded; without the content of the request or the answer. It serves to manage the costs and daily limits of these features and to detect their abuse
• food searches without a result — when you search for a food in the Food diary and we find nothing, we store the search term (lower-cased, without accents, shortened), the day and how many times it was searched that day, without any link to you or your device; terms that look like an e-mail address, a link, a phone number or a user's name are not stored. It serves to extend the catalogue, synonyms and typo corrections, only our team sees it and we delete it after 90 days

3.7 Health data — special category of personal data (Art. 9 GDPR)

If you grant explicit consent to the Health Sync feature, the App reads the following data from Apple HealthKit (iOS) or Google Health Connect (Android), only to the extent you allow in the device settings and in the Health Sync settings:

• steps and active energy expenditure
• workouts (type, time and duration, energy expenditure, distance)
• heart rate
• sleep
• body weight
• food intake (energy, protein, carbohydrates, fat, sugars, saturated fat, fibre, sodium) — if another app writes it to Apple HealthKit or Google Health Connect and you switch on Food intake in the App; by switching it on you give explicit consent for this category as well, after switching it off we no longer read new data and delete the data read earlier

The App writes nothing to Apple HealthKit or Google Health Connect.

This data falls under special categories of personal data per Art. 9 GDPR and we process it solely on the basis of your explicit consent. You may withdraw consent at any time in the App settings or at the device system level; after withdrawal we no longer synchronise the data and existing records can be deleted on request.

We use data from Apple HealthKit and Google Health Connect only for the features you see in the App (statistics, badges, challenges, Smart coach, Food diary). We never use it for advertising, marketing or data mining, we do not sell it and we do not store it in iCloud. We do not pass it to anyone else except as described in this Policy (to a trainer only with your explicit consent within the Food diary, Section 3.11; to other users only in the form of badges and calories under the next paragraph; staff access under Section 3.15; processors running our servers, Section 5.1), we do not send it to artificial intelligence and we do not use it to train any models.

Synced steps and workouts count towards badges (e.g. “10K Steps” for 10,000 steps in a day), and the energy your device measures during a workout you are booked into in fitliftly counts as the calories of that workout. Others can therefore see a badge you earn — its name, icon, description of its condition, the date you earned it and the points for it: your friends see it in their feed (for a trainer, so do their clients), and other users see it on your profile according to your profile's privacy settings (a trainer's profile is visible to every signed-in user). The same settings decide who sees the points for your badges in leaderboards, the total calories on your profile and your score in a challenge that counts calories. We do not show other users the underlying data on your steps, workouts, heart rate, sleep and weight from Apple HealthKit and Google Health Connect.

3.8 Feedback data

When you use the feedback widget, we store the message text, a screenshot of the current screen, the page URL and the browser type. This data is transferred via webhook to our internal issue tracking system (GitLab).

3.9 Publicly available data about venues

Our directory also lists venues that do not yet have a manager on fitliftly. Their details (name, address, location, and where available contact and opening hours) come from public sources, in particular OpenStreetMap (© OpenStreetMap contributors, ODbL licence). We process them on the basis of our legitimate interest (Art. 6(1)(f) GDPR) — maintaining a directory of venues. If you are a venue operator, you may request to take over management, to correct, or to remove the data directly at the given venue in the app or at info@stelixholding.cz, and you may object to the processing at any time.

3.10 Communication on our social media profiles and in the app stores

When you comment, message or review us on our social media profiles (Facebook, Instagram, Threads, LinkedIn) or in the App Store or Google Play, our internal tool keeps your public name or handle, the text and time of the post, the rating and our reply, so that we can answer and resolve the matter. This also applies to people who are not Users of the App. The legal basis is our legitimate interest (Art. 6(1)(f) GDPR) — handling enquiries and caring for our community. We may pass the text of the enquiry to Anthropic (see Section 5) to draft a reply; a person always reads and sends the reply. We keep the data for 12 months from receipt and delete it afterwards. You may object to the processing at any time at info@stelixholding.cz.

3.11 Food diary

The Food diary is an optional feature. If you use it, we process records of what and how much you ate (date, meal of the day, food, amount, its nutritional values and any note), your own foods and dishes, your favourite foods, your daily targets, the data your target is calculated from (weight, height, age and sex from your profile, basal metabolic rate, usual activity level and whether you want to lose, maintain or gain weight), and your preferences (e.g. hiding calories). Dietary data can reveal information about health, so we process it only on the basis of your explicit consent, which you give when you first open the Food diary, and we treat it as health data: we do not show it in the feed or on your profile, and other users cannot see it. You can withdraw your consent at any time in the Food diary settings; we then delete the records. The recommendations the Smart coach derives from the Food diary are described in Section 3.13.

You can add a photo to a meal of your own. Only you and a trainer you share your Food diary with see it; we do not offer it to the shared catalogue, we do not send it to artificial intelligence and we store it downsized and without the place and time it was taken. We delete it when you remove it, delete the meal, withdraw your consent to the Food diary or cancel your account; it is part of your data export (Section 7).

We make the Food diary available to a trainer only if you explicitly allow sharing, separately for each trainer. The trainer then sees all your records including older ones (meals including the photos you added to them, amounts, notes, calories and nutrients, even if you have hidden calories), your targets and how you meet them, the intake read from Apple HealthKit and the calories of your workouts; the calculator suggests a target for them from your profile. You can withdraw this consent at any time in the Food diary settings, and the trainer then loses access to earlier records as well.

A product with a barcode that you save in the Food diary is offered to the shared catalogue unless you switch this off for it when saving (the option “Offer to the catalogue” is pre-selected for products with a barcode; you can also switch offering off for all products in the Food diary settings). Foods and dishes without a barcode are offered only if you offer them yourself. Only product data goes into the catalogue — name, brand, barcode, nutritional values, portions and category, possibly a photo of the packaging — never your name or when and how much of the product you ate. Our team reviews every food before publication; please still do not put personal data in its name. We store a photo of the packaging without the location and time of capture and, after review, show it with the food; it should not show people or personal data. You can also suggest a photo for a catalogue product that has no packaging photo; until review only our team sees it, after approval we show it with the product to everyone (without your name), and a rejected or unused one is deleted. We keep only which product you suggested the photo for, when, and the outcome of the review; this list is part of your data export (Section 7), and pending suggestions are deleted when you withdraw your consent to the Food diary or delete your account. Keeping a shared product catalogue is our legitimate interest (Art. 6(1)(f) GDPR). You may object to the offer at any time: by unticking the option, switching it off in the settings or by a request to info@stelixholding.cz; we then unlink a published food from your account and withdraw it if it contains personal data itself. After your account is deleted, published foods and photos stay in the catalogue without any link to you. A label photo taken only to read the values is not stored (see the next paragraph).

If you use reading a nutrition label from a photo or entering a meal as text, we pass the photo or text to Anthropic (see Section 5), whose artificial intelligence model reads the nutritional values or the individual items of the meal from it. We attach neither your name, e-mail nor any other identifier, and we remove the location and time of capture from the photo before sending it. We store neither the photo nor the text; only what you confirm is saved, together with a record that you used the feature (Section 3.6). Anthropic keeps them only temporarily, for at most 30 days, for security and abuse prevention, and does not use them to train models; it may keep them longer only exceptionally, if the content violates its usage policy. Please therefore do not write details about your health or about other people in the text. The result of the reading may be inaccurate; check it before saving.

When you scan the barcode of a product we do not know yet, our server sends only the code to Open Food Facts, an open database; no data about you is attached to it.

When you search for a food in the Food diary and we find nothing, we store the search term without any link to you (Section 3.6) so that we can extend the catalogue.

3.12 Workout suggestions using artificial intelligence

A trainer can enter a workout as text or a photo (for example of a whiteboard or a sheet of paper), or have a workout suggested from a brief (category, duration, equipment, their own description). We pass the text, photo or brief to Anthropic (see Section 5), whose artificial intelligence model builds a list of exercises from our catalogue. We do not attach the trainer's name, e-mail or any other identifier, and we remove the location and time of capture from the photo before sending it. We store neither the photo, the text nor the brief; only the workout that the trainer reviews and saves is stored, together with a record that the trainer used the feature (Section 3.6). Anthropic keeps them only temporarily, for 30 days at the most, for security and abuse prevention, and does not use them to train models; it may keep them longer only exceptionally, if the content violated its usage policies. Client names and data about their health therefore do not belong in the text or on the photo. The trainer starts the feature themselves; the legal basis is performance of a contract (Art. 6(1)(b) GDPR).

You can have your own training (Section 3.17) suggested in the same way. We pass the brief — the length of the training, the equipment you have at hand and your own description — to Anthropic on the same terms: without your name, e-mail or any other identifier; we do not store it, and only the training you review and save yourself is stored. Do not include data about your health in the brief. The number of suggestions per day is limited. You start the feature yourself; the legal basis is performance of a contract (Art. 6(1)(b) GDPR).

3.13 Smart coach

The Smart coach is a weekly evaluation of your own records by fixed rules (text templates, no artificial intelligence; nothing leaves our server). We roll the coach's features out gradually; the description below covers the full scope, including parts still being built — the App tells you when they go live. The Smart coach works with:

• your workouts (own trainings and the coaching plan included, Sections 3.14 and 3.17) — the day and type of workout, the exercises and sets you logged or the class plan prescribes, the effort (RPE) and whether you completed, skipped or missed it;
• your personal records, the estimated maximum from your logs and your statistics;
• your visits to venues outside a class (entry, exit and length of the visit);
• the challenges you take part in (progress, target and end of the challenge) and the programme you are enrolled in (adherence and the next programme day);
• your chosen goal and the age from your profile;
• if you have Health Sync switched on (Section 3.7), your sleep, heart rate, steps, weight and workouts from your device (type, time and duration);
• if you use the Food diary, your average intake over the last week (energy, protein, fibre, salt, sugars, saturated fat), its ratio to your targets and your energy balance.

The readiness you fill in before a coaching session or an own training (sleep, energy, muscle soreness; Sections 3.14 and 3.17) is not evaluated by the Smart coach.

The result is a score and recommendations, for example how many days a week you are active (workouts from your device and venue visits outside a class count too), which muscle groups you have not trained for a long time and which workouts train them, the balance of your training, a plateau on a particular exercise, progress in a challenge or programme, protein intake relative to a strength goal, a large energy deficit during a high training load or an intake that stays below your basal metabolic rate for a long time. Only you see the recommendations (in the Smart coach and its card on your overview) — neither your trainer nor anyone else does; nothing else in the App depends on them (your statistics, streaks, XP and badges do not change because of them) and they are for guidance only (Section 4.4 of the Terms and Conditions). In the coach's weekly history we keep only summary values (score, the number of active days and workouts, weekly averages and ratios to targets, which muscle groups have gone untrained for a long time), not individual records, for the lifetime of your account. The evaluation of the Food diary is part of your consent to the Food diary and you can switch it off in the Smart coach settings; once you withdraw that consent it stops and we delete the derived values.

Once a week we may send you a notification that your weekly summary is ready. It contains at most your overall score and its change from the previous week; never any individual health or food data, the values of the individual areas or the recommendations — you see those in the App. The notification is delivered by the processors listed in Section 5.1 (Expo, Apple, Google). You can switch it off in your notification settings.

3.14 Hybrid coaching

Hybrid coaching is an optional feature a trainer offers to their clients: the trainer plans standalone workouts that they train on their own, outside classes. If a trainer prepares coaching for you, we process their plan (day, exercises, sets, reps, load, rest, tempo, notes), your entries (sets done, exercise swaps where the trainer allowed them, completing or skipping the workout, effort on the RPE scale and your note), working maxes and their estimate from your sets, the nutrition targets the trainer sets for you, and the trainer's reactions and comments. Your working maxes (also those you set yourself, for instance for your own trainings, or adopt from an estimate) are seen by a trainer whose client you are and who offers coaching — they need them for percentage prescriptions; they can change only the maxes they set themselves. Before a workout you can fill in your readiness (sleep, energy and muscle soreness on a scale of 1–5). This data may reveal information about your health, you fill it in only voluntarily, and the first time you do, you explicitly consent by ticking a box to it being stored with your coaching workouts and to your trainer seeing it; without the consent readiness cannot be sent, the workout can. The consent applies to one trainer and you can withdraw the trainer's access at any time in the privacy settings ("Privacy & data" in the mobile app, the profile settings on the web) — the trainer then also stops seeing the readiness you sent earlier; your entries stay in your coaching history and you can ask for their deletion at any time (Section 7). When you stop being the trainer's client, the consent ends and we will ask again for any later coaching.

Coaching data is visible to you and to this trainer; other trainers and venues have no access to it. When you stop being the trainer's client, they lose access and the workouts already sent stay in your history. We delete the trainer's unsent drafts after 30 days, or as soon as you stop being their client. When you delete your account, we delete the plan, your entries, maxes and targets. Coaching does not use artificial intelligence and is not paid through the App.

3.15 Support and staff access to your account

• Support chat — messages you write to the "fitliftly Support" account are read and answered by authorised staff of the Controller; replies are signed by Support, not by an individual. You can write to Support without being friends or sharing a venue.
• Signing in to your account — to handle your request, fix an error or investigate suspected misuse of the Service, an administrator of the Controller may sign in to your account and see the App as you see it, including chat messages, health data from Health Sync, the Food diary and own trainings if you use them. They may act in the account only to the extent necessary for that purpose. This is available only to the Controller's administrators after two-factor authentication, not to moderators or support staff; we record every such sign-in and its end (who, when and which account). Administrator accounts cannot be opened this way.
• Moderation — moderators see reported content to the extent of the report. We do not otherwise look into private conversations, except when signing in to your account under the previous point.
• Record of administrator actions — we record administrators' actions in the administration (e.g. changes to accounts and Credits, signing in to an account, data exports) so that we can account for them and detect their misuse.

3.16 Strava connection

Connecting Strava is optional. You switch it on in the App by signing in to your Strava account, which grants us permission only to write activities. We store your Strava account identifier, the first and last name from it and the access tokens (encrypted). After each workout that is counted as completed for you in the App for the first time, we send Strava an activity with the workout's name, type (strength or circuit workout), start date and time, duration and the text "Recorded with fitliftly", including private workouts. We send no heart rate, location or other health data and read nothing from Strava. Strava, Inc. (USA) then handles the activity as an independent controller under its own terms and policies; who can see it is determined by your Strava settings. The transfer to Strava (USA) takes place on your explicit instruction, which is connecting the accounts (Art. 49(1)(a) GDPR); Strava states that it relies on Standard Contractual Clauses for international transfers, but once the data is transferred its protection is governed by Strava's terms and may not reach the EU level. You can cancel the connection in the App — we revoke the permission and delete the connection data — or directly in Strava — we then suspend the connection and send nothing further.

3.17 Own trainings

Own trainings are an optional feature: a training you plan and log yourself, without a trainer and without a venue (at home, outdoors or at the gym). We process its day, start time, duration, the place you write in, the title and notes, the exercises with their prescription, the sets you did, exercise swaps, whether you completed or skipped it, the effort on the RPE scale and your note. From these we calculate your statistics (you choose whether they include own trainings or verified classes only) and personal records, and the Smart coach counts them as days you trained (Section 3.13). Own trainings are your own records that nobody verifies: nobody else sees them, they do not appear in the feed, on your profile or in leaderboards, and they never count towards XP, badges, challenges or streaks (Art. 4.12 of the Terms). Please do not write other people's data or details of your health into the text fields (place, notes).

Before a training you may fill in your readiness (sleep, energy and muscle soreness on a 1–5 scale). This data may reveal health, you fill it in only voluntarily, and the first time you explicitly consent, by ticking a box, to storing it with your own trainings; readiness cannot be saved without the consent, the training can. You can withdraw the consent at any time in the privacy settings ("Privacy and data" in the mobile app, profile editing on the web) — we then erase the readiness from all your own trainings.

You can show your own trainings to a trainer whose client you are and who offers hybrid coaching (Section 3.14). You do so by explicit consent, separately for each trainer, on the own-trainings page; the trainer then sees their title, day, time, length, place, exercises, logged sets, RPE and notes, earlier trainings too, but cannot change them. The trainer never sees the readiness of your own trainings. You can withdraw the consent at any time on the own-trainings page or in the privacy settings; the trainer stops seeing them at once, earlier ones too. The consent also ends when you stop being the trainer's client, and we ask again if you become their client later. You can delete an own training at any time; when your account is deleted we delete them all. Personal records that came from an own training stay among your records after the training is deleted, until you delete them yourself or delete your account. The feature uses artificial intelligence only when you have a training suggested yourself (Section 3.12); nothing is paid for it.

4. Processing Purposes, Legal Bases and Retention

5. Recipients of Personal Data

5.1 Processors

We share your data only to the necessary extent with the processors listed below. We have data processing agreements (DPAs) in place with all of them in accordance with Art. 28 GDPR.

5.2 Venues and trainers

Venues (Partners) and trainers whose services you use through the App receive your data to the extent needed to provide their service (managing members, checking you in, attendance, accounting). We are responsible for this disclosure. For their further handling of the data (their own records, accounting, communication with you) the venue or trainer is responsible as an independent controller of personal data; in the Terms (Section 15.3) they undertake to use it only to provide their service, to protect it and not to pass it on. You can exercise your rights with us as well as with them; we will forward a request concerning data held by them and help you have it handled.

• A venue you are a member of — you become a member yourself, by joining the venue, by registering through its link or by booking a trainer's own class held there. The owner, branch managers and reception (for the branches they staff) see your name, username, profile photo, the e-mail from your profile, your registration date, since when you have been a member, your visits (times and payment method), completed and upcoming classes, your Credit balance and movements with this Partner including the bonus part and shared wallet payments (Section 3.5), the type and validity of your saved benefit cards and whether the full card code is stored, your progress in the venue's challenges you take part in, and the free perks the venue gave you (the owner and branch managers including the reason and note, reception only at check-in). The phone and address from your profile are seen only by the owner and branch managers — to communicate about your membership and to issue a receipt; reception does not see them. After you leave the venue, staff no longer see you in the member list; payment and entry records remain with them as records.
• Check-in at reception — when staff scan your QR code, they see your name and the details needed to check you in (benefit card type, a pending challenge prize, the birthday notice if you allow it), even if you are not a member.
• Renting space — if you rent space at a venue or a renter invites you to a rental, the owner, branch managers and reception see the renter, the list of participants (name, username, profile photo) and their entries during the rental; the renter sees the participants they invited, and the participants see the renter (Article 9.7 of the Terms).
• Statements for payees — the Partner or trainer you top up Credits with receives a monthly statement of top-ups with your name, e-mail and payment details as an accounting record. Other monthly reports for venues contain aggregate figures only.
• A trainer whose client you are — sees your name, username and profile photo, your attendance at their workouts (completed, no-shows and their share, upcoming bookings), the programmes they assigned to you and your progress in them, and, for their workouts you are booked on or completed, your log of sets done ("My performance"). The trainer may keep their own notes and intake details about you (goal, injuries and limitations), which no other user than the trainer sees and which you will find in your data export (Section 7); the trainer is responsible for their content and may record only the health information you tell them yourself, and only with your explicit consent (Section 15.3 of the Terms). They see your Food diary only with your explicit consent (Section 3.11); coaching is described in Section 3.14, and they see your own trainings only with your consent (Section 3.17). You become a trainer's client with the “Become a client” button on their profile, by accepting their invitation, or by signing up through their link (once your e-mail is verified). When you stop being the trainer's client, which you can do at any time on their profile, they lose access to this data. We keep the trainer's notes and intake details until your or their account is deleted, or until the trainer deletes them; the trainer sees them again only if you become their client again. You can ask for their deletion at any time (Section 7).
• The trainer of a full workout you watch — sees your name and profile photo, your place in the queue and the mode you chose (automatic booking or a notification, Section 3.4) until the workout starts.

Venues and trainers never see your date of birth, year or age, your benefit card number, health data from Health Sync (except as described in Sections 3.7 and 3.11) or your password.

5.3 Services you connect yourself

If you connect your account with a third-party service, we pass data to it on your instruction and it handles the data as an independent controller under its own terms. This applies to Strava (Strava, Inc., USA) — the data passed is described in Section 3.16.

We do not sell your personal data to third parties for marketing purposes.

6. Transfers to Third Countries

Some of the services listed above (Google, Apple, Meta, Cloudflare, GitLab, Sentry, Anthropic, Expo, Resend) operate as part of global infrastructures. Sentry and PostHog data is stored in EU data centres; for Sentry, the US parent company may have limited access. We pass data to Strava (USA) on your instruction (Section 5.3). When transferring personal data outside the European Economic Area we rely on:

• EU-US Data Privacy Framework (DPF) — for the United States with certified recipients;
• Standard Contractual Clauses (SCCs) adopted by the European Commission — for other cases;
• supplementary organisational and technical measures (encryption, pseudonymisation) where relevant.

We will provide a copy of the safeguards used on request.

7. Your Rights as a Data Subject

Under the GDPR you have the following rights:

• Right of access (Art. 15) — to obtain information about what data we process about you.
• Right to rectification (Art. 16) — to correct inaccurate or incomplete data.
• Right to erasure ("right to be forgotten", Art. 17) — to request deletion of data when no longer needed or upon withdrawal of consent. This also covers manual deletion of health data. We will not erase data we must keep by law (in particular accounting records) or for the establishment, exercise or defence of legal claims (Art. 17(3) GDPR); we delete it once those reasons end.
• Right to restriction of processing (Art. 18).
• Right to data portability (Art. 20) — to receive your data in a machine-readable format (JSON/CSV).
• Right to object (Art. 21) — to processing based on legitimate interest or for direct marketing purposes.
• Right to withdraw consent (Art. 7(3)) — at any time, with effect for the future (in particular for marketing and Health Sync).
• Right not to be subject to automated decision-making (Art. 22) — the App does not perform automated decision-making with legal or similarly significant effects. The Smart coach (Section 3.13) evaluates your records automatically by fixed rules; the result is only a recommendation that you see.

How to exercise your rights

Rights can be exercised:

• in the App under "Privacy & Data" (export, deletion, withdrawal of consents);
• by e-mail to info@stelixholding.cz.

We handle requests free of charge within one month of receipt; for complex or numerous requests we may extend the period by a further two months and will tell you so (Art. 12(3) GDPR). We may refuse manifestly unfounded or excessive requests or charge a reasonable fee for them (Art. 12(5) GDPR).

Deleting your account

You can delete your account in the App under "Privacy & Data" (Delete account) or in the web app in your profile. If you cannot access the App, the steps are at app.fitliftly.com/delete-account, where you can also request deletion by e-mail. When the account is deleted we delete or anonymise your personal data and keep only the data we must or may keep longer under Section 4 (in particular accounting and payment records). Deletion is irreversible.

8. Cookies and Similar Technologies

8.1 Strictly necessary (no consent required)

• session cookie (fitliftly_session, XSRF-TOKEN) — authentication and CSRF protection
• language preference (locale)
• role preference (active_role_context)
• App localStorage (remembered UI settings, such as venue chat visibility)

8.2 Application usage analytics

To understand how the App is used we rely on PostHog, operated exclusively in the EU (Frankfurt data centre), in both the web and the mobile app. The processing covers:

• usage measurement (page and screen views, clicks, performance metrics);
• key events in the App (e.g. signing up for a workout, QR check-in, adding or spending Credits) with their basic parameters (venue, amount of Credits) — recorded by our server, not by your device;
• session replay — in the web app only; a visual recording of navigation through the App used to improve usability; all form inputs are masked and sensitive blocks (chat messages, health data, food diary, credit balances, benefit-card numbers) are excluded from the recording entirely; no session recordings are made in the mobile app;
• for logged-in users, matching under a pseudonymous numeric identifier (no name or e-mail), supplemented only by the account roles and the month of registration.

The web app is configured so that the tool stores no cookies or other identifiers on your device — which is why no cookie-banner consent is required. The mobile app keeps a random technical installation identifier in its own storage; after login it is matched with your pseudonymous numeric identifier and on logout it is replaced by a new one, which ends the link to your account. We do not use the device's advertising identifiers (IDFA / Advertising ID), do not share the data with other apps and do not use it for advertising.

The legal basis is our legitimate interest in improving the Service (Art. 6(1)(f) GDPR). You may object to this processing at any time using the contacts in Section 7.

8.3 Marketing (with consent)

Currently not used.

8.4 Measuring website traffic

We measure traffic on the fitliftly.com websites with Umami, which we run on our own server (the data is not shared with anyone). It stores no cookies or other identifiers on your device and does not store your IP address. From the IP address and browser details it creates a one-way fingerprint that changes every month and serves only to tell visits apart, and it derives the approximate country and city from the IP address; the result is only aggregate statistics (numbers of visits and pages viewed, where visitors came from, country, device and browser type). The legal basis is our legitimate interest in improving the website (Art. 6(1)(f) GDPR). You may object to this processing at any time using the contacts in Section 7.

9. Security of Personal Data

We implement in particular the following technical and organisational measures:

• transport encryption (TLS 1.2+, HTTPS);
• password hashing (bcrypt);
• restricted access to the production database (administrators only);
• regular backups (daily incremental, weekly full);
• network segmentation (PostgreSQL and Redis are not exposed to the internet);
• security headers (HSTS, X-Frame-Options, etc.);
• protection against automated attacks (Cloudflare Turnstile, honeypot);
• regular operating system and library updates;
• access monitoring.

In the event of a security breach with risk to the rights of data subjects, we will notify you in accordance with Art. 33 and 34 GDPR.

10. Children

The App is not intended for persons under 18 and registration in this age group is prohibited. If we discover that we have collected data from a person under 18, we will delete the data immediately.

11. Changes to the Privacy Policy

This Policy may be updated from time to time. We will inform Users of material changes via e-mail and/or via in-App notification at least 15 days before the change takes effect. The current version is always available at fitliftly.com/privacy.

12. Complaint to the Supervisory Authority

If you believe that your personal data is being processed in breach of the GDPR, you have the right to lodge a complaint with the supervisory authority:

Office for Personal Data Protection (ÚOOÚ)
Pplk. Sochora 27
170 00 Prague 7, Czech Republic
uoou.gov.cz

13. Contact

For any questions regarding the protection of personal data, please contact us: