Version 1.2 — 1 October 2026.
This policy covers PadelWear Tracker on Android and Wear OS, its connected services and padelweartracker.com.
Controller and contact
Data controller: Valentin Arnaud. Contact: support@padelweartracker.com.
Data and purposes
We process authorised Google account details (identifier, name, email, photo), your profile and Community connections, bookings and matches (dates, venues, players, scores, corrections, statistics), invitations and drafts. Data comes from you, your watch, other participants or your imports. Playtomic text is parsed locally; importing a Pista link contacts that service.
During a match, the watch can record accelerometer and gyroscope data for shot analysis, including with its screen off. Raw recordings stay on the watch and phone and can be exported to a PC; they are not sent to Firebase. Normal use does not collect a precise GPS route.
Available steps, heart rate, estimated calories and distance may be recorded after a separate health choice and required permissions. Private health backup needs another choice. Refusing this optional data leaves scorekeeping available. Accepting terms or granting a permission is not health consent.
Account, match and synchronisation data is needed to provide the service (GDPR Article 6(1)(b)). Security, support and proportionate histories involving other players rely on legitimate interests (Article 6(1)(f)), subject to their rights. Optional health processing relies on explicit consent (Articles 6(1)(a) and 9(2)(a)). Handling rights requests meets our legal obligations (Article 6(1)(c)).
Who can see data
After Google sign-in, some match information is automatically published to signed-in Community members: players, teams, scores, progression, points, decisive moments and some bookings. Live scores can appear before a match is saved. Following a player does not restrict this audience; a link can be forwarded to another signed-in member.
Advanced statistics remain available to this audience for 24 or 48 hours from the original match end, depending on the applicable policy; the older policy keeps 24 hours. Afterwards, only the recorder and confirmed players have access. Scores and basic recaps remain visible. Editing, importing or restoring a match does not extend this period.
Private backups, original photos and current health data are restricted to the account holder. A profile thumbnail is visible by explicit choice. Some unconverted older publications may still contain health data shared under earlier rules. Access expiry deletes neither the match nor copies made by others.
Providers and transfers
Google provides sign-in and Firebase account, storage and sharing services. The match database is in Zürich, Switzerland; authentication operates in the United States. Other processing may occur in other countries. Transfer terms and safeguards, including applicable standard contractual clauses, are available at https://firebase.google.com/terms/data-processing-terms or from support. Pista receives a request when you import one of its links.
Cloudflare hosts the website and processes IP addresses, browser details and requests needed to deliver and secure it through a global network. Its data protection and transfer terms are available at https://www.cloudflare.com/cloudflare-customer-dpa/. The site has no accounts, forms, advertising or third-party audience analytics. The app includes no advertising, Firebase Analytics or Crashlytics.
We receive information sent to support to answer your requests. Providers also process technical identifiers needed to operate and secure the service. Authorities may receive data required by law. Private records are protected by secure connections and authenticated access controls.
Retention and deletion
Accounts, histories and local recordings remain until deleted, subject to specific legal exceptions. Support requests are kept as needed to handle them and meet applicable obligations. Providers retain logs and backups for their own periods; Firebase states a maximum of 180 days to remove authentication data after user deletion.
Deleting a match starts its cleanup on the phone, watch and cloud; PC exports remain separate. Deleting the cloud account removes its backups, publications, profile, Community data and PadelWear authentication. It deletes neither your Google account nor local matches or watch/PC copies. A minimal record may remain to prevent restoration. Uninstalling does not delete the cloud account; clearing app data can delete local recordings.
Stopping health recording or backup does not delete earlier measurements. Delete the relevant match or account, or contact support to remove them. The Account deletion page explains the in-app and email procedures. Deletion cannot retract independent copies made by others; any lawful retention will be explained.
Your rights
Contact support to request access, correction, deletion, restriction, portability of eligible data or objection to processing based on legitimate interests. Guests without accounts can use the same contact. Requests are verified proportionately.
You can withdraw health consent in the relevant device settings without affecting earlier lawful processing. You can complain to the CNIL or another competent authority. We make no solely automated decisions with legal or similarly significant effects.
Accounts are for people aged 18 or over. Report data about minors or unwanted sharing to support. Material policy changes are brought to your attention; new optional purposes need their own choice where required by law.