Skip to content
Create a club

Data Processing Agreement

Version 2.1 Dated

Table of contents
  1. Scope of this translation
  2. § 1. Conclusion and duration
  3. § 2. Subject matter and scope
  4. § 3. Our obligations
  5. § 4. Further processing
  6. § 5. Personal data breaches
  7. § 6. Audit
  8. § 7. End of processing
  9. § 8. Obligations of the Club and liability
  10. § 9. Changes and governing law
  11. Annex No. 1: Technical and organizational security measures
  12. Changes in the version of November 4, 2026
  13. Regional notice: United States, Canada, United Kingdom and Ireland

concluded under Art. 28 of the GDPR by acceptance in the Wizard for creating a Club Account in the SportDesk system

Scope of this translation

This document is an informational working translation of the Polish document “Umowa powierzenia przetwarzania danych osobowych | SportDesk”, version 2.1 of November 4, 2026, which is binding. It has not been reviewed by a lawyer. Acceptance in the System always concerns the Polish version, and any changes are made only in the Polish text; if the English text differs from the Polish text, the Polish text prevails. Items that apply only in some cases, such as the PESEL number (the Polish national identification number), apply only where a Club collects them.

§ 1. Conclusion and duration

  1. The Club concludes this Agreement in electronic form (Art. 28(9) GDPR), by ticking the acceptance box when it creates the Club in the Wizard, or by clicking “I accept on behalf of the Club” in the panel. The person who accepts this Agreement declares that they may represent the Club for this purpose.
  2. We record each acceptance in the acceptance register. The register shows who accepted (account, first name and surname, e-mail and role in the Club), on behalf of which Club (identifier and name), when (date and time with seconds, in UTC), from where (IP address and browser), and what (document, version number, language, method of acceptance and the SHA-256 hash of the content of that version). The management of the Club can see its acceptances in the panel (Club settings, Documents and acceptances) and download the accepted version as a PDF.
  3. This Agreement applies for as long as the agreement on the use of SportDesk (the Terms) applies. The obligations under § 7 last until they are performed.
  4. In matters concerning personal data, this Agreement prevails over the Terms.
  5. This version replaces the earlier version of the Agreement from the moment the Club accepts it (§ 9(1)).

