Who we are
ForeLeft is a buddies golf trip app published by ForeLeft, LLC (New Jersey). This Privacy Policy describes personal information we collect when you use the ForeLeft mobile apps (iOS and Android), the web app at https://www.foreleft.golf, and our API.
Contact / privacy requests: help@foreleft.golf. Publisher: ForeLeft, LLC.
Information you provide
Depending on how you use ForeLeft, you may provide:
- Account details: name, email address, and password (stored as a hash). If you use Sign in with Apple, we receive an Apple-provided identifier and, when Apple shares them, your name and email (which may be a private relay address). If you use Continue with Google, Google shares your Google account identifier, name, email address (and whether Google has verified it), and profile photo URL; we use them only to create or sign in to your ForeLeft account, and if your Google email matches an existing ForeLeft account we link the two. We do not receive your Google password or access to your Google data beyond that basic profile.
- Profile details: handicap index and optional profile image.
- Trip content you and your crew enter: trip names and locations (free text), roster/buddy-group membership, lodging guest names and confirmation numbers, dinner reservation addresses and confirmation numbers, packing lists, schedule items, and similar trip-planning data.
- Scores and competition data: hole-by-hole strokes, match formats, awards, team assignments, and related scorekeeping metadata.
- Messages: group chat and direct messages, including message text and reactions.
- Side bets: bet names, types, stake amounts, participants, and a settlement ledger that tracks who owes whom. Side bets are tracking-only — ForeLeft does not transfer money, process wager payments, or move funds between users.
- Support communications you send to us by email.
Information collected automatically
- Session and security data: session tokens, and (for sessions) approximate IP address and user agent, used to keep you signed in and for account/admin security activity.
- Device location: with your permission, GPS coordinates used for live yardages on the course map and optional trip “presence” (approximate location shared with trip members while you use Live features).
- Push notification tokens: Expo push tokens and platform, so we can send trip and chat notifications you enable.
- Purchase records: when you unlock a trip, we store payment provider, external transaction id, amount, and related verification payload. On the web we use Stripe Checkout; on iOS/Android we use Apple App Store / Google Play in-app purchase for the trip unlock product.
- Website visits: on foreleft.golf we count anonymous, cookieless page views and clicks to improve the site, with no personal data and no cross-site tracking. We don't count browsers that send Do Not Track or Global Privacy Control.
How we use information
- Provide and operate ForeLeft (accounts, trips, scoring, chat, live presence, notifications).
- Process trip unlock payments and verify App Store / Play / Stripe transactions.
- Send transactional email such as password-reset messages.
- Maintain security, prevent abuse, and support account deletion and admin tools.
- Respond to support requests.
We do not sell your personal information. We do not use third-party product analytics SDKs (such as Segment, Mixpanel, Amplitude, Firebase Analytics, Sentry, or PostHog) in the ForeLeft apps today.
Third parties and service providers
We use service providers to run the product. They process data on our behalf or as independent payment platforms:
- Hosting and database: Render (API, Postgres, static web hosting).
- Authentication: Better Auth on our API; optional Sign in with Apple (Apple Inc.); optional Continue with Google (Google LLC, Google Identity Services on the web and the Google Sign-In SDK in the apps).
- Email delivery: Resend (password-reset and similar transactional email).
- Payments: Stripe (web trip unlock); Apple and Google (native in-app purchase verification).
- Maps: Apple Maps on iOS; Google Maps on Android when a Maps API key is configured (map tiles / location display).
- Push delivery: Expo / platform push services (APNs, FCM).
- Course data: GolfCore and OpenGolfAPI / OpenGolf open data used for course catalogs, tees, and scorecard helpers. We send them course names and locations only, not your account data.
- AI itinerary reading: OpenAI, only when you agree before an itinerary import (see “AI itinerary reading” below).
AI itinerary reading
When you import a resort itinerary (an uploaded PDF, saved email, or text file, or a pasted email), ForeLeft can use OpenAI, an outside AI service, to pick out tee times, lodging, and dinner reservations. We send OpenAI the text of that itinerary only after you agree in the app. We ask before your first import, and again if we ever switch AI providers.
- What is sent: the text of the itinerary you import, which can include course names, dates, tee times, lodging and dinner reservations, guest names, and confirmation numbers. We don't send your password, payment details, location, scores, chat messages, or other trips.
- How OpenAI handles it: under OpenAI's API terms, the text is not used to train OpenAI's models. OpenAI may keep it for up to 30 days to monitor for abuse, then deletes it. We ask OpenAI not to store the response.
- What ForeLeft keeps: we read your file in memory and don't store the file or its full text. We save only the trip details you review and confirm (for example tee times and lodging rows).
- Your choice: if you say no, imports still work with our built-in reader, and nothing is sent to OpenAI. You can withdraw consent at any time by emailing us or from the import screen.
Location
Location access is used for golf yardages and optional live trip presence with other members of your trip. You can deny or revoke location permission in system settings; yardage and presence features that need GPS will not work without it. Presence locations are stored with the trip while the feature is used.
Side bets (no money movement)
ForeLeft’s side-bet and settlement features are for tracking wagers and IOUs among buddies. The app does not collect bank or card details for side bets, does not escrow funds, and does not transfer money. Any payment of a side bet happens outside ForeLeft.
Retention and account deletion
You delete your account from Settings after you sign in, on the web app and in the iOS and Android apps. The public page at /delete-account explains the steps and what data is removed; it does not delete an account by itself. Deletion removes your sign-in credentials, profile fields we store for you, push tokens, live location records tied to you, and your memberships where applicable. Some crew-facing content may be retained in anonymized or redacted form so remaining members keep a usable trip history (for example, messages replaced with a removed-message placeholder, and side-bet ledger rows re-labeled as a deleted member).
Children
ForeLeft is not directed to children under 13, and we do not knowingly collect personal information from children under 13.
Your choices
- Update your name and handicap in Settings.
- Control location and notification permissions in your device settings.
- Delete your account from Settings after you sign in, as described above.
- Email us at help@foreleft.golf to ask questions about this policy or your data.
Changes
We may update this policy as the product evolves. The “Last updated” date at the top of the in-app page reflects the current version. Material changes will be reflected in the app and on the web routes /privacy and /terms.