Security & data
It is the members' data, not ours.
A golf club holds names, addresses, payment history and health-relevant dietary information. Club Driver is built so a committee can answer questions about that data with confidence.
Isolation & access
One club cannot see another
- Club-scoped data isolation is enforced through platform-wide security policies
- Staff permissions are granted by role, not by who knows the password
- Committee, management and staff see different things by design
- Platform support access is limited and recorded
Accountability
A trail that survives the AGM
- Wallet top-ups, tab opens and closes written to an audit log
- Refunds, voids and overrides carry an approver and a reason
- Allergen and menu changes recorded with who changed them
- Committee decisions, policies and acknowledgements retained
- 1Link credentials to the live membership lifecycle
- 2Record denied access and exceptions for review
Continuity
Backups, restores and getting your data out
Resilience is only real if it has been tested, and portability is only real if the export exists.
- Regular backups with a documented restore procedure
- Restore rehearsals rather than untested assumptions
- Health monitoring and incident response documented
- Exportable data, so the club is never trapped in the platform
GDPR in practice
Consent is recorded per communication channel and respected by the messaging tools. Member records can be exported or erased on request, and the club remains the data controller throughout — Club Driver processes data on its instruction.
See what Club Driver could look like at your club.
Explore the platform with the Club Driver team and see how golf, membership, payments, events and clubhouse operations can work together.