§ 2. Subject matter and scope

  1. We process data only to provide the SportDesk service to the Club. We store and organise the data, make it available to people in the Club according to their roles, send e-mails and SMS messages on behalf of the Club, prepare summaries, documents and exports, pass payment data to the payment operator chosen by the Club, make backup copies and delete data. The processing is automated and lasts for as long as the Club uses the service.
  2. This Agreement applies to persons whose data the Club enters into the system or collects through the system:
    1. athletes and members of the Club, including children;
    2. parents and legal guardians of athletes;
    3. coaches and other staff;
    4. members of the management board and other persons with access to the Club panel;
    5. candidates who submit a membership declaration, and their guardians;
    6. guests at training sessions (e.g. a trial training session);
    7. persons who buy in the Club shop, pay into the Club’s fundraising, or pay online to the Club.
  3. Categories of data (the scope in a given Club depends on the modules enabled and the fields the Club fills in):
    1. identification and contact: first name, surname, gender, date of birth or birth year, PESEL number (§ 2(5)), address, school, e-mail, telephone number, emergency contact, relationship of the guardian to the athlete;
    2. membership and sport: group, level, status, dates of joining, suspension and leaving, family, sports licence numbers, height, weight, clothing and footwear sizes, results and competitions, call-ups for matches, age categories;
    3. activity in the Club: attendance at training sessions, registrations for events, camps and competitions, together with the answers in the registration form, club equipment issued and reserved, orders in the Club shop, donations to fundraising;
    4. consents and documents: membership declarations, consents and statements, with the version and language of their content and information on who gave them (the athlete or a guardian), participant agreements with scans, athletes’ documents (type, number and validity dates), statuses and dates of coach verification (without the content of certificates);
    5. finances: receivables, discounts and reductions, payments, balances, online payments, sender and account number from transfers and bank statements uploaded by the Club (to assign payments);
    6. communication: content and delivery status of e-mails and SMS messages sent by the Club, the recipient’s e-mail address or telephone number;
    7. accounts: e-mail, first name and surname, telephone number, role and permissions, password hash, two-step verification data, account language;
    8. descriptive fields: notes and additional fields defined by the Club;
    9. the Club’s event journal: who and when performed, in the Club account, an action recorded for security and accountability (e.g. revealing sensitive data, downloading a scan, export, changing settings), together with the e-mail address of the account and, in some entries, the IP address.
  4. Children. SportDesk processes children’s data. The Club decides whether a child has its own account (from the age of 13 at the earliest; in Poland a person is independent by default from the age of 16). Up to the age that the Club’s market provides for consent to digital services (16 years in Poland), consents in the declaration are given by the guardian, and the system records who gave them.
  5. PESEL. The PESEL field exists only in Clubs from Poland and is not mandatory. The Club decides whether to collect it (e.g. for a sports association licence or insurance). Only the management of the Club can see the PESEL number, and we record each time it is revealed.
  6. Health data (Art. 9 GDPR). The Club may process health data in SportDesk: health information on an athlete’s card (e.g. allergies, chronic diseases, medicines), health statements and consents to medical assistance from the declaration, and the type and validity date of medical examinations and certificates. The Club decides whether it uses these fields and must have a basis under Art. 9(2) GDPR (e.g. the explicit consent of the athlete or guardian, or a provision of law). For the field “Health information” we apply additional safeguards: only the management can see it, each time it is revealed we record it, the field is not included in the ZIP export, is not passed to the AI assistant, and is not shown to our staff in operator mode. These safeguards do not cover descriptive fields (notes, additional fields), so the Club should not enter health information there.
  7. Our own purposes. Apart from the service for the Club, we process some data for our own purposes, and for those purposes we are the controller of that data. The SportDesk privacy policy describes them. They are:
    1. data of the Club as our customer and of the persons who represent it, needed to conclude and perform the agreement, for settlements and invoices;
    2. the acceptance register (§ 1(2)), as evidence that the agreement was concluded. We keep it for the limitation period of claims, also after the Club leaves;
    3. server logs (e.g. IP address and time of the request) and a record of actions of our staff in the operator panel (who, when, on which Club account and for what reason, without data from the Club’s records), to operate and secure SportDesk;
    4. the “Janusz” help chat on the website and in the panel: the content of users’ questions and answers. Janusz has no access to data in the system. It works only after the user’s explicit consent to passing the content of the conversation to the model provider (DeepSeek, China); the basis for this transfer is under consideration (page Sub-processors, § 3). The Club’s event journal (paragraph 3, point 9) is not our own purpose: we process it on the Club’s behalf. We do not use the data of athletes, parents and coaches for marketing, we do not sell it, and we do not use it to train AI models.
  8. Statistics on the Club’s instruction. The Club instructs us to create from the data in the system aggregated statistics of the whole platform (e.g. the number of clubs, accounts and athletes, and the total of online payments), from which neither individuals nor the Club can be identified. We use them to develop SportDesk.

§ 3. Our obligations

  1. We process data only on the Club’s documented instructions, including when the instruction concerns transferring data outside the European Economic Area (EEA). The instructions are this Agreement, the Terms, the Club’s settings, and the actions performed in the panel by persons authorised by the Club. If EU or Polish law requires us to process data in a different way, we inform the Club in advance, unless that law forbids it. If we consider that an instruction of the Club infringes data protection law, we inform the Club without undue delay.
  2. Only persons authorised by us have access to the Club’s data. They have undertaken to keep the data confidential, also after they stop working with us. They use the access only when it is needed to maintain the service or to provide the help the Club asks for. When our employee enters the Club’s account (operator mode), we record the entry together with the reason.
  3. We apply the security measures required by Art. 32 GDPR. They are described in Annex No. 1. We may change them to measures that are at least as effective.
  4. We help the Club:
    1. to respond to requests from data subjects. The panel allows the management to review, correct, export, anonymise and delete data on its own. If a request reaches us, we pass it to the Club within 5 business days and do not respond to it ourselves, unless the Club asks us to;
    2. to meet the obligations under Art. 32–36 GDPR (security, breaches, impact assessment, prior consultation), to the extent that the nature of the service and the information we hold allow.
  5. We provide the Club with the information needed to demonstrate that we comply with this Agreement and Art. 28 GDPR, and we allow audits (§ 6).

