Skip to content

Legal document

Privacy Policy

Effective from:
17 November 2026
Last updated:
17 November 2026

1. Controller and scope

Rexly s. r. o. Registered office: Račianska 14350/64B, 831 03 Bratislava, Slovak Republic Company ID: 57 516 812 · Tax ID: 2122791220 · VAT ID: SK2122791220 Commercial Register of the Bratislava III Municipal Court, Section Sro, Insert No. 197507/B Email: support@trely.eu · privacy: privacy@trely.eu Web: https://trely.eu

The privacy contact is privacy@trely.eu. Trely assessed GDPR Article 37 and, as of the effective date, is not required to appoint a data protection officer; this is reviewed regularly.

2. Our roles

Trely is the controller for account, public-profile, enquiry, subscription, support, security and service-operation data. For client data entered by a trainer, physiotherapist or another professional, that professional is the controller and Trely is the processor under GDPR Article 28. The professional determines the purpose, legal basis and information supplied to clients. Trely’s processor duties are included in section 5 of the Terms accepted by the trainer together with this policy. For card-payment processing, Stripe acts under its own terms and privacy policy.

3. Data we process

Identity and contact data; data of a client without the app entered by the trainer (name, email, phone number and language); account, public-profile, enquiry and subscription data; communications, chat, support and reviews; calendars, bookings, training and rehabilitation plans; height, weight, BMI, body measurements, goals, injuries, test results and progress; photos, videos with sound, documents and other files; IP address, device identifiers and time zone, logs, app and OS version; billing data, payment amount, currency, status and identifier, Stripe connected-account identifier and verification state. Trainers provide identity and payment-account verification details directly to Stripe. Trely does not see full payment-card numbers. Trely is not intended to process data about people under 16.

4. Purposes, legal bases and retention

