Most clubs didn't choose WhatsApp as their club management system — it just sort of became one. A captain needed to reach the team quickly, someone added the rest of the committee, and a few seasons later it's where fixtures get arranged, results get shared, and new members get their first introduction to the club. It works, right up until someone asks who has access to what, how long it's kept, or how to get their data removed.

That gap matters more than it looks. Under GDPR, a bowls club that holds member contact details — even informally, even in a group chat — is a data controller, with the same basic obligations as any other organisation. The committee carries that responsibility personally, whether or not anyone signed up for it.

Why WhatsApp Falls Short for Club Management

Beyond the compliance question, a group chat simply isn't built to run a club:

• There's no member database — just a thread that scrolls past everything older than a week.
• When an admin leaves the club, the group (and often the only working phone number) leaves with them.
• You can't message just the Tuesday league, or just the people who haven't paid — it's everyone, every time.
• There's no record of who saw a message, agreed to play, or paid their subs.
• It doesn't connect to fixtures, payments, or bookings — everything still happens twice.
• It only works for members who are comfortable with smartphones and happy to hand over a personal number.

The GDPR Problems Hiding in Your Group Chat

The audit above isn't a worst-case scenario — it's a fairly ordinary Tuesday. Here's what's actually going on underneath it:

• No documented lawful basis. Phone numbers and addresses get shared because it's convenient, not because anyone agreed to it being shared that way.
• Special category data, by accident. Health details mentioned as an excuse for missing a match count as special category data, with extra legal protection a group chat can't offer.
• No retention or deletion policy. Messages — and the personal data in them — sit on personal phones indefinitely, often long after someone has left the club.
• No way to act on a request. If a member asks to be forgotten or asks what data the club holds on them, there's no practical way to find, export, or erase it.
• Data is processed on volunteers' own, unmanaged devices — lost phones, old backups, and personal accounts all become part of the club's data footprint.

How Bowls Hub Solves This

Bowls Hub gives the committee a proper system of record, without losing the speed a group chat is good at:

• A proper member database — contact details are captured with consent, kept in one place, and never broadcast to the whole club just to reach one person.
• UK-hosted and GDPR compliant — each club's data is isolated, encrypted, and backed up, with full GDPR compliance built in rather than bolted on.
• Access tied to a role, not a phone number — when a volunteer steps down, admin access goes with them. The club keeps everything else.
• Targeted communication — email and push notifications reach exactly the right people, without exposing anyone else's number to do it.
• Data members can actually access — the club retains ownership of its data and can export or remove it whenever it's needed.

This page is general guidance, not legal advice. If your club needs specific GDPR guidance, the ICO is a good place to start.