Українська версія: Політика конфіденційності
Version 1, effective 6 October 2026.
Flexa is an app for personal trainers and their clients. This policy explains what data we collect, why, who we share it with, and how you can control it.
This policy applies to the Flexa app (“Flexa”, “we”). The person responsible for processing your data is Davyd Nykytiuk, the developer of the app. For any questions about your data, write to support.flexa@gmail.com.
Flexa has two kinds of accounts. A trainer creates programmes, plans workouts and keeps track of sessions. A client does the workouts, records their own measurements and, if they choose, shares health data.
A trainer may enter a client’s data before the client signs up: their name, programme, schedule, session balance and notes. The trainer is responsible for having a basis to enter this data. When the client accepts the invitation, this data moves to their account.
Account. Email address, first and last name, profile photo, role (trainer or client), language, units, time zone. If you sign in with Google or Apple — the identifier of that account.
Client profile. Date of birth, sex, height, weight and target weight, fitness level, goals, injuries and limitations — if you provide them.
Workouts. Programmes, schedule, completed sets (weight, repetitions, duration), skipped exercises, substitutions, the trainer’s comments on workouts.
Weight history. Weigh-ins you enter manually or import from Apple Health or Health Connect.
Health data from your device. Only if you allow access to Apple Health (iOS) or Health Connect (Android): sleep duration and stages, active and resting calories, weight. We only read this data and never write anything to Apple Health or Health Connect.
Communication. Chat messages between trainer and client, and the photos, videos and voice messages you send.
Video calls. We do not record calls. We store only the start and end time and who took part.
Trainer’s notes. A trainer’s private notes about a client. Only the trainer who wrote them can see them.
Session tracking. The number of sessions in a package and their use. No payments are processed in the app.
Technical data. Device token for notifications, platform, app version.
| Purpose | Data | Legal basis |
|---|---|---|
| Provide the service: account, programmes, workouts, schedule, chat | Account, profile, workouts, communication | Performance of the contract (Terms of Use) |
| Show analytics: muscle group balance, progress, weight | Workouts, weight history | Performance of the contract |
| Show sleep and calories to you and, if you choose, to your trainer | Health data from your device | Your explicit consent |
| Turn a trainer’s text note into a workout | Text of the note | The trainer’s consent |
| Send notifications about messages and workouts | Device token, names, workout titles | Your permission in the phone’s settings |
| Protect the service and fix errors | Technical data | Legitimate interest |
We do not sell your data, we do not show ads, and we do not use health data for marketing.
Your trainer sees your profile, workouts, weight history and notifications about missed sessions. Your trainer sees sleep and calories only if you have turned on “Share with trainer” in the settings; you can turn it off at any time. When your work together ends, the trainer loses access to your data: your programmes are archived on their side, future workouts are cancelled, and the chat becomes read-only.
A client sees their own data, programmes and messages. A client does not see the trainer’s private notes.
Services that help us operate (section 6) — only to the extent needed for their function.
Public authorities — only on a lawful request.
| Service | Purpose | Where data is processed |
|---|---|---|
| Supabase | Database, files, sign-in | EU (Ireland) |
| Google Gemini API | Turning text notes into workouts | Google, including the USA |
| Google Firebase Cloud Messaging | Delivering notifications | Google, including the USA |
| Google Sign-In | Sign-in with Google | |
| Apple: Sign in with Apple, APNs, HealthKit | Sign-in with Apple, iPhone notifications, Apple Health data | Apple; Health data is read on the device |
| Google Health Connect | Health data on Android | Read on the device |
| LiveKit | Video calls between trainer and client | LiveKit Cloud — servers in several countries; calls are not recorded |
Some of these services may process data outside Ukraine and the EU. In those cases we rely on agreements with the providers that ensure adequate data protection.
When a trainer pastes a text note with a workout, we send its text and the exercise names from their library to the Google Gemini API. The model returns the structure of the workout: exercises, sets, weights. The trainer reviews the result before saving it.
We use the Gemini API on its paid tier. Under its terms, Google does not use the data sent to train its models and processes it as a data processor under contract. Do not put data in notes that is not needed for the workout.
Before the first conversion, the trainer gives separate consent in the app; it can be withdrawn in the settings.
You can:
To exercise a right, write to support.flexa@gmail.com. We reply within 30 days.
Flexa is intended for people aged 16 and over. We do not knowingly collect data from younger users. If you learn that such an account exists, write to us and we will delete it.
Data is transmitted only over encrypted connections. Access in the database is restricted by rules: everyone sees only their own data and the data of those they work with. Files — photos, videos, voice messages — are kept in private storage and opened through temporary links.
We will notify you in the app about material changes before they take effect and ask for your consent where needed. The version number and date are at the top of this document.
Davyd Nykytiuk, developer of the Flexa app — support.flexa@gmail.com.