AI and Member Data: What Did Your Club Just Share?
Your Member List Was Uploaded to AI. Who Approved That?
The spreadsheet was supposed to help plan next month’s event.
Someone exported the attendee list, opened an AI tool and typed: “Tell me which members are most likely to book again.”
A sensible question. A shortcut on a busy afternoon.
But what was in the file?
Names, email addresses, booking history, perhaps a few notes about dietary requirements or accessibility requests. Information collected to organise an event had just been handed to another service.
Before the club discusses the answer, there’s a more pressing question:
Was anyone authorised to share the information in the first place?
For club CEOs and boards, this is where the conversation about AI becomes practical. A staff member doesn’t need bad intentions to create a privacy problem. They might simply be trying to get through their workload.
Members are already uneasy about AI using their information
The concern isn’t hypothetical.
In the OAIC’s Australian Community Attitudes to Privacy Survey 2026, 69% of respondents identified AI using their personal information among the biggest privacy risks they faced, compared with 43% in 2023. These figures describe people’s concerns, rather than how often information has been mishandled.
The same research found that 71% considered it unacceptable for an organisation to use personal information originally supplied for a service to train AI after that service had finished. That question concerned AI training specifically; it doesn’t mean every use of an AI tool involves training a model.
For a club, the underlying issue is easy to understand.
A member gives you their email address to receive a ticket. They provide an accessibility request so they can attend comfortably. They might expect those details to stay within the arrangements for their visit.
Would they expect the same information to appear in an external AI service?
That’s a question worth asking before uploading the file.
A booking doesn’t give you permission for every possible use

“We already have the information” can sound like a reasonable justification.
It doesn’t settle what the club may do with it.
The OAIC’s guidance on privacy and commercial AI products explains that organisations covered by the Privacy Act must apply the Australian Privacy Principles when using AI with personal information. The original purpose of collection matters, alongside any applicable basis for a secondary use or disclosure.
Consent isn’t the only possible basis. Equally, a broad statement about improving services shouldn’t be treated as permission for anything staff might find useful.
Start with the task.
If you want to compare ticket sales across three events, you may only need dates, ticket categories and totals. A complete attendee list could add information without adding much value.
The first question should be “What information does this task need?”
The AI account matters as much as the task
“Staff use AI” tells a board very little.
Which product? Which account? With what settings?
A personal account, an organisation-managed service and an AI feature inside another business application may handle information differently. The OAIC’s workplace guidance on GenAI tools highlights these differences and advises regulated organisations to refrain from entering personal, particularly sensitive, information into publicly available generative AI tools.
Before approving a product, someone needs to establish:
- Whether submitted information can be used for model training.
- How long prompts and uploaded files are retained.
- Who can access them.
- Where information is processed and stored.
- Whether connected services receive it.
- What controls the club can actually enforce.
These are due diligence questions identified in the OAIC’s commercial AI guidance. A paid subscription, or a setting that disables training, doesn’t answer all of them.
And “we deleted the conversation” shouldn’t become the club’s entire response plan.
A policy in a folder won’t stop an upload
The OAIC describes a fictional insurer, CarCover, in a case study based on a breach notification.
An employee uploaded a financial hardship application containing sensitive information to a public chatbot, despite an internal policy prohibiting that use. The example illustrates how an ordinary work task can bypass a written rule. CarCover is a fictional example, rather than a named club or insurer involved in an incident.
For clubs, staff guidance needs to be more concrete than “use AI responsibly”.
Give people examples they recognise.
Make the boundary easy to understand
A practical staff guide could distinguish between:
| Task | Information to consider |
| Drafting promotional copy | Event details, dates and approved public information |
| Comparing event performance | Totals and categories, where sufficient for the task |
| Summarising attendee feedback | Reviewed comments with identifying and sensitive details removed |
| Analysing individual booking behaviour | Personal information requiring an approved purpose and process |
These are starting points for an internal policy, rather than automatic approvals.
Removing names alone also deserves a closer look. A comment mentioning a particular incident, role or personal circumstance may still point to someone.
Staff need to know when to stop and ask. They also need somewhere useful to ask.
Five questions your club board should put on the agenda

Boards don’t need to inspect every prompt. They do need confidence that someone owns the rules.
In September 2026, ASD and the Australian Institute of Company Directors published AI cyber threat guidance for boards, including recommendations to strengthen governance of AI use and assess risks associated with AI providers. Its scope extends beyond staff uploads, but the oversight message is relevant.
Here are five questions to bring that oversight into everyday club operations.
1. Which AI tools and accounts have we approved?
Ask for a current list, an owner and a process for approving new tools. Include AI features inside software already used by the club.
2. What member information may staff enter?
Define the boundary clearly. Event details, anonymous totals, identifiable booking records and sensitive requests shouldn’t be treated as interchangeable.
3. Who has checked the provider’s handling of information?
Someone should be accountable for reviewing relevant terms, settings, retention and access arrangements. Approval should be revisited when material conditions change.
4. Who checks the output before it affects a member?
A confident answer can still contain an error. The OAIC identifies accuracy risks where AI produces personal information. Member-facing decisions deserve appropriate review.
5. What happens if someone uploads the wrong file?
Staff should know whom to contact promptly and what details to preserve: the product, account, file, time and relevant settings.
Make reporting straightforward. A problem hidden out of embarrassment is harder to assess.
Useful reporting doesn’t always need a member list
Club managers need answers.
Which event sold well? Which ticket category performed poorly? Did members book earlier this time? Were people buying tickets but failing to attend?
Many initial questions can be explored through event totals and reporting categories.
Sticky Tickets’ event reporting tools include sales dashboards, ticket-type breakdowns, attendee exports and check-in reporting. The sensible approach is to start with the report that answers the question, then consider whether an export is necessary.
An available export isn’t an instruction to upload it somewhere else.
For a management discussion, a summary of sales and attendance may be enough. If individual records are required, the purpose and handling should be clear before the file moves.
Ask before the next upload
AI can help staff draft, organise and summarise work. The approval process needs to keep pace with that convenience.
For your next leadership meeting, bring one ordinary example: an attendee spreadsheet, a feedback summary or a proposed campaign.
Walk through what staff would do with it.
Which account would they open? What would they upload? Who approved that use? What would they do if the wrong file went in?
Those answers will tell you more than a policy nobody has opened since induction.
For clubs reviewing their event setup, booking process and reporting needs, book a club ticketing review with Sticky Tickets.
Before asking AI what your members might do next, check what your club is about to do with their information.