Account and service features: performance of the contract while the account exists; after that, we delete or anonymise the data without undue delay. Public profiles and enquiries: performance of the contract and steps requested before an agreement with a trainer; a profile remains public until the trainer hides it, and enquiry data is retained while it is handled and then for as long as necessary for that purpose, after which it is deleted. When a client deletes their account, we promptly remove their access, contact and profile data, messages, progress photos, measurements, intake forms, private notes linked to their account and client-specific training records; a note written on a shared group session remains with the trainer, because it belongs to the session, not to an individual participant. We keep messages and photos in the chat with your trainer for as long as the account exists. Videos and documents sent in private and group chats are deleted automatically 90 days after they were sent; the message stays in the chat with a note that the file is no longer available. If a message has been reported, we delete the file only after the report has been dealt with. We delete it sooner if the sender removes it, and in the same cases as photos in a chat. After you are disconnected from the trainer, you no longer see the chat in the app; the messages stay stored. If you delete your account, we delete the whole chat with your trainer. If the trainer deletes their account, we delete their messages; yours stay stored but are no longer shown in the app. When a trainer deletes their account, the trainer’s record of the client is disconnected from the trainer. If the client has their own account, the client’s name and email stay in that record, because they are the client’s data and belong to the client’s account; they are erased when the client deletes their own account. If the client has no account of their own, we send a notice to the email address the trainer provided, offering to move this record and the history of sessions and payments to the client’s own account. If the client does not do so within 7 days of the trainer’s account being deleted, we erase the client’s name and contact details from that record. If we have no email address or the notice cannot be delivered, we erase them within the same period without a notice. Messages and photos in a group chat stay in the chat history after a member leaves the chat, is removed from the group or is disconnected from the trainer, and the others still see them under the author’s name. When you delete your account, we also delete the messages and photos you sent in group chats; when you erase your data with a particular trainer, we delete them in that trainer’s groups. After you are disconnected from a trainer, you can remove that trainer’s access to your data: the trainer no longer sees it, we delete the notes the trainer kept about you, your sessions and your payments, and your measurements, progress photos and intake forms stay in your account. If you erase your data with that trainer, we also delete your measurements, progress photos, intake forms, habits, achievements and the photos you sent the trainer in the chat. If a trainer deletes a group or their account, the whole group chat is deleted. If the trainer switches the group chat off, the history stays stored: the trainer can read it, the clients no longer can, and nobody writes in the chat. Otherwise we keep the messages for as long as the group exists. Historical bookings, payments and operational audit records remain without the client’s original identity. Client data: on the professional user’s instructions. Clients without the app: a trainer can work with a client who has no Trely account. The trainer enters the client’s name, email and, where relevant, phone number and language; the trainer is the controller of this data and Trely processes it on the trainer’s instructions. The client receives emails about sessions and payments (proposal, confirmation, change, cancellation, reminder, payment and refund) with a private link for viewing and handling the session without signing in. The link is intended for that client only and is valid for a limited time. Proposals and reminders can be unsubscribed from via a link in every email; messages about confirmed sessions, changes and payments continue. Anyone who received an email by mistake can report it via a link in the email. The trainer can see whether emails are reaching the client and whether the client has unsubscribed. Emails are sent by Resend; we record whether an email was delivered, not whether it was opened. To protect against misuse, on the public page of a group session we store a fingerprint of the IP address for a few minutes; the address cannot be recovered from it. We keep the data of a client without the app, and the contact details of a guest who joined a group session via the web, for as long as necessary for sessions and payments, and then anonymise or erase them. Payment records are kept as for other payments. Support: contract or legitimate interest, for as long as necessary to handle the request. Accounting and payment records: legal obligation, 10 years from the end of the relevant accounting period. We retain records of failed payment attempts together with the other payment records. Subscriptions and payments: contract, security and fraud prevention, subject to statutory periods and the rules of Apple, Google, RevenueCat and Stripe. Saved card and consent to automatic payments: the legal basis is performance of the contract. The card itself is stored by Stripe on the trainer’s account; Trely holds only the payment-method identifier, the card brand, the last four digits, the expiry date and the consent record (text version, time, amount, currency and date). Trely keeps the card data until the client removes the card, withdraws consent or deletes the account; it keeps the consent record for as long as necessary to demonstrate the consent and to handle the payments made under it. A client without the app can also save a card via their private link. The same applies: the card is stored by Stripe on the trainer’s account, and Trely holds the payment method identifier, card brand, last four digits, expiry date and a record of consent to each charge. When the card is removed, we erase this data and detach the card at Stripe as well. E-mails about a failed payment and required authentication: the legal basis is performance of the contract; they are sent by the Resend service. E-mails to trainers during the trial: the e-mail after you confirm your registration, the notice one week before the trial ends and the e-mail after it has ended are sent for the performance of the contract. Further e-mails with tips on getting started with Trely (for example connecting your first client or scheduling your first session), including a reminder before the trial ends, are sent on the basis of legitimate interest. To choose an e-mail we use the state of your account: connected clients, sessions and recurring sessions, packages, groups and group chat, public profile, online payments, working hours, reviews and review requests, subscription, last activity and device time zone. You can object to them at any time with the unsubscribe link in each such e-mail, without signing in; we will then not send them to you again. The e-mails contain no tracking pixels. We record which e-mail we sent, when and with what result, and, if you click a link in the e-mail, which link and when. We keep these records for as long as necessary for that purpose and the unsubscription for as long as the account exists. We send news, offers and tips from Trely by notification or e-mail only with your consent, which you can withdraw at any time in Settings. Consent to news, offers and tips that you gave for notifications before this version of the policy also covers e-mails; you can withdraw it in Settings or with the link in the e-mail. We keep a record of when and to which wording you gave or withdrew consent for as long as needed to prove it. Product analytics: legitimate interest in improving security and usability; we use a pseudonymous account identifier, role, app version, OS and feature-use data, not chat content, photos, videos, documents or health data. We retain product analytics data for as long as necessary for that purpose; the analytics provider (PostHog) retains it for 7 years. Our plan with the provider does not let us set a shorter period. When you delete your account, we ask PostHog to delete the data linked to your account. Ad measurement: only with your consent, which you can withdraw at any time in Settings. Once you consent, Google (Firebase Analytics) and Meta receive your device’s advertising identifier and information that you opened the app, registered and in which role, completed your profile, added your first client, had your first session and bought a subscription, including its type, amount and currency. In doing so, Google also derives an approximate location, such as country and city, from your device’s IP address. This tells us which ads bring people to Trely. Without consent these tools are not started. Google and Meta also process this data in the USA and use it under their own policies as well. Notifications: to send you a notification about a session, message or payment, we store your device’s notification identifier and its model name (performance of the contract). Notifications are delivered by Expo through Apple and Google services. We erase the identifier once it has not been used for a longer period. You can turn notifications off in your device settings. We retain message delivery records, booking status history, security and administrator audit records and records of administrative tasks for as long as necessary to keep the service secure and running. Error diagnostics: legitimate interest in a secure and working service. When an error occurs, and for a share of performance measurements, we send Sentry a technical description, the app and system version, the account identifier and the role. We do not send your email, name, message content or screenshots. Sentry and PostHog process data in the EU. Account activity: we record the time of the last sign-in, the days on which the account was active and the app version on the device, so that we can help with support and understand how the service is used (legitimate interest). Only the Trely team can see this data. We retain operational logs, error reports and database backups for as long as necessary for their purpose. We keep backup copies of files for 30 days; after that they are overwritten. Data you have deleted remains in them until then. Data held by external providers (Sentry, PostHog, Stripe, Resend, RevenueCat) and in backups is retained according to those providers’ settings. We permanently retain the record of who accepted which version of the legal documents and when, and the record of how a data-subject request was handled. We retain contact details and notes on handling a request for 3 years after it is closed and then delete them. After an account is deleted, we keep a record of the deletion: when it took place and how it went. With it we keep the email address of the deleted account for 12 months from the deletion request, so that we can prove the deletion and protect the service against misuse (our legitimate interest). After 12 months the address is erased automatically and the deletion record no longer contains it. We provide the copy of your data (export) through a link; the link and the file are valid for at most 7 days, after which we delete the file. During a complaint, dispute or official proceeding, we retain only the records needed to resolve it until it ends. Reporting a message: legitimate interest in keeping the service safe. We store who reported the message and why, and a copy of its text and photo so that the Trely team can review it; if a video or document is attached to the message, we keep it while the report is being dealt with. We keep the copy while the report is being handled and afterwards for as long as the message itself exists. If the Trely team removes a message, we delete its photo, video or document within one day; the text of the message stays stored and is not shown. If the author of the message deletes their account, we also delete the copy from the report; only the record that a report was made and how it was handled remains. Reviews: legitimate interest in trustworthy information about trainers. A review (rating, text and your name) is public on the trainer's profile, on the web and in data for search engines. In a review without your name, “Anonymous client” is shown instead and the trainer does not see your name; only the Trely team sees it when checking the review. When you erase your data with a trainer, we delete the text of your review of that trainer and your name on it; the review is then shown everywhere with the label “Anonymous client”. Disconnecting alone does not change the review. When you delete your account, we delete the text and your name and the review is shown as “Anonymous client”. The rating remains part of the trainer's rating. If the trainer deletes their account, the reviews of them are deleted too. We delete the copy of a review's text in a report together with the text.