§ 4. Further processing

  1. The Club agrees that we may use further processors (sub-processors). The current list is on the page Sub-processors and in the Club’s panel. It states the entity, its country, the scope of services, the categories of data, the place of processing and the basis for transferring data outside the EEA.
  2. We have a contract with each sub-processor that provides the data protection required by Art. 28(3) GDPR. At the Club’s request we make its essential terms available. We are responsible to the Club for the acts of a sub-processor as for our own (Art. 28(4) GDPR).
  3. We inform the management of the Club in the panel at least 14 days in advance about a planned addition or change of a sub-processor. During that time the Club may raise an objection with reasons, to [email protected]. We then look for a solution. If we do not reach an agreement, the Club may terminate the agreement before the change takes effect, without any termination fees. In that case we refund the fee for the unused part of the paid billing period.
  4. We store the Club’s data in Poland, in the OVH data centre (EU). Outside the EEA, data may reach only through the sub-processors indicated in the list:
    1. Cloudflare (USA), which handles all traffic to SportDesk, on the basis of the EU-U.S. Data Privacy Framework and standard contractual clauses;
    2. Z.ai (Singapore, a service of a company in the Zhipu AI group, whose parent company is based in China), only when a Club from Poland on the Pro AI Plan itself turns on the AI assistant. Singapore has no European Commission decision of adequacy. The basis for this transfer is under consideration: we are checking whether the contract with the provider includes standard contractual clauses, and we are assessing the consequences of the transfer. Until it is confirmed, the assistant works only in a Club that turns it on itself, and data goes to Z.ai only after pseudonymisation (Annex No. 1, point 9). The Club may turn it off at any time.
  5. The payment operator through which parents pay the Club (e.g. Tpay, PayU, Przelewy24, Autopay, Stripe) is not our sub-processor. The Club concludes its own agreement with it, and the operator is a separate controller of the payer’s data. On the Club’s instruction we pass payment data to it.

§ 5. Personal data breaches

  1. We inform the management of the Club about a breach of the Club’s data without undue delay, and no later than 48 hours after we establish it, by e-mail to the Club’s address and to the members of the management.
  2. We pass on what we know at the time of the report: what happened, which categories of persons and data it concerns and approximately how many, what the possible consequences are, what we have done or propose to limit them, and whom to contact. We pass on missing information as soon as we establish it.
  3. Notifying the President of the Personal Data Protection Office (UODO) and notifying the data subjects belongs to the Club as the controller. We help it with this.

§ 6. Audit

  1. The Club may check whether we comply with this Agreement. First we answer its questions in writing or by e-mail, within 14 days.
  2. If that is not enough, the Club, or an auditor it authorises, may carry out an audit. The Club informs us at least 14 days in advance, and not more often than once a year, unless a breach has occurred or the supervisory authority requires it. The auditor undertakes to keep the information confidential. An audit may not give access to data of other clubs or disrupt the operation of the service.
  3. The Club bears the costs of an audit, and we charge our working time for the audit at reasonable rates agreed before the audit. If the audit shows a material breach of this Agreement on our part, we bear the costs.

§ 7. End of processing

  1. During the term of this Agreement, the management may download the Club’s data in the panel (Club settings, Data export) as a ZIP archive with CSV files and scans. Health information from the athlete’s card is not included in the export (to protect against accidental sending of the file further). At the management’s request we provide it separately, in a secure way.
  2. After the end of use of SportDesk, the Club has 30 days to download its data (§ 12 of the Terms). Then we delete the Club’s data, no later than within a further 30 days. We also delete the entries of the Club’s event journal (§ 2(3), point 9); until then the management may download them together with the data export. Data disappears from backup copies in the cycle of their overwriting. We provide the length of this cycle to the Club on request.
  3. After the end of the agreement we keep only the data that we must keep by law (e.g. settlement documents with the Club), and the data of our own purposes under § 2(7): the data of the Club as our customer, the acceptance register, server logs and a record of actions of our staff. We process them only for those purposes.

§ 8. Obligations of the Club and liability

  1. The Club is responsible for ensuring that:
    1. it has a legal basis to process the data it enters, including a basis under Art. 9(2) GDPR for health data;
    2. it informs athletes, parents, guardians and coaches about the processing of their data (Art. 13 and 14 GDPR), including that it uses SportDesk. A template privacy policy for the Club is available in the panel;
    3. it obtains the consents of legal guardians where they are required;
    4. it enters only the data needed for its purposes, gives access only to persons who need it, and withdraws it from persons who leave;
    5. it decides on enabling features that pass data further (SMS, AI assistant, online payments), after reviewing the list of sub-processors.
  2. Each party is liable for damage caused by the processing of personal data under the rules of Art. 82 GDPR. We are liable when we have not met the obligations that the GDPR imposes on processors, or when we acted outside the lawful instructions of the Club or contrary to them.
  3. Our liability to the Club under this Agreement is subject to the limit and the exclusions in § 10 of the Terms. The limit is common to the Terms and this Agreement and is the higher of two amounts: the sum of the fees paid by the Club in the 12 months before the event that caused the damage, or PLN 500. The limit also covers the Club’s recourse claims against us under Art. 82(5) GDPR and our liability for sub-processors (Art. 28(4) GDPR). It does not cover damage caused intentionally.
  4. If we pay compensation to a data subject, or bear the costs of proceedings for damage for which the Club is responsible, we may demand from the Club reimbursement of the appropriate part (Art. 82(5) GDPR). The Club also releases us from liability towards third parties and covers reasonable defence costs, if a claim results:
    1. from the lack of a legal basis for processing on the Club’s side;
    2. from data entered by the Club contrary to this Agreement;
    3. from our carrying out the Club’s instruction in accordance with its content. The release does not cover damage that results from our breach of this Agreement or of the GDPR, nor a case in which we established that the instruction infringes the law and did not warn the Club (§ 3(1)). It does not cover administrative fines imposed on us. We inform the Club of such a claim without delay and allow it to take part in the defence.
  5. Paragraphs 3 and 4 do not limit our liability towards data subjects, nor administrative fines that the supervisory authority may impose on us (Art. 83 GDPR). They also do not limit liability for damage caused intentionally.
  6. Towards a Club that is a natural person conducting a sole business activity, for which the agreement does not have a professional character (a Consumer with entrepreneur rights, § 1(8) and § 6(8) of the Terms), the limit in paragraph 3 and the release in paragraph 4 do not apply. We are liable to it on general terms.

