Your club's data, and where it lives

This page summarises how ClubHub stores and handles club information. The Privacy Policy is the authoritative document.

Where the data lives

• The main ClubHub production database and sign-in service is provided by Supabase and hosted in Sydney, Australia.
• Lovable supplies application hosting and development infrastructure and managed application email delivery. Supporting providers may process technical logs, email content and delivery records.
• Google Analytics measures designated public website pages using cookies or similar identifiers. Google uses global infrastructure, including in the United States. Sydney database hosting does not mean all application, email, support or analytics processing stays in Australia.

Where club information comes from

• what your club's Admins and Selectors enter directly, including authorised manual match details where a fixture is not linked
• authorised PlayHQ reports your club chooses to upload. These supply player and registration detail
• if your club connects it, the PlayHQ Public API. This supplies supported public competition, fixture and result information. A documented public match summary may also provide publicly visible player names, source identifiers, participation indicators and performance figures where available and permitted by the credential's scope and terms. Coverage follows PlayHQ visibility settings. This connection does not supply private registration profiles, dates of birth, contact or payment details
• association rule documents and public competition information used for selection checks.

An API connection needs authority from the organisation responsible for the credentials. Credentials are handled server-side and are not returned for display to other Users. An Admin can disconnect the connection. Reports and manual entry remain available; disconnection does not itself delete previously imported history.

What ClubHub keeps as history

ClubHub preserves the records needed to explain a Club's selection and match administration. Depending on the features used, that can include Finalised selection versions, Wrap Up and participation records, two-day Day 1/Day 2 history, recorded changes between days, acknowledgements and overrides, match-planning information, and versioned performance evidence from supported sources.

Account creation also records the accepted versions of the User Agreement and Privacy Policy. Those acceptance records are audit records and are not editable by ordinary users.

Service administration and optional public information

ClubHub also holds Club contacts, subscription and billing records, notification preferences and delivery records, and derived measures such as team, player, competition and authorised-user counts, completed selection weeks and import pathway. Authorised ClubHub personnel use relevant information for onboarding, support, billing, security and service planning. Derived measures do not automatically change your Foundation Season price.

The launch checklist is shared by Club Admins and records who updated each action and when. Prompt dismissals are recorded for the individual Admin. An Admin can opt into or remove a public listing containing the Club's name, location, Association, website and listing date. Player records, selected teams, internal notes, Admin contact details and uploaded private logos are not included in that listing.

Launch email drafts open in your own email application. ClubHub does not save recipient addresses entered solely for those drafts or send the drafts automatically.

How long information is kept

ClubHub keeps information for as long as it is reasonably needed to run the service, preserve legitimate club selection, match and participation history, meet audit, security and legal requirements, and resolve disputes. Legal-document acceptance records and other audit/history records may be retained after an account or workspace is closed where that is reasonably required. When information is no longer reasonably required, it may be deleted, de-identified or securely archived.

ClubHub has not yet adopted fixed retention periods for every category of information. Before setting them we will confirm the approach with participating clubs and update the Privacy Policy.

How access and security work

ClubHub uses individual accounts, role-based access and club-scoped database controls. Selectors receive the player information needed for selection, while restricted identity details such as full date of birth are reserved for authorised Admin workflows. These measures reduce risk, but no internet service can guarantee absolute security.

Uploaded Club logos use private storage and authorised links. Printed plans, browser-saved PDFs and copied team lists are separate copies: they do not automatically update or fall under ClubHub's permissions after sharing. The Club must manage their recipients and disposal. A legacy logo hosted elsewhere also follows that external host's practices.

Closing a workspace

A club can ask ClubHub to close its workspace or discuss deletion of its information. Closure is currently handled by contacting ClubHub rather than through a self-serve button. Some records may be retained where there is a legitimate legal, security, audit or record-keeping reason.

Cancelling a subscription or removing a User's access does not itself delete the workspace or all records. Ask ClubHub about an appropriate export before closure and about any information that must be retained.

Access and correction

People can ask ClubHub about access to or correction of their personal information. Where a club controls the information, ClubHub may work with or refer the request to that club. Club users can also correct much of the information they administer directly in ClubHub.