Privacy policy for Turnierklar

1. Controller

NorthProfit UG (haftungsbeschränkt)
Waldnieler Straße 28
40549 Düsseldorf
Germany

Email: kontakt@northprofitstudio.de

2. Data on your device

The app stores this content in an encrypted database on your device:

• tournament name, date and format
• teams (name, short name, colour) and groups
• fields and schedule (for leagues, the matchdays with date and kick-off)
• matches and results
• assigned event passes
• your settings
• reminders per tournament (whether and when)

The key is stored in the device’s protected storage (Keychain or Android Keystore). Without an account and without a live score, we don’t receive this content.

The app creates PDF and CSV exports and the calendar file (“Share date”) on your device. You decide yourself where you share or store them.

From version 2.1.5, the app optionally asks during setup what you are organising (club youth tournament, company or hobby tournament, or school sports). Your answer stays on the device and only determines which notes the Pro screen shows. You can skip the question.

From version 2.2.7, the app suggests your own default from your recent tournaments, for example for match length, breaks or start. Whether you accept it or keep the previous one is remembered only on the device.

3. Permissions

Turnierklar doesn’t request camera, microphone, location or contacts. The app only displays QR codes; they are scanned with another camera app.

The app asks for permission to send notifications only when you turn on reminders for a tournament or accept the reminder before the trial ends. The app schedules reminders before kick-off and before the rounds, for a league before the next three matchdays, on your device. In the same way, on tournament day it shows “Now / Up next” on the Lock Screen (iPhone: Live Activity, Android: notification). We use no push service for this and transfer no data. You can withdraw the permission at any time in your device settings.

Reminder before the trial ends. When you start the free trial of the annual subscription, the app explains that it can remind you two days before the trial ends. After you tap “Continue”, your phone asks for permission to send notifications; only if you agree does the app schedule the reminder and tell you the date. The reminder is a local notification: it is scheduled only on your device, and we transfer no data for it. If you cancel or the trial ends, the app removes it again. The app reads the end of the trial from the purchase data that runs through Apple or Google and RevenueCat anyway (see “Purchases”).

4. Optional account (from version 2.0)

The account is optional. It is used for

• backing up your tournaments,
• a second device,
• helpers
• and unlocking Pro on your devices.

You sign in without a password. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR).

• With Apple (Apple Distribution International Ltd., Ireland):
  We receive a signed confirmation from Apple with an identifier that applies only to Turnierklar, and your email address. If you wish, this is a relay address (“Hide My Email”).
  We also exchange a one-time code for a token and store it encrypted. We use it to revoke the sign-in with Apple at Apple when you delete your account.
  On Android, “Continue with Apple” opens Apple’s sign-in page in the browser. Apple sends the result directly to our server.
• With Google (Google Ireland Limited, Ireland): we receive a signed confirmation with your Google identifier for Turnierklar and your verified email address.
• With an email code:
  We send you a six-digit code (section 5).
  It is valid for 15 minutes and allows at most five attempts.
  We store it only as a checksum.

We don’t request names, profile pictures or contacts. The respective provider learns that you are signing in to Turnierklar; its privacy notices also apply.

For the account we store:

• a random account ID and your email address
• the sign-in methods with their identifier
• the times of creation and last sign-in
• the version of the accepted terms of use
• your sessions: device type (iOS, Android or web) and times, sign-in tokens only as a checksum

You link further sign-in methods under “More” → “Account”. Methods are linked only if you have confirmed both yourself, never just because the email address is the same.

For subscriptions, the app logs in to RevenueCat with your account ID. This is a random identifier, not an email address. This way Pro applies on all devices on which you are signed in.

Under “More” → “Account” you export your account data including backed-up tournaments (JSON) and delete the account. Without the app, you delete it at apps.northprofit.eu/turnierklar/en/delete-account/ (section 13).

5. Sending emails

