Privacy

Privacy notice

This notice explains what Fairway Live handles for clubs, societies, organisers, golfers and spectators, and how that information is used.

Last updated: 22 September 2026

Who is responsible

Nyle Challinor trading as Fairway Live provides Fairway Live and is responsible for the account, enquiry, billing, support and service records it controls.

When a club or society enters player names, playing handicaps, groups, teams and scores, that club or society decides what is entered and who receives scoring or spectator links. Fairway Live stores and processes that competition information to provide the service to that club or society.

Information handled by Fairway Live
  • Account details: organiser email addresses, sign-in records, organisation names, membership roles and the active club or society chosen in the browser.
  • Enquiries: name, email address, club or society name, estimated player count, event date, message, enquiry source and an anti-spam request key made from the request details.
  • Competition data: event names, dates, course names, hole pars and stroke indexes, player names, competition playing handicaps, roster entries, team or group assignments, match pairings and player status such as picked up, no return or disqualified.
  • Scores and results: stroke entries, picked-up or cleared holes, Ryder Cup-style hole outcomes, final results snapshots, exports and score-change history.
  • Scoring and spectator links: private link records, whether a link is active or revoked, the linked player, match or group, public leaderboard status, creation details and last-opened timestamps.
  • Invitations: invited organiser email address, society name, invitation expiry, acceptance, revocation and email-delivery status.
  • Billing references: plan, payment status, renewal date, cancellation-at-period-end status, payment-event references, provider customer/subscription/payment identifiers and refund records where a refund is processed. Card details are handled by the payment provider and are not stored by Fairway Live.
  • Support and audit records: support session organisation, platform-admin user, read-only or editing state, reason for enabling support editing, timestamps, affected records and recorded changes.
Why it is used and lawful bases
  • Providing the service: creating accounts, saving competitions, opening scoring links, calculating leaderboards, finalising results and keeping exports available. This is needed to perform the service contract with organisers and clubs or societies.
  • Responding to enquiries: replying to messages and pilot requests. This is a legitimate interest in answering requested contact, and may also be steps before a contract.
  • Payments and account records: confirming cover, preventing duplicate purchases, recording renewals, cancellations, failed payments and refunds. This is needed for contract administration, legal obligations and legitimate interests in preventing payment errors.
  • Security and support: checking who may view or change an organisation, restricting private links, recording support access and keeping audit logs. This is a legitimate interest in protecting the service and customer records.

Consent is not currently used as the main basis for running competitions in the app. If a club or society needs player consent or another notice for its own event, it is responsible for collecting and providing that.

Who can see competition and link data
  • Owners and organisers of the owning club or society can see and manage that organisation's events.
  • Members can have view-only access where their organisation grants it.
  • A host club can see hosted visiting-society rounds but does not get write access to the society's event.
  • A golfer scoring link shows the event, course card and only the assigned player, match or group needed for that link. It does not show account details or emails.
  • A spectator leaderboard link is read only. Anyone who has that link can see player names, teams and results; it does not show email addresses, account details or scoring links.
  • Fairway Live support access is limited to platform support sessions and is recorded in audit logs. Support editing requires a reason.
Browser storage and cookies checked for this implementation

The app uses browser storage so the service can remember the signed-in session, selected organisation, fictional demo competitions, pending invitation, scoring-link hole position, cached scoring card and pending offline score or match-result entries. Offline entries stay on that device until they are synced, rejected, overwritten or the device storage is cleared.

Fairway Live does not add advertising cookies or an analytics cookie. A sidebar preference cookie exists in the shared interface library but is not used by the current Fairway Live screens. The payment form and managed account services may use their own cookies or storage when their screens are opened.

Suppliers and transfers

Fairway Live uses Lovable Cloud for hosting, database, authentication and managed email, and Stripe for checkout, billing and payment-event records. Email invitations are sent through the managed Fairway Live email setup.

Lovable's published privacy and data-processing documents state that app builders are responsible for data people submit to their apps, and that Lovable processes customer personal data on the customer's instructions while also using service, log, aggregated and de-identified data for analytics, security, billing and product development. Lovable's public subprocessor page points to its Trust Center for the full subprocessor list.

Stripe's published privacy materials state that Stripe may act as a processor and controller depending on the activity, uses service providers, subprocessors and affiliates, and relies on transfer mechanisms including the Data Privacy Framework, EU Standard Contractual Clauses and the UK International Data Transfer Addendum where applicable.

Stripe Payments UK Ltd is the payment provider for United Kingdom accounts. Stripe's published documentation states that records needed for accounting, tax and anti-fraud purposes are kept for several years to meet legal obligations, and that United Kingdom transfers rely on the International Data Transfer Addendum, including its extension to the EU-US Data Privacy Framework where relevant.

The exact data-centre locations used for this app and each supplier's full subprocessor list are published and maintained by the suppliers rather than set by Fairway Live. They can be confirmed on request.

Retention

Competition records, final results, billing references, payment-event records and audit logs are kept while they are needed to provide the service, maintain historical results and exports, resolve disputes, meet legal or accounting needs and protect the service. Account and competition records are kept for the active life of the club or society unless deletion is requested. There is no fixed automatic deletion date for historical results.

Invitation links expire after 7 days. Support sessions expire after 4 hours, though audit records of support access and changes are retained. Browser-stored demo data and offline entries remain on the device until the app updates or clears them, or the user clears browser storage.

Your rights

You can ask to access, correct, erase, restrict or receive a copy of your personal data, and you can object to certain processing. Some requests may need to be handled by the club or society that controls the relevant player data. Contact hello@fairwaylive.co.uk.

You can complain to the UK Information Commissioner's Office at ico.org.uk. If your concern relates to competition data entered by a club or society, you may also need to contact that club or society.

Related pages

See the Terms and Refunds & Cancellation pages for service and payment information.