PART B — DATA PROCESSING AGREEMENT (version dpa-1.0)
This Data Processing Agreement ("DPA") forms part of the Licence Terms between the Customer (controller) and Endurance Lab (processor) and meets Article 28 of the EU General Data Protection Regulation (GDPR).
1. Roles
1.1 The Customer is the controller of personal data in Customer Data. Endurance Lab is the processor.
1.2 Endurance Lab is a controller only for its own account, billing and support data about the Customer and its users.
2. Instructions
2.1 We process Customer personal data only on the Customer's documented instructions. The Licence Terms, this DPA and the Customer's use and configuration of the Service are those instructions.
2.2 We will tell the Customer if we believe an instruction breaks data protection law.
2.3 We do not sell Customer personal data and do not use it for our own purposes. Any future benchmarking feature will use only anonymised data and only where the Customer opts in under separate terms.
3. Confidentiality
Everyone we allow to access Customer personal data is bound by confidentiality. We access a Customer's account for support only when the Customer asks or allows it, or when needed to keep the Service secure.
4. Security
We apply the technical and organisational measures in Annex 2 and keep them appropriate to the risk, taking into account that Customer Data may include health data.
5. Sub-processors
5.1 The Customer gives general authorisation for the sub-processors in Annex 3.
5.2 We will give at least 30 days' notice before adding or replacing a sub-processor, by email or in the Service. The Customer may object on reasonable data-protection grounds; if we cannot resolve the objection, the Customer may cancel without penalty and receive a refund of any prepaid fees for the remaining period.
5.3 We put data protection terms in place with each sub-processor that are no less protective than this DPA, and remain responsible for them.
6. International transfers
We aim to keep Customer Data in the European Economic Area. Where a sub-processor processes personal data outside the EEA, the transfer is covered by an adequacy decision or the EU Standard Contractual Clauses.
7. Helping the Customer
Taking into account the nature of the processing, we will help the Customer to:
(a) respond to data subject requests (access, correction, deletion, portability, objection), mainly through the Service's own tools; we will pass on any request we receive directly;
(b) carry out data protection impact assessments and consult the Data Protection Commission where needed;
(c) meet its security and breach notification obligations.
8. Personal data breaches
We will notify the Customer without undue delay, and in any case within 48 hours of becoming aware of a personal data breach affecting Customer Data. We will give the information the Customer reasonably needs to notify the Data Protection Commission and affected people, and take reasonable steps to contain it.
9. Deletion and return
When the Customer's account ends, the Customer may export its data for 30 days. We then delete Customer personal data within 90 days, including from backups as they roll over, unless EU or Irish law requires us to keep it.
10. Records and audits
We will make available the information reasonably needed to show compliance with this DPA. The Customer may audit once a year (or after a breach), with 30 days' notice, at its own cost, during business hours and subject to confidentiality. We may answer by providing written information or third-party certifications of our sub-processors where that is sufficient.
11. The Customer's responsibilities
The Customer is responsible for: having a lawful basis for processing, including a condition under Article 9 GDPR for health data (usually explicit consent); giving clients a privacy notice; obtaining parental consent where clients are under 16 and consent is relied on; only collecting the data it needs; and setting staff access appropriately in the Service.
12. Liability and order of precedence
Liability under this DPA is subject to the limits in the Licence Terms, except where the law does not allow it. If this DPA conflicts with the Licence Terms on data protection, this DPA wins.
Annex 1 — Details of processing
- Subject matter and duration: providing the Service for the life of the Customer's subscription plus the deletion period in section 9.
- Nature and purpose: hosting, storing, organising, displaying, analysing and transmitting data so the Customer can manage clients, bookings, tests, reports, coaching, events and payments.
- Data subjects: the Customer's clients and athletes (including prospects and, where applicable, minors with parental consent), the Customer's staff and users.
- Personal data: identity and contact details; account and log-in data; booking, attendance and subscription records; payment status and references (card details are handled by Stripe, not stored by us); training data, testing data and reports.
- Special category data: health data, including physiological test results (for example lactate, VO2, heart rate, power, body composition and anthropometry), health screening answers, injury information and therapy notes.
- Frequency: continuous while the Service is used.
Annex 2 — Security measures
- Each business's data is separated by database row-level security, so one business cannot see another's data.
- Role-based access inside each business; health and therapy records restricted to staff given clinical access.
- Data encrypted in transit (HTTPS/TLS) and at rest by our hosting provider.
- Payment card data handled only by Stripe (PCI-DSS certified); we never store card numbers.
- Payment notifications verified with signed webhooks.
- Automated backups by the hosting provider.
- Access by Endurance Lab limited to what is needed for support and security, with audit logging of key actions.
- Secrets and keys stored in the hosting provider's secret store, not in code.
- Changes tested before release; undo records kept for database changes.
- Strong passwords required; users encouraged to use unique passwords. Multi-factor authentication will be added.
Annex 3 — Sub-processors
| Sub-processor | Purpose | Location |
|---|---|---|
| Lovable (Lovable Labs Incorporated) | Application hosting, database, file storage and authentication (built on Supabase) | London, United Kingdom (AWS eu-west-2) |
| Supabase Inc. (via Lovable) | Database and authentication infrastructure | Same region as above |
| Stripe Payments Europe Ltd | Subscription billing and the Customer's connected payment account | Ireland (with transfers under Stripe's DPA/SCCs) |
| Lovable (Lovable Labs Incorporated) — managed email sending | Sending account, booking and receipt emails | [Confirm with Lovable — location not published] |