Data Processing Agreement
1. Parties, roles and scope
This Data Processing Agreement ("DPA") is part of the Coach Terms between Arohanui Ltd, registered in Cyprus (registration number HE 420908, registered office 5 Kekropos St., Larnaca, Cyprus) ("we", "us", the "Processor") and the coach or gym that uses EZY Fitness ("you", the "Controller"). It applies to the personal data of your athletes and gym members that we process for you through the Service (the "Athlete Data"). It does not apply to personal data for which we are the controller (your own account and billing data, the early-access list, security logs, support requests), which the Privacy Policy covers.
The terms "personal data", "controller", "processor", "data subject", "personal data breach" and "supervisory authority" have the meaning they have in Regulation (EU) 2016/679 (GDPR). If this DPA and the Coach Terms conflict on data protection, this DPA prevails.
2. Details of the processing
| Subject matter | Providing the EZY Fitness service: storing and showing training programs, logging and showing results, feedback, personal records, gym groups and whiteboards, and the sign-in of your athletes. |
|---|---|
| Nature and purpose | Hosting, storage, retrieval and display of the data you and your athletes enter, on your instructions and only to provide the Service to you. For AI import: sending the file you choose to a third-party AI service to turn it into a draft program. |
| Duration | As long as your account is active, and until deletion as set out in section 8. |
| Data subjects | Your athletes and gym members, the coaches you add to a gym account, and people named in the files you import. |
| Categories of personal data | Name and email address, the group a member belongs to and the date they joined, programs and training content, results (loads, reps, times, rounds, completion), scores shown on a group whiteboard, personal-record history, notes and feedback between athlete and coach, and technical data needed to run the Service (timestamps, security tokens). |
| Special categories | We do not ask for health data and ask users not to enter it. If you or your athletes choose to enter health-related data (injuries, for example) in notes, we process it only to store and show it to you, as your processor, and you are responsible as set out in section 6. |
3. What we do as your processor
- Instructions. We process Athlete Data only on your documented instructions, which are: the Coach Terms, this DPA, and what you do in the Service (adding athletes, entering programs, deleting data). If we believe an instruction breaks the law, we tell you.
- Confidentiality. Everyone who can access Athlete Data for us is bound by a duty of confidentiality, and access is limited to what is needed to run, secure and support the Service.
- Security. We apply the measures in Annex 2 and keep them appropriate to the risk, as GDPR Article 32 requires.
- Sub-processors. You grant us general written authorisation to engage the sub-processors listed in Annex 1 (and kept up to date at this page) to support the delivery of the Service. We bind each sub-processor to written data protection obligations no less protective than those in this agreement, and we remain fully liable to you for their performance.
We will notify you by email or in-app notice at least 30 days before adding or replacing a sub-processor. You may object to a new sub-processor on reasonable data protection grounds within 14 days of receiving notice. If we cannot reasonably accommodate your objection, you may terminate your subscription and receive a pro-rata refund for any prepaid, unused period.
- Help with data subjects' rights. We give you the tools and, on request, the help you reasonably need to answer an athlete's request for access, correction, deletion, restriction, portability or objection. If an athlete contacts us about data you control, we refer them to you, unless the law requires otherwise.
- Breaches. We tell you without undue delay, and in any case within 48 hours, after we become aware of a personal data breach affecting Athlete Data, with what we know about its nature, the data and people affected, likely consequences and our response, and we keep you updated. You decide whether to notify the authority and the athletes, and we help.
- Assistance. We help you with data protection impact assessments and prior consultations to the extent they relate to our processing.
- Records and audits. We keep a record of our processing for you and give you the information needed to show we meet this DPA. You, or an auditor bound by confidentiality, may audit our compliance once a year, or after a breach, on 30 days' notice, during working hours and without harming other customers; we may meet the request by sharing recent test reports and documentation first.
4. Transfers outside the EU/EEA
The database and its backups are stored in the EU. Some sub-processors, including the AI import service, may process data in the United States or elsewhere. We rely on the EU-US Data Privacy Framework where the recipient is certified and otherwise on Standard Contractual Clauses, and we tell you of any change in section 3.4.
5. AI import
When you use Import, the content of the file you choose is sent to a third-party AI service to produce a draft program that you review. We use a paid service under which the provider does not use the content to train its models. Do not import files containing data you do not want processed this way.
6. What you are responsible for
- You are the controller of the Athlete Data. You decide which athletes you add and what you ask them to record, and you need a valid lawful basis and the required privacy notices before adding them.
- If you record health-related or biometric data, you must obtain the athlete's explicit consent as the law requires.
- You must not add athletes under 16 (or under the age of digital consent where you are) without verifiable consent from a parent or guardian.
- You keep the people you add as coaches to a gym account, and what they do, under your control.
7. Group whiteboards and visibility
Members of a gym group see each other's names and scores on that group's programs, as described to them when they join. You can hide a member from the whiteboard at any time. You are responsible for telling your members.
8. Deletion and return
You can delete athletes and programs yourself at any time. When your account ends, or on your written request, we delete or anonymise the Athlete Data within 30 days, unless the law requires us to keep it. Backups containing it expire on their own schedule (up to 30 days). If you ask before the account closes, we send you an export of your data in a common machine-readable format (such as JSON or CSV) within 30 days of a written request to ezyfitnessforlife@gmail.com.
9. Liability, term and law
Liability under this DPA is subject to the limits in the Coach Terms, except where the law does not allow it. This DPA lasts as long as we process Athlete Data for you. It is governed by the law that governs the Coach Terms (Cyprus).
10. Changes and contact
We may update this DPA to follow the law or changes to the Service, with at least 30 days' notice for a material change. Questions or a data protection request: ezyfitnessforlife@gmail.com.
Annex 1. Sub-processors (categories)
| Category | Purpose | Location |
|---|---|---|
| Cloud infrastructure and hosting provider | Sign-in, database, hosting, serverless functions, abuse protection, secret storage and backups | Database and backups in the EU; some services may process data in the United States |
| AI service provider | AI-assisted program import | United States or elsewhere outside the EU/EEA |
| Content delivery provider | Delivers the open-source libraries that read PDF and spreadsheet files in the browser; receives the visitor's IP address | Global |
The names of the sub-processors in each category are given on request at ezyfitnessforlife@gmail.com. A payment provider handles payment data for our billing of you as an independent controller; it does not receive Athlete Data and is described in the Privacy Policy, not here.
Annex 2. Security measures
- Encryption in transit for every connection to the Service; data encrypted at rest by the hosting provider.
- Separation between customers. Access rules enforced in the database, not only in the app: each coach or gym reaches only their own athletes and data; each athlete reaches only their own data and what their group is meant to see. The rules are tested automatically, including attacks that try to cross between customers.
- Sign-in by emailed link, no passwords stored; abuse protection (App Check) on the database and functions.
- Application hardening. A strict content security policy, no third-party advertising or analytics trackers, and input checks on what can be stored.
- Secrets (payment keys and similar) kept in a secret manager, never in the code; automatic secret scanning of the code before each change is saved.
- Access control for our team. Production access limited to the people who need it, with two-step verification on the owner accounts for the cloud, code and email.
- Backups. A daily backup kept 30 days and point-in-time recovery for 7 days, stored in the EU; a restore has been rehearsed.
- Testing and monitoring. Automated tests on every change, a dependency audit, a security review with a penetration-test pass of the rules and the app (October 2026), and a written procedure for a compromised account.
- Incident response. A documented procedure for investigating and containing an incident and for telling affected customers (section 3.6).
- Deletion. Data is removed on request or when an account ends, as in section 8.
See also the Coach Terms and the Privacy Policy.