Privacy and analytics.
FairwayBooker collects the information needed to check course fit, configure authorized tee time booking attempts, run the account workflow, and understand which public pages and product actions are useful.
Information FairwayBooker handles
Public course-fit forms may collect reply email, course name, membership context, booking URL, and setup notes. Account pages handle course login details, booking preferences, scheduled jobs, booking status, and result evidence needed to operate the service.
Stripe handles subscription checkout and billing. FairwayBooker stores billing status references such as subscription state and Stripe IDs, not raw card numbers.
Google Analytics
Public pages may send anonymous page views and declared CTA events to Google Analytics. Logged-in app pages may also send a pseudonymous FairwayBooker user ID, account provider, account type, event name, and event label.
Browser analytics events are intentionally limited. They do not send raw course passwords, payment card details, full form field values, raw usernames, or raw email addresses.
Service providers
FairwayBooker may use Google Analytics for measurement, Stripe for checkout and billing, email delivery for course-fit and support messages, and web push infrastructure for optional booking notifications.
Course booking systems are contacted only as needed for setup, availability checks, booking attempts, and result verification using the account permissions you provide.
Choices and contact
You can avoid public analytics by using browser-level blocking tools. You can cancel billing through the app billing flow when available, and you can contact FairwayBooker about account or data questions.
Questions: contact@fairwaybooker.com