Your information.

Community submissions

When you submit an event, business listing, or news item, we store your name, email, and the details you provide so an editor can review the submission. Your contact name and email are kept in the private review area and are not included in public listing data.

Approved listing details, including any phone number or website you choose to include, can appear publicly. Do not include personal or sensitive information in listing descriptions. A hashed request address is stored to help limit spam.

Golfer profiles & open rounds

Creating a golfer profile is optional and free. Your chosen name appears publicly as the host of a round or as an accepted player. Full golfer profiles, including age, profile photo, self-reported Handicap Index, usual courses, availability, playing preferences, and introduction, are visible only to signed-in golfers. Your date of birth is stored privately to calculate your age and is returned only to your own profile settings. Your optional phone number is shared only with you and accepted Playing Partners; it is removed from their view when the connection is removed. Playing Partner requests require acceptance from both golfers. The signed-in Profile page may suggest golfers based only on accepted mutual Playing Partners, ranked by their count. Suggestions do not use contact uploads, location, course preferences, or activity outside this site, and they do not create connections automatically. Profile photos are stored separately, available only to signed-in golfers, and stripped of embedded location metadata. Junior profiles for ages 13–17 remain unavailable to other golfers and cannot use community actions until a parent or guardian approves using the specified verified email account. We store the guardian email, approval name, account identifier, and approval timestamp. Profiles are available to ages 13 and older. We store an internal sign-in identifier to connect your profile, rounds, and requests. Your sign-in email is not published.

Hosts can add confirmed site members, named guests, and placeholders directly to an outing. Each occupies a player spot, including the organizer. Guest and placeholder labels are visible to signed-in golfers. Members added by a host see the outing in their Games tab. Round listings, including course, date, tee time, cost notes, and round notes, can be public. Keep phone numbers, email addresses, and booking confirmation numbers out of these fields. Join-request notes are visible only to the requester and the host; accepted golfers appear in the round roster with their chosen profiles. Hosts manage requests, and editors may remove inappropriate listings. In-app notifications alert you to partner requests, join replies, roster changes, outing changes, published pairings, and cancellations. Notifications are private to the recipient account. Check the Games tab in Profile for current details; email and phone push notifications are not enabled. Organizers may invite accepted Playing Partners to an outing. Invitation messages and replies are visible only to the organizer and each invitee. Invitations do not reserve spots; accepting fills an available spot, and unanswered invitations close when the outing fills or closes. Push is optional and enabled separately on each device. We store a browser push subscription endpoint associated with your profile and a device cookie. Your browser’s push provider handles delivery. Push alerts contain a short event summary, such as an invitation or tee-time change, without private messages or contact details. Opening an alert takes you to your signed-in inbox. Turning push off or signing out removes this browser’s saved subscription; other devices keep their own settings.

To request profile removal or a correction, use the correction form below and identify your profile or round. We may verify ownership before changing it.

Accounts & external websites

The public guide does not require an account when public access is enabled. Golfer accounts use Firebase Authentication with email/password or Google sign-in. Email accounts must verify their email address before using community features. Firebase stores account credentials and manages sign-in; this website stores a protected session cookie. Editor access separately uses ChatGPT sign-in. While this site is private for review, the hosting platform requires sign-in. Links to courses, organizers, mapping services, and other websites follow those providers' privacy practices. Fonts are loaded from Google Fonts. The news page includes Facebook embeds. When a feed loads, your browser connects directly to Meta, which applies its own privacy and cookie practices. You can also open the source pages directly.

To request a correction or removal, use the news submission form, identify the item, and describe your request. We may need to verify your connection to the submission.

Updated October 26, 2026.