LegalData processing agreement
The Article 28 GDPR agreement between each gym and miaforo about its members’ data.
Last updated: 18 November 2026
Clauses
1. Subject matter and scope
1.1. This agreement is the contract Article 28(3) GDPR requires for the personal data the Processor processes on behalf of the Controller to provide the miaforo service (the Service).
1.2. Annex II describes the subject matter, duration, nature and purpose of the processing, the types of personal data and the categories of data subjects. Annex III sets out the technical and organisational measures. Annex IV lists the authorised Sub-processors. The annexes are part of this agreement.
1.3. This agreement does not cover the data the Processor processes as controller about the Controller as a customer, such as its account, its invoices and the collection of its subscription to the Service. The terms of the Service and the Processor's privacy policy govern that data.
2. Definitions and applicable law
2.1. The GDPR is Regulation (EU) 2016/679. Terms defined in the GDPR have the same meaning in this agreement. The Controller and the Processor are the parties identified in Annex I. A Sub-processor is a processor that the Processor engages to process the personal data. Management means the people with the owner profile in the Controller's account.
2.2. Data Protection Law means the GDPR and the national data protection law that applies to the Controller (in Spain, Organic Law 3/2018, LOPDGDD). No clause of this agreement may be read to contradict the rights and obligations of Data Protection Law.
3. The Controller's instructions
3.1. The Processor must process the personal data only on the Controller's documented instructions, including on international transfers, unless Union or Member State law requires the processing. In that case the Processor must inform the Controller of that legal requirement before processing, unless that law forbids this on important grounds of public interest.
3.2. The Controller's documented instructions are this agreement, the terms of the Service, and the way the Controller and its staff use the Service's functions and settings, including switching on optional functions.
3.3. The Controller must give any other instruction in writing to chema@miaforo.com or to the Processor's contact address in Annex I. If an instruction needs work the Service's functions do not offer, the Processor may charge its reasonable cost, told to the Controller in advance. If such an instruction is not technically feasible, the Processor may refuse it and must explain why.
3.4. The Processor must inform the Controller immediately if it considers that an instruction infringes Data Protection Law. The Processor may suspend that instruction until the Controller confirms or changes it.
3.5. The Processor must not process the personal data for its own purposes, disclose it or sell it. If the Processor determined the purposes and means of any processing, it would be a controller of that processing under Article 28(10) GDPR.
4. Obligations of the Controller
4.1. The Controller warrants that it has a legal basis for the processing and for entrusting it to the Processor. It also warrants that it informs data subjects as Articles 13 and 14 GDPR require, including anyone who asks for a trial class from its public page.
4.2. The Controller must not enter into the Service special categories of data (Article 9 GDPR), data on criminal convictions and offences, or bank or card details, free text fields included. Annex II («Data the Service does not process») names the fields where that risk is highest.
4.3. The Controller is responsible for the content it and its staff enter or publish through the Service, including its messages to members and the photographs on its public page. The Controller must obtain the consents that content needs.
4.4. The Controller must supervise how its staff use the Service. The Controller must keep its account's access credentials safe.
5. Confidentiality
5.1. The Processor ensures that everyone it authorises to process the personal data is bound to confidentiality, by their own commitment or by law, also after their relationship with the Processor ends.
5.2. The Processor must give access to the personal data only to the people who need it to provide, maintain and support the Service.
6. Security of processing
6.1. The Processor must apply the measures in Annex III to ensure a level of security appropriate to the risk, as Article 32 GDPR requires. The Processor must keep each Controller's data separate from the data of its other customers.
6.2. The Processor must review those measures periodically and whenever the Service changes significantly. The Processor may replace or update them if the overall level of security does not decrease.
7. Communications to data subjects
7.1. On the Controller's behalf, the Processor emails data subjects only the notices in Annex II («Communications to data subjects»), which are needed to provide the Service.
7.2. The Processor must not send data subjects any commercial communication of its own. The Processor must not use their addresses for any purpose of its own.
8. Sub-processors
8.1. The Controller gives the Processor general written authorisation to engage Sub-processors. Annex IV lists the Sub-processors authorised on the date of this agreement.
8.2. The Processor must notify the Controller by email at least 30 days before adding or replacing a Sub-processor. Within that period the Controller may object on reasonable data protection grounds. The parties must then seek a solution in good faith. If they find none, the Controller's only remedy is to terminate the contract for the affected Service before the change takes effect, without penalty and with a refund of any amounts paid in advance for the unused period.
8.3. The Processor must impose on each Sub-processor, by contract, the same data protection obligations this agreement imposes on the Processor, in particular sufficient guarantees to implement appropriate technical and organisational measures. On the Controller's request, the Processor must provide a copy of that contract's data protection clauses. The Processor may leave out confidential commercial information.
8.4. The Processor remains fully liable to the Controller for each Sub-processor's performance of its obligations, as Article 28(4) GDPR provides.
9. Providers the Controller engages directly
9.1. When the Controller switches on online collection of its members' fees and personal training, members pay through direct charges on a Stripe account that the Controller opens under its own contract with Stripe. In that role Stripe is the Controller's provider, not a Sub-processor, and receives data on the Controller's instruction.
9.2. In that role the Processor, on the Controller's instruction, only creates the payment session and the account onboarding link through the Stripe API, and receives the signed notices Stripe sends about those payments. Annex II («Online collection of fees with Stripe») lists the data sent to Stripe and the data that comes back.
9.3. The Controller's own agreement with Stripe governs their relationship, including where Stripe processes the data and with which safeguards. The Processor is not liable for the processing Stripe carries out under that agreement.
9.4. The function ships switched off. It sends nothing to Stripe until the Controller switches it on and completes the onboarding Stripe requires.
10. International transfers
10.1. The Processor and its Sub-processors process the personal data within the European Economic Area (EEA), unless Annex IV expressly says otherwise.
10.2. The Processor may transfer personal data outside the EEA only on the Controller's documented instructions and with one of the safeguards in Chapter V GDPR. A new transfer through a Sub-processor follows the notice and objection procedure of clause 8.2.
10.3. The Controller's relationship with its own providers governs the data it orders sent to them under clause 9.
11. Assistance to the Controller
11.1. Taking into account the nature of the processing, the Processor must assist the Controller, through appropriate technical and organisational measures, in answering requests from data subjects who exercise their rights. The Processor gives this assistance mainly through the Service's self-service functions (access, rectification, export and erasure of data), at no extra cost.
11.2. If a data subject contacts the Processor directly, the Processor must not answer on its own account unless the Controller instructs it to. The Processor must pass the request to the Controller without undue delay.
11.3. Taking into account the information available to it, the Processor must assist the Controller in complying with Articles 32 to 36 GDPR, in particular by providing the information in this agreement for impact assessments and prior consultations.
11.4. The Processor may invoice assistance beyond the Service's functions and the information in this agreement at its reasonable cost, told in advance, unless the request arises from a breach by the Processor.
12. Personal data breaches
12.1. The Processor must notify the Controller of any personal data breach affecting the personal data processed under this agreement without undue delay after becoming aware of it and, where possible, within 48 hours, in writing to the Controller's contact address in Annex I.
12.2. The notification must include the information in Article 33(3) GDPR that the Processor has. The Processor must provide the rest in phases, as it obtains it.
12.3. The Processor must take reasonable measures to contain the breach and mitigate its possible effects. The Processor must assist the Controller in notifying the competent supervisory authority and, where appropriate, the data subjects. Those notifications are the Controller's responsibility.
12.4. Notifying a breach is not an admission of fault or liability by the Processor.
13. Information and audits
13.1. The Processor must make available to the Controller the information needed to demonstrate compliance with Article 28 GDPR and this agreement. The Processor must keep the record of processing activities Article 30(2) GDPR requires.
13.2. The Controller must first exercise its audit right through the Processor's documentation and the Processor's answers to a reasonable questionnaire. If that does not demonstrate compliance, the Controller may carry out an audit or inspection, itself or through an independent auditor, on these conditions:
- at most once a year, unless a supervisory authority requires it or it follows a personal data breach affecting the personal data processed under this agreement;
- with at least 30 days' written notice and a scope agreed in advance;
- during business hours and without unjustified disruption to the Processor's activity;
- under a confidentiality undertaking from the Controller and the auditor, who may not be a competitor of the Processor;
- without access to other customers' data or to information that could compromise the security of the Service.
13.3. The Controller bears the costs of the audit, including the reasonable time the Processor spends on it. If the audit reveals a material breach of this agreement by the Processor, each party bears its own costs. The Processor must then remedy the breach at no cost to the Controller.
14. Duration, return and deletion
14.1. This agreement takes effect on the date it is signed or accepted and lasts as long as the Processor provides the Service to the Controller. Clause 5 and this clause survive its end.
14.2. Return. When the Service ends, the Controller chooses whether the Processor returns the personal data before deleting it, or deletes it without returning it. While the Service lasts and for 30 days after it ends, the Controller may download its data itself from the panel, in a structured, machine-readable format (Annex II, «Download of the Controller's data»). That file holds the database rows, not the image files of the account: its logo, the photos of the gym and the coaches' photos. On the Controller's written request before the account closes, the Processor hands those files over too. The Processor must not close the account before that period ends. If the account is suspended, the Processor must make the download available on the Controller's written request.
14.3. Deletion. When that period ends, the Processor closes the account and the data is no longer accessible through the Service. 30 days after closure (31 at worst), an automatic process deletes the personal data: every row of the account that relates to a person, member or staff, active or not, as Annex II («Duration and retention periods») details. Those 30 days allow a mistaken closure to be reversed. The Controller accepts this period as its choice of deletion. Before the end, the Controller may erase each member itself with the Service's erasure function. If the Controller asks in writing for deletion before the return period ends, the Processor must close the account without waiting for the period to end. Deletion then follows 30 days after closure. In either case, the Processor must confirm the deletion in writing if the Controller asks.
14.4. Backups are not modified: they expire within the period in Annex II. The rows that Annex II keeps after a member's anonymisation stay subject to this agreement until they are deleted with the account. Deletion does not cover data that Union or Member State law requires the Processor to keep. This agreement protects that data for as long as the Processor keeps it.
15. Liability
15.1. Each party is liable for the damage it causes by breaching this agreement or Data Protection Law.
15.2. Towards data subjects, Article 82 GDPR applies and this agreement does not limit it. A party that has compensated a data subject may claim back from the other party that party's share of the liability, under Article 82(5) GDPR and within the limit in clause 15.3.
15.3. Between the parties, each party's total liability under this agreement may not exceed the amount the Controller paid the Processor for the Service in the 12 months before the event giving rise to it, or 500 euros if that is higher.
15.4. The limit in clause 15.3 does not apply to damage caused intentionally or by gross negligence, or to administrative fines imposed on a party for its own infringement, which that party bears in any case.
16. Order of precedence and changes
16.1. On data protection matters, this agreement prevails over the terms of the Service and over any other agreement between the parties.
16.2. The Processor may update Annexes II and III to reflect changes in the Service. The Processor must notify the Controller of each update by email. No update may reduce the overall level of protection or extend the processing to any purpose other than providing the Service. Changes to Annex IV follow clause 8.
16.3. A change that is not material under clause 16.4 takes effect on notification. Non-material changes include, among others, wording corrections, clarifications, measures that keep or raise the level of protection, and new optional functions whose processing is described in the Annex II notified before the Controller can switch them on, since they process no data until the Controller switches them on under clause 3.2.
16.4. Apart from those optional functions, a change is material if it adds a category of personal data or of data subjects, a new purpose or a longer retention period. The Processor must notify a material change at least 30 days before it takes effect. Within that period the Controller may object with the procedure and remedy of clause 8.2.
16.5. Any other change needs the agreement of both parties, in writing or by electronic means.
16.6. This agreement is written in English and translated into Spanish and German. If the versions differ, the English version prevails.
17. Electronic conclusion
The parties may sign or accept this agreement electronically, as Article 28(9) GDPR allows. Electronic acceptance by a person with authority to bind the Controller has the same effect as a signature.
A Controller that opens its own account in the Service accepts this agreement, together with the terms of the Service, by ticking the box that names them when it opens the account. The Service records the date, the person who accepts and the version accepted.
18. Governing law and jurisdiction
The law of the Member State where the Processor is established, stated in Annex I, governs this agreement, and the parties submit to the courts of that State. This does not affect the GDPR, the data protection law that applies to the Controller, the powers of the supervisory authorities, the right of data subjects to go to the courts the GDPR gives them, or any mandatory rules that apply.
Annex I. Parties
Controller
The gym that signs this agreement or accepts it when opening its account in the Service (clause 17). If it accepts when opening its account, its details are those of the account, the person accepting is whoever opens it on its behalf, and the date of acceptance is the one the Service records.
Processor
- Contact email: chema@miaforo.com
Annex II. Description of the processing
Categories of data subjects
- The Controller's members.
- The Controller's staff: Management and coaches.
- Anyone who asks for a trial class from the Controller's public page without being a member, when the Controller has those requests switched on.
- A visitor who pays a fee from the Controller's public page, until the payment settles, when the Controller has that switched on.
The last two are the only people the Service keeps data about without them having an account.
Categories of personal data
| Category | Specific data |
|---|---|
| Identification | Name. The name they go by in class, if the Controller records one. Email. Phone, if the member gives it. Date of birth, if Management records it. The age is calculated from the date of birth and not stored |
| Staff note | One sentence of free text that Management or a coach writes about a member, to know which exercise to give them. It is stored with its author's identifier and the date |
| Authentication | Cryptographic hash of the password. Verification tokens, including one for a pending email change, which holds the new address until it is confirmed or expires. If the member turns on two-step verification, the key of their code app and their ten recovery codes, both encrypted. The key and codes are deleted when the member turns verification off, or when Management removes it because the member lost it |
| Connection | Sign-in date, IP address, browser and operating system |
| Language | The language the member chooses for the app and the emails, if they choose one. It identifies nobody, and erasure does not delete it |
| Membership | Places per month, start date, end date, status (active or paused) |
| Payments | Amount and currency. Payment method (cash, transfer, card, Bizum or other). Month covered and payment date. Whether the entry is a receipt or a correction, and the entry a correction corrects. A free note from whoever records it. Recording «card» by hand stores no card data. A payment collected online keeps its payment attempt: the identifiers Stripe gave the payment session and the charge, the amount, the currency, the month and the outcome. When Management or the member opens a payment's Stripe receipt, the Service fetches the link from the Controller's Stripe account and does not keep it. No data of the card or Bizum used to pay |
| Bookings | Class booked, date and time of the booking, attendance, cancellation with its reason and notice in minutes, cancellation note |
| Place balance | Ledger of every place spent and returned, per month |
| One-to-one sessions and entitlements | Member and coach identifiers. Duration, start and end. Creation, rescheduling, attendance and cancellation, with who asked for it and the cancellation cutoff. The sale or plan the session uses, with its service if it has one, and whether it is for a named coach or any coach of the Controller. Pack size and any last usable date. Credit reservations, releases and explicit corrections. A brief: plain text of up to 1000 characters that the assigned coach or Management writes, stored with its author and time and replaced by the next save. The same account may also hold separate class entitlements. No clinical records are added. Each change records the Controller, the action, the actor, the affected member, the record identifiers and the time. A session change also records the previous and new time, coach or attendance value. A credit change records the credit movement. |
| Personal-training purchases, plans and credits | A purchase from the Controller's catalogue: member and service identifiers; the agreed price for one session or a pack, and its currency; the service's name as sold; duration; quantity; whether it is for a named coach or any coach of the Controller; any last usable date. A plan that the Controller sets up for one member without a catalogue service: member and coach identifiers; number of sessions; total price and currency; a fixed session length; who set it up and when. A plan has no service identifier, service name or last usable date. Both keep credit grants and explicit corrections. The terms as sold stay when an offer changes. A coach change that Management records keeps the previous and new coach identifiers, the actor identifier, the date and the reason, and does not rewrite the original terms. Credit entries keep their actor identifier, date and reason. Class entitlements stay separate. |
| Personal-training financial history | The agreed price for one session or a pack, and its currency. Unpaid charges, amounts received or returned with their method and date, refunds due, and linked corrections or waivers with their reason. An unpaid charge is not a payment received. Each entry records its kind (receipt, refund or bookkeeping correction), the date it was recorded, the actor identifier, the reason, any link to the original entry and any receipt or invoice link. A receipt or refund also records its amount, currency, method and the date the money moved. A correction keeps the original entry and is not money returned. With online collection, each Stripe payment, refund or dispute is one more entry, with the identifiers Stripe gave the payment session and the charge, the amount, the currency and the date. |
| Personal records | Exercise, value and unit. Repetitions, if the member counts them. The class, if the member records it from there. Date and a free note. The member writes them, and only if they want to. Management and the coaches read them |
| Workout results | One per member and class, on a workout the Controller posts with a way of scoring it. The result in that scoring (a time, rounds and repetitions, a load or repetitions) and whether it was done as written (Rx) or scaled. No free text. The member writes it, and only if they want to |
| Photo of a coach on the public page | Optional image of whoever teaches, uploaded by Management as JPG, PNG or WebP of up to 5 MB. The browser shrinks it and only that version is kept. It is the only data in this annex published from a person's record: it appears on the Controller's public page, which anyone reads without an account and search engines index. The Controller must obtain the consent of the person pictured and is responsible for it. The photo stops being served the day the person leaves |
| Photos of the gym | Up to two optional images the Controller chooses for its public page. They may show identifiable people, with the consent duty of «Photo of a coach on the public page». They are deleted when the account closes. A copy left behind by a failed deletion is deleted with the Controller's files 30 days after closure (31 at worst) |
| Role | Profile within the Controller's account: member, coach or Management |
| Notices sent | Which notice type of «Communications to data subjects» it was, to which member, when it was queued and when it went out. The mail server's answer to each attempt to send it. While queued, the notice keeps what its text needs, such as the day and time of the class or the link token. The Service deletes that content from the queue as soon as the notice goes out or is discarded, except in a notice that runs out of attempts. Once sent, a copy of the notice as it went out: the address, the subject and the text, with any link token or code removed, so the Processor can check that it was sent. Whether the member has turned off the reminder or the email copies of notices already kept in the app. When the email delivery service reports that an email bounced permanently or was marked as spam: the address, which of the two it was and when. After a bounce the Service sends that address none of the notices in «Communications to data subjects»; after a spam report it stops only the reminder, the morning summary of member messages and the notices the Controller writes. The Controller sees the reason on the member's record. The entry is deleted when the address on the account changes, when the person is anonymised, or with the account's other rows, 30 days after closure (31 at worst) |
| The gym's messages | The subject and text the Controller wrote, who on its team wrote it, which members it reached and when, so a member can read it again on their profile. The notices the Service leaves only in Management's app when a member's card payment is disputed or a month is paid twice: the amount and the month, without the member's name. When one-to-one session notices are on, their in-app copies: the event, scheduling details, recipients and time. When the Controller sets up a plan for a member to pay by card, the request the Service sends, with no author: the Controller's name, the number of sessions and the link to the member's payments, without the price. |
| Trial class request | Name, email, phone if they leave it, and the class they asked about. Whether the Controller accepted or declined it, who decided and when. If accepted, the account created |
| Joining from the public page | A visitor gives name and email, picks a fee and pays the first month through Stripe. The Service keeps these three while the payment is open and creates the account when it settles. If Stripe closes the payment session unpaid, the Service deletes them at once. A join nobody finished is deleted after four days (five at worst) |
| Application faults | When a screen breaks, on the server or in the browser: the screen, what it was doing, the method and path of the request, the Controller, the requester's profile, the error message and the first lines of its trace. The Service strikes out emails, identifiers and long runs of digits in the message before saving it. It never keeps who the requester was, what they typed, the request body, its headers, their IP address or their browser. A browser fault is recorded only if someone is signed in, with an hourly cap |
| Action log | What the Controller's team does to another person's situation, and what the Processor does to the Controller's account: add, remove, readmit or erase a member; send their invitation again; cancel it without sending another; replace it with a new one with the same expiry, shown in the panel so it can be read to them in person, which stops the link in their email working; the Controller setting the password instead of the member choosing it; changing their role between member, coach and Management; removing their two-step verification when they have lost it and cannot get in any other way; correcting their name, the name they go by in class, their phone or their date of birth; writing or changing the staff note; changing the email they sign in with, recorded when the member confirms it from the new address and not when the Controller asks for it; changing, pausing or resuming a membership; adding a one-off class; downloading the Controller's data, the whole file or the payments; cancelling a class, restoring a cancelled class, changing a class's time or changing its places, by hand or because its weekly schedule moved it to a smaller room; cancelling another person's booking; suspending or reactivating the Controller's account; closing it when the agreement ends; changing the Controller's plan with the Processor; settling by hand, as paid or as never charged, a charge to a member's saved card that Stripe left unanswered; opening, from the platform, the copy of a notice sent; and entering or leaving the Controller's account from the platform. Each line holds the Controller, the action, the identifier of who did it, that of the member it happened to if there is one, that of the row it refers to, and the date and time. In the six actions that change a number, a plan, a role or a time, it also holds that value before and after; in a settled charge, which of the two outcomes. A line never holds a name, an email, a free text, the request, the invitation link, the confirmation link or the password |
Data the Service does not process
Special categories. The Service is not designed to process health data or other special categories. The fields where that risk is highest are the staff note and the session brief. They are for the adjustment to training («nothing overhead until October») or the plan for a session, not for the diagnosis, injury, operation or medication. The Service warns about this above each field, limits its length and shows the whole text to the member it is about. These measures limit the risk without removing it, because a free text field accepts anything. This agreement does not cover processing health data in the Service.
Bank and card details. The Service does not see or store a member's card number, IBAN or receipt stub. The Controller's staff record by hand, in the «Payments» category, the payments the Controller receives outside the Service.
Online collection of fees with Stripe
Clause 9 governs Stripe's role and the Controller's relationship with Stripe.
The Controller is the one who collects. The payment opens on the Controller's Stripe account and the money goes straight there. It never passes through an account of the Processor. The Processor takes no commission on it and is not named as beneficiary. The Controller handles refunds and chargebacks from its own Stripe dashboard.
What is sent to Stripe to open a payment:
- the amount and the currency;
- the name of the line the member reads («Membership fee for September 2026» or «Strength: bundle of 10 sessions»);
- the language of the page;
- the two addresses on the Controller's public page where Stripe returns the member when they finish or back out;
- an opaque reference to recognise the payment;
- the member's email, which fills in Stripe's page in advance and receives Stripe's receipt if the Controller has that on in its Stripe account;
- a description of the charge with the member's name and what they pay for (the month, the one-to-one session, the bundle or the plan), so the Controller recognises each charge in its Stripe dashboard.
Neither the member's identifier nor the Controller's is sent. The name and email stay in the Controller's Stripe account under its own agreement with Stripe (clause 9.3). Erasing or anonymising the member in the Service does not delete them there. Deleting them there, where appropriate, is for the Controller. Stripe asks the member on its own page for what it needs to collect (the card details, or the Bizum phone number and the payment confirmation). That data does not pass through the Service.
What comes back from Stripe: a signed notice. From it the Service writes a «Payments» row (amount, payment method, month covered, date and a short note). It keeps the identifiers Stripe gives that payment and its attempt, so the same payment is never recorded twice. Each refund and each chargeback writes an offsetting negative row and leaves the original row unchanged. A refund or chargeback notice also contains a summary of the payment method and the details the payer typed on Stripe's page. After checking Stripe's signature, the Service reads only the payment attempt's identifier, the amount refunded and the currency, and keeps nothing else from it. The log of notices received keeps each notice's identifier, type and dates, never its content.
The Controller's Stripe account. To create it, the Service sends Stripe the country the Controller states, the Controller's identifier and an email address: the Controller's contact address or, if there is none, that of the team member who starts the onboarding. The Service keeps that address only while the account is being created, so a failed request can be repeated. Of the account, the Service keeps its reference; Stripe's answers on whether it can collect, whether onboarding is complete and whether Bizum is active; the dates of those answers; and the date the Controller paused the function, if it did. Onboarding happens entirely on Stripe's screens. No document or bank account of the Controller reaches the Service.
What each profile reads
- Management reads everything. Only Management can download the Controller's data.
- A coach reads each member's bookings, attendance, place balance with each movement, date of birth, staff note and the numbers of their personal records. A coach sees only their own one-to-one sessions, with the brief and the minimum identity and eligibility, credits included, needed to arrange them. A coach does not read a member's contact details (email, phone, address), identity documents or anything about money: membership, payments, payment method, invoices, what they owe, amounts, payment status or refunds. A coach does not read the email or phone of a trial class request. The Service does not ask the database for that data when the reader is a coach.
- A member sees their date of birth on their profile and cannot change it. They read the staff note about them in full on their profile, with its author and date. They see their own one-to-one sessions and the whole brief on each. Apart from Management, only the member reads the amounts, payment records, document links and any outstanding balance of their personal training.
- Other members read a member's workout result, with the member's name, on that class's board while the member keeps their place in the class, unless the member turns off appearing in class lists on their profile. Other members do not see a member's staff note or one-to-one sessions.
Communications to data subjects
The Service supports eighteen notice types on behalf of the Controller. Sixteen follow an action; two are scheduled: the class reminder and the morning summary of member messages.
| Notice | When it goes out |
|---|---|
| Class cancelled | The Controller cancels a class the member had booked |
| Class restored | The Controller restores a cancelled class the member had booked |
| Time changed | The Controller moves a class the member has booked to another time |
| Place free | A place is freed and goes to the member from the waiting list |
| Booking made from the panel | The Controller books the member into a class from the panel |
| Booking cancelled from the panel | The Controller takes the member out of a class from the panel |
| One-to-one session | Confirmation, change or cancellation of the recipient's one-to-one session. It gives when the event happened, the relevant session dates and times, the previous time if it changed, and a link to the recipient's page in their own account. It names no other client and carries no contact details, payment or debt amounts, medical notes or free-text cancellation reason. Service and financial details are shown only inside the account. |
| Class reminder | The evening before a class the member has booked |
| Fee reminder | The Controller asks the Service to remind members who still owe a closed month's fee |
| Price rise | The Controller raises the fee of a member who keeps a card saved to pay it. It gives the old and new price, the month the new one starts with and the first day the card is charged it, so the member can remove the card or ask to end their membership first |
| Member message | A member writes to the Controller. Each morning at 08:00 in the Controller's time zone, while nobody on the staff has opened it, the staff who may read it get one email: Management for every conversation, a coach only for those they may read. It names the Controller and links to its messages. It names no member, gives no count and carries no message. It goes only while the Controller uses member messages, and the email-copy switch turns it off |
| Invitation | The Controller creates the member's account without setting a password, or gives them a new link because they cannot get in; or the visitor's payment settles and the account is created |
| Password | The member asks to reset theirs |
| Sign-in code | The member asks to sign in with a code instead of their password. It carries an eight-digit code that lasts ten minutes and works once |
| Notice written by the Controller | The Controller writes to its members or to its own team (Management and coaches) and chooses who. The Service also sends one, with no author, to a member when the Controller sets up a plan of one-to-one sessions for that member to pay by card. Its in-app copy names the Controller, the number of sessions and the link to the member's payments; the email adds the price |
| Email change confirmation | The Controller asks to change the address the member signs in with. It is the only notice sent to an address not yet on record: the new one, so whoever reads it confirms it |
| Email change started | On that same request, the Service tells the address the member still signs in with which address the account is to move to, that nothing has changed yet, and that the member should tell the Controller if they did not expect it |
| Security notice | Two-step verification on the recipient's account is turned off, the Controller lifts it, or new recovery codes are made, so the recipient can act if it was not them |
The reminder is the only notice the member can turn off completely, from their profile or with the reminder's one-click unsubscribe link. The Service discards a reminder whose class has already started. Another switch stops the email copies of the notices already kept in the app: the cancellation, the time change, the free place, the booking cancelled from the panel, the Controller's notice, the morning summary of member messages, and one-to-one session notices. A notice the Controller sends by email only is kept in the app for each member with that switch off, instead of being emailed to them. The reminder, the Controller's notice and the morning summary of member messages carry a one-click unsubscribe link for the recipient's mail app, which turns that notice's switch off without signing in. The other email copies carry no such link. All remaining emails always go out, without one, except to an address the email delivery service has reported («Notices sent»).
Each notice carries the member's name and email; the day, time and title of the class it is about; whether the place was taken from the balance or returned to it, and whether that balance is weekly or monthly; whether the booking can still be cancelled; and the links to the app that notice needs, including, in the invitation and the reset, the one with the token to choose a password. The sender shown is the Controller's name over a miaforo address. No notice carries the booking history, the payments or the personal records. Only the fee reminder and the price rise carry the membership: the fee reminder names the unpaid month and the amount owed, and the price rise the old and new fee. Only the email asking a member to pay a plan by card carries the plan's price.
The notice written by the Controller carries its subject and text as written, without review or translation. The Controller is responsible for its content. It is for service notices: the Service asks for no consent, so it is not fit for advertising. Its email carries that one-click link, which stops only the email copy: the notice then reaches that member in the app.
The Processor also sends Management these notices as a controller, for its own contract with the Controller (clause 1.3), not on the Controller's behalf.
| Customer notice | Scope |
|---|---|
| Subscription trial ending | A billing notice the Processor may send before the Controller's free month ends. It names the end date, the plan, the price before VAT and how to cancel. A cancelled subscription gets no notice. |
| Agreement changed | One notice before a material change to this agreement takes effect, as clause 16.4 requires. It names the change and the date it takes effect. |
| First steps | In the Controller's first 14 days: one notice if the Controller has no weekly class 24 hours after opening, and one if it has no member 72 hours after its first class. Each is sent once per Controller. |
| Subscription payment refused or gym frozen | A billing notice the Processor sends when a debit for the Controller's subscription fails for the first time, naming the reason in general terms, the next attempt and the link to pay the invoice; and one when the Controller's account is blocked for an unpaid subscription, naming the amount owed. Each is sent once per invoice or per block. |
Nature and purpose
Collection, recording, organisation, storage, consultation, alteration, disclosure by transmission in the cases this annex describes, anonymisation and erasure. The sole purpose is to provide the Service to the Controller: account creation, class booking, control of capacity and memberships, attendance records, payments, notices, workout results on the workouts the Controller posts and, if the Controller switches them on, personal records and trial class requests. The purpose also covers the support, security and maintenance of the Service, including the fault log in «Application faults».
Duration and retention periods
The processing lasts as long as the Service, with these periods. An automatic process runs once a day, so each period may run one day longer at worst.
- Active member: their data is kept while they stay active. The date of birth and the staff note have no period of their own: they go when the Controller removes them, on the member's erasure or on automatic anonymisation.
- Member who has left: their record no longer appears in the app and their bookings in upcoming classes are released. It is anonymised 365 days after they leave (366 at worst).
- Closed account: 30 days after closure (31 at worst), every row of the account that relates to a person is deleted: records, bookings, attendance, place balance, payments, personal records, workout results, the action log, trial class requests, the Controller's messages and the notices. After that date the Processor keeps no personal data of the Controller, except backups until they expire. A record whose leaving period ends earlier is anonymised on its own date.
- Trial class request: deleted entirely 90 days after it arrives (91 at worst), whether the Controller accepts it, declines it or does not answer it. Its legal basis, steps taken at the data subject's request before entering into a contract (Article 6(1)(b) GDPR), runs out once the class they asked about has passed.
- Application fault: each distinct fault takes one row, deleted 30 days after it last occurred (31 at worst).
- Action log: each line is deleted 365 days after the action (366 at worst), the same period as the member's record. There are 31 actions, listed in the «Action log» category of this annex.
- Copy of a notice sent: its address, subject and text are deleted 30 days after it was sent (31 at worst). The record that it was sent, with its type, member, time and the mail server's answer, is deleted 365 days after it was sent (366 at worst).
- Sign-in sessions: expire 30 days after their last use.
- Backups of the database and the photos: kept seven days, eight at worst, then deleted automatically. The period counts from when the record is anonymised or deleted or the photo deleted, not from when the member leaves.
When a member who left is anonymised while the account stays open, the remaining rows (bookings, attendance, place balance, workout results, payments without their note, and the action log until its period ends) stay as the Controller's history until the account closes. Nothing in them identifies the person within the Service, but they stay linked to a stable internal identifier, and the Controller may hold other information that links them to that person. Clause 14.4 keeps them subject to this agreement.
One-to-one sessions, agreed charges, personal-training terms as sold, coach changes, credits and financial history follow the retention periods and the deletion of the rest of the account. Money and credit entries, with their actor identifiers, times and internal links, are an accounting and credit history of their own: they are not action log lines and do not take its shorter period. After a member's anonymisation, this history stays linked to the stable internal identifier until the account closes and the deletion period passes. It is part of the member's own data and of the Controller's data download, under the access rules in «What each profile reads». When a member's account is removed, their future one-to-one sessions are cancelled. Any credit or refund owed as a result stays recorded for the Controller to settle. Anonymisation does not turn a refund due into a refund made.
Erasure of a member
When a member's right to erasure is exercised, or their automatic anonymisation is due, the Service anonymises their record. It does not delete the rows:
- The name is replaced with a generic label and the email with an address on the reserved
.invaliddomain, which can never resolve. - The name they went by in class, the phone and the date of birth are removed.
- The staff note is removed, with its author's identifier and the date.
- The access credentials are removed and, if two-step verification was on, the key of their code app and their recovery codes.
- Every open sign-in session is removed, with the IP address and browser it held.
- The trial class request their account came from, if any, is deleted entirely, with the name, email and phone left in it, without waiting for its period. Notices waiting to be sent are cancelled unsent, and the invitation link they carried is deleted.
- The copies of the notices sent to them lose the address, the subject, the text and the mail server's answer. The record that each was sent stays until its own period ends.
- The free texts of the personal records, the cancellations and the payments are emptied.
- Their photo, if they taught, is deleted from the server: the member's whole folder is removed, including the photo on the public page. Earlier backups hold it until they expire.
- Bookings, attendance and the place balance are kept without the data that identifies the member, as the Controller's occupancy history, including their place on the waiting list of a class already held.
- Workout results are kept without the data that identifies the member: each is a number and whether it was done as written, for one class, with no free text. They leave the class board.
- What has not happened yet is not kept this way: their upcoming bookings are cancelled, each place returns to its balance and to the calendar, and they leave the waiting lists of those classes.
- Payments are kept without their note: the amount, payment method, month and date are the Controller's accounting record, which it may have to keep. The Stripe payment attempt kept with a payment also stays. It has no free text. Its identifiers point to the Controller's Stripe account, where the Controller can find the charge with the name and email sent when it was opened («Online collection of fees with Stripe»), which the Service cannot delete.
- One-to-one sessions, charge adjustments, and personal-training purchase, coach-change, credit and financial entries are kept against the internal identifier. Personal free-text notes are cleared and session briefs deleted. Stored service names that identify the member are cleared or replaced with a generic label. Receipt, invoice or other document links that identify the member are removed. Amounts, currency, movement kinds, dates and structured internal references stay. The Controller may still be able to link this history to the person from its own records.
- The lines of the action log are kept unchanged, because they hold only identifiers and the name of an action, until their own period ends.
If the Controller needs those rows physically deleted, it must ask in writing. Before asking, it must consider whether a legal obligation prevents the deletion. A trial class request is not anonymised: it is deleted entirely at the end of its period, or earlier with the erasure of the member who came from it.
Download of the Controller's data
Management downloads from the panel a JSON file with the database rows, including the action log and the rows of members who have left or been anonymised. It holds no image files; clause 14.2 says how the Controller gets them.
Annex III. Technical and organisational measures
Encryption and credentials
- Encryption in transit with TLS on all traffic, with a certificate renewed and applied automatically.
- Passwords stored as a cryptographic hash, never in clear and never recoverable.
- Two-step verification keys and recovery codes stored encrypted.
- Secrets kept out of the code repository and injected as environment variables at deployment.
Access control
- Separation by customer: every query to a table with member data is filtered by Controller in the data access layer.
- Access control by profile, checked on the server and not in the browser (Annex II, «What each profile reads»).
- Sign-in sessions that expire after the period in Annex II.
- The Processor's staff reach the platform administration only with a second authentication factor. The action log records each time they enter or leave a Controller's account from the platform or open the copy of a notice sent, and the Controller receives that log in its data download.
Infrastructure and availability
- Database with no port published on the internet: only the application's own containers reach it.
- Daily backups of the database and the photos, encrypted before they leave the server and kept for the period in Annex II in a separate location (Annex IV).
- Reproducible deployment from container images, with the option to go back to the previous version.
Development and organisation
- Code changes reviewed and checked automatically before release.
- Application faults logged in the Service's own database, not sent to third parties, with personal data in the message struck out.
- Review of these measures under clause 6.2.
Annex IV. Authorised sub-processors
| Sub-processor | Service | Location of the data | Contract and safeguards |
|---|---|---|---|
| IONOS SE | Server, database and the mailbox the notices in Annex II go out through | Berlin, Germany (EEA) | |
| Hetzner Online GmbH | Encrypted backup of the database and the photos, in a Storage Box. It receives only bytes encrypted before they leave the server, which it cannot read | Falkenstein, Germany (EEA) | Processing agreement (Art. 28) accepted in the account, 2026-08-30 |
The Processor makes no transfer outside the EEA.
The Service uses no other Sub-processors: no advertising, visit measurement or analytics services, no content delivery networks (the fonts are served from the Service's own domain), and no external error logging services.
Stripe is not in this annex. For collecting members' fees online it is a provider the Controller engages directly (clause 9). For collecting the Controller's subscription to the Service it falls outside this agreement (clause 1.3).