
When a club uses an online booking system, the club stays in charge of its members’ data and the supplier works for the club. In UK data-protection terms, the club is the “controller” and the booking supplier is the “processor”. Ownership in the everyday sense matters less than the question the law actually asks: who decides why and how the data is used, and who answers to members and the regulator if it goes wrong? This guide shows club managers, committee members and competition secretaries how to keep that control, and what to put in writing.
TL;DR
- Under UK GDPR the club decides the purposes of processing, so it is the controller and carries the heaviest responsibility, even when a supplier holds the data.
- The supplier, as processor, may only act on the club’s instructions, and the contract must say what happens to the data when the relationship ends.
- Tell members at the point of booking what is collected, why, for how long and who sees it.
- Plan for access, correction and deletion requests: you generally have one month to respond.
- Before you sign, check exports, retention, security, sub-suppliers and exit terms. BallChute offers a 14-day free trial with no automatic fees, so a club can see how the waiting room works before it commits.
Table of Contents
- What “data ownership” means for a golf club
- Who can see what: club, supplier or both
- The UK rules that apply to booking data
- Telling members what you do with their data
- What to check in the contract with your booking supplier
- Handling access, correction and deletion requests
- Why fair booking and data control go together
- Our view: the club sets the rules, the system follows them
- Trying BallChute with your own rules
- FAQ
- Sources
What “data ownership” means for a golf club
Search for the phrase and most results talk about corporate data governance. A golf club has a simpler situation. It holds names, contact details, membership categories, handicap-related information and a record of who played when. Members hand this over so the club can run the course and the competitions.
Lawyers rarely talk about “owning” personal data. They talk about roles. The Information Commissioner’s Office (ICO), the UK data-protection regulator, explains that the controller decides the purposes and means of processing, while a processor handles personal data on the controller’s behalf and only on its instructions.
For a club, that translates as follows:
- The club decides who may book, which membership categories get which slots, how long records are kept and who sees them.
- The booking supplier stores and processes the data to deliver the service the club has chosen, and does nothing else with it.
- The member keeps their rights over their own information, whatever the club or supplier prefers.
The same ICO guide adds that controllers carry the highest compliance responsibility, must be able to demonstrate compliance with the UK GDPR principles, and remain responsible for their processors’ compliance. You can hand over the work. You cannot hand over the accountability.
A published example from a UK club
This split already appears in clubs’ own policies. Ealing Golf Club’s data-protection policy names the club as controller and lists tee-booking records among the personal data it uses to monitor course use by membership category. It describes booking and member information handled by external service firms as processor activity carried out to deliver member services. That is the model to aim for: the club states the role, the supplier carries out the task.
Who can see what: club, supplier or both
In practice both hold the data, but for different reasons.
| Question | Club (controller) | Supplier (processor) |
|---|---|---|
| Who decides what is collected? | The club | Follows the club’s configuration |
| Who sets retention periods? | The club | Applies them as instructed |
| Who answers a member’s access request? | The club | Assists the club |
| Who reports to the ICO if there is a breach? | The club decides and reports, with the supplier’s help | Tells the club without delay |
| Who decides to share data with a third party? | The club | Only where instructed or contracted |
There is one more category: national bodies. The Golf Business reported in 2020 that England Golf’s central handicapping system would receive specified member information from golf software providers, intended for player identification, handicap-system integrity and handicap communications. Clubs should know which such flows exist and say so in their privacy notice.
The UK rules that apply to booking data
The core rules are the UK GDPR principles. A UK legal guide summarises them as lawful, fair and transparent processing, specified purposes, data minimisation, accuracy, storage limitation and security. The UK GDPR text puts the same idea in plain terms: collect data for explicit and legitimate purposes, keep it to what is necessary, keep it no longer than needed, and protect it from unauthorised access or use.
The same legal guide notes that the Data (Use and Access) Act 2025 received Royal Assent on 19 June 2025, with its changes being brought in stages through secondary legislation. For a club this is a reason to review your notices and contracts once a year rather than treating them as finished. The ICO website is the place to check the current position.
A tee-time booking system needs very little. Name, membership number, category, email address and a booking history cover most of it. If a field does not help run the course, do not collect it.
Telling members what you do with their data
Members should not have to guess. The ICO’s small-organisation checklist says a privacy notice should state:
- who is responsible for the data;
- why it is held and the lawful basis;
- where it came from;
- who receives it, including any transfers abroad;
- how long it is kept;
- how to make a rights request;
- how to complain to the ICO;
- any automated decisions or profiling.
Point 8 deserves a thought for any club that releases popular tee times through a queue or turn-based system. If the order in which members choose is set by a rule the club has published, say so in plain words. Members should be able to see how the process works and that it applies equally to all.
Open competitions and visitors
Guidance reported by The Golf Business suggests that for open-competition online bookings, people should be told at the time of booking that their data will be used only to administer the competition and will not be stored or used for future marketing. Put that sentence on the booking page, and make sure the settings match it.
For more on what a club should say and when, our own guide to data privacy in tee-time booking goes deeper on the practical side. Clubs that let members bring guests will also want to read how guest booking controls interact with UK GDPR.
What to check in the contract with your booking supplier
This is where ownership is won or lost. The ICO says the contract between controller and processor must set out the subject matter and duration of the processing, its nature and purpose, the type of personal data and the categories of data subject, and the controller’s obligations and rights. The minimum terms it lists include processing only on documented instructions, a duty of confidence, appropriate security, rules on sub-processors, help with data subjects’ rights, end-of-contract provisions, and audits and inspections.
Turn that into a checklist a committee can use:
- Instructions. Does the contract say the supplier uses member data only to provide your booking service?
- Exports. Can you download your member and booking records in a usable format at any time, not only when you leave?
- Retention. Who sets how long booking history is kept, and can you change it?
- Exit. The ICO says that at the end of the contract, at the controller’s choice, the processor must delete or return all the personal data and delete existing copies, unless UK law requires it to be stored. Make sure your contract says so, and how quickly.
- Security. What measures protect the data, and how will the supplier tell you about a breach?
- Sub-suppliers. Which other companies touch the data (hosting, email delivery), and where are they based?
- Member requests. How will the supplier help you answer an access or deletion request within the deadline?
- Integrations. If the system connects to your membership platform or national handicapping flows, who sends what, and on whose instruction?
Email is an easy one to overlook. Booking confirmations and tee sheets travel by email, so how those messages are sent matters. Our note on email deliverability for clubs covers it.
Handling access, correction and deletion requests
Members can ask what you hold, ask for mistakes to be corrected, and in some cases ask for data to be erased. The ICO checklist asks small organisations to have a plan for these requests, to recognise that they may come verbally or in writing, and to know the response time.
The UK GDPR text says requests should be answered without undue delay and at the latest within one month, with reasons given if you will not comply. An access response covers the purposes of processing, the retention period where possible, the recipients, and any relevant automated-processing logic and its consequences.
A simple routine for the club office:
- Name one person who receives requests, and tell members who it is.
- Log the date each request arrives, because the month starts then.
- Check the member’s identity before releasing anything.
- Pull the booking history and member record from the system.
- Reply in writing, and keep a note of what you did.
A realistic example: a member asks what you hold about them. The secretary exports the member record and booking history, adds the privacy notice and sends both within the month. If the same member asks for a booking record to be deleted, the club considers whether it still needs it, for example to show fair use of competition slots, and explains its decision either way.
Why fair booking and data control go together
A fair booking process depends on trustworthy data. If members have duplicate accounts, or the wrong category attached to their name, the queue stops being fair. Our guide to preventing duplicate accounts shows how clean member records protect fairness, and the booking fairness policy checklist helps you write the rules down so members can see them.
The less data the process needs, the easier all of the above becomes. A club that decides in advance who may book, when, and for how long has already answered most of the questions a member or regulator might ask.
Our view: the club sets the rules, the system follows them
We build BallChute around one idea: the club is in charge. Each club defines its own booking rules and time limits, and the waiting room applies them to every member in the same way.
That matters for data as much as for fairness. A club that controls how a booking release runs, who may take part, and when members choose, knows what the system is doing and can explain it to a member in a sentence. Member verification and group selection are part of the service so that the club’s own rules, not the speed of someone’s clicking, decide who gets which slot.
Clubs also tell us they want the output without the admin. That is why the tee sheet can be downloaded or emailed to officials once the selections are made.
Our advice for any committee choosing a booking system is to start from your own policy: write down what you collect, why, who sees it and how long you keep it. Then choose the system that lets you apply that policy simply.
Simon
Trying BallChute with your own rules
BallChute is tee-time booking software for golf clubs. It gives members an online waiting room and turn-based booking, with club-controlled rules, member verification, group selection and tee sheets that can be downloaded or emailed. Clubs that use an Intelligent Golf membership system can choose the integration plan, described on our page about fairer tee-time releases for integrated clubs.
Pricing is per club: the Standard plan is £29 per month or £290 per year, and the Intelligent Golf plan is £35 per month or £350 per year. Every club can try the service free for 14 days, with no automatic fees. See the plans on the BallChute site.
If you also want to see how a release works under heavy demand, our guide to booking surge control walks through it.
FAQ
Does the golf club or the booking supplier own member data?
The club decides how member data is used, so under UK GDPR it is the controller and stays accountable. The supplier is the processor and acts on the club’s instructions. Your contract should make this explicit.
How long do we have to answer a member’s data request?
The UK GDPR says requests should be answered without undue delay and at the latest within one month. If you will not comply, you must give reasons. Log the date each request arrives so you can show you met the deadline.
What should we tell members when they book a tee time?
Tell them who is responsible for their data, why it is used, how long it is kept and how to make a request or complain to the ICO. For open competitions, say the data is used only to administer the event and not for future marketing.
What happens to our data if we stop using a booking system?
The contract should say that, at your choice, the supplier deletes or returns all personal data and deletes existing copies unless UK law requires storage. Agree the format and timing before you sign.
Do we need a new privacy notice when we change booking system?
Check your existing notice against what the new system does. If it adds a new recipient, purpose or retention period, update the notice and tell members. Review it at least once a year in any case.
Sources
- A guide to controllers and processors | ICO
- What needs to be included in the contract? | ICO
- How well do you comply with data protection law | ICO
- UK GDPR text on legislation.gov.uk
- Data Protection Guide UK, England and Wales
- Data Protection Policy, Ealing Golf Club
- Data compliance clarification sought over new handicapping system, The Golf Business
- Golf clubs and General Data Protection Regulations, The Golf Business