Privacy Policy

We collect the minimum we need to run your golf event: your email to sign you in, the roster you build, the scores everyone enters. We don't sell your data. You can delete your account and everything we have on you any time. The longer version follows.

scoring.golf is operated from Ohio, USA. For questions about this policy, email support@scoring.golf.

From event admins (you create an account):

• Email address (used to sign you in via magic link)
• The events you create and the courses you import
• The roster of players you add to those events (names, and any optional email / phone / handicap you provide)
• Usage telemetry for our own product analytics: how many events you create, how many players you add, how many scorecards are submitted. We use this to plan future pricing and improve the product.

From players (you join an event via a scoring link):

• The name your admin added you under (and email/phone if they entered them; or your own if you self-registered)
• The scores you enter during the round
• Your handicap, if your admin entered one or you provided one at registration
• A session token stored in your browser's cookies and localStorage so you can return to your scorecard

Technical data:

• Request logs (IP address, user agent, page path) kept briefly for security + debugging
• Crash reports via Sentry when the app errors — includes browser type, the error message, and the page you were on
• No third-party advertising trackers, no Google Analytics, no Facebook pixel

We use the data above to:

• Run your events — show leaderboards, score holes, submit cards
• Sign you in and let you come back to your account
• Send transactional email — magic-link sign-ins, scoring links you ask us to email to a player
• Improve the product — find bugs, plan features, model future pricing
• Communicate important changes to the service (e.g. when pricing launches)

We do not sell your data, rent it, trade it, or use it to target advertising.

We use a small number of third-party service providers to run scoring.golf. They have access only to the data they need to do their job, and they're contractually bound to keep it private. Categories include:

• Hosting and database providers — where the application runs and where your event data is stored
• Authentication provider — handles magic-link sign-in and session management
• Transactional email provider — sends sign-in links and the scoring-link emails you ask us to deliver to your players
• DNS and inbound email routing — delivers email sent to support@scoring.golf
• Error and crash monitoring — alerts us when something breaks so we can fix it
• Golf course data provider — looks up par, yardage, and handicap indexes when you add a course to an event

We do not share your data with any other third party unless required by law or to protect against fraud or abuse.

The current list of named subprocessors is available on request — email support@scoring.golf and we'll send it.

Active accounts: as long as you keep using the service.

Deleted accounts: within 30 days of your deletion request, your account and the events you created are permanently removed from our database. Backups age out within an additional 30 days.

Anonymized aggregates (“how many events ran in June 2026”) may be retained indefinitely for product analytics, but contain no personally identifying information.

Whatever your jurisdiction, you can always:

• Ask us what data we have on you (we'll respond within 30 days)
• Ask us to correct it if it's wrong (also 30 days)
• Ask us to delete your account and everything attached to it
• Export your event data as a CSV (built into the admin tool)

For any of these, email support@scoring.golf. If you're in the EU, UK, California, or another jurisdiction with specific data-privacy regulations (GDPR, CCPA, etc.), you may have additional rights. Same email — we'll handle the request.

We use a small number of cookies and browser storage keys, all functional. None are for advertising and we don't use any third-party analytics or tracking cookies. What we set falls into these categories:

• Player session — so you can come back to your scorecard without re-entering your invite link
• Offline scoring queue — saves your taps locally when you're in a dead zone so they sync when signal returns
• Event context cache — remembers which event you're scoring so the “Resume scoring” banner can take you back in one tap
• Admin authentication — keeps event admins signed in

You can clear all of these via your browser settings. If you do, you'll be asked to sign in again (or use a fresh scoring link).

scoring.golf is not directed at children under 13. We don't knowingly collect data from children under 13. If a coach or organizer registers a junior golfer who is under 13, please use a parent's contact email and don't collect a personal phone for the minor.

If you believe we've unintentionally collected data from a child under 13, email support@scoring.golf and we'll delete it promptly.

We protect your data with industry-standard practices: TLS for all traffic, row-level security on the database, scoped session tokens with sha256 hashing, hosted authentication via Supabase. Service-role keys are stored as environment secrets and rotated when team members change.

No system is perfectly secure. If we discover a breach that affects your data, we will notify affected users within 72 hours and explain what happened.

Our infrastructure is primarily in the United States. If you use scoring.golf from outside the US, your data may be transferred to and processed in the US. By using the service, you consent to that transfer.

We may update this Policy from time to time. When we do, we'll change the “Last updated” date and, for material changes, notify account admins by email or via a banner on the site.

Questions, requests, or concerns? Email support@scoring.golf.