PADELWEAR TRACKER / Privacy

Privacy Policy

Version 1.13 — 19 November 2026.

This policy covers PadelWear Tracker on Android, Wear OS, iPhone and Apple Watch, its connected services and padelweartracker.com.

We do not sell your data.

iPhone and Apple Watch

On iPhone you can also use Sign in with Apple. Firebase uses the Apple account identifier for the app and the name or email address that Apple provides. You may choose an Apple relay email address. Deleting your PadelWear account leaves your Apple Account intact.

With your permission, Apple Watch uses HealthKit to record a padel workout and available heart rate, steps, distance and energy. The watch transfers match data to the paired iPhone. Saving health data to your private cloud backup requires a separate choice. Raw motion recordings stay on your devices. Calculated shot statistics can be included in your private backup and are subject to the sharing rules below.

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 you sign in, signed-in Community members can see synchronised match recaps on your profile, including the players, teams, scores, progression, points and decisive moments. Live scores and some bookings can also be visible to signed-in members. Following a player does not limit the audience. A member can forward a link to another signed-in member.

“Automatically publish in the feed” controls whether future saved matches are also added to the Community feed. For a new account on Android, this option is preselected before you confirm. On iPhone it starts turned off when there is no saved choice. You can change it under My account → Privacy. The app records the choice when you save the match. Turning it off leaves profile recaps and existing feed entries visible. Turning it on applies to future matches.

Advanced statistics remain available to this audience for 48 hours from the original match end. 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.

After each author personally accepts this notice, their derived shot counts may be shared individually, independently of whether their teammate has a watch. This applies to each of the four confirmed players across both teams. The Detected shots tile, including counts per game and set and the player summary (total, winners and unforced errors), is visible to signed-in Community members for 48 hours after the original match end, even with only one usable recording. Afterwards, the recorder and currently confirmed players retain access. Shared views identify players by name. When two confirmed teammates have compatible saved recordings, their shares use only games fully recorded by both watches. Missing data is not reconstructed. Late synchronization does not restart the window. Heart rate, calories, distance and raw recordings remain personal. Removing a player or deleting either recording revokes their individual data and related comparisons when the change reaches the server. Explicit image export is a separate sharing action.

Private backups, original photos and current health data are restricted to the account holder. When you save a profile picture, a small thumbnail is visible by default to other signed-in Community members, including for an existing picture after you acknowledge this notice. There is no separate photo-sharing setting. Older publications containing personal recording data are restricted until converted to this policy. Access expiry deletes neither the match nor copies made by others.

Providers and transfers

Google provides Google sign-in and Firebase account, storage and sharing services. Apple provides Sign in with Apple on iPhone. 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.

On iPhone, Google Sign-In may use your IP address to estimate your general location for fraud prevention. The Google and Firebase components used for sign-in and cloud storage can process identifiers, sign-in activity and technical diagnostics to operate, secure and evaluate those services.

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.

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.

Technical diagnostics and compatibility

On Android, the “Share technical diagnostics” setting, under Account → Privacy, is enabled by default and can be turned off at any time without losing functionality. It supports maintenance, reliability and watch compatibility. Versions with uploads disabled retain this choice without transmitting a report. The iPhone app does not send these watch diagnostics reports.

When uploads and sharing are enabled, the report contains the watch manufacturer and model, watch system and app versions, the phone app version and build number, available or enabled features, their permissions and technical sensor-delivery summaries, including sampling frequency and data gaps. This sharing excludes health measurements, match data, location, serial numbers and raw sensor data. Diagnostics are not used to train artificial intelligence.

Reports are linked to your account and stored in Firebase. Access is limited to you and authorised maintenance staff. Only the latest report for the selected watch is retained, without a history. Changes are transmitted at most once every 24 hours. Turning sharing off stops new uploads and deletes the stored report once the app can reconnect. Deleting the account also deletes this report.

Usage measurement

The app does not collect usage statistics with Google Analytics. It includes no advertising or Crashlytics.

Security monitoring

For proportionate security investigations, temporarily activated server audit logs can record authenticated account identifiers and authentication claims, IP addresses, document paths, request times and outcomes. This collection covers qualifying service traffic during the investigation and relies on legitimate interests in protecting the service (Article 6(1)(f)). Access is restricted to authorised operators. Suspensions are reviewed manually; no account is banned automatically.

Retention and deletion

Audit logs activated for our security investigations have one-day retention and private incident/action reports are kept only as necessary for the investigation and applicable obligations. These periods do not replace providers’ separate lawful retention.

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 on the phone removes it from that phone and from your account (server backup and publications); the copy on the watch is not deleted and can be deleted from the watch history. Deleting a match on the watch removes only the watch copy. PC exports remain separate. Deleting the cloud account removes its backups, publications, profile, Community data and PadelWear authentication. Your Google or Apple account, local matches and watch or PC copies remain. 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.