Data Processing Agreement
Last updated: 12 November 2026
This Data Processing Agreement (“DPA”) is part of the Terms of Service. It applies when an organizer uses GldComp to process personal data, as required by Article 28 of the General Data Protection Regulation (EU) 2016/679 (“GDPR”). An organizer accepts it when it accepts the Terms. No signature is necessary.
1. Parties and roles
- Controller: the organizer that creates a competition on GldComp (“Organizer”).
- Processor: Matej Plch, Czech Republic, operator of GldComp (“GldComp”). Contact: info (at) gldcomp.com.
2. Details of the processing
| Subject matter | Hosting and operation of the Organizer’s competition on GldComp |
| Duration | While the Organizer uses GldComp, plus the deletion period in section 9 |
| Nature and purpose | Storing, organizing, showing, publishing on the Organizer’s instruction, and sending emails, to run competition registration, administration and results |
| Data subjects | Pilots and co-pilots, crew, team captains, the Organizer’s staff and helpers, other people the Organizer enters |
| Categories of data | Name, email, phone, address, club, glider and device data (registration, competition number, Flarm and logger IDs), IGC ranking ID, flight logs (IGC files), entry and payment status, fields the Organizer adds to its forms, messages sent through GldComp |
| Special categories | None are expected. The Organizer must not collect them through GldComp |
3. Instructions
GldComp processes the data only on the Organizer’s documented instructions. These Terms, this DPA, and the Organizer’s settings and actions in GldComp are the instructions. If GldComp must process the data for another reason by EU or Czech law, it tells the Organizer first, unless the law prohibits this. GldComp tells the Organizer if it thinks an instruction breaks the GDPR.
4. Confidentiality
Only persons who need the data to operate GldComp have access. They are bound to confidentiality.
5. Security
GldComp uses appropriate technical and organizational measures (Art. 32 GDPR), including:
- hosting in data centers in the EU;
- TLS encryption for all connections, including those to the database;
- the database on a private network that is not reachable from the internet;
- sign-in with passkeys for admins and single-use email links for pilots; sessions expire;
- role-based access, so each admin sees only the competitions they manage;
- logs of access and errors.
6. Subprocessors
The Organizer gives general authorization to use subprocessors. GldComp uses these:
| Subprocessor | Purpose | Location of data |
|---|---|---|
| Hetzner Online GmbH | Servers and database | Germany |
| Scaleway SAS | File storage and transactional email | France |
| Redis Ltd. (Redis Cloud on Google Cloud) | Background job queue | Germany |
| Better Stack, Inc. | Logs, error reports, uptime monitoring | EU (Germany) |
| Cloudflare, Inc. | Bot protection on the sign-up page (Turnstile) | Global network; USA |
| Netlify, Inc. | Website gldcomp.com and its contact form | USA |
GldComp has a data processing agreement with each subprocessor with the same data protection duties as this DPA. Transfers to the USA rely on the EU-US Data Privacy Framework or the EU Standard Contractual Clauses.
GldComp announces a new subprocessor on this page before it starts. An Organizer can object for a valid data protection reason within that period by writing to info (at) gldcomp.com. If the parties do not find a solution, the Organizer can stop using GldComp.
Integrations that the Organizer turns on (for example Soaringspot, Glide and Seek or PureTrack) are not subprocessors. They receive data because the Organizer instructs it.
7. Help to the Organizer
GldComp helps the Organizer, as far as it can, to:
- answer requests from data subjects (access, correction, deletion and others). Most of these the Organizer can do itself in the admin interface. GldComp forwards to the Organizer every request it receives about a competition;
- meet its duties on security, breach notification, impact assessments and consultation with the supervisory authority (Art. 32 to 36 GDPR).
8. Personal data breaches
GldComp tells the Organizer without undue delay after it becomes aware of a personal data breach that affects the Organizer’s data. It gives the information that the Organizer needs to meet its own duties.
9. Deletion at the end
When the Organizer stops using GldComp, GldComp deletes the Organizer’s personal data, unless the law requires GldComp to keep it. Copies in backups are deleted when the backups expire. The Organizer can export its data before that, for example the competitor list.
10. Audits
GldComp gives the Organizer the information needed to show that it meets this DPA. Write to info (at) gldcomp.com. The parties agree on any audit beyond this in advance, with reasonable notice and at most once a year. The Organizer pays its own costs.
11. Liability and law
The liability rules of the Terms of Service apply, unless the GDPR requires otherwise. Czech law applies. If this DPA and the Terms conflict on data protection, this DPA wins.