CourtBeam Cookie Notice

1. What these technologies do

Cookies are small files saved by your browser. Session cookies ordinarily last for a browser session; persistent cookies remain until expiry or deletion. Browser local storage, session storage, authentication storage and mobile app storage can serve similar purposes. Third-party scripts, embedded content and mobile software libraries can also transmit information without setting a cookie. Removing cookies does not delete information already held on a server.

2. Authentication, security and preferences

• CourtBeam session and request security: courtbeam_session and courtbeam_csrf support authenticated sessions and protect applicable requests. The default session duration is five days, with a configurable maximum of fourteen days. Signing out clears the applicable session cookies. Firebase may also use authentication storage and verification technologies.
• Browser and device storage: authentication state, preferences, consent-version records, public club configuration and temporary booking state may be stored locally. Session storage is tied to the browser session; persistent site or device storage lasts until replaced, cleared or removed by the relevant feature. Clearing it may sign you out or reset preferences.
• Payments and fraud prevention: an enabled Stripe checkout or payment component may use provider cookies, device information and similar technologies to process payments and prevent fraud. These are governed by the provider's configuration and Stripe's privacy notice.

3. Website analytics and campaign attribution

On enabled website surfaces, Google Analytics measures pages, navigation, events and conversions using identifiers such as _ga and _ga_* cookies. These are persistent cookies whose expiry depends on Google's configuration and your browser; the actual expiry is visible in browser site-data settings. CourtBeam's website configuration disables Google Signals and ad-personalization signals, but still collects website measurement and campaign identifiers. That setting does not mean all collection is anonymous or disabled.

CourtBeam also uses courtbeam:first-touch-attribution in session storage to retain campaign parameters and referral context, and courtbeam-ga:* session markers to avoid duplicate conversion events. Campaign context may be passed between CourtBeam's marketing and signup sites and associated with demo or signup records. The cb_owner_first_touch cookie records limited owner-acquisition context across CourtBeam's own domains; it is a session cookie whose stored snapshot is treated as stale after 24 hours. This does not set a 24-hour deletion period for resulting server records.

Demo scheduling can use Calendly's embedded calendar and a session-scoped courtbeam:booking-id to connect a booking with its campaign context. An embedded calendar can receive network and browser information when loaded, before a booking is submitted.

4. Support, diagnostics and app usage

Help Scout's support widget can use browser storage and receive support messages and page/device context. Sentry receives error and diagnostic information where enabled. Provider cookies and storage depend on the enabled feature and provider settings. See Service Providers and Subprocessors.

CourtBeam's own player usage collection uses session and installation identifiers, platform and coarse screen activity; signed-in activity can be linked to an account for club reporting. This is distinct from website Google Analytics. Mobile apps also use authentication storage and push tokens. Disabling push permission does not disable usage reporting. Native player usage reporting currently has no in-app opt-out.

5. Available controls

• Use your browser's privacy settings to inspect, block or clear cookies and site storage. Blocking necessary storage may prevent sign-in, checkout or preferences from working.
• Google's Analytics opt-out browser add-on provides a provider-specific choice on supported browsers. It does not control CourtBeam's own reporting or every third-party service.
• CourtBeam's own player web usage collector and limited owner first-touch collection respect Global Privacy Control and Do Not Track. These signals are not currently a site-wide control for Google Analytics, all campaign handling, embedded calendars or support providers. Do not assume one signal stops every technology described here.
• Use device settings for push notifications and available app permissions. Clearing app storage or uninstalling an app does not delete your account or server-side records.
• Contact support@courtbeam.com to exercise applicable privacy rights or ask about measurement. Apply browser and device controls separately on each device you use.

CourtBeam does not currently provide a single cookie-preference dashboard across these services. This Notice and acceptance of the Terms are not consent to optional technologies. Where prior consent is legally required, optional technologies require that consent before use; describing a technology here does not remove that requirement.

6. Changes and contact

We update this Notice as practices change. For questions, contact PicklePro Tech LLC, operating as CourtBeam, at support@courtbeam.com or 1021 E Lincolnway STE 7756, Cheyenne, WY 82001, United States.