5. Health data and photos

Height, weight, BMI, measurements, injuries, rehabilitation, tests and progress photos may be special-category data under GDPR Article 9. The professional obtains and records the appropriate basis, usually explicit consent under Article 9(2)(a). As processor, Trely does not use this data for marketing, profiling or AI-model training. Progress photos and the materials you exchange in the app are not public; access to them is controlled by authentication and access rules. Blurring the face on a progress photo happens only on your device; the photo is not sent anywhere in the process. A trainer can switch on a group chat for one of their client groups; members of the group who have a Trely account are in it straight away and may leave it. In a group chat, your name, profile photo, messages and the photos, videos and documents in your messages are seen by the other members of the chat and by the group’s trainer. A new member sees messages from the moment they were added; the trainer sees the whole chat history. In a chat between a trainer and a client and in a group chat you can send a photo, a video with sound and a document. Photos, videos and documents in a chat are not public: only those who can see the message can see them, and the Trely team when it reviews a reported message. You can remove a photo, video or document you sent from the chat. The app uses the camera and microphone only when you choose to record a video. If you turn on adding sessions to your phone’s calendar, the app writes your confirmed sessions into it. We do not send the contents of your calendar to our servers; we store only the identifier of the event we added and of the calendar, so that we can update the event when the session changes. A video or document may contain health data or data about other people; send only what is necessary. A client’s profile photo is not public. It is seen by the client, their connected trainers and the members of their group chats. A former trainer no longer sees it. A trainer’s profile photo, however, is publicly accessible: it appears on the public profile and is loaded from a public address, so it can be opened without signing in. If a trainer hides their profile, it stops appearing in search and on the public profile, but the photo itself may remain reachable through a known address or from a browser or network cache. A trainer who wants the photo gone should replace or delete it in profile settings.

