Privacy policy

Who is responsible

The controller under the GDPR is REPLACE-BEFORE-SUBMIT (name, address, legal form).

Contact for data protection questions: REPLACE-BEFORE-SUBMIT (email address).

A data protection officer is REPLACE-BEFORE-SUBMIT (appointed / not appointed, with contact details if appointed).

What the app stores

Match data: the format, the date, every point you count as an event, the names you enter for the players, plus surface, occasion and your own note about the match. Names are free text. What goes in there is your decision.

Account data: your email address. It is needed to sign in and comes from our authentication provider (see below). There is no password; signing in uses a code sent by email.

Technical sync data: a random identifier for this device and the position this device last synced to. The identifier is generated inside the app and is not a device fingerprint.

Consent: when you confirm that you are a parent or legal guardian, that is stored with a timestamp. A withdrawal is stored with a timestamp as well.

Requests to the server produce connection data for technical reasons (IP address, time, requested path). It is processed to run the service and to protect it from overload.

Without an account

Without an account, match data never leaves the device. Scoring, history and export all work offline.

The first sign-in needs an internet connection once. After that the app keeps working offline.

Where the data is

On the device, in a local database only the app reads.

On the server, in a PostgreSQL database in the EU. Host and location: REPLACE-BEFORE-SUBMIT (provider, data centre region, data processing agreement).

Purposes and legal bases

Account and sync: performance of the contract, Art. 6(1)(b) GDPR. In the published build the app cannot start without an account, because backing up the matches is part of what is offered.

Uploading match data that belongs to a child: your consent as a parent or legal guardian, Art. 6(1)(a) together with Art. 8 GDPR. Until you confirm, everything stays on the device.

Protecting the servers from overload and abuse: legitimate interest, Art. 6(1)(f) GDPR.

Who else processes the data

Authentication: Clerk, Inc., USA. Clerk processes the email address and the sign-in code as a processor. Basis for the transfer to the USA and status of the data processing agreement: REPLACE-BEFORE-SUBMIT.

Hosting of the database and the API: REPLACE-BEFORE-SUBMIT (provider, location, data processing agreement).

There are no other recipients. The data is not sold, not traded and not passed to advertising networks.

The website waitlist

On the website you can leave your email address to hear when the app is in the stores. That is the only purpose.

What is stored: the address, the language you entered it in, how far the confirmation has got, two random strings for the confirmation and unsubscribe links, and the times of the signup, the confirmation and the unsubscribe. No name, no IP address, no browser, no referrer.

The legal basis is your consent, Art. 6(1)(a) GDPR, taken as a double opt-in: after the signup one email goes out with a confirmation link, and the address is on the list only once you click it. The confirmation link lasts seven days and works exactly once.

You can leave at any time through the link at the bottom of every email. That is the withdrawal under Art. 7(3) GDPR and the deletion at the same time: the entry is marked as unsubscribed and receives nothing further.

The address stays until you unsubscribe or the list is no longer needed, at the latest once the app has been released and the message has gone out.

A service provider will send the emails. Provider, location and data processing agreement: REPLACE-BEFORE-SUBMIT. In the current build no provider is configured: addresses are stored and nothing is sent.

The waitlist has nothing to do with an account in the app. It is a separate record with no link to matches or to an account, which is also why deleting your account in the app does not remove it. The unsubscribe link is the way to do that.

Crash reports

This build of the app has no crash reporting enabled.

If it is enabled, the reports contain no names, no notes and no match content. The app logs only a fixed list of technical fields, and that is covered by tests.

What the app does not do

No advertising, no ad SDKs, no third-party trackers.

No profiling, no automated decision-making, no sale of data.

No AI models trained on your data.

No public leaderboards and no public discoverability of players.

How long the data stays

Match data stays until you delete it. A deleted match disappears from the server too, not only from the device.

If you delete your account, the account, the matches and their events are deleted. They leave the backups with the backup retention period, within 30 days at the latest.

The record of consent and withdrawal is deleted with the account.

Children

The app is built for a parent recording a child’s matches. The account belongs to the adult, and that person confirms before the first upload that they are a parent or legal guardian.

You can withdraw that confirmation in settings at any time. Nothing new is uploaded afterwards. Matches already backed up stay until you delete them.

Children have no public visibility in the app. There is no people search and no leaderboard.

Your rights

You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and objection (Art. 21).

Two of them are built into the app and cost nothing: exporting every match as JSON and as CSV, and deleting your account with all its data.

You can withdraw consent at any time with effect for the future, Art. 7(3) GDPR.

You can complain to a data protection supervisory authority, Art. 77 GDPR. Competent authority: REPLACE-BEFORE-SUBMIT (depends on where the controller is based).

Changes

If this policy changes, the date at the end changes. If a change affects your consent, the app asks again afterwards.