Privacy and analytics.

Information FairwayBooker handles

Public course-fit forms may collect an email address, course name, membership context, booking URL, and setup notes. A free FairwayBooker account stores your email and a hashed FairwayBooker password so you can sign in and resume setup across devices. Your FairwayBooker password is separate from your course password. Password recovery uses a time-limited link sent to your account email.

Booking-plan drafts contain your selected course, date, time range, group size and any player names you enter. Before you create an account, a draft is kept in your browser session; after signup, it can be saved to your account. Connecting a course account separately verifies your course login. Account pages handle those course credentials, booking preferences, scheduled booking attempts, 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 pseudonymous page views and button-click events to Google Analytics. A short source label records which FairwayBooker page led to a fit check without changing the visitor’s original traffic source. If an account is created from a campaign link, FairwayBooker may keep the source, medium, campaign, content, and FairwayBooker CTA-origin labels with the account and include those labels in Stripe checkout metadata when the account later subscribes. Advertising click IDs are not attached to the account or sent to Stripe. FairwayBooker may retain Google Analytics client and session IDs so a verified account creation, valid course-fit submission, checkout start, or confirmed Stripe purchase is counted once. Logged-in app pages may also send a pseudonymous FairwayBooker user ID, account provider, account type, event name, and event label.

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.

Bug reports and optional diagnostics

When you submit an in-app bug report, FairwayBooker stores the description you choose to provide and links it to your account so support can investigate. Do not include passwords, payment details, or other sensitive information in the description.

You can choose whether to include technical diagnostics. Collection starts only while the report is open and the option remains selected. The diagnostics are limited to the current route without query parameters, viewport size, browser family, error types and script locations, and app actions that FairwayBooker explicitly tags for diagnostics. They do not include form values, visible page text, console messages, stack traces, or a screenshot.

Bug reports and their optional diagnostics are retained for up to 30 days, then deleted automatically. Support summaries expose only the information needed to investigate the report.

Choices and contact

Browser-level blocking tools can limit page and CTA analytics. If you submit an accepted course-fit request or complete Stripe checkout, FairwayBooker may still report that conversion from the server without sending your raw email address or form text. You can cancel billing through the app billing flow when available, and you can contact FairwayBooker about account or data questions.

Course credentials remain encrypted while the account needs them for authorized automation. To close an account or request deletion of stored course credentials and associated personal data, email the address below from the account contact email. FairwayBooker will verify the request, disable pending automation, remove credentials and data that are no longer legally or operationally required, and confirm completion. Limited billing, security, or transaction records may be retained where required for fraud prevention, accounting, dispute handling, or law.

Questions: contact@fairwaybooker.com