Data Processing Agreement
Version: 1.2 · Effective date: 2026-11-08
Version 1.2 applies from 2026-11-08. Until the day before that date, version 1.1 of 2026-10-29 applies.
Concluded pursuant to Art. 28 of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 (GDPR)
This Data Processing Agreement (hereinafter: "Agreement" or "DPA") forms an integral part of the TrainOne Platform Terms of Service and is entered into between:
- Controller — the Company registering on the TrainOne Platform (hereinafter: "Controller")
- Processor — NEXTLEVEL GROUP SP. Z O.O., ul. Głogowska 35A lok. 6/2, 60-736 Poznań, Poland, NIP 7812086892, KRS 0001165259 (hereinafter: "Processor" or "TrainOne")
This Agreement is accepted by checking the relevant checkbox during registration on the TrainOne Platform, which constitutes a declaration of intent to enter into this Agreement.
§ 1 Subject Matter and Purpose
- This Agreement sets out the terms under which the Processor will process personal data on behalf of the Controller in connection with providing the TrainOne Platform services (SaaS), pursuant to Art. 28 GDPR.
- The purpose of processing is the provision by the Processor of TrainOne Platform services to the Controller, including storing, managing, and making available the personal data of the Controller's Staff and Clients.
- This Agreement enters into force upon its acceptance during registration and remains in force for the entire period of the Controller's use of the TrainOne Platform.
§ 2 Scope, Nature, and Purpose of Processing
- Scope: The Processor processes only personal data that the Controller enters into the TrainOne Platform or which is generated by it during the use of services.
- Types of personal data:
- Identification data: first name, last name
- Contact data: email address, phone number
- Demographic data: date of birth, gender
- Health data (Art. 9 GDPR): training plans, workout history (exercises, sets, reps, weights, RPE), nutrition plans, meal diaries, anthropometric indicators (weight, body measurements), body photos (front, side, back), data from Apple Health and Health Connect (sleep, steps, calories burned, workouts), well-being and fatigue level, and answers in onboarding and report forms, which may contain health information
- Financial data: package purchase history, Stripe transaction and customer IDs, brand and last four digits of a saved payment card
- Behavioural data: session booking history, check-in timestamps, login history
- Staff HR and payroll data: contracts and pay rates, payroll settlements, schedules and working-time records, and absences (vacation, sick leave — data concerning the Staff member's health)
- Communication data: the content of chat messages between Clients and the Controller's team, and Staff notes about Clients together with attached files
- Invoicing data: buyer data (name, tax ID, address) on invoices issued by the Controller, submitted to the National e-Invoice System (KSeF) on the Controller's behalf using its KSeF token
- Integration data: Google Calendar access tokens, iCal calendar addresses and CalDAV access credentials
- Categories of data subjects: The Controller's Staff (trainers, instructors, dietitians, reception staff), Clients (trainees, class participants) and persons interested in the Controller's services (leads).
- Nature of processing: storage, reading, modification, deletion, and backup of personal data in the TrainOne Platform information system.
- Purpose: management of training sessions and bookings, creation and sharing of training and nutrition plans, billing and payment processing, staff settlements (schedules, contracts, payroll), issuing invoices and submitting them to KSeF on the Controller's behalf, calendar and Apple Health / Health Connect integrations, client communication (including chat), and other Platform functions defined in the Terms of Service.
§ 3 Processor Obligations
The Processor undertakes to:
- Process only on the Controller's instructions. The Processor processes personal data solely on documented instructions from the Controller, constituted by the configuration and use of the TrainOne Platform. The Processor immediately informs the Controller if, in its opinion, an instruction infringes GDPR or other data protection law. Exception: processing required by EU or Polish law — the Processor informs the Controller before processing, unless prohibited by law.
- Maintain confidentiality. The Processor ensures that persons authorised to process personal data have committed to confidentiality or are subject to an appropriate statutory obligation of secrecy.
- Implement appropriate security measures. The Processor implements and maintains appropriate technical and organisational measures to protect personal data (detailed in § 5 of this Agreement), ensuring a level of security appropriate to the risk.
- Engage sub-processors. The Processor shall not engage another sub-processor without prior authorisation from the Controller given in documentary form. General authorisation for sub-processors listed in Annex 1 is given by the Controller's acceptance of this DPA. The Processor informs the Controller of any planned changes to the sub-processor list at least 30 days in advance, allowing the Controller to object. If the Controller objects and parties cannot agree, the Controller may terminate the Agreement.
- Assist the Controller with data subject rights. Taking into account the nature of processing, the Processor assists the Controller through appropriate technical and organisational measures in fulfilling the obligation to respond to requests from data subjects exercising their rights: access, rectification, erasure, restriction, portability, and objection.
- Assist the Controller with obligations under Art. 32–36 GDPR. The Processor assists the Controller in ensuring compliance with obligations under Art. 32–36 GDPR (security, breach notification, data protection impact assessments, prior consultation), taking into account the nature of processing and information available to the Processor.
- Delete or return data upon termination. Upon cessation of services, the Processor — at the Controller's choice — deletes or returns all personal data and deletes existing copies, unless EU or Polish law requires storage. In practice, data is deleted after the Company is deleted in the Platform and is preceded by a 30-day archiving period, during which the Controller may cancel the deletion and download the Company's records archive (invoices, sales, settlements, contracts and working-time records). Ending a paid subscription does not delete data — the Company moves to the free Starter plan.
- Provide information and enable audits. The Processor makes available to the Controller all information necessary to demonstrate compliance with obligations under this article and allows and contributes to audits, including inspections, conducted by the Controller or an auditor mandated by the Controller. Audits are conducted on written notice of at least 30 days, during business hours, no more than once per year, at the Controller's cost.
- Report breaches. Upon discovering a personal data breach, the Processor notifies the Controller without undue delay, no later than 48 hours, with information required by Art. 33(3) GDPR to the extent available to the Processor at the time of notification.
§ 4 Controller Obligations
- The Controller confirms it has an appropriate legal basis for processing the personal data being entrusted, in particular for processing health data under Art. 9(2) GDPR.
- The Controller fulfils information obligations towards data subjects under Art. 13 and 14 GDPR.
- The Controller is responsible for the accuracy, currency, and completeness of personal data entered into the Platform.
- The Controller issues documented instructions to the Processor regarding the purposes and means of processing personal data through the configuration and use of the TrainOne Platform.
- The Controller ensures that Staff and Clients invited to the Platform have been informed of the scope of processing of their personal data by the Controller and the Processor.
§ 5 Technical and Organisational Security Measures
The Processor has implemented the following data protection measures:
- Encryption in transit: HTTPS/TLS 1.3 protocol for all Platform connections.
- Encryption of sensitive data at rest: sensitive data (e.g. CalDAV passwords) encrypted server-side.
- Authentication: Platform access via one-time OTP codes (Magic Link) — the Platform does not store user passwords.
- Access control: role-based access control system (RBAC); production data access limited to authorised TrainOne personnel.
- Multi-tenant data isolation: each Company's data is logically separated via Row Level Security in the database.
- Backups: regular automated encrypted backups stored in a secure location.
- Infrastructure: servers hosted by Hetzner Online GmbH in an EU data centre (Finland, Germany), ISO 27001 certified.
- Principle of least privilege: each employee and system has access only to data necessary for their assigned tasks.
- Breach response procedure: the Processor has a documented procedure for detecting, analysing, and reporting personal data breaches.
§ 6 Sub-Processors (Annex 1)
The Controller grants general authorisation for the Processor to use the following sub-processors:
| Entity | Role | Purpose | Location | Transfer basis |
|---|---|---|---|---|
| Hetzner Online GmbH | Hosting provider (servers) | VPS and dedicated servers running the TrainOne platform (database, storage, web application) | EU (Finland, Germany) | DPA (EU-based entity) |
| Stripe, Inc. | Payment processor | Processing subscription and client package payments | USA | DPA, SCC (Art. 46(2)(c) GDPR) |
| Apple Inc. | Mobile infrastructure | Push notifications (APNs) to iOS apps | USA | DPA, SCC |
| Google LLC | Mobile infrastructure | Push notifications (FCM) to Android apps | USA | DPA, SCC |
The Processor has entered into data processing agreements with each sub-processor imposing data protection obligations no less stringent than those set out in this Agreement. The Processor remains fully liable to the Controller for the sub-processor's compliance with its data protection obligations.
Transfers to the USA are made on the basis of Standard Contractual Clauses (SCC) adopted by European Commission Decision 2021/914.
§ 7 Personal Data Breaches
- Upon discovering a personal data breach that may pose a risk to the rights or freedoms of natural persons, the Processor notifies the Controller without undue delay — no later than 48 hours from discovery.
- The breach notification includes at least: description of the breach, categories and approximate number of affected persons and records, contact details of the point of contact, likely consequences, and measures taken or proposed.
- The Controller (as the entity obliged under Art. 33 GDPR) assesses whether the breach must be notified to the President of the Polish Personal Data Protection Office (UODO) within 72 hours, and whether data subjects must be notified (Art. 34 GDPR).
- The Processor immediately takes measures to minimise the consequences of the breach and prevent similar breaches in the future.
§ 8 Health Data — Special Conditions
- The TrainOne Platform enables processing of Clients' health data (Art. 9 GDPR), including training plans, workout history, nutrition plans, anthropometric indicators, body photos, and data from Apple Health and Health Connect.
- The Controller confirms it has obtained explicit consent from the Client (Art. 9(2)(a) GDPR) or another appropriate basis under Art. 9(2) GDPR before activating modules that enable health data processing.
- The Processor provides a consent collection mechanism in the Platform during client onboarding. The Controller is responsible for its proper configuration and use.
- The Processor does not process health data for its own purposes and does not share it with third parties beyond the scope of this Agreement.
§ 9 Term and Final Provisions
- This Agreement is effective for the period of the Controller's use of the TrainOne Platform and expires upon termination of the Terms of Service agreement.
- Upon expiry, the Processor deletes all personal data entrusted by the Controller, including backups, unless EU or Polish law requires retention. Deletion takes place after the Company is deleted in the Platform, following the 30-day archiving period described in § 3(7).
- Matters not regulated by this Agreement are governed by the TrainOne Terms of Service and GDPR and Polish data protection law.
- This Agreement is governed by Polish law. All disputes shall be resolved by the court competent for the Processor's registered seat.
- This Agreement supersedes all prior arrangements between the parties regarding the processing of personal data in connection with TrainOne services.
- This Agreement is concluded in electronic form (Art. 28(9) GDPR) — by acceptance in the Platform during registration. Amendments are made in documentary form: the Processor notifies the Controller of a planned change by email at least 30 days in advance and publishes the new version at trainone.app/data-processing-agreement. Continued use of the Platform after that period constitutes acceptance of the changes; if the Controller objects, it may terminate the Agreement under the Terms of Service.
This Data Processing Agreement was prepared in Polish. In case of any discrepancy with the translation, the Polish version prevails.
