Privacy Policy — TrainOne
Version: 1.3 · Effective date: 2026-11-16
Version 1.3 applies from 2026-11-16. Until the day before that date, version 1.2 of 2026-11-08 applies.
Data Controller: NEXTLEVEL GROUP SP. Z O.O., ul.
Głogowska 35A lok. 6/2, 60-736 Poznań, Poland, NIP 7812086892, KRS 0001165259
Contact: kontakt@trainone.app
1. General Information
This Privacy Policy describes how NEXTLEVEL GROUP SP. Z O.O. (hereinafter: Service Provider or TrainOne) processes personal data in connection with operating the TrainOne platform at trainone.app and in TrainOne mobile applications.
Processing is carried out in accordance with GDPR (EU) 2016/679 and applicable Polish data protection law.
Roles of the Service Provider:
- Data Controller — with respect to Companies' (business clients') personal data: registration and billing data.
- Data Controller — with respect to User account data (email address, account ID, login sessions), which is a single account for all Companies a person has access to, as well as reports submitted from the app and data serving Platform security (section 2.4).
- Data Processor — with respect to Staff and Client data of Companies. The Company is the controller; TrainOne processes data under a Data Processing Agreement (DPA).
2. Personal Data of Companies — Registration and Platform Use
2.1 Scope of data
We process:
- Registration data: company name, registrant's name, email address
- Company contact data: address, phone, VAT EU number
- Billing data: payment history (card data held by Stripe)
- Login data: IP address, session timestamps
- Communication data: email correspondence with TrainOne
2.2 Purpose and legal basis
| Purpose | GDPR basis |
|---|---|
| Conclusion and performance of Agreement | Art. 6(1)(b) — contract performance |
| Invoicing and tax compliance | Art. 6(1)(c) — legal obligation |
| Technical support and customer service | Art. 6(1)(b) — contract performance |
| Platform change notifications | Art. 6(1)(b)/(c) |
| Platform security | Art. 6(1)(f) — legitimate interest |
TrainOne does not send Companies commercial or marketing messages. We send only system messages needed to provide the service: login codes, confirmations, notifications about payments and subscriptions, information about changes to the Platform and the legal documents, and replies to reports. Registration does not require marketing consent.
2.3 Retention periods
- Company account data: duration of Agreement; after the Company is deleted — 30 days of archiving (panel closed, deletion can be cancelled, and the Company's records can be downloaded as an archive), then permanent deletion of all the Company's data, including invoices, the audit log and the record of the deletion confirmation. Only a technical invoice-numbering counter remains (year, last sequence number and the Company's technical identifier), without its name, contact details or invoice content, and without data of its staff or clients — it ensures that an invoice number already accepted by KSeF is never reused
- Billing data and invoices: 5 years from end of the tax year, and if the Company is deleted — until its data is permanently deleted (copies of invoices in the Platform, including invoices issued to the Company by TrainOne and their corrections, are deleted together with the Company; invoices sent to KSeF remain in KSeF)
- Audit log (separate from system logs): entries are deleted automatically, every day; the entries from the current and the previous calendar month are kept, so each entry is stored for 1 to 2 months (and, once the Company is deleted, no longer than until its data is permanently deleted)
- System logs: 12 months
- Email correspondence: 3 years from last contact
2.4 User account data, reports and security
A TrainOne login account is a single account for the whole Platform: the same person may have access to more than one Company, while the data of individual Companies remain separated from each other. As controller we process:
- Account data (email address, account ID, login sessions, IP address) — to authenticate with one-time email codes and maintain one account shared across Companies; basis: Art. 6(1)(f) GDPR — legitimate interest.
- Reports submitted from the app (description of a bug or idea, the reporter's email address and ID, attached screenshots and logs) — to handle the report; they go to the issue tracker (YouTrack) and, for bug reports, to the support mailbox, and attached files are deleted after the message is sent; basis: Art. 6(1)(f) GDPR.
- Security data (event logs and technical logs) — to ensure Platform security; basis: Art. 6(1)(f) GDPR.
3. Personal Data of Staff and Clients — Processor Role
3.1 Scope of data processed
On behalf of Companies, TrainOne processes:
- Basic data: first name, last name, email, phone, date of birth, gender
- Health data (Art. 9 GDPR): training plans, workout history, nutrition plans, meal diaries, anthropometric indicators, body photos (front, side, back), reports, data from Apple Health and Health Connect (sleep, steps, calories burned, workouts), well-being and fatigue level, answers in onboarding and report forms, which may contain health information, and Staff notes about Clients together with attached files. We process it only with the Client's explicit consent (section 9); we record its date, text version and channel (app, sign-up form on the website, kiosk at the club, online booking) as proof that it was given
- Financial data: Stripe transaction IDs, purchase history, brand and last four digits of a saved payment card
- Behavioural data: booking history, check-in timestamps, login history
- Staff HR and payroll data: contracts and pay rates, payroll settlements, schedules and working-time records, absences (vacation, sick leave — data concerning the Staff member's health)
- Communication data: chat message content
- Invoicing data: buyer data (name, tax ID, address) on invoices issued by the Company and submitted to KSeF on its behalf
- Integration data: Google Calendar access tokens, iCal calendar addresses and CalDAV access credentials
3.2 TrainOne's role
TrainOne is a Processor — it processes data solely under the Data Processing Agreement with the Company. The Company is the Controller and is responsible for the legal basis of processing, information obligations, and health data consents.
3.3 Exercise of data subject rights
- Data export: in the web panel Profile → "Download my data (JSON)", in the app Settings → "Export my data"
- Account deletion: in the web panel Profile → "Delete account", in the app Settings → "Delete account" (within 30 days; in the app the deletion covers all Companies the account has access to)
- Data correction: Profile → edit
What remains after account deletion. The account's personal data is deleted or anonymised, but not the records the Company is obliged to retain (Art. 17(3)(b) and (e) GDPR): invoices, point-of-sale sales, the entries ledger, payroll settlements, contracts, schedules and working-time records, and Staff absences, as well as the audit log (accountability of events; in its entries the user name is replaced with the label "Deleted user"). This data stays in the Platform for as long as the Company exists, and the audit log for the period stated in section 2.3 (no longer than until the Company is deleted); when the Company is deleted the data disappears with it, and the Company can download an archive of its records beforehand (section 2.3). The login account is not erased but — once it is no longer linked to any Company — blocked and scrubbed: the email address is replaced with a random one, the name and phone number are removed, and sessions and linked notification devices are revoked. This keeps the account ID from being reused by another person.
4. Contact Form / Leads
The data controller for the public leads form is the Company whose form it is — TrainOne acts as processor. Leads in every status except “Acquired” are automatically archived (personal data removed) 12 months after the last change to the lead or the last staff comment. A lead with the status “Acquired” is not removed automatically: the Company deletes it on request of the data subject or as part of its day-to-day lead handling (a Company Administrator or Manager can delete a lead in the panel). A lead linked to a client account is deleted together with that client's data, and when the Company is deleted — together with the rest of the Company's data.
5. Cookies and Tracking Technologies
| Name | Type | Duration | Purpose |
|---|---|---|---|
trainone-session | Essential | Session / 1 year | Authentication — required for Platform to work |
active_company | Preference | 1 year | Remember active company (multi-company mode) |
CookieConsent | Essential | 1 year | Store consent choice (Cookiebot) |
_ga, _ga_* | Analytics | 2 years | Visit analytics, loaded through Google Tag Manager — only after consent is given |
rybbit_* | Analytics | 1 year | Visit analytics on our own Rybbit instance — only after consent is given |
_fbp | Marketing | 3 months | Advertising performance measurement (Meta Pixel) — only after consent is given |
Consent is managed by Cookiebot, loaded through Google Tag Manager. The consent script always runs, because without it no choice could be collected or remembered — but analytics and marketing tags stay blocked until the visitor gives consent. Without consent, analytics and the Meta Pixel store no data at all.
Consent can be changed or withdrawn at any time with the “Cookie settings” link in the footer of the trainone.app home page.
6. Sub-Processors and Data Recipients
TrainOne infrastructure is self-hosted on Hetzner servers in the
European Union. The database and authentication layer (Appwrite), mail (Mailcow, mail.nextlevel-group.pl), analytics (Rybbit, analytics.nextlevel-group.pl) and the issue tracker (YouTrack) all run as
self-hosted instances — no data is entrusted to the vendors of that software.
| Entity | Purpose | Location | Basis |
|---|---|---|---|
| Hetzner Online GmbH | Server infrastructure (hosting for all services) | EU (Finland, Germany) | DPA |
| Stripe, Inc. | Payment processing | USA | DPA, SCC |
| Apple Inc. | Push notifications (APNs) | USA | DPA, SCC |
| Google LLC | Push notifications (FCM), Google Tag Manager and analytics, embedded YouTube video and Google Calendar (section 6.1) | USA | DPA, SCC |
| Usercentrics A/S (Cookiebot) | Cookie consent management | EU (Denmark) | DPA |
| Meta Platforms Ireland Ltd. | Advertising performance measurement (Meta Pixel) | EU (Ireland) | DPA, SCC |
| KSeF (Polish National e-Invoicing System) | Submission of structured invoices (including invoices issued by Companies on their behalf) | Poland | Legal obligation |
Transfers to the USA are based on Standard Contractual Clauses (SCC) approved by the European Commission. Submitting invoices to KSeF is not a processing entrustment — it follows from a legal obligation (Art. 6(1)(c) GDPR in conjunction with the Polish VAT Act) and is not subject to consent.
6.1 Features that use external services
The features below connect the user's device or account to an external service. They work only when the user uses them.
- YouTube (Google): an exercise preview with video in the mobile app
and in the panel embeds a YouTube player in privacy-enhanced mode (
youtube-nocookie.com). Once such a preview is opened, the browser or app connects to YouTube, which sees the IP address and device data. TrainOne does not pass the Client's personal data to YouTube. - Google Calendar, iCal and CalDAV: a Staff member can connect their calendar so that booking slots avoid their busy hours. For Google Calendar TrainOne asks for read-only access to the calendar and for the “openid” and “email” permissions, which tell it the email address of the connected Google account; it stores that address (shown in the profile to identify the connected account) and access tokens; for iCal and CalDAV it downloads the calendar file from the given address (optionally with the calendar login and password). From events we store only the identifier, start and end — not their titles, descriptions or attendees. We write nothing to the user's calendar. The integration can be disconnected in the profile.
- Apple Health and Health Connect: with permission granted in the device system, the mobile app reads sleep, steps, calories burned and workouts from Apple Health (iOS) and Health Connect (Android), and writes completed workouts to Apple Health or Health Connect. The exchange takes place on the device — TrainOne does not pass this data to Apple or Google. What TrainOne receives is the data read, which is health data (sections 3.1 and 9).
- KSeF for Companies' invoices: invoices a Company issues in the Platform are submitted to KSeF on its behalf using its KSeF token. Besides invoices issued to the Company by TrainOne (section 2), this covers the buyer data on the Company's invoices (section 3.1).
7. Data Subject Rights
Every person whose data is processed by TrainOne as controller has the right to:
- Access (Art. 15 GDPR) — obtain information about data processed
- Rectification (Art. 16) — correct inaccurate data
- Erasure (Art. 17) — "right to be forgotten"
- Restriction of processing (Art. 18)
- Data portability (Art. 20) — JSON format
- Objection (Art. 21) — to processing based on legitimate interest
- Withdrawal of consent — without affecting prior lawful processing
Requests via Platform settings or email: kontakt@trainone.app. Response within 1 month.
Right to lodge a complaint with the supervisory authority: President of the Polish Personal Data Protection Office (UODO), ul. Stawki 2, 00-193 Warsaw, kancelaria@uodo.gov.pl.
8. Data Security
Technical measures: HTTPS/TLS 1.3 encryption, OTP authentication (no passwords stored), Company data isolation through Appwrite row- and team-level permissions, encryption of sensitive data, regular encrypted backups.
Organisational measures: production system access limited to authorised personnel, principle of least privilege, breach response procedure.
9. Health Data — Special Protection (Art. 9 GDPR)
The Platform processes Clients' health data (training and nutrition plans, workout history, meal diaries, body measurements, body photos, reports, Staff notes, data from Apple Health and Health Connect, well-being) — special category data.
Consent is mandatory. The Company as controller obtains the Client's explicit consent (Art. 9(2)(a) GDPR) at sign-up — in the app, in the sign-up form on the website, at the kiosk in the club or when booking online. A Client who created an account before consent became mandatory gives it on the consent screen the next time the app is opened. Consent is a condition of using the app at a given Company: without it the Client's account at that Company is not activated, and the Company's Staff cannot record the Client's health data, activate their plans or add notes about them.
Withdrawal of consent: The Client may withdraw it at any time — by deleting their account in the app settings (the "Delete account" option), by asking the Company's administrator to delete their membership, or by writing to kontakt@trainone.app. Because consent is a condition of using the app at a given Company, withdrawal causes the irreversible deletion of the Client's membership together with their health data; deleting the account in the app covers all of the Client's Companies, and the login account is then blocked and scrubbed (section 3.3). Documentation that the Company is required to keep (section 3.3) remains. Withdrawal of consent does not affect the lawfulness of processing carried out before its withdrawal (Art. 7(3) GDPR).
10. Changes to This Policy
Material changes will be notified by email at least 30 days in advance. The current version is always available at trainone.app/privacy-policy.
11. Contact
NEXTLEVEL GROUP SP. Z O.O.
ul. Głogowska 35A lok. 6/2, 60-736
Poznań, Poland
email: kontakt@trainone.app
Response to personal data queries: within 30 days.
Version 1.3 applies from 2026-11-16. Previous version: 1.2 of 2026-11-08.
This Privacy Policy was prepared in Polish. In case of any discrepancy with the translation, the Polish version prevails.
