PICKLEBALL ADVENTURES
Privacy and data practices
Implementation summary ยท September 2026
Pickleball Adventures uses account information and trip information to provide authenticated departure, booking, readiness, itinerary, announcement, clinic, and account settings features.
Information used by the app
- Email and authentication-session data used for email OTP sign-in and sign-out.
- Traveler profile, readiness, booking, departure, itinerary, and announcement data.
- Payment, refund, accounting, and operational records needed to preserve transaction history.
- Notification preferences and delivery state for supported trip communications.
- Selected trip state stored locally on the device so supported offline views can work.
Deletion and retention boundary
Account deletion removes or anonymizes active account and private profile data, revokes sessions and access, and clears local account state. Booking, payment, refund, accounting, immutable event, and security records may remain in anonymized or detached form when needed to preserve business, operational, or legal integrity. The implementation does not define a fixed legal retention period.
Services and permissions
The current source audit found no analytics or crash-reporting SDK and no account-owned upload flow. Network access is used for the authenticated service boundary. The app does not require broad external-storage access for its supported workflow.
This page is an evidence-based implementation summary, not a substitute for the owner-approved legal privacy notice required for store publication.