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.

A private course compatibility review may separately collect your course username, course password, usual group size, and permission to inspect the member portal. Both login fields are stored encrypted, outside booking accounts and schedules. This permission allows a read-only review of tee-time availability and existing reservations; it does not authorize making, changing, or cancelling bookings. The private intake page does not load analytics.

Stripe handles subscription checkout and billing. FairwayBooker stores billing status references such as subscription state and Stripe IDs, not raw card numbers.

Google Analytics

Analytics and advertising are optional and off until you choose to allow them. Essential cookies keep accounts, forms, payments, and bookings working and remember your privacy choices for up to 180 days. When you allow analytics, public pages may send pseudonymous page views and button-click events to Google Analytics. FairwayBooker retains labels supplied with course checks and requests in its own operational records, even when optional analytics is off. These records do not enable Google Analytics. A short action label records which FairwayBooker page led to a fit check.

With analytics permission, FairwayBooker also remembers the first recognized external source or campaign for up to 180 days from capture, using the existing privacy-choice record rather than another tracking cookie. Later internal links and campaigns do not replace that original source. Updating privacy preferences does not extend this source record’s expiry. The record contains bounded source, medium, campaign and content labels; it does not keep the full referring URL, query string, advertising click IDs, or raw contact details. When you create an account, those labels may become part of its operational history so FairwayBooker can connect acquisition with course connection, scheduling and payments. Source labels may also be included in Stripe checkout metadata when you subscribe. Withdrawing analytics permission clears the anonymous source record and stops its future reuse; labels already attached to account and transaction history remain subject to the account-data choices described below.

With advertising permission, Google may use advertising cookies and click IDs to measure ad results and personalize ads. 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

Use Cookie preferences at the bottom of any public or account page to accept, reject, or customize optional cookies for this browser. Analytics permission also governs server-side reporting of course-fit requests, account activity, and purchases to Google. Withdrawing permission stops future reporting tied to that choice and clears optional browser identifiers; it does not erase reports already sent. Browser-level blocking tools may further limit analytics. You can cancel billing through the app billing flow when available, and 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.

For a private compatibility review, access expires seven days after you share your login. Automatic cleanup removes the encrypted login fields from active storage after expiry. Revoking review access from the same browser removes them immediately; you can also request revocation by email. Invitation, permission, expiry, and access audit records remain for accountability. Older encrypted copies may remain in database backups until their normal backup lifecycle ends.

Questions: hello@fairwaybooker.com