Privacy Policy
Effective 17 November 2026, last updated 17 November 20261. About this policy
This Privacy Policy explains how Pavilion Cricket ("Pavilion", "we", "us") handles personal information when you visit pavilion-cricket.com, use a club's public Pavilion pages, public calendars or private links, or use Pavilion's products: Archive+, Calendar+, Intelligence+, Net Manager+, Media Design+ and Curator+.
We handle personal information in line with the Australian Privacy Principles in the Privacy Act 1988 (Cth).
Clubs decide much of what is entered into Pavilion about their players and members. Your club's own privacy notice may also apply to you.
2. Public records and private club data
Public sporting records. When a club makes its Archive+ public, match results, scorecards, player statistics, honours and club history can be read by anyone, much like a club scorebook or a public cricket association website. Public club pages can appear in search engines. Profiles whose names a cricket data provider has withheld are not offered to search engines.
Private club data. Intelligence+, Net Manager+, Curator+, Media Design+ and Club Settings hold information visible only to the people that club has given access to. Private club pages are not offered to search engines.
3. Information we handle
Pavilion does not take payments through this website, so it does not collect card details.
4. How we collect it
We collect information directly from you, when you sign in, send an enquiry, reply to a private link or use a product. We receive it from your club, when its administrators, coaches and staff enter or import it, and from the cricket data providers your club connects, such as PlayHQ and PlayCricket. We also collect some technical and usage information automatically, as the Cookies and Analytics Policy explains.
5. How we use it
We use personal information to provide Pavilion, manage accounts and club access, prepare what clubs ask the products to prepare, publish what clubs choose to make public, respond to enquiries and support requests, keep the service secure and reliable, fix faults, and understand in aggregate how Pavilion is used, so we can improve it.
We do not sell personal information, and we do not use it for targeted advertising.
Pavilion does not send marketing emails. The emails it sends are service emails, such as club invitations, booking and enquiry notifications, and replies to support requests.
6. Junior players
Cricket club records often include junior players. Pavilion protects them in these ways:
- Names that a cricket data provider has withheld are left out of named rankings and statistics, and those profiles are not published or offered to search engines.
- Junior players' photos can be stored privately for authorised club staff in Media Design+. They are not published as public Archive+ profile photos, and they are not shown in Intelligence+ or Net Manager+.
- A junior player's photo appears on a Media Design+ graphic only when a staff member chooses it for that graphic. Pavilion does not publish graphics. Your club decides whether to download and post one.
Other junior records, such as names in scorecards that the data provider has not withheld, may appear where a club publishes its history in Archive+, and can be found through search engines. A parent, guardian or player can ask the club, or us, about a particular record (see section 13).
7. Injury information
Some information in Pavilion can be health information, which is "sensitive information" under the Privacy Act: an availability reply that says a player is injured, and a training limit a coach enters, such as returning from injury. It is visible only to the club staff who have access to the product that holds it. Pavilion uses it only to prepare what the club asks for, such as selections and training sessions.
Clubs are responsible for having consent to collect it. Please do not enter medical detail that Pavilion does not need.
8. Automated suggestions
Pavilion's computer programs prepare suggestions from club data, using set rules: selections, training plans, pitch strips and post content. A suggestion can help a selector or coach make a decision, but Pavilion does not make the decision. A person at your club decides, and suggestions can be incomplete or wrong.
The kinds of personal information these suggestions use are availability, selections, playing records and statistics, training attendance and coach-entered training limits.
Two features use machine-learning models: photo cut-outs in Media Design+, which run in your browser, and Coach Mode voice calls in Net Manager+, generated on Pavilion's server. Neither makes decisions about people.
9. Who we share it with
Publicly, where a club chooses to publish, as described above. Within a club, according to the roles and access its administrators set. If the law requires it. And with these service providers, which help us run Pavilion:
Map, address and weather services receive ground locations and addresses, not player information. When a map loads in your browser, its provider receives your IP address, as with any website image.
Our service providers may only use the information to provide their services to Pavilion.
10. Overseas processing
Some information is stored or processed outside Australia:
- Pavilion's application and main database are hosted by Railway in Singapore.
- Sign-in (WorkOS), email (Resend), error reporting (Sentry) and product analytics (PostHog) are provided by companies based in the United States, and information they handle may be stored or processed there. Our Sentry and PostHog data is held in their United States regions.
- Cloudflare runs a global network, including in Australia, so information passing through it may be processed in other countries.
11. Cookies and analytics
The Cookies and Analytics Policy explains the cookies, browser storage and analytics Pavilion uses. In short: a sign-in cookie keeps you signed in, public marketing pages set no Pavilion cookie, PostHog runs only inside the signed-in product with session recording off, and public club page counts are kept per club and per hour and are not linked to you.
12. Security
Sign-in is through WorkOS. Each club's data is kept separate and access is set by role. Connections use HTTPS. Sessions can be signed out from your account page, and access removed by a club is checked on every request. We keep backups.
No system is completely secure, and we do not claim any security certification. If a data breach is likely to cause serious harm, we will notify the people affected and the Office of the Australian Information Commissioner (OAIC), as the Notifiable Data Breaches scheme requires.
13. How long we keep information
- Account and club membership information is kept while you have access to a club, and while it is needed to show who did what in that club's records.
- A club's data is kept while the club uses Pavilion, and until the club asks us to delete it.
- A sign-in session ends 30 days after it was last used, or sooner (see the Cookies and Analytics Policy).
- Off-site backups are replaced on a rolling schedule: a daily copy for 30 days and a monthly copy for 12 months. Information deleted from Pavilion can remain in a backup until that backup is replaced.
- Error reports and analytics are kept by Sentry, PostHog and Cloudflare for the periods their services set.
14. Access, correction and deletion
Your information. To ask for access to or correction of your personal information, or to ask about deleting it, email [email protected] or use . We check identity or authority first, and we respond within a reasonable time. If we cannot do what you ask, we will explain why in writing.
Leaving a club. A Club Admin can remove your access, or you can ask them to. Your club's records stay with your club.
Club data. An authorised club administrator can ask us to delete a club's data through Support in Club Settings. Deletion is handled by request and is not a self-service action.
Public records. If you want a public sporting record changed or removed, contact your club or us. Requests are looked at individually.
15. Questions and complaints
Email [email protected] or use to ask a question or make a privacy complaint. If your club already uses Pavilion, you can also use Support in Club Settings. We will look into your complaint and reply in writing.
If you are not satisfied with our response, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.
16. Changes to this policy
We will update this policy when our practices change, and show the date of the change at the top of this page.
17. Contact
Pavilion Cricket. Email [email protected], or use .