§ 9. Changes and governing law

  1. We inform the management of the Club in the panel at least 14 days in advance, with a list of the changes and the date from which we propose the new version. A change binds the Club only from the moment the management accepts it with a button in the panel (we record the acceptance in the register, § 1(2)). Continued use of SportDesk does not mean acceptance. Until the Club accepts the change, the version it accepted earlier applies to it. A Club that does not accept the change may at any time stop using SportDesk, free of charge (§ 12 of the Terms).
  2. A change of the list of sub-processors is not a change of this Agreement. We announce it in the manner set out in § 4, paragraph 3.
  3. Matters not regulated here are governed by the GDPR and Polish law, including the Act of 10 May 2018 on the protection of personal data. The competent court is indicated in § 15 of the Terms.
  4. If any provision proves invalid, the remaining provisions remain in force.
  5. This Agreement is available at sportdesk.pro/data-processing-agreement and in the Club’s panel.

Annex No. 1: Technical and organizational security measures

  1. Encrypted connection. The browser connects to SportDesk only over HTTPS (TLS). Traffic passes through the Cloudflare network, which ends the encrypted connection, so it has technical access to the content of requests (see Sub-processors).
  2. Separation of club data. Each Club has its own subdomain, and every database query made through the application data layer is limited to the Club from which the request came. A separate guard stops the operation when a record of another Club gets into memory.
  3. Access by roles. A coach sees only the athletes of its groups, and a parent sees only its own children. Only the management can see the PESEL number, the full date of birth, the address and health information. We record every revealing of this data, every download of a contract scan and every data export in the register. Contract scans are stored outside the server’s public directory, and only the management or a coach with the “Contract scans” permission can download them.
  4. Logging in. We store passwords only as a one-way hash. The system requires a strong password. After 5 failed login attempts, logging in is suspended for 15 minutes. Two-step verification (a code from an app and backup codes) may be enabled by anyone, and the management may require it from staff and management members. A session expires after 2 hours of inactivity. Changing the password or the e-mail address invalidates remembered logins.
  5. Protection of forms. Actions in the panel require a CSRF token, and requests from foreign websites are rejected.
  6. Encryption of secrets. We store the Club’s payment gateway keys and the two-step verification secrets in encrypted form.
  7. Backup copies. We make backup copies of the database so that data can be restored after a failure. Only authorised persons have access to them. Deleted data disappears from the copies in the cycle of their overwriting (we give the length of that cycle to the Club on request).
  8. Access of our staff. The operator panel requires a separate role and two-step verification. Entering a Club’s account requires giving a reason, and the entry is recorded. In this mode, PESEL numbers, addresses and health information are not visible, and data export, password changes and payment key changes are blocked.
  9. AI assistant. It works only after the Club enables it. Before a question is sent to the model, the system replaces first and last names, telephone numbers, e-mail addresses and dates of birth with codes, and the table of codes stays on our server. The system blocks a question in which it detects a PESEL number, an account number or health information of a specific person.
  10. Retention in the system. The Club may anonymise the data of former athletes and of processed declarations. We review conversations with the AI assistant once a week: conversations without activity for 30 days are deleted, and from conversations still in use we delete messages older than 30 days. The content of questions saved for quality control is deleted after 90 days, and the journal of actions performed by the assistant at a user’s request (what it changed, and the state before and after the change) after 24 months. Entries of the Club’s event journal (§ 2(3), point 9) are deleted no later than after 25 months.
  11. Updates. We install security patches for the system and its libraries on an ongoing basis.

