Role and location-based access
Access is invite-only. Customer administrators assign roles and locations so club managers, area leaders, Accounts, sales and executive users receive the tools and records relevant to their responsibilities.
Separated customer workspaces
Each business group operates in its own workspace. Customer users cannot browse another organisation. Authorised ClubPilot support may access a workspace when required to operate, secure or troubleshoot the service, and platform support activity is audited.
Evidence and audit history
Operational records retain relevant ownership, status, comments, attachments and completion history. This supports accountable follow-through; it does not replace a customer's legal, safety, accounting or records-management obligations.
Data minimisation
ClubPilot does not require access to member payment details or a member CRM to run its core operational workflows. Customers should provide only the business information needed for the task and must not upload passwords, online-banking credentials or unnecessary health, banking or member data.
Files, integrations and optional AI
Files and connections are activated for an agreed purpose and access method. Third-party availability, charges and permissions are confirmed before activation. ClubWalk AI review is optional, customer-controlled and requires human confirmation before a finding becomes action.
What we confirm before rollout
- Required roles, locations and approval boundaries.
- Which information enters ClubPilot and why.
- Any file exchange, integration or third-party dependency.
- Support, export and retention expectations for the pilot.
- Which workflows need human review or customer sign-off.
Ask a security question
Security and privacy questions can be included in a pilot brief or sent to admin@clubpilot.au. We will answer against the proposed workflow rather than handing you a decorative shield icon and hoping for the best.