1. Who we are
Trainzeno is published by different operators depending on the platform:
- iOS version and this website: RC Portal s. r. o., Dunajská 8, 811 08 Bratislava, Slovakia, Company ID 44233493, Tax ID 2022645328, VAT ID SK2022645328.
- Android version: Štefan Marinčák, an individual developer based in Bratislava, Slovakia.
In this policy, “operator”, “we” and “us” refer to the operator responsible for the version of Trainzeno you use, or to RC Portal s. r. o. for this website. Both operators apply this same Privacy Policy. You can contact either operator through the Trainzeno support form.
2. What Trainzeno is
Trainzeno is a business organisation app for independent trainers. It helps users manage clients, sessions, attendance, training packages, payments, notes, progress records and financial summaries.
Trainzeno is free to use. The free version shows ads and includes the client app for up to three clients. An optional one-time purchase removes ads, and the optional Trainzeno Pro subscription removes the three-client limit of the client app and the ads (see section 11).
The same app also has an optional client mode (the “client app”): a trainer can invite a client, and the client then sees their own upcoming sessions and package balance in Trainzeno, can cancel a session with a short message, can take part in challenges set by the trainer, collects medals, receives resources from the trainer, can, with their consent, send the trainer a short check-in once a week, and may choose to share daily step and activity totals with that trainer. The client app is described in section 7.
3. Roles and responsibility for client records
The trainer using Trainzeno determines which client information is entered into the app and why it is processed. For this information, the trainer is generally the data controller and is responsible for having an appropriate legal basis, informing clients, keeping information accurate and deleting it when no longer needed.
We do not operate a central Trainzeno account system with names, email addresses or passwords, and we do not have routine access to client records stored in the app or in a user’s private platform cloud storage. Only when a trainer uses the client app is the limited information described in section 7 stored in our cloud service, so that it can be shown to the invited client and the trainer.
4. Information processed in the app
Depending on how the user uses Trainzeno, the app may process:
- client names, telephone numbers, profile photos and active status;
- birth dates, goals, health or training limitations and free-form notes;
- progress information such as body weight, waist measurement and progress notes;
- session dates, times, locations, duration, whether in person or online, an optional call or video link, group membership, attendance status and session notes;
- training package names, credit balances, the start and end date of a time-based online package, payment amounts, payment methods, payment status and due dates;
- challenges, milestones and medals, and messages to clients written by the trainer;
- financial summaries and reports calculated from the records entered by the user;
- clients’ weekly check-ins – these are stored only in the cloud service described in section 7, not on the trainer’s device.
Users should only enter information that is genuinely necessary for their training services. Sensitive health notes require particular care and an appropriate legal basis under applicable law.
5. Where app data is stored
On the device
Core Trainzeno records are stored locally on the user’s iOS or Android device. App widgets may access selected data through a shared app container on the same device.
Private platform cloud services
Where private cloud synchronisation or backup is available and enabled, app records may be synchronised or backed up through services provided by the user’s mobile platform, such as Apple iCloud and CloudKit on iOS or the Android backup to the user’s Google account. Platform providers process this data under their own terms and privacy policies. We do not use these services to create a central database accessible to other Trainzeno users.
Client app (only when used)
If a trainer turns on the client app and invites a client, the limited information listed in section 7 is stored in Google Cloud Firestore (Firebase) in Europe, provided by Google Ireland Limited. Notifications for the client app are delivered through Firebase Cloud Messaging and, on iPhone, the Apple Push Notification service. Everything else stays on the device as described above.
Manual backups and exports
Users may create backup files and financial PDF or CSV exports. These files are controlled by the user after export. The user is responsible for choosing a secure destination and for sharing them appropriately. Current manual app backups exclude client profile photos.
6. Device permissions and optional features
Notifications
If enabled, Trainzeno schedules local notifications on the device for unfinished session statuses, client birthdays, the end of a Trainzeno Pro free trial (see section 11) and, in the client app, optional session reminders. In the client app, the trainer and the client may also receive push notifications about the connection (see section 7). Notification permission is optional and can be withdrawn in the device settings.
Calendar
If the user enables calendar export and grants permission, Trainzeno creates and updates session events in a dedicated calendar on the user’s device. Calendar access is optional and can be disabled in the app or device settings.
Photos
The app may request access when the user chooses a client profile image, and may save a congratulation picture to the photo library when the user asks for it. Photos are used for the selected client profile and are not uploaded to our servers. The only exception is the optional small photo a trainer chooses to show to their clients in the client app (section 7).
Contacts
The user may import clients from the contacts on the device. On iOS, the system contact picker is used: Trainzeno receives only the contacts the user selects and does not get access to the rest of the address book, so no contacts permission is requested. On Android, where the system picker allows only one contact, the app asks for contacts permission when the user starts an import and reads the address book on the device only to show the list to choose from. From each selected contact the app takes only the name, one telephone number, the birthday and the photo, and stores them as a client record on the device (and in the user’s private platform cloud where enabled). Contacts are not uploaded to our servers, and the rest of the address book is not stored. Contacts permission on Android is optional and can be withdrawn in the device settings.
7. Client app, challenges and step sharing
The client app is optional. It is used only when a trainer turns it on and invites a client, and the client enters the personal invite code in Trainzeno. The client does not register with a name, email address or password: the app creates a random anonymous account (Firebase Authentication) so that only the right phones can read and write the shared information. The trainer signs in with Sign in with Apple (iPhone) or with Google (Android), so that invited clients stay connected on a new phone. The app asks Apple for no name and no email address; Google passes the Google account’s email address and name to Firebase Authentication. The app does not store them anywhere else and never shows them to clients. A trainer who turned the client app on earlier keeps an anonymous account until signing in. An invite code works once, on one phone, and for at most 7 days.
What is stored in the cloud for the client app
For each invited client, the following is stored in Google Cloud Firestore (Firebase):
- the invite code, its validity and status, and when the client connected;
- the first name or nickname the trainer chose for the client (not the full name stored in the trainer’s app), the type of the client’s phone (iPhone or Android) and when the client last opened the app;
- the name the trainer chose to show to clients and, if the trainer adds them, a small profile photo and telephone number;
- the client’s own sessions (date, time, length, individual or group, group name, place, whether it is in person or online and, if the trainer adds one, the link to the online call or to a video of the session, and whether the session is planned, attended or cancelled), sessions the client cancelled in the app, the optional message the client wrote with a cancellation and the trainer’s one reply;
- the client’s package balance (for example “3 of 10 left”), for an online package its start and end date, and whether it is paid or awaiting payment;
- challenges the trainer created for the client (type, goal, dates, the client’s progress and result, whether the client accepted it, days the client ticked off, and the trainer’s short words of encouragement); in group challenges only the group total is shown, never other clients’ names or results;
- medals the client earned (for example for the number of attended sessions or a met challenge) and an optional personal message from the trainer to a medal;
- for notifications: the notification token of the client’s and the trainer’s phone, the app language, the client’s notification choices and the trainer’s time zone (so that times in notifications are correct). Notification items are deleted as soon as they are sent, or after 24 hours;
- a technical counter per trainer of how many notifications were sent in the last hour, used only to prevent abuse; it contains no personal data;
- if the client allows it, the daily step totals and activity totals described below;
- if the client switches it on and their trainer has Trainzeno Pro, the watch measurements and workouts described below;
- if the client gives consent, their weekly check-ins and the trainer’s response to them (see Weekly check-ins below);
- if the client gives consent, their progress – the measurements the trainer records for them (see Progress and measurements below).
Payment amounts, notes, goals, health notes and the client’s stored telephone number are never sent to the client app. (Answers in the weekly check-in are entered by the client themselves, and measurements go to the client app only with the client’s consent – see below.)
A call or video link is opened in the app it belongs to (for example Google Meet or Zoom). Trainzeno does not take part in the call and receives nothing from it.
Notifications in the client app are limited to: a new challenge, encouragement from the trainer, a new medal and a message to a medal, the trainer’s reply to a check-in (for the client, each group can be switched off in the client app under Profile), and, for the trainer, that a client cancelled a session, joined the app or left it, or sent a check-in. The text of notifications to the trainer is created on our server from the information listed above.
Resources from the trainer (Trainzeno Pro)
A trainer with a Trainzeno Pro subscription can send a connected client up to five resources – for example a training plan, a meal plan, a video or an article – as a PDF file, an image (JPG or PNG) or a link, with an optional name and note (up to 500 characters). Files are stored in Cloud Storage for Firebase in the European Union (Belgium), provided by Google Ireland Limited. The client’s cloud record holds each resource’s name, type, size and date, the note, the address of a link and whether the client has opened it. Resources can be read only by that trainer and that connected client; only a trainer signed in with Sign in with Apple or Google can upload them, up to 10 MB per file and 1 GB per trainer in total. Photos are made smaller on the phone before sending. A new resource in the same place replaces the previous one, and the previous file is deleted. We do not read or otherwise process the content of resources – the trainer chooses it and is responsible for it (see section 3). A link opens in the app or browser it belongs to.
When the trainer sends a new resource, the client gets a notification; it can be turned off in the client app under Profile (New resources).
Weekly check-ins (Trainzeno Pro)
If a trainer with a Trainzeno Pro subscription sets up a weekly check-in for a client, the client answers, once a week, a few questions the trainer has chosen or written – for example body weight, waist measurement, strength in a main lift, performance, energy, fatigue, sleep, stress, hunger, pain, number of workouts and adherence to the meal plan, or a short text answer – and may add a message of their own. The trainer then marks the check-in as seen or sends a short reply.
Some answers are health data. Before the first check-in, the client app therefore asks the client for explicit consent (Article 9(2)(a) GDPR). Without consent, nothing is sent, and the client can continue to use the app without check-ins.
- Answers are stored in Google Cloud Firestore (Firebase) in the European Union with the client’s information. A check-in that has been started but not yet sent stays only on the client’s phone.
- Only the client and their trainer can see them. On the trainer’s phone they are only displayed – they are not saved in the trainer’s records, in the private platform cloud (for example iCloud) or in backups.
- They are not used for advertising, usage statistics or in crash reports, are not sold and are not shared with any other party (except Google as the cloud provider that stores them for us).
- The notification to the trainer about a new check-in contains only the client’s name and the date of the check-in; the notification to the client about a reply contains the beginning of the trainer’s reply. The trainer can switch off check-in notifications under Settings → Notifications, the client under Profile (Check-ins). The reminder on the check-in day is scheduled locally by the client’s phone.
- Consent can be withdrawn at any time in the client app under Profile → Check-ins → Withdraw consent; this immediately deletes all of the client’s check-ins. They are also deleted immediately on disconnection – whether started by the client or by the trainer – and automatically about 6 months after the last activity (section 14).
Progress and measurements (Trainzeno Pro)
If the trainer has Trainzeno Pro and the client has given consent to check-ins, the client app also shows the client’s progress (My progress): the measurements the trainer records for that client – for example body weight, waist or other measurements the trainer picks from the catalogue or creates, such as a 5 km time, cycling power (FTP) or resting heart rate – at most one value per measurement and day, without the trainer’s notes, together with the numbers from the client’s check-in answers. Measurements are entered by the trainer or by the client in a check-in; if the client switches it on, some (for example weight, resting heart rate or sleep) also come from the client’s watch or smart scale – see Watch measurements and workouts below.
- Some measurements are health data. They are sent to the client app only with the client’s explicit consent given for check-ins (Article 9(2)(a) GDPR).
- They are stored in Google Cloud Firestore (Firebase) in the European Union with the client’s information. The client’s phone also stores there the numbers from its check-ins used for the chart and the progress medals the client has earned; the trainer can hide a single point from the chart.
- Only the client and their trainer can see them. They are not used for advertising, usage statistics or in crash reports, are not sold and are not shared with any other party (except Google as the cloud provider that stores them for us).
- When the trainer’s Pro ends or the client withdraws consent, progress is no longer sent to the client app. The data is deleted on disconnection and automatically about 6 months after the last activity (section 14).
Protection against misuse
To protect the cloud service from fake or modified apps, Trainzeno uses Firebase App Check with Apple App Attest on iPhone and Google Play Integrity on Android. These services confirm to Firebase that requests come from a genuine copy of the app on a genuine device. They do not give us any personal information about the user.
Steps and activity from Apple Health and Health Connect
With the client’s permission, the client app reads from the phone’s health platform – Apple Health (HealthKit) on iPhone and Health Connect on Android – only the following, as daily totals:
- Steps – the number of steps per day;
- Active minutes – on iPhone the daily exercise time, on Android the total length of the day’s exercise sessions;
- Number of workouts – how many workouts or exercise sessions were recorded that day (and how many of them count towards a workout challenge);
- whether the latest data came from the phone or from a watch.
Apart from these totals and the watch measurements and workouts described below, the app reads no other health data, and it never reads location or routes. It never writes data to Apple Health or Health Connect and reads only while the client app is open on the screen – never in the background. The daily totals of the last 45 days are stored in the cloud (older days are removed automatically) so that the client’s own trainer can see them and challenges can be counted. They are shown only to the client and to that trainer; in a group challenge, only the sum for the whole group is shown to its members.
Data from Apple Health and Health Connect are used only to show the client and their trainer these daily totals and the watch measurements and workouts described below, to count challenges and to prefill the client’s check-in. It is not used for advertising or analytics, is not sold, is not shared with any other party (except Google as the cloud provider that stores it for us) and is not used to make decisions about the client. Trainzeno’s use of information received from Health Connect adheres to the Health Connect Permissions policy, including the Limited Use requirements.
Watch measurements and workouts (Trainzeno Pro)
If the trainer has a Trainzeno Pro subscription, the client app also offers the client to share data that their watch, phone or smart scale writes to Apple Health or Health Connect. Nothing is switched on in advance: the client switches on only the items the trainer should see, or shares nothing. The app reads only the items that are switched on:
- Workouts – start, duration, sport, distance, active calories, elevation gain, average and maximum heart rate, time in heart-rate zones and the name of the device or app that recorded the workout (for example Garmin);
- Resting heart rate – resting heart rate and heart rate variability (HRV), one value per day;
- Sleep – how many hours the client slept per night;
- Weight and body fat – from a smart scale, one value per day;
- VO2max – from the watch, one value per day.
The app never reads location, routes or raw heart-rate curves. A workout’s heart-rate zones are calculated directly on the client’s phone – individual heart-rate readings never leave the phone. For the zones, the trainer may send an estimated maximum heart rate based on the client’s age (never the date of birth).
- Data are read only while the client app is open on the screen – never in the background. Nothing is ever written to Apple Health or Health Connect.
- The data are stored in Google Cloud Firestore (Firebase) in the European Union with the client’s data: daily measurements for the last 120 days and workouts for the last 42 days (older ones are removed automatically). On the trainer’s phone they are only displayed – they are not saved in the trainer’s records, in the private platform cloud (such as iCloud) or in backups.
- Only the client (My progress) and their trainer (the client’s progress and workouts) can see them – never other clients. They may prefill answers in the weekly check-in, but nothing is sent until the client sends the check-in themselves.
- They are health data. The legal basis is the client’s explicit consent (Article 9(2)(a) GDPR), given by switching on the individual items and allowing access in Apple Health or Health Connect. Everything stated above about data from Apple Health and Health Connect applies to them: no advertising, no analytics, no sale and no sharing with any other party (except Google as the cloud provider).
- Deletion: an item that is switched off is removed from the cloud immediately, and switching all items off deletes all watch data. The data are also deleted on disconnection (whether started by the client or the trainer), when the trainer’s Trainzeno Pro ends, and automatically about 6 months after the last activity (section 14). With a new connection – for example to another trainer – everything is off again and the app asks again.
Your choices as a client
- Sharing is optional: the client can choose “Not now” and use the client app without it.
- Each item (steps, active minutes, number of workouts or watch items) can be switched off at any time in the client app under Profile; it then stops being sent immediately and is removed from the cloud with the next update.
- Permission can be withdrawn at any time in Apple Health (Settings → Health → Data Access & Devices → Trainzeno) or in Health Connect (Settings → Health Connect → App permissions → Trainzeno).
- Notifications for challenges and medals can be switched off in the client app under Profile, or all notifications in the device settings.
- “Disconnect” in the client app ends the connection and deletes the client’s data from the cloud, as described in section 8.
Usage statistics and crash reports in the client app
The client app uses the same crash reports and usage statistics as the trainer app, described in section 9. After connecting with a code, the client app asks once whether it may send anonymous usage statistics; they are sent only if the client chooses “Allow”. Crash reports are on and can be switched off. Both can be changed at any time in the client app under Profile → Other. The choice applies to the whole phone, so a phone that has already answered in the trainer app is not asked again. Neither ever contains the client’s name, steps, session dates or health information.
Demo for app reviewers
The code DEM-001 opens a demonstration of the client app with sample data stored only on the device. It does not create an account and sends nothing to the cloud.
Roles
The trainer decides to invite a client and is generally the data controller for the client information shown in the client app (see section 3). The client decides whether to share step and activity totals and watch measurements and workouts with their trainer and whether to send weekly check-ins. We provide the service and store the information described in this section only to make the client app work.
8. How to delete your data
Trainzeno does not have user accounts with a name, email address or password. You can delete your information directly in the app, without contacting us:
Clients (client app)
- In the client app, open Profile → Disconnect. Your daily step and activity totals, your watch data, your check-ins, your sharing choices and your notification token are deleted from the cloud immediately, and your phone no longer has access. The rest of your client app information (sessions, package balance, challenges, medals and messages copied for you) is deleted when your trainer’s app processes the disconnection, at the latest within 30 days.
- To delete only your check-ins, open Profile → Check-ins → Withdraw consent. All your check-ins are deleted from the cloud immediately, and no more are sent until you give consent again.
- You can also ask your trainer to disconnect you, with the same effect.
- Challenges that were running when you disconnected end that day. Your result up to that day stays only in your trainer’s own records on their phone, like any other record the trainer keeps; it is not sent back to the cloud, and if you are invited again later, earlier challenges and messages are not shown to you as new.
- Switching off an item in Profile (steps, active minutes, number of workouts or watch items) removes only that item from the cloud with the next update.
Trainers
- To disconnect one client, open the client in the app and choose Client app → Disconnect (or cancel a pending invite). That client’s cloud information is deleted.
- To delete everything stored in the cloud for the client app, open Settings → Client app → Turn off the client app. This deletes all invite codes, all clients’ cloud information, your card shown to clients, your notification token and your account (anonymous, or the Apple or Google sign-in – with Apple, the app also revokes the Sign in with Apple authorization). All connected clients are disconnected. Only the technical notification counter described in section 7, which contains no personal data, remains. Your records on your own phone are not affected.
- Records stored on the device (clients, sessions, payments and notes) can be deleted in the app at any time, or completely by deleting the app. Copies in your private platform cloud (for example iCloud) or in backup files you exported are under your control and can be deleted there.
Crash reports, usage statistics and support
- Crash reports and usage statistics can be switched off in the trainer app under Settings → About and in the client app under Profile → Other; reports not yet sent are then deleted. Already collected data is deleted automatically after the periods in section 9.
- For anything else, or if you cannot use the app any more, send a request through the Trainzeno support form and we will delete the information we can identify, normally within 30 days.
- To delete one resource, open the client and choose Info → Resources → ⋯ → Delete; the file is deleted from the cloud within a few seconds. All of a client’s resources are also deleted when the client is disconnected, when a new invite code is created, when the client app is turned off and when your account is deleted.
9. Crash reports and usage statistics
Trainzeno uses Firebase Crashlytics and Google Analytics for Firebase, services provided by Google Ireland Limited, to keep the app stable and to understand which features are used. They work the same way on iOS and Android and apply to everyone who uses Trainzeno – trainers in the trainer app and clients in the client app.
Crash reports
When the app crashes or a technical error occurs, Crashlytics receives a report with the technical details of the error (where in the program it happened and an error code), the device model, operating system and app version, the name of the screen in use, a random installation identifier and rough usage ranges such as the number of clients as a range (for example “6–15”) in the trainer app. Crash reports are switched on by default because we have a legitimate interest in finding and fixing errors. They can be switched off at any time in the trainer app under Settings → About and in the client app under Profile → Other; reports not yet sent are then deleted. Google keeps crash reports for up to 90 days.
Usage statistics (only with your permission)
Usage statistics are off until the user chooses “Allow” when the app asks – a trainer once after setting up the app, a client once after connecting with a code. If allowed, Google Analytics for Firebase receives which screens are opened and which actions are completed (for example that a client, payment or session was added, or that a backup was exported; in the client app, for example, that a challenge was accepted or a session cancelled), coded details such as the session type or payment status, whether Trainzeno Pro is active and when its offer was shown or a subscription started (without prices, payment details or store account information), ranges instead of exact numbers, the app language and currency, device and operating system details, the approximate country derived from the IP address and a random app-instance identifier. Permission can be withdrawn at any time in the trainer app under Settings → About and in the client app under Profile → Other; collection then stops immediately. Event-level data is kept for 2 months; aggregated reports may be kept longer.
What is never sent
This applies equally to trainers and clients: neither service receives client names, telephone numbers, photos, birth dates, notes, messages, health information, step or activity data, check-in answers, resources from the trainer, progress measurements, payment amounts, session dates or any other content of the records entered in the app. We do not assign a user ID, do not use the advertising identifier for analytics, have switched off Google signals and do not use these statistics for advertising or ad personalisation.
More information is available in Firebase privacy and security information.
10. Advertising and consent
The free version of Trainzeno shows ads in the trainer part of the app using Google Mobile Ads and Google’s User Messaging Platform. No ads are shown after the one-time “Remove ads” purchase or while Trainzeno Pro is active, and the client app never shows ads. Subject to the user’s region, consent choices and device settings, Google and its partners may process information such as device identifiers, IP address, approximate location derived from IP, advertising interactions, diagnostics and consent signals to provide, measure and protect advertising. Ads are not loaded before the consent choice has been made where consent is required.
Where required, the app displays a consent request before personalised advertising is used. On Apple devices, permission to track across other companies’ apps and websites is requested through Apple’s App Tracking Transparency framework when applicable. On Android devices, users can reset or delete their advertising ID in the device settings. Refusing tracking does not prevent use of the app.
More information is available in Google’s Privacy Policy and Google’s advertising information.
Ad measurement (Meta)
We also promote Trainzeno with ads on Facebook and Instagram. To know how many installs and new trainers these ads bring, the trainer app includes the Meta SDK from Meta Platforms Ireland Limited. It starts only if the trainer chooses “Allow” when asked “Help improve Trainzeno” (the question lists this purpose). It then sends only that the app was installed or opened and how long it stayed open, and once that the trainer finished setting up the app (completed registration, without any details), together with device, operating system and app version details and the IP address. The advertising identifier is sent on Android with this consent and on iOS only if the user has also allowed tracking (App Tracking Transparency). Meta receives no client records or any other content entered in the app; automatic events and purchase events are switched off. The client app never uses the Meta SDK. Measurement can be switched off at any time in Settings → About → Ad measurement (Meta).
More information is available in Meta’s Privacy Policy.
11. In-app purchases and Trainzeno Pro
Trainzeno offers two optional purchases in the trainer part of the app:
- Remove ads – a one-time purchase that permanently removes ads on the store account it was bought with.
- Trainzeno Pro – an auto-renewable subscription, billed monthly or yearly, that removes the three-client limit of the client app (so challenges can include whole groups), removes ads and unlocks resources for clients, weekly check-ins and clients’ watch data (section 7). New subscribers may be offered a free trial of one month. Prices are shown in the app and in the store before purchase and may differ by country.
All purchases are processed by the platform store – Apple’s App Store on iPhone and Google Play on Android – and are subject to the store’s terms (for iOS, the Apple Standard End User License Agreement). Payment is charged to the user’s store account. A subscription renews automatically at the end of each period unless it is cancelled at least 24 hours before the period ends; a free trial converts into a paid subscription at its end unless cancelled before. Subscriptions are managed and cancelled in the store account settings (on iPhone: Settings → your name → Subscriptions; on Android: Google Play → Payments & subscriptions → Subscriptions) or from Settings → Trainzeno Pro in the app. Refunds are handled by Apple or Google under their rules.
We do not receive or store payment card details, billing addresses or store account information. The app checks with the store on the device whether a purchase or subscription is active (including its type, renewal or end date and whether a free trial is running) and keeps only this status on the device; it is not sent to our cloud service. Two days before a free trial ends, the app shows a local reminder notification if notifications are allowed; it is removed if the trial is cancelled.
When Trainzeno Pro ends, nothing is deleted: connected clients stay connected and keep their sessions, package balance and running challenges. Only new invitations beyond three clients and new challenges with more than three participants require Pro again, and ads return unless “Remove ads” was purchased.
To send resources and for weekly check-ins (section 7), the app does send proof of the subscription from the store to our server (Cloud Functions for Firebase in Europe) – on iPhone the signed App Store transaction, on Android the Google Play purchase token. The server checks it directly with Apple or Google and stores only the date until which the subscription is valid, the store, the time of the check and an identifier of the subscription, so that one subscription can be used by only one trainer account. We do not receive payment or store account details this way.
The exception to the previous paragraph is resources from the trainer: when Trainzeno Pro ends, the client can still see the resources sent for 30 days; after that the files and their records are deleted automatically. If the trainer renews Pro within that time, nothing is deleted. New resources can be sent only with Pro. The same applies to new check-ins: clients can send them only while Pro is active (and for another 7 days after it ends, while the server checks whether the subscription has been renewed); check-ins already sent remain while the client is connected.
12. Website and support enquiries
13. Legal bases
Where we process personal information directly, the legal basis may be performance of a contract or steps requested before a contract, performance of the purchase or subscription contract (concluded through the platform store), compliance with legal obligations, legitimate interests in operating and securing Trainzeno (including protection against misuse), fixing errors (crash reports) and providing support, or consent where required for usage statistics, advertising, step sharing or optional permissions. For weekly check-ins, which may contain health data, and for watch data, the legal basis is the client’s explicit consent (Article 9(2)(a) GDPR), which can be withdrawn at any time.
Trainers using the app must determine their own legal basis for processing their clients’ information.
14. Retention
App records remain on the device and, where enabled, in the user’s private platform cloud storage until changed or deleted by the user. Client app information (section 7) is kept while the client is connected; daily step and activity totals are kept for the last 45 days only, watch data for at most 120 days (workouts 42 days), and check-ins only for as long as the client’s consent remains valid. When the connection ends, the client’s step and activity totals, their watch data, their check-ins, sharing choices and notification token are deleted immediately and the rest is deleted at the latest within 30 days (see section 8). If the client app is no longer used and nobody ends the connection – for example because the trainer or the client deletes the app – the client app information, the trainer’s card shown to clients and the notification tokens are deleted automatically about 6 months after the last activity. Invite codes stop working once used or after 7 days and are then deleted automatically. An invited client’s sessions and package balance are sent to the cloud as soon as the invite is created, so the client sees them right after entering the code; if nobody uses the code, they are deleted automatically one week after it expires. Notification items are deleted when sent, or after 24 hours. Exported files remain wherever the user saves them. Crash reports are kept for up to 90 days and event-level usage statistics for 2 months, as described in section 9. Support emails are retained only for as long as reasonably necessary to answer the request, handle related issues and meet applicable legal requirements. Resources from the trainer (section 7) are kept until the trainer deletes or replaces them and while the client is connected; they are deleted automatically 30 days after Trainzeno Pro ends. Subscription check data is kept while the trainer’s account exists.
15. Data sharing
We do not sell client records. Information may be processed by service providers only where necessary to provide the relevant feature, including Apple and Google for mobile platform services, notifications, app attestation and store purchases and subscriptions, Google (Firebase) for crash reports, with permission usage statistics, and for storing the client app information described in section 7, Google for advertising, consent management and email support, Resend for delivery of website support enquiries, and infrastructure providers used to host this website. Information may also be disclosed where required by law or to protect legal rights. With consent (section 10), Meta Platforms Ireland Limited also processes ad measurement information. Files of resources from the trainer (section 7) are stored by Google in Cloud Storage for Firebase.
16. International transfers
Client app information is stored in Google Cloud Firestore in the European Union. Apple, Google and hosting providers may still process some information outside Slovakia or the European Economic Area, for example to deliver notifications. Where applicable, those providers use recognised transfer mechanisms and safeguards described in their own privacy documentation. Meta may also process ad measurement information in the United States under the EU–U.S. Data Privacy Framework and standard contractual clauses. Resources from the trainer (section 7) are stored in Cloud Storage for Firebase in the European Union (Belgium).
17. Security
Trainzeno uses security features provided by iOS, Android and their associated platform services. Information sent to the cloud is encrypted in transit, access is limited by security rules so that each phone can read and write only its own connection, and Firebase App Check helps block requests from modified apps. No method of storage or transmission is completely secure. Users should protect their device with a passcode, keep its operating system updated, limit access to exported files and avoid entering unnecessary sensitive information.
18. Your rights
Depending on applicable law, individuals may have rights to access, correct, erase, restrict or object to processing, receive data in a portable form and withdraw consent. For information entered by a trainer about their clients, requests should normally be directed to that trainer. For information processed directly by us, use the Trainzeno support form. Section 8 describes how to delete your data directly in the app. Usage statistics and crash reports can also be switched off in the trainer app under Settings → About and in the client app under Profile → Other. Clients can stop step sharing or disconnect directly in the client app under Profile.
Individuals in the European Economic Area may also lodge a complaint with their local supervisory authority. In Slovakia, this is the Office for Personal Data Protection of the Slovak Republic.
19. Children
Trainzeno is intended for professional trainers and is not directed to children. A trainer who records information about a minor, or invites a minor to the client app, is responsible for meeting applicable legal requirements, including obtaining parental consent where necessary and limiting the information entered. Step sharing in the client app should be enabled for a minor only with the consent of a parent or guardian where the law requires it.
20. Changes to this policy
We may update this Privacy Policy as Trainzeno develops or legal and technical requirements change. The latest version will always be published on this page with a revised date.
21. Contact
iOS version and website
RC Portal s. r. o.
Dunajská 8
811 08 Bratislava, Slovakia
Company ID: 44233493
Tax ID: 2022645328
VAT ID: SK2022645328
Android version
Štefan Marinčák
Bratislava, Slovakia