ClubPilotBuild a pilot

SECURITY & DATA PROTECTION

Operational visibility with sensible boundaries.

ClubPilot is designed to give each person the work they need while keeping customer workspaces, locations and responsibilities separated. This page explains the controls available today and the questions we confirm during a pilot.

Security at a glance

  • Where your data lives: ClubPilot runs on Cloudflare. The customer database and uploaded files are stored in Cloudflare's Oceania region, and Cloudflare encrypts stored data at rest.
  • Encrypted connections: every page and API request uses HTTPS only, enforced with HTTP Strict Transport Security, plus a content security policy and anti-framing headers.
  • Sign-in: accounts are handled by Supabase Authentication with email confirmation. ClubPilot never sees or stores your password in plain text.
  • Payments: card details are entered on and held by Stripe, never by ClubPilot.
  • Sensitive settings: connection credentials and bank details are additionally encrypted by ClubPilot before they are stored.
  • Backups: a full backup is taken every night and encrypted to an offline recovery key held by the owner.
  • Monitoring: errors and service health are monitored automatically, and every production release passes an automated verification gate before it goes live.
  • Reporting a concern: email admin@clubpilot.au. Our security contact is also published at /.well-known/security.txt.

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.

HomePrivacy PolicyTerms of UseBuild a pilot