PICKLETOUR separates operational tournament data, temporary Court Control relay data and optional shared performance statistics. The current build adds account-isolated cross-device operational sync, explicit deletion controls and performed-match-only statistics sharing.
The product does not treat tournament records as analytics. Operational data is used to run and synchronize the organizer's event. Court Control relay data exists to deliver live court workflows. Optional shared statistics are a separate reduced dataset.
Players, divisions, schedules, results, court layouts, templates and relevant settings are stored for the organizer's workflow. In the web build, the signed-in account can synchronize this operational state through PickleTour Cloud so the same working data is available on another device. It is not published as shared analytics.
The cloud operational copy is isolated by the authenticated PickleTour account. It is used only to provide the signed-in organizer's cross-device service. The Settings page includes manual sync and deletion of the account's cloud operational copy.
While Court Control is active, the relay temporarily holds the match state required by paired official devices. Stopping the network clears the live match snapshot in this build.
Disabled by default. If enabled in Settings, only genuinely started, completed, non-test tournament statistics with real timing data are eligible. Names, event names and division names are not included in the shared analytics payload.
In the application Settings, organizers can enable or disable performed-statistics sharing, clear the downloaded statistics cache and delete statistics contributed by the signed-in account from the shared statistics store.
No central statistics identity or upload is started until the organizer enables sharing.
Drafts, test runs, simulated matches and completed matches without real start/end timing are excluded from shared statistics.
Shared records contain format, counts and relative match-duration data needed for prediction calibration — not player names, contact details, event titles or division titles.
The current Cloudflare/D1 paths use separate retention rules for operational sync, shared statistics and Court Control relay data.
Operational sync data is retained while it remains active for the signed-in account, with a 24-month inactivity cap in this build. The organizer can delete the cloud copy earlier from Settings. The browser's Export Data function can export the current account state.
Privacy-reduced performed-match analytics are retained for up to 24 months, then opportunistically removed. A signed-in organizer can delete their own contributed rows earlier from Settings.
The cloud operational copy is isolated by the authenticated PickleTour account. It is used only to provide the signed-in organizer's cross-device service. The Settings page includes manual sync and deletion of the account's cloud operational copy.
Stopping Court Control clears the live match snapshot immediately. Queued actions are removed on stop; stale actions are retained no longer than 7 days, event relay history 30 days, and paired device records 30 days.
The shipped build has no GA4 Measurement ID and no custom analytics endpoint configured. If analytics are enabled later, the controller should assess GDPR and ePrivacy requirements before deployment.
For access, correction, deletion or other privacy questions relating to PICKLETOUR, contact info@pickle-tour.com. Tournament organizers remain responsible for the personal data they collect and the lawful basis for using it.