Data Processing Agreement (DPA)
How Reservo, as a processor, handles players' data on behalf of the club.
Version 0.3-borrador · Last updated September 29, 2026
Summary
| Item | Details |
|---|---|
| Nature | Data protection annex to the club terms, pursuant to Article 28 GDPR. It governs the processing carried out by Reservo, as processor, of the data of the club’s players, with the club acting as controller. |
| Subject matter and duration | Providing the booking, competition and payment management service described in the club terms, for as long as that contractual relationship remains in force. |
| Data subjects | The club’s players with a Reservo account, customers the club registers without an account, and club staff with access to the panel. |
| Types of data | Identification and contact data (first name, surname, email address, phone number, profile photo and, where a competition requires it, Spanish ID number (DNI or NIE)), booking, class and competition participation data, match chat messages, notes the club records about its customers and, where the club enables online payment, payment transaction data. No special categories of data are processed. |
| Sub-processors | Reservo may engage sub-processors (infrastructure, payments, email, analytics) under a general authorisation, with an obligation to report changes. Up-to-date list at sub-processors. |
| Who accepts | Only the club’s owner, in a single act that accepts both the club terms and this DPA. |
1. Subject matter of the processing
Under this Data Processing Agreement (DPA), the club (controller) engages Reservo (processor) to process the personal data of its players as necessary to provide the service described in the club terms: management of bookings, competitions, operational communications and, where applicable, online payment.
Nature of the processing. Reservo collects, records, stores, consults, modifies, discloses to data subjects and to authorised sub-processors, and erases the data, exclusively through the platform and to the extent necessary to provide the service.
Data subjects and types of data. The data subjects are the club’s players with a Reservo account, customers the club registers without an account, and club staff with access to the panel. The data processed are identification and contact data (first name, surname, email address, phone number, profile photo and, where a competition requires it, Spanish ID number (DNI or NIE)), booking, class and competition participation data, match chat messages, notes the club records about its customers and, where the club enables online payment, payment transaction data. No special categories of data (Art. 9 GDPR) are processed.
2. Controller’s instructions
Reservo processes the data solely on the club’s documented instructions, as reflected in the configuration of the platform (which data is collected, which communications are sent) and in this Agreement. If Reservo considers that an instruction infringes the GDPR or other data protection legislation, it will inform the club before carrying it out.
3. Confidentiality and security
Reservo staff with access to the data are subject to a duty of confidentiality. Reservo applies technical and organisational measures appropriate to the risk (set out in the annex below) to protect the data processed on the club’s behalf.
Annex: technical and organisational measures (Art. 32 GDPR)
- Encryption in transit: all communications with the platform take place over HTTPS (TLS).
- Location and encryption at rest: the database is hosted in the European Union (Frankfurt, Germany), with a provider that encrypts data at rest.
- Role-based access control: each club can access only its own data, and within the club access is graded by role (
owner,admin,staff). - Authentication: passwords are stored using a salted key derivation function, never in plain text; email verification is required; sessions use secure cookies with an expiry.
- Abuse protection: request limits per IP address and per user.
- Payment data: Reservo does not store card numbers; payments are processed by Stripe, which is PCI DSS certified.
- Traceability: the platform records which user creates, modifies or cancels bookings and till operations.
- Backups: the database can be restored to an earlier point in time using the provider’s functionality, to recover from data loss or corruption.
- Minimisation: when a player closes their account, their identification data is anonymised, on the terms set out in the privacy policy.
- Staff access: access to production systems is limited to the people who need it to provide the service, who are subject to a duty of confidentiality.
- Incident management: security breaches are notified to the club in accordance with section 6.
4. Sub-processors
The club grants Reservo a general authorisation to engage the sub-processors needed to provide the service (cloud infrastructure, payment gateway, email delivery, analytics), always imposing on them data protection obligations equivalent to those in this Agreement. The up-to-date list of sub-processors is available at /en/subencargados. Reservo will inform the club of any intended change to that list reasonably in advance, giving the club the opportunity to object on justified grounds.
5. Data subjects’ rights and assistance to the club
Reservo will assist the club, insofar as possible and within the technical scope of the platform, so that the club can respond to requests from its players to exercise their rights (access, rectification, erasure, objection, restriction, portability). If a data subject sends Reservo a request concerning data that Reservo processes on the club’s behalf, Reservo will forward it to the club without delay.
Reservo will also assist the club, taking into account the nature of the processing and the information available to it, in complying with its obligations regarding security of processing, notification of personal data breaches, data protection impact assessments and prior consultation of the supervisory authority (Arts. 32 to 36 GDPR).
6. Personal data breaches
Reservo will notify the club without undue delay, and in any event within 48 hours of becoming aware of it, of any breach of security affecting the personal data processed on the club’s behalf of which it becomes aware, together with the information available, so that the club can comply, where applicable, with its own duty to notify the supervisory authority.
7. International transfers
Where the processing involves a transfer of data outside the European Economic Area, an adequacy decision of the European Commission or the appropriate safeguards under Chapter V GDPR (in particular, the Standard Contractual Clauses) will apply. Details for each sub-processor are available at /en/subencargados.
8. Return or deletion of data
On termination of the service, the club has 30 days to request the return of the personal data processed on its behalf. Once that period has elapsed, or earlier if the club so requests, Reservo will delete that data and any existing copies, unless applicable law requires it to be retained.
9. Audit
The club may ask Reservo for the information reasonably necessary to demonstrate compliance with the obligations under this Agreement. As a general rule, audits will be carried out on a documentary basis: Reservo will answer the club’s reasonable questionnaires and provide it with documentation demonstrating compliance with this Agreement. The club may request an audit no more than once a year, unless there has been a security breach affecting it or a supervisory authority so requires, and with 30 days’ notice. The costs of the audit are borne by the club. On-site inspections will take place only where documentary verification proves insufficient or a supervisory authority so requires, and will be agreed in advance between the parties.
10. The club’s obligations as controller
As controller, the club is responsible for:
- having a valid legal basis for each processing operation it entrusts to Reservo;
- informing its players and customers about the processing of their data (Arts. 13 and 14 GDPR), including the use of Reservo as processor;
- handling data subjects’ requests to exercise their rights, with the assistance from Reservo provided for in section 5;
- entering into the platform only data that are necessary and accurate and, in particular, not recording special categories of data (for example, health data) in its customer notes;
- diligently managing its staff’s access to the panel and revoking it when no longer needed;
- notifying the supervisory authority and, where applicable, data subjects of personal data breaches as required.
11. Acceptance
This Agreement is accepted in the same act as the club terms, through the action of the club’s owner in the administration panel. Both documents are recorded with the same date and time of acceptance.