Changes in the version of November 4, 2026

  • Version 2.1: amendments before entry into force. Seat of JCD.PL according to the KRS register. The limit of liability is the higher of two amounts: the fees paid over 12 months or the fixed amount in § 8(3); it covers the Club’s recourse claims under Art. 82(5) GDPR and liability for sub-processors, and does not cover intentional damage (§ 8(3)). A narrower release from third-party claims, without administrative fines (§ 8(4)). Statistics only on the Club’s instruction (§ 2(8)). The Club’s event journal is included in the export and deleted together with the Club’s data (§ 2(3), point 9; § 7). Z.ai and the “Janusz” chat: basis for the transfer under consideration (§ 4(4), § 2(7)). A change of the Agreement binds the Club only from its acceptance in the panel (§ 9(1)). More precise deletion periods for AI assistant data (Annex No. 1, point 10).
  • A new structure of the Agreement (§ 1–9) and simpler language. The earlier provisions on the obligations under Art. 28(3) GDPR remain (§ 3).
  • § 1(2): the acceptance register also records the role in the Club, the name of the Club, the time in UTC with seconds, the browser, the language and the SHA-256 hash of the accepted version.
  • § 2: a fuller list of persons and data, according to what SportDesk actually processes (including children, PESEL, the shop, fundraising, equipment and bank statements).
  • § 2(6): health data described explicitly: which fields, that the Club has the basis under Art. 9(2) GDPR, and which additional safeguards we apply.
  • § 2(7): our own purposes, for which we are the controller (including the acceptance register kept for the limitation period of claims, and the “Janusz” help chat).
  • § 4: the list of sub-processors on a separate page (formerly Annex No. 2). Changes are announced in the panel 14 days in advance. An objection with reasons, and, if no agreement is reached, termination of the agreement without fees and a refund for the unused period.
  • § 5: the time limit for notifying a breach is 48 hours from establishing it (it was 36 hours).
  • § 7: data is deleted no later than 30 days after the 30-day period for export. Health information is provided on request, separately.
  • § 8: liability of both parties under Art. 82 GDPR, a common limit with § 10 of the Terms, reimbursement by the Club (Art. 82(5) GDPR), and release from third-party claims resulting from the Club’s actions.
  • § 9: changes are announced by a message in the panel (without an e-mail).
  • Annex No. 1, point 7: backup copies are described in general terms. We removed the details about the time of making copies, their encryption and where they are kept.
  • Annex No. 1: added measures that work in the system (blocking after failed logins, session expiry, protection of forms, operator mode, the AI assistant using codes instead of data).

Regional notice: United States, Canada, United Kingdom and Ireland

This notice is general information for Clubs outside Poland. It does not change the Polish version, the terms of this Agreement or the governing law in the Terms, it is not a statement that SportDesk or the Club complies with any particular law, and it has not been reviewed by a lawyer. The binding additional terms for Clubs outside the European Economic Area are set out in the document Terms for Customers Outside the EEA.

  • GDPR Art. 28. This Agreement is built on Art. 28 of the GDPR, which requires a written contract (which may be in electronic form) between a controller and a processor. For Clubs in Ireland, the EU GDPR applies together with the Irish Data Protection Act 2018; for Clubs in the United Kingdom, the UK GDPR applies, with its own processor-contract requirements. The Club, as the controller, should check whether this Agreement meets the requirements that apply to it and whether additional terms are needed for transfers of data out of the United Kingdom.
  • United States. US privacy laws, such as the California Consumer Privacy Act as amended by the California Privacy Rights Act (CCPA/CPRA), use the terms “business” and “service provider”, not “controller” and “processor”, and may require a contract with specific terms. The terms that apply to Clubs in the United States are set out in section R.2 of Terms for Customers Outside the EEA. The Processor does not sell the Personal Data. Under the Children’s Online Privacy Protection Rule (COPPA), operators of online services directed to children under 13, or with actual knowledge that they collect personal information from them, need verifiable parental consent. In SportDesk, accounts are created by the Club or by a parent or guardian; athletes under 13 do not have their own accounts. The Club is responsible for its parental consents and for the notices it gives to families.
  • Canada. Under the federal Personal Information Protection and Electronic Documents Act (PIPEDA), the fair information principles include accountability and apply to private-sector organizations handling personal information in commercial activities; how they apply to a Club’s use of a service provider is a question for the Club’s counsel. Provincial laws may also apply.

Sources (accessed November 3, 2026):

Questions about this document? Write to [email protected]. Other documents: Terms of service · Data processing agreement · Privacy policy.