Privacy
Last updated: 17 November 2026
This notice tells you which personal data TKDR (Taekwondo Registration) processes, why, who receives it and what rights you have. It applies to the platform at tkdr.eu and tkdr.de. This English version is a translation; the German version prevails.
1. Controller
Benjamin Güntner
Boxau 12
91604 Flachslanden
Germany
E-mail: [email protected]
We have not appointed a data protection officer because there is no legal obligation to do so. For all questions about data protection, write to [email protected].
2. Who is responsible for what
TKDR passes entries between clubs and organisers. This results in three roles:
- We (the operator) are responsible for the platform: accounts, storage, sending e-mails and everything published on TKDR.
- The club enters the data of its athletes and officials and enters them for tournaments. It is responsible for being allowed to enter this data and obtains the consent of the athletes itself, for minors that of the parents or guardians.
- The organiser receives the entries for its tournament and is itself responsible for their further use (running the tournament, its tournament software, its own notices and publications, entry fees). The organiser is named on the tournament page.
3. Which data we process
- Account: first and last name, e-mail address, language, time zone, optionally a phone number; the password only as a non-reversible hash; with passkeys the public key; with two-step sign-in the encrypted secret and recovery codes as hashes; a list of your signed-in devices (browser identifier, IP address, last use); your roles (club, organiser, athlete account, admin).
- Club: name, country, town, state association, members with roles.
- Athletes: first and last name, date of birth, sex, grade, optionally photo, Global Athlete Licence, DTU database number and weight; e-mail address of the athlete and, for minors, name and e-mail address of a parent or guardian.
- Officials (coaches, trainers, team staff etc.): name, function, e-mail address, optionally licence numbers (ETU, WT, DTU, state association) and DTU database number.
- Entries: tournament, age class, performance class and weight class, start number, status of the entry, waiting list, entry fee, payment request and payment status, accreditation card, fight numbers, weigh-in result, results and placings, certificates and pass entries.
- Payment receipts: in the entry mode "buy start places in advance" the club uploads a bank transfer receipt. It may contain names, account details and amounts.
- Documents: signed consent forms and arbitration agreements with a record (see section 8) and uploaded scans of paper signatures.
- Requests to us (tickets) and e-mails we send.
- Technical data with every request (see section 10).
4. Purposes and legal bases
- Account, club management, entering, payment requests, accreditation cards, lists and results for club and athlete: performance of the contract of use (Art. 6 (1) (b) GDPR).
- Data of athletes and officials entered by a club, and passing it to the organiser: legitimate interest of club, organiser and athlete in taking part in the tournament (Art. 6 (1) (f) GDPR); in addition the club obtains the consent of the athletes or their parents or guardians.
- Publication of participants, lists and results (section 5): legitimate interest in a transparent competitive sport with public start and result lists (Art. 6 (1) (f) GDPR), based on the consent the club obtains.
- Signatures with a record: proof of who signed what and when (Art. 6 (1) (b) and (f) GDPR).
- Security, protection against abuse, action log, backups: legitimate interest in secure operation (Art. 6 (1) (f) GDPR).
- Legal obligations, for example information to authorities: Art. 6 (1) (c) GDPR.
5. What is public
Once an athlete is entered for a tournament, the following becomes visible to everyone on TKDR, each as soon as it exists or the organiser publishes it:
- full first and last name, also of minors, with club, country of the club, class and start number;
- fight numbers and path through the bracket, the live display per court (bout, score) and the lists the organiser publishes (for example pool lists and schedule);
- results, placings and the organiser's result files;
- the verification page of a pass entry (/verify, reached through the QR code of the label) with name, tournament, date, class, place and organiser.
Not public are date of birth, e-mail addresses, photo, weight and weigh-in result, documents, payment receipts and payment status. Public pages can be found by search engines. Results stay public permanently as a tournament archive (see section 13).
6. Who receives data
- The organiser of a tournament receives the entry data for its tournament: athletes with date of birth, sex, grade, classes, licence numbers and photo (for the accreditation card), officials, the club and the contact details of the person who entered, and the status of payments and documents. It can download them, import them into its tournament software (for example TaekoPlan) and fetch them through an interface.
- The club sees the data of its own athletes and officials. An athlete account sees only its own data or that of its own children.
- Hosting and sending e-mail: netcup GmbH, Daimlerstraße 25, 76185 Karlsruhe, Germany. Server and mailbox are located in Germany. netcup works on our behalf (processor under Art. 28 GDPR).
- Protection and delivery of the site: Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA. All requests pass through Cloudflare; Cloudflare processes your IP address and the technical data of the request to fend off attacks and deliver the site quickly. Cloudflare works on our behalf (Art. 28 GDPR).
- Google (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland), only in two cases: when you use "Continue with Google" (section 7) and for encrypted backups in Google Drive (section 13).
- Anthropic, PBC, San Francisco, USA, only if the AI check of payment receipts is switched on (section 9).
- Authorities only if we are legally obliged.
We do not sell data, do not show advertising and do not pass on data for advertising.
7. Account, sign-in and "Continue with Google"
When you sign up you give your name and e-mail address. You are signed in only after you have set a password through the link in the e-mail and so confirmed your address. Athletes, parents or guardians and officials get their account when a club enters them with an e-mail address; they then receive an e-mail with a link to set their password.
Passkeys and two-step sign-in are optional; for platform admins two-step sign-in is mandatory. If you use "Continue with Google", Google tells us your name, your e-mail address and a fixed account number. We use them only to sign you in and to set up your account; we do not store any Google access tokens and do not get access to other Google data.
8. Documents and signatures
Consent forms and arbitration agreements are sent by e-mail to the athlete or the parents or guardians and signed online or on paper. With an online signature we store a record: version of the document with checksum, name, role and e-mail address of the signer, time, IP address, browser identifier and the image of the signature. A signed PDF is made from it. It can be seen by the signers, the club, the organiser of the tournament and, for central documents, the platform admin. Paper scans are checked by the platform admin or by an organiser for whose tournament the athlete is entered.
9. Payment receipts and AI check
TKDR does not accept money and does not process payments. When a club uploads a bank transfer receipt, TKDR checks it for plausibility (amount, payment reference, recipient, date). By default this happens on our own server. Optionally the check can use the AI interface of Anthropic (Claude); the receipt is then sent to Anthropic in the USA to be read. This AI check is only active if we have switched it on for the platform and the organiser has not switched it off for its tournament; the upload form says so. The decision is never made by the AI but by our own program code, and the organiser always confirms that the money has arrived. Receipts are seen only by the club and the organiser.
10. Server, logs and protection against abuse
With every request Cloudflare and our server process your IP address, time, requested address and browser identifier to deliver the site and protect it against attacks. Our program does not write IP addresses or personal links to its technical log. Important actions (signing in, entering, changes, actions of organisers and admins) are recorded with time, account and IP address in an action log. Against abuse we count sign-in attempts, sign-ups and e-mails per IP address and per e-mail address; these counters are deleted automatically after a short time.
11. Cookies
We only use cookies that are technically necessary:
- the session cookie while you are signed in (it ends after 12 hours without use, with "stay signed in" after 30 days); it contains only a random identifier, and the protection against forged forms (CSRF) is tied to this session;
- the cookie "lang" with the language you chose (1 year).
To protect against bots, Cloudflare may set its own technically necessary cookies. The legal basis is § 25 (2) no. 2 TDDDG. We use no analytics or advertising cookies, no tracking, and do not load external content such as fonts or maps; the fonts are on our server.
12. E-mails
We send e-mails that are part of using the platform: confirmation and password links, access e-mails, entry confirmations and payment requests, reminders, documents to sign, answers to requests and, on the tournament day, info e-mails about lists and changes. The info e-mails can be switched off. There is no newsletter.
13. How long we store data
At present we do not delete content automatically after a fixed period. Accounts, clubs, athletes, entries, results, payment receipts and signed documents remain stored until they are deleted: by yourself (athlete account, see section 14), at your request, or by us by hand when they are no longer needed. We check regularly whether stored data is still needed.
Results and placings remain permanently as a tournament archive. If an athlete is deleted, only class and place remain there, without a name.
Only technical data is deleted automatically: expired sessions, used or expired links and the counters against abuse. If an organiser replaces or withdraws a result file, the old file is deleted at once.
Backups of the database and the uploaded files are stored encrypted on our own storage and in Google Drive. Deleted data may remain in them until the backup concerned is replaced by a newer one. Statutory retention obligations remain unaffected.
14. Deleting an account
An athlete can delete their account themselves, for minors the parent or guardian: in "My area" under "My account", confirmed by an e-mail link and the password. The deletion takes effect at once. Immediately before, we store a backup of the data concerned that only the platform admin can access, so that an accidental or abusive deletion can be undone. Entries for upcoming tournaments are withdrawn; if the entry and late entry period is already over, the entry remains without a name.
Accounts of club members and organisers are deleted on request to [email protected]. A club can deactivate an athlete but cannot delete them; the athlete keeps access to their data. A stored e-mail address of an athlete is changed only by the platform admin on request, so that nobody else decides who sees the data of an often under-age athlete.
15. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection (Art. 21). You can withdraw consent at any time with effect for the future (Art. 7 (3)). Write to [email protected]. If your request concerns the use by an organiser or club, please contact them as well; we will help.
Right to object: where we process data on the basis of a legitimate interest (Art. 6 (1) (f) GDPR), you can object at any time on grounds relating to your particular situation. We will then no longer process the data unless there are compelling legitimate grounds or the data is needed for legal claims.
16. Complaint to the supervisory authority
You can lodge a complaint with a data protection supervisory authority. The authority responsible for us is the Bavarian State Office for Data Protection Supervision (Bayerisches Landesamt für Datenschutzaufsicht, BayLDA), Promenade 18, 91522 Ansbach, Germany, https://www.lda.bayern.de
17. Transfers to third countries
Cloudflare and Anthropic are based in the USA; with Google a transfer to the USA is possible. Cloudflare and Google are certified under the EU-US Data Privacy Framework, for which the EU Commission has found an adequate level of protection (Art. 45 GDPR). For Anthropic we base the transfer on the EU standard contractual clauses (Art. 46 GDPR) or on the Data Privacy Framework, as far as Anthropic is certified.
18. Minors
Many athletes are minors. Their data is entered by the club, their account is held by the parents or guardians (if a minor has their own e-mail address, they get access too). With the entry for a tournament the details from section 5 are published; the club obtains the consent of the parents or guardians for this beforehand.
19. Changes
We adapt this notice when the platform or the law changes. The version shown here applies.