TourneyHQ
Privacy
What we collect, why, who else sees it, and how to have it removed. Written to describe what the software actually does, not what sounds reassuring.
Who holds your data
TourneyHQ is used by golf clubs, societies and event organizers to run competitions. When a club enters you into a tournament, the club decides what to collect and why. We store and process it on their behalf and act on their instructions.
In data-protection terms the club is the controller and TourneyHQ is the processor. In practice that means: if you want your details corrected or removed, your club can do it directly, and that is usually the fastest route. If they cannot, write to us at privacy@tourneyhq.example and we will act on it.
You may be in here without ever having signed up. That is normal for club golf — an organizer enters the field from the club’s own membership records. It does not reduce your rights below, and it is why this page is readable without an account.
What is collected
About players in a tournament, from the club:
- Name
- Email address and phone number, where the club provides them
- Handicap index, and whether it is a 9 or 18-hole index
- Scores, results and any note attached to a card
- Weekly availability, in leagues that ask
About people who sign in to run an event:
- Email address and name
- A password, stored only as a hash — we cannot read it
About the club itself: its name, town or region, colours and logo.
If an organizer opens self-service registration, whatever a person types into that form — typically the same name, contact details and handicap.
What is not collected
No payment card details — TourneyHQ does not take payments. No location tracking. No advertising identifiers, and no third-party analytics or advertising trackers.
Sign-in and abuse limits are counted against a hashed identifier. The code that stores those counts never receives the original value.
Cookies
One cookie signs you in and keeps you signed in. It holds a signed reference to your account and nothing else. A second, similar cookie is used when a player joins a round with a code instead of an account.
They are not used to track you between sites or to build a profile.
Who else sees it
Only what is needed to run the service:
- Vercel — hosting. Serves the app and keeps standard server logs.
- Our database provider — stores the tournament data described above.
- unpkg (Cloudflare) — the icon stylesheet loads from this public CDN, so your browser’s IP address and user-agent reach it on each visit. It receives no tournament data.
- Anthropic — only for the features your club switches on, and only when someone uses them:
- Reading a scorecard from a photo. The photograph is sent, along with the name of the player whose scores are being read. A photograph of a card may also show other players’ names and scores, and handwriting.
- AI-written commentary. Current standings, which include player names, are sent to generate a line of text.
- Describing a tournament in words. Only the sentence the organizer types is sent. No player data is included.
- Drafting an announcement. A summary of the event is sent: its name, the size of the field, the rounds, the leading players by name with their scores or points, and, where a league runs skins, who is up or down on the season and by how much. Contact details are never included.
We do not sell personal data, and we do not share it for advertising.
Public leaderboards
An organizer can publish a leaderboard on a link anyone can open, for a clubhouse screen or to share with a field. It shows what a leaderboard shows: names, scores and standings. It does not show email addresses or phone numbers.
Whether to publish one is the organizer’s decision, and they can stop sharing it at any time.
How long it is kept
Tournament data is kept until the club deletes it or asks us to. We do not currently delete it automatically on a schedule, and this page will say so plainly until we do.
An organizer can remove a player, or a member from the club roster, at any time.
Your rights
Depending on where you live you may have the right to see the personal data held about you, have it corrected, have it deleted, or object to how it is used.
Ask your club first — they hold the relationship and can act immediately. If that does not resolve it, write to privacy@tourneyhq.example and we will action it, and tell the club we have.
Children
Junior competitions are part of club golf, and a club may enter players under 18. Where it does, the club is responsible for having the right permission from a parent or guardian. TourneyHQ collects nothing extra from a junior player, and no account is needed to appear in a field or on a leaderboard.
Security
Traffic is encrypted in transit. Passwords are stored only as hashes. Access to a tournament is scoped to the organization that owns it, and checked on the server rather than only hidden in the interface.
No system is perfect; if you believe you have found a problem, please tell us.
Changes
If this policy changes in a way that affects what is collected or who it is shared with, the date below changes and the change is described here rather than made quietly.
Last updated 9 August 2026.