Sub-processors
Last updated: 20 August 2026
A sub-processor is a company Fareway engages to help deliver the Services, and which may handle personal information in the course of doing so. This page is the current list referred to in Section A.5 of the Fareway Hub Terms.
Fareway imposes data-protection obligations on each sub-processor no less protective than those in the Data Processing Annex, and remains responsible for their performance. We keep this page up to date. An Operator may object to a sub-processor on reasonable data-protection grounds, as described in Section A.5.
Sub-processors that handle Customer Data
These providers may handle golfer and operator information submitted to or generated by the Fareway platform.
| Sub-processor | What it does for Fareway | Information it may handle |
|---|---|---|
| Microsoft Corporation (Microsoft Azure) | Hosting, application database, file and image storage, message queues, content delivery, secret storage, and application telemetry | All Customer Data stored in the platform |
| Okta, Inc. (Auth0) | Account sign-in and identity for golfers and operators | Name, email address, phone number, authentication events |
| Stripe, Inc. | Payment processing for registration fees, entry fees, and payouts | Name, email address, billing details, payment and payout records |
| Twilio Inc. | Text (SMS) messages to golfers and operators | Phone number, message content |
| MailerSend | Transactional email — registration confirmations, reminders, receipts, and account notices | Name, email address, message content |
| Google LLC (Firebase Cloud Messaging) | Delivery of push notifications to mobile devices | Device push token, notification content |
| Apple Inc. (Apple Push Notification service) | Delivery of push notifications to iOS devices | Device push token, notification content |
| Google LLC (Google Maps Platform) | Venue address lookup and geocoding | Venue and course addresses and search terms entered by an operator |
| OpenAI, L.L.C. | Reading scores from a scorecard photo submitted by a user | The submitted scorecard image and the scores read from it |
| Functional Software, Inc. (Sentry) | Error and crash monitoring across the app, web, and backend | Account identifier, device and diagnostic data, and any personal information incidentally present in an error report |
| Catamorphic Co. (LaunchDarkly) | Feature flag management | Account identifier and attributes used to target a feature |
| Slack Technologies, LLC (Salesforce, Inc.) | Routing in-product feedback, submitted photos, and operational alerts to the Fareway team | Account identifier and the content a user submits with feedback |
Providers used for the Fareway website
These providers support fareway.golf and Fareway’s own sales and marketing contacts. They do not handle Customer Data from the platform.
| Provider | What it does for Fareway | Information it may handle |
|---|---|---|
| Vercel Inc. | Hosting of fareway.golf | Website request data |
| Google LLC (Google Sheets) | Record of contact and demo requests submitted on the website | Name, email address, and the message submitted |
| Resend | Notifying the Fareway team that a website enquiry has arrived | Name, email address, and the message submitted |
Changes to this list
We keep this page up to date as our sub-processors change.
We do not email everyone when it changes, but you can ask us to tell you. Leave your email address in the form below this page and we will send you a note whenever this list changes — before the new sub-processor starts handling data, so you can raise it while it still matters. You can stop at any time by replying to one of those notes.
If you have a question about anything here, or an objection to a sub-processor on data-protection grounds, write to us at hello@fareway.golf.
Tell me when this list changes
We do not email everyone when a sub-processor changes. We will email you when the sub-processor list on this page changes, before the new sub-processor starts handling data. Reply to any of those emails to stop.