Committee5 min read

Five questions to ask before putting your club's data in anyone's software

Where the data lives, who can see it, what happens if you leave, how juniors are handled, and who is behind the company. Our own answers, weak ones included.

By Alex Baker, Tadpole

A membership list is the most valuable thing a club owns and the thing it protects least. Ours lived on a laptop for years. When a committee finally decides to put it into software, the conversation is usually about features and price, and the questions that actually matter get asked afterwards, if at all.

These are the five we would ask now, of anyone, including us. Our own answers are at the end, and they include the ones we are not proud of.

1. Where does the data actually live?

Not "in the cloud". In which country, on whose servers, and is it encrypted while it sits there? A club's list has names, addresses, phone numbers, dates of birth and payment history. If the answer is a server outside the EU, the club has a GDPR problem it did not have before. If the answer is vague, that is the answer.

Ask a second question underneath: is there a backup, where is it, and has anyone ever actually restored from it? A backup nobody has tested is a hope.

2. Who can see it?

Three separate questions hiding as one. Which committee members can see what, and can that be limited by role, so the match secretary does not see the treasurer's screen? Can the company that makes the software see your members' data, and under what rules? And is there a record of who looked at what, so if something goes wrong the club can find out?

The honest answer from most software is that everyone with a login sees everything. That is fine for a club of forty and a real problem for a club of four hundred.

3. What happens if you leave?

Every club will change software eventually, even if it is in fifteen years. Ask now: can we export everything, in a format a spreadsheet can open, without asking permission? Do we own our own domain name, or does the provider? What is deleted when we go, and when?

A provider that makes leaving hard is telling you something about how they expect to keep you.

4. How are junior members handled?

This is the one that most club systems get wrong, and it is the one with real consequences. Under-16s need a parent's consent before their data is processed. Their photos need separate handling. Their contact details should reach the parent, not the child. If the software treats a twelve-year-old as a small adult with an email address, the club is carrying the risk.

Ask to see the parental consent flow. If there isn't one, there isn't one.

5. Who is actually behind the company?

Names. Where they are. Whether they have ever sat on a club committee. Whether the company will exist in three years, and what happens to your data if it does not. A small company is not a bad answer, but an anonymous one is.

Our answers

Where it lives. In an encrypted database in Ireland, on Supabase, with payments handled by Stripe inside the EU and email by Brevo in France. Backed up daily by the database provider and separately by us to a second EU location, encrypted before it goes. We have restored from that second backup and written down what it took, because a backup nobody has tested is a hope.

Who can see it. Access is by role, and the club sets the roles: chairman, secretary, treasurer, water keeper, whatever the club calls them. A keeper on the bank sees a name, a photo and whether the membership is current, and nothing else. Every significant action by a committee member is recorded and the record cannot be edited. We, the company, can see club data for support and only for that, and it is covered in the agreement every club signs.

If you leave. The data is the club's. It exports from the admin as spreadsheets, without asking us. The club buys and owns its own domain. We keep member photos out of exports for privacy reasons, and we delete on request.

Juniors. A parent consents before a junior's record is created. We do not store photos of under-18s at all; the database itself refuses them. Renewals and messages about a junior go to the parent. We wrote the policy down and it is public.

Who we are. Three people. It came out of the committee at Trim, Athboy & District Angling Association, where one of us still sits, and other clubs asked for it. We are a small Irish company and the club data is the point, not a by-product.

What we do not do well

Honesty is the whole reason to write this post, so here is the other side.

We are three people. If the company folded, the export above is what protects you, and it is the only thing that does. The platform has been security-reviewed, internally and by an outside audit, but no independent penetration test has been run yet. Billing is annual only. The club website comes in one design, dark, with the club's colours, and if you want a page that we have not built, you cannot add it. If a club changes its web address we keep the old one working, but we set that up by hand: there is no self-service screen, and the old address does not redirect to the new one.

None of those are reasons not to ask us. They are the answers we would want from anyone else.


We built Tadpole for our own club and other clubs asked for it. Seven clubs are live on it now, with three more onboarding.

See how Tadpole handles member data →

Encrypted & Isolated
GDPR Built In
Junior Protection
Full Audit Trail
How we protect your data