Privacy Policy
Controller
Florian Winkler (RacketWatch)
Sömmeringstraße 63
50823 Cologne, Germany
Email: racketwatch@gmail.com
Hosting
This website is hosted with Google Firebase Hosting (Google Ireland Limited, Ireland). When you visit the site, the provider processes technically necessary access data (e.g. IP address, time, requested file) on the basis of Art. 6(1)(f) GDPR (legitimate interest in secure and stable operation).
Waitlist
If you join the waitlist, we store your email address, your platform preference (Android, iPhone / Apple Watch or both), the time and the source of the entry, in order to inform you about the app launch (Art. 6(1)(a) GDPR). The data is stored with Google Firebase (Firestore, EU region). It is not shared with third parties; for sending the launch information it is used exclusively for that purpose. You can request deletion at any time by email to racketwatch@gmail.com.
reCAPTCHA (waitlist)
To protect against abuse and spam, the waitlist form uses Google reCAPTCHA v3 via Firebase App Check (Google Ireland Limited, Ireland). reCAPTCHA is loaded only when you actually submit the form, not during a normal visit to the website. Data is transferred to Google, including to the USA — covered by the European Commission's adequacy decision on the EU-US Data Privacy Framework. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in preventing abuse). For further information, see Google's privacy policy at policies.google.com/privacy and Google's terms of service.
Cookies and tracking (website)
This website does not set cookies and does not use analytics or tracking services. This section refers to the website only — the apps use analytics and diagnostic services (see below).
The RacketWatch apps (Android phone & Wear OS watch)
Account and profile: when you create an account in the app, the app processes your email address and display name (Firebase Authentication, Google Ireland Limited, Ireland). In your profile you can additionally add a photo as well as a club and team. This data is used exclusively for your account, your community profile and the app's features (Art. 6(1)(b) GDPR — contract performance; for voluntary information additionally Art. 6(1)(a) — consent). Through the name search, any signed-in person can find you — regardless of whether your profile is public or private (the setting only controls follow confirmation and the visibility of match details, not findability); the search result shows only the name, profile picture and public status.
Matches, live scores and notifications: your own history stays on your devices. When you live-score a match, the score is stored in the cloud and shared with your confirmed followers in real time (Cloud Firestore, EU region); shared results and notifications are stored there too. Notifications (for example about running matches and results of your contacts) reach the devices via a push token (Firebase Cloud Messaging). You confirm every follow request — you decide who follows you (Art. 6(1)(b) GDPR).
Analytics and diagnostics: the apps use Firebase Analytics (usage statistics) and Firebase Crashlytics (crash reports) on the basis of Art. 6(1)(f) GDPR (legitimate interest in improving and stabilising the apps).
Deleting your data: you can delete your account yourself in the app at any time ("Delete account" in the account area) and confirm it with Google or your password. This submits the deletion request: your account is immediately invisible to others (search, profile, follower lists, feeds, live matches), no more notifications are delivered to you, and the app deletes this account's local data on the device — your matches and profiles; anything that only lived there is gone for good. Your Firebase account and the associated cloud data — profile, photo, the cloud backup of your matches, shared results, feed rows and follow connections — stay stored invisibly during the 30-day grace period and are permanently deleted afterwards. Until then you can restore the account by signing in to the app again and confirming the restore; the data then comes back from the cloud. Step-by-step instructions for both paths are on our Delete account page; the email path follows the same process. For further deletion or information requests, send a short email to racketwatch@gmail.com, unless statutory retention obligations prevent this.
Data of people without their own account
If someone plays with you who does not have their own RacketWatch account, their name is recorded in the match: as a freely entered name for an opponent or partner when creating a match, or as a guest name in a guest invite. These names are stored locally on the device of the person who entered them and additionally on our servers (Google Firebase/Firestore, EU region), because they are part of the cloud backup of the matches (since version 0.24.4). They are visible in the live ticker to confirmed followers and — with a public profile — to all signed-in users. The legal basis is Art. 6(1)(f) GDPR (legitimate interest): match history, stats and guest invites require the opponent to remain nameable. Since version 0.25.5 the app automatically creates a reusable profile for every entered name — the name is stored permanently, not only in the individual match. The persons concerned have the rights under Art. 15 and Art. 17 GDPR (access and erasure); please send requests to racketwatch@gmail.com.
Your rights
Under the GDPR you have the right to access, rectification and erasure of your data, as well as the right to lodge a complaint with a data protection supervisory authority. For this, contact racketwatch@gmail.com.