6. Recipients and transfers

Supabase (EEA, Frankfurt) – database, authentication and storage; RevenueCat – subscriptions; Apple and Google – distribution, purchases and push; Stripe – payment-account verification, storing cards for automatic payments, card payments, refunds and fraud prevention; Resend – email delivery; Expo – push infrastructure; Sentry – diagnostics; PostHog – product analytics; Vercel – web hosting and traffic measurement; Hetzner (Germany) – encrypted backup copies of files; Google (Firebase Analytics) and Meta – ad measurement, only with your consent. This current list forms the generally authorised subprocessors for client-data processing; trainers receive reasonable advance notice of a material change. Transfers outside the EEA use GDPR Chapter V safeguards, especially the EU–US Data Privacy Framework or Standard Contractual Clauses. Some of these providers also process data in the United States, in particular Stripe, RevenueCat, Resend, Expo, Apple, Google, Meta and Vercel, on the basis of these safeguards. If a trainer operates in a country outside the EEA, they receive the data you make available to them in Trely, and the payment data, in that country. The trainer is responsible for any further use of that data. In a group chat, the recipients of your messages, photos, videos and documents are the other members of the chat and the group’s trainer. Advisers and public authorities may receive data where legally required.

7. Security and incidents

Measures include TLS, encryption at rest, least-privilege access, database access policies, monitoring, backups and security updates. As controller we report qualifying breaches to the authority generally within 72 hours and notify people where risk is high. As processor we notify the professional without undue delay. Authorised members of the Trely team can see account data (name, contact details, account status, connections and payments) to the extent necessary for support, payment issues, security and handling requests. When a team member looks up a person in the admin interface or opens a record showing their name or contact details, we log who looked, when and at what; the data itself is not copied into the log. An authorised system administrator can see the messages of the private chat between a trainer and a client only after stating a reason (a report, a dispute, a user’s request or security); the reason and the access are logged. A message a user deletes in a private or group chat is no longer visible to the other participants either. We erase its content; if an open report relates to it, only after the report is resolved.

8. Your rights and account deletion

You may request access, correction, deletion, restriction and portability, object, withdraw consent and complain. Email privacy@trely.eu; we normally respond within one month. For trainer-entered data, contact the trainer first; Trely assists the trainer with the request. Cancelling a subscription does not delete an account. Delete in the app or email support@trely.eu. Practical steps and retention details are at https://trely.eu/en/delete-account. Trely does not make decisions under GDPR Article 22.

9. Cookies and similar technologies

The mobile app does not use browser cookies; it uses essential authentication tokens and device identifiers. The website uses no advertising cookies, third-party cookies or other non-essential storage; the language is determined by the URL. For traffic measurement we use Vercel Web Analytics: it is cookieless, stores nothing in your browser and builds no cross-site profiles. It processes the page visited, the referring source, country, device type, operating system and browser; unique visitors are counted using an identifier that changes daily, so it cannot follow you over time. On the pricing page and the trainer directory we determine your country from your IP address in order to show prices and trainers for your country; we do not store this information. When an invitation code is entered, we store a fingerprint of the IP address for a short time to prevent code guessing; the address cannot be recovered from it. On trely.eu/app and trely.eu/pair we also measure whether a visitor went on to an app store or into the app. Our server sends this to PostHog without cookies and without storing anything in your browser: the device type, the campaign and the domain the visit came from, and a random visit identifier that is gone when the page is closed. PostHog builds no person profile from it and does not determine location. Before enabling analytics that requires cookies or other non-essential storage, we will update this policy and obtain valid consent.

10. Changes, contact and authority

We provide appropriate notice of material changes. The current version is always available at trely.eu. Supervisory authority: Office for Personal Data Protection of the Slovak Republic, Hraničná 12, 820 07 Bratislava 27, statny.dozor@pdp.gov.sk, +421 2 3231 3214, https://dataprotection.gov.sk. You may also lodge a complaint with the supervisory authority of the EU or EEA country where you live or work. In the United Kingdom, this is the Information Commissioner’s Office. If you live in the United States, you can exercise your rights under the law of your state by writing to privacy@trely.eu. The Slovak version is binding.

Rexly s. r. o.17 November 2026
Privacy Policy · Trely