• We send codes for signing in, adding an email address and deleting the account via Amazon Simple Email Service (Amazon SES) of Amazon Web Services EMEA SARL, 38 Avenue John F. Kennedy, L-1855 Luxembourg. Amazon Web Services acts as our processor (data processing agreement under Art. 28 GDPR).
• Sending runs via the AWS region EU (Frankfurt). Amazon SES receives your email address, the content of the email with the code and technical delivery information, such as the time and whether the email arrived.
• We measure neither opens nor clicks. The emails contain no tracking pixels and don’t load images.
• If an address is permanently undeliverable or someone complains about an email, Amazon SES reports this to us and the address is put on a suppression list to which we no longer send anything. We use these reports only to secure delivery. On request, we remove an address from the suppression list.
• Where data may reach the USA, the transfer is based on the European Commission’s adequacy decision for the EU-U.S. Data Privacy Framework, under which Amazon Web Services, Inc. is certified. In addition, the EU standard contractual clauses apply (Art. 45 and 46 GDPR).
• The legal basis for sending the codes is Art. 6(1)(b) GDPR. For the suppression list and delivery reports it is Art. 6(1)(f) GDPR; our legitimate interest is reliable delivery without abuse.

Proof of delivery. Since 9 October 2026, Amazon SES reports to our own administration system via the notification service Amazon SNS (also Amazon Web Services EMEA SARL, AWS region Frankfurt) whether an email was sent, delivered or delayed, whether it could not be delivered or whether someone complained about it. There we store the recipient address, sender, subject, delivery status, time and the technical ID of the email. We make sequences of three or more digits and long character strings unrecognisable in the subject, so codes don’t appear there; we don’t store the content of the email. The administration system runs on our own server at STRATO GmbH in Germany; we delete the entries after 30 days. The purpose is to prove delivery and to be able to help you with support requests. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is demonstrably reliable delivery.

6. Backup and second device

With an account, the app backs up your tournaments in your account. This way they are kept when you change devices, lose a device or reinstall, and are the same on your devices.

Backed up are:

• name, date, format and settings of the tournament
• teams (name, short name, colour), groups, fields and schedule
• matches with results and decisions
• the link to a live score
• an assigned Event Pass: product, purchase ID and time of purchase

For every change we store the time, a version number and whether it came from one of your devices, a helper or the server.

The backup is stored on our server in Germany (section 11). It isn’t end-to-end encrypted because the server has to read the score for helpers, the live page and the projector. The transfer is encrypted, and so are the backup copies.

If you delete a tournament, we remove its content from the backup immediately. An empty deletion marker (identifier and time) remains so that your other devices apply the deletion.

The legal basis is the performance of the contract (Art. 6(1)(b) GDPR).

7. Live score, projector and “My team”

Only if you choose “Publish live score” does the app transfer this content to our server:

• tournament name, date and format
• teams (name, short name, colour)
• groups, fields and schedule
• matches and results

Spectators open the score via a random link or QR code, also as a projector view for the hall.

• A separate admin code allows changes; we store it only as a checksum.
• With an account, the live score belongs to your account and is updated from the backup.
• The pages fetch the latest score from our server about every ten seconds, without cookies and without tracking.

If a spectator chooses “My team”, their browser remembers the choice for this live score in local storage.

• This serves only the display, because they explicitly want it.
• We don’t link the choice to a person.
• It can be deleted via the browser’s website data.

You can delete a live score in the app at any time. Otherwise we delete it automatically 90 days after the last update. The legal basis is Art. 6(1)(b) GDPR.

8. Helpers

With an account and Pro or an Event Pass, you invite helpers who enter results.

• The invitation via link or QR code contains a random code; we store only its checksum.
• We also store the chosen fields and the expiry: the end of the day after the tournament (for a league: after the last matchday), at least 24 hours.
• You can revoke an invitation at any time; this takes effect immediately.

Helpers don’t need an account.

• When they start on a device, we store a device token (only as a checksum), the device type (iPhone, iPad, Android or browser) and the start and last use.
• In the app you see on how many devices an invitation is used and when it was last used.
• In the browser, the helper form sets a technically necessary cookie, only for this invitation and only until it expires.

Helpers only enter results.

• We log every entry: which match, before and after, time and which helper device.
• This lets you check entries and undo them if necessary.
• We delete the log after 90 days. We delete invitations and helper devices 30 days after expiry.

Legal bases:

• for you as the organiser, the performance of the contract (Art. 6(1)(b) GDPR)
• for the helper devices, our legitimate interest in secure, traceable result entry (Art. 6(1)(f) GDPR)

9. Purchases, Event Pass and RevenueCat

Monthly and annual subscriptions and event passes are processed via the Apple App Store or Google Play.

• For the offer, purchase verification, unlocking Pro and restoring, we use RevenueCat, Inc.
• RevenueCat processes a random app-specific identifier or, if you are signed in, your account ID. In addition, product ID, platform, store environment and purchase status. Version 2.2.2 also sends the paywall group (e.g. hart_v1 for new installations, otherwise bestand) in order to evaluate purchases by version of the paywall (legitimate interest, Art. 6(1)(f) GDPR). From version 2.2.3, this happens only with your consent to product analytics (Art. 6(1)(a) GDPR, Section 25(1) TDDDG); if you decline or withdraw it, the app deletes the group at RevenueCat.
• We don’t send any functional app content, names, email addresses or advertising IDs to RevenueCat.

An Event Pass applies to exactly one tournament. To prevent it from being assigned twice, the app reports the assignment to our server.

• We store an irreversible check value of the purchase ID, the product and the random tournament ID. We don’t store names, email addresses or accounts in the process.
• Our server can verify the purchase with RevenueCat. For this, it queries the purchases for your RevenueCat identifier and compares the purchase ID on the server.
• It also checks Pro before you invite helpers.

The legal basis is the performance of the contract (Art. 6(1)(b) GDPR). In addition, the privacy policies of Apple, Google and RevenueCat apply.

10. Operational counters and optional product analytics

Operational counters without an identifier. Release versions explicitly built for production send limited counting events to our own server, for example:

• app and session start, full active minutes, moving to the background
• onboarding
• start and completion of a core function or an export
• display and result of a system prompt (for example for notifications)
• calling up the rating prompt of the App Store or Google Play (from version 2.1.5)
• a notice of a new version (a quiet notice or the full-screen “Please update”) and whether the App Store or Google Play was opened from it (from version 2.2.11)

From version 2.2.7, the operational counters also count the steps of a purchase: opening the Pro screen, start, completion, cancellation and errors of a purchase and restoring, each only as an event type. This doesn’t tell us which plan or price was chosen or who bought. This lets us see, even without your consent, whether the Pro screen and purchasing work. Up to version 2.1.1 the operational counters counted these steps in the same way, from version 2.1.2 to 2.2.6 only with your consent.

Each report contains only:

• the contract version and a one-time retry ID
• the official app ID and channel: store version, review device (App Review, TestFlight, Google’s review devices) or simulator or emulator; only store versions on real devices go into our statistics
• platform, app version, build and event type

It contains no user, account, installation, session, advertising or device identifier and no functional app content. The server stores daily aggregates. The retry ID only prevents double counting; the server stores it as a hash and deletes it after eight days. The purpose is checking function and stability (Art. 6(1)(f) GDPR).

So that review and test installations (such as Apple’s or Google’s app review) don’t count as usage, the app marks such reports. For this it reads on the device only a system setting (Android) or the file name of the purchase receipt (iOS); from version 2.2.1 it also checks the installation source on Android and counts only installations from Google Play as a store version. Only the marking is transferred.

Error and crash reports, setup. If an error occurs in the app or it crashes, it sends our server, without an identifier, only the error name (such as “TypeError”) and the affected place as a machine word (such as “create” for the tournament planner), plus app version, build, platform and channel (store or test version). After a crash it sends the report immediately; it keeps it until the next launch only if you have agreed to usage statistics. During the first setup, the app also counts without an identifier which steps were shown, completed or skipped (onboarding, question about usage statistics, first schedule), with a rough duration class. From version 2.2.5: if you leave the planner during the first setup without creating a tournament, you can optionally tap a reason (such as “My tournament isn’t fixed yet”). Only your answer and the step are sent, plus app version, build, platform and channel, immediately and without a device, user or installation identifier; nothing is stored on the device. If you close the question without answering, nothing is sent. Error messages, stack traces, app content and device, user or installation identifiers are not transferred. The IP address is not stored; the server summarises the counters daily. The purpose is checking function and stability (Art. 6(1)(f) GDPR). If you have agreed to usage statistics, product analytics also counts the setup steps shown.

Optional product analytics. Only after your explicit consent do we measure app-specific active installations, sessions, screen changes and strictly limited function steps. From version 2.1.2, these also include the steps of a purchase: opening the Pro screen, start, completion and cancellation of a purchase and restoring. From version 2.1.5, the version of the Pro screen and your answer to the onboarding question as a fixed value (such as “School sports”) are added. Without consent, from version 2.2.7 we count the purchase steps only as operational counters without an identifier (see above), and the other steps not at all. We learn about purchases, trial periods and renewals themselves independently of this via the App Store, Google Play and our billing service RevenueCat (see the section on purchases). From version 2.2.3, your consent also covers the paywall group at our billing service RevenueCat (see section 9). From version 2.2.11, for the update notices, which of the two notices appeared is added.

• The app generates a random installation identifier that applies only to Turnierklar, and changing session identifiers.
• The server stores the installation identifier only as a project-specific one-way hash. It is not linked to your account.
• Your functional app content, names, email addresses, advertising or device IDs or free texts are never transferred.
• You can withdraw your consent under “More” → “Privacy & analytics”. The transfer then stops and the app requests the deletion of the associated event history.
• Regular retention: at most 180 days.
• The legal basis is Art. 6(1)(a) GDPR.

Turnierklar contains no advertising, no cross-app tracking and no advertising, attribution or analytics SDK from other providers.

11. Server, backup copies and protection against abuse

• The account, backup, helpers, pass assignments and live scores run on our own server at STRATO GmbH in Germany.
• The database is backed up daily in encrypted form and kept for 30 days. An additionally encrypted copy is stored at Hetzner Online GmbH in Germany.
• Data processing agreements exist or apply with both providers (Art. 28 GDPR).
• The service doesn’t log individual requests. To ward off abuse, it counts requests per IP address only briefly in memory, for a few minutes and as a hash (Art. 6(1)(f) GDPR).

12. Support, content reports and website

Support. If you contact us, we process your message and contact details to handle it (Art. 6(1)(b) or (f) GDPR). Please don’t send sensitive app content.

Content reports. Every live page contains a reporting function.

• For a report, we store the random live code, the chosen reason for the report, an optional note and the processing status.
• The live score concerned is blocked until it has been reviewed.
• We delete reports 180 days after receipt.

Website. When you visit the website, the server processes technically necessary connection data for secure delivery and to limit abuse. We don’t set marketing cookies.

Notice of new versions. From version 2.2.11, on launch the app asks our server apps.northprofit.eu for the current and the minimum required version number in order to point out updates: after a successful request at most once a day; if the request fails, for example without a connection, it tries again at the next launch. No identifiers, no cookies and no tournament data are transferred; the server processes the IP address only for delivery (Art. 6(1)(f) GDPR). On the device the app stores only the retrieved version numbers, the time of the last request and for which version it has already shown the notice (Section 25(2) No. 2 TDDDG).

Measuring the reach of this website. We measure how this website is used ourselves, without Google Analytics or other third parties. Without your consent we measure without measurement cookies and without storing anything on your device for measurement: pages viewed, the name of the referring website, campaign parameters from the address and clicks on our download buttons and on links to the App Store, Google Play and other websites, each without content. From the information your browser sends anyway, we derive device type, browser, operating system and language in broad categories, and from the IP address on receipt the country, region and city. From the IP address and browser identifier we form, with a key that is newly generated each day and held only in memory, an identifier that stays the same only for that day; only its hash value is stored, never the IP address. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is improving the pages based on aggregated usage figures. The live pages at apps.northprofit.eu/turnierklar/live/ with projector view, reporting function and helper form are delivered by our Turnierklar service; we don’t measure reach there.

With your consent we also set our own cookies: “__Host-np_vid” with a random visitor ID for 12 months and “__Host-np_sid” for the session for 30 minutes. This lets us recognise returning visits. We then also record scroll depth, active time, page load times and a broad screen size class. The legal basis is your consent under Section 25(1) TDDDG and Art. 6(1)(a) GDPR.

We store your choice in “Privacy settings”, including a refusal, for 12 months in the cookie “__Host-np_consent”; this is necessary so that we respect it (Section 25(2) No. 2 TDDDG). As long as you don’t make a choice, we store nothing. Via “Privacy settings” at the end of every page you can withdraw your consent at any time or switch measurement off completely; we then delete the measurement cookies and the measurement data stored with your visitor ID. If your browser sends the “Global Privacy Control” signal, we don’t measure at all. We store the measurement data in our access-protected NorthProfit Cockpit on servers of STRATO GmbH in Germany and delete it after 180 days. We determine the location on our own server with the database IP Geolocation by DB-IP (opens in a new tab) (licence CC BY 4.0).

Deletion page. On the page for deleting the account, we process the email address you enter in order to send you the confirmation code (section 5). It belongs to our account service and contains no reach measurement.

Feature board: On apps.northprofit.eu/turnierklar/wuensche/ you can suggest features for Turnierklar and vote for other people’s suggestions. We store the suggestions you submit (title, optional details, language) in our NorthProfit Cockpit on servers of STRATO in Germany. So that each device can vote only once, the page stores a random device key in your browser’s local storage; the Cockpit receives it only as an irreversible check value (hash), together with your votes. We don’t store names, email or IP addresses for this; the IP address is used only briefly in memory to limit abuse. Suggestions appear only after our review and without reference to you (Art. 6(1)(f) GDPR). You can delete the device key via your browser’s website data.

13. Storage period and deletion

• On the device: until you delete the data or the app.
• Account:
  until you delete it
  Sessions end after 180 days without use. We remove ended or expired sessions 30 days later.
  We delete email codes one day after they expire.
• Backup: until you delete the tournament or the account.
• Live scores: until you delete them, at the latest 90 days after the last update. Reports: 180 days.
• Helpers: invitations and helper devices 30 days after expiry, the log after 90 days.
• Pass assignments: three years after assignment (regular limitation period).
• Server backup copies: 30 days.
• Deleting the account:
  in the app under “More” → “Account” → “Delete account” or without the app at apps.northprofit.eu/turnierklar/en/delete-account/
  We immediately delete the account, sign-in methods, sessions, the backup, helper invitations with their log and the live scores of your account. A reported live score remains until the review is complete.
  We revoke a sign-in with Apple at Apple. We delete the token stored for this after the revocation, at the latest after 30 days.
  The tournaments on your devices are kept. You cancel a subscription in your store.
• Purchases: store transactions are subject to the rules of Apple or Google. For a RevenueCat privacy request, you can send the privacy ID shown in the app to support@northprofitstudio.de.

14. Your rights

Subject to the legal requirements, you have the right to access, rectification, erasure, restriction, data portability and objection. You can take your tournaments with you at any time as PDF or CSV, with an account also as an account export. Contact: kontakt@northprofitstudio.de. Competent supervisory authority: Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen.

15. Changes

We update this policy when features, service providers or legal requirements change.