Credential and payment boundaries ยท
Public fit checks stay separate from account credentials.
The public course-fit and checkout pages ask for course context, not a course password. Credentials are handled only in authenticated setup flows when a supported account must be verified.
Credentials at rest
Stored booking-provider passwords are encrypted with dedicated credential-encryption material. Production configuration requires a sufficiently strong credential key that is separate from the application session secret.
Bounded account use
A supported run uses the golfer's authorized account and the booking details they configured. Unsupported course, membership, or portal behavior stops the normal setup path.
Payments
Stripe hosts checkout and billing management. FairwayBooker keeps billing status references and Stripe identifiers, not raw payment-card numbers.
Sessions and transport
Production sessions use secure, HTTP-only cookies and the site is served over HTTPS. State-changing forms use request-forgery protection.
Report a concern
Do not email a course password. Contact FairwayBooker with the affected page, time, and a non-sensitive description so the issue can be investigated safely.