Matchups

Privacy policy

Last updated 6 September 2026

Matchups (“we”, “us”) runs the training planner at matchups.training. This policy says what personal information we hold, why, where it lives and how to get it changed or removed. It is written to follow the Australian Privacy Principles in the Privacy Act 1988 (Cth), and we apply it to every club we serve wherever it is.

The two kinds of people we hold information about

Coaches and club administrators

Your name, email address, a password we store only as a one-way hash, your role at the club, and when you last logged in. We use these to run your account and to send you the emails you would expect: your setup link, an approval, a reset. For security we also keep, for the application form and for your most recent login, the internet address it came from, the rough place our hosting matched it to (a city, never an exact location) and the kind of device and browser. Your club’s administrator can see the place and device against your name, so a login that was not you can be spotted; the address is kept for our own checks.

Players

Your club enters the players it trains: name, mobile number, email if given, team, whether they bat, bowl or keep, how the coaches rate them, and, for juniors, a date of birth so the app can apply the junior bowling limits for their age. Coaches can also record short notes such as an injury to work around and whether a player is available on a given night. The app then stores what training each player was invited to, how they replied, where they were placed and whether they attended.

Coaches can also write coaching notes on a player through the season (what they saw in the nets, what to work on). At a club these are cricket notes for the club’s coaches only: they are shown on the player’s page to the club’s logged-in coaches, never to players, parents or anyone outside the club, and never in a message (a coaching business can share a note with its client, see below). The app asks coaches to keep them to cricket and not to record health or personal details. A note can be removed by the coach who wrote it or a club administrator, and a player can ask their club to see or remove notes about them.

The club is the one collecting this information from its players and their parents; Matchups holds it on the club’s behalf and only to run the club’s training. Clubs should tell players and parents that their details go into Matchups for training texts and planning, and should not enter anything the player would not expect a coach to know.

Coaching clients

A coach or coaching business on Matchups has a public booking page. When you book a session from it you give the coach your name, mobile, email, date of birth and, for a player under 16, a parent or guardian’s name and contact details, plus what you want to work on. We hold the booking (when, where, with whom, the price, whether it is paid), the coach’s session plan, and the texts and emails sent about it, and the coach can keep notes on your sessions as above. A coach chooses whether a note is shared with the player (and a parent) on their own page or kept to coaches. The coach is the one collecting this information; Matchups holds it on the coach’s behalf to run the bookings.

Payments. Card payments are taken by Stripe on its own payment page. The card number never reaches Matchups: we keep only whether the booking was paid, when, and Stripe’s reference for it. A coach taking bank transfers puts their own account details on the confirmation. Paying in person is between you and the coach.

Trial applicants

When a club runs trials through Matchups, applicants (or their parents) fill in the club’s own form: name, date of birth, contact details, a parent’s details for juniors, cricket questions such as where they bat and how they bowl, and anything else the club asks. We hold the answers, the trialist number the club gives out, the selectors’ scores and comments from the day, the club’s notes and decision, and the texts and emails sent about the trial.

The form can ask for an optional headshot so selectors can put a face to a number on the day. It is shrunk on the applicant’s own phone before it is sent, stored in the club’s database in Sydney, shown only to the club’s logged-in coaches and to whoever the club gives its scoring link, and never appears in a message, an export or anywhere public. Photos are deleted automatically thirty days after the last trial day (or 120 days after upload if the trial never set a day), earlier if the club removes them, and whenever the trial is deleted. Anyone can ask the club to remove theirs at any time.

AI features, and what is never sent to them

Some parts of the app can use a language model (Claude, made by Anthropic) to read a coach’s typed instructions, to answer a coach’s questions about their club’s data, and to summarise the comments that selectors write at a trial and that coaches write about players through the season. The plan builder itself never uses a model: it is a fixed set of cricket rules that run on our own servers.

Nobody is named to the model. Before anything is sent, every player, coach and selector is replaced by a short code (“P7”, “C2”), and the app puts the names back into the answer before anyone reads it. Dates of birth, ages (an age band such as “junior, 13 to 14” goes instead), injury notes, mobile numbers, email addresses, home suburbs, photos and trial application answers are never sent. What is sent is the cricket: teams, roles, ratings, scores, attendance and bowling counts, the club’s venue and session names, the words a coach types into the box, and the comments coaches and selectors have written, which the app asks them to keep to cricket. Trialists are sent as their trialist number.

Anthropic processes what we send under its commercial terms: it does not use it to train its models, and it deletes it within thirty days of the request. Anthropic is a United States company and stores data in the United States, so those coded cricket details leave Australia (or the UK or wherever your club is) for the time it takes to answer. A club administrator can switch every AI feature off in Settings; the app then uses its own built-in reading and nothing about the club leaves our systems.

What we use it for

We do not sell personal information, use it for advertising, or share it with anyone other than the providers listed below.

Where it lives and who else touches it

Some of these providers run infrastructure outside Australia to deliver a message or an answer; by using the app to text, email or use the AI features, you agree to that limited transfer. Each provider is bound by its own privacy terms and only ever receives what is needed for its job. The full list, with where each one is and what it holds, is on our security page.

Clubs outside Australia

For clubs in the United Kingdom or the European Union, the club is the controller of its players’ information and Matchups is its processor under UK and EU GDPR: we act on the club’s instructions, hold the data in Australia under the safeguards described here and on the security page, and help the club answer a player’s or parent’s request to see, correct or delete their information. The lawful basis for a club entering its players is the club’s legitimate interest in running its training, and for texting a player, the player’s (or parent’s) consent given to the club. Players and parents in those countries have the same rights described under Your rights, and can also complain to their local authority (the ICO in the UK). We will sign a data processing agreement with any club that needs one; email us.

Children

Junior players’ details are entered by their club. We hold a junior’s date of birth only to apply age-group bowling limits and never contact a junior directly except through the same training text every player receives. Clubs are responsible for having a parent or guardian’s agreement before entering a junior’s mobile number.

Trial applications from juniors should be made by, or with, a parent or guardian; the form asks for a parent’s details for that reason, and the messages about the trial go to the parent as well. A junior’s headshot is optional, is only ever used to identify them at the trial, and is deleted afterwards as described above. Clubs agree, as a condition of using the feature, that their coaches and selectors will not save, share or publish a trialist’s photo, and that everyone given the scoring link holds a current Working With Children Check or the equivalent where they are.

How long we keep it

For as long as the club uses Matchups. A club can mark a player inactive at any time, which keeps their history for reports, or remove the player entirely. Trial applications stay until the club deletes the applicant or the trial; headshots go on the timetable above. When a club leaves, its data is kept for ninety days in case it comes back and then deleted, backups included within the thirty-day backup cycle after that. Text logs are kept so a club can see what was sent.

Your rights

You can see what a club holds about you by asking that club; coaches can show or export a player’s record from the app. You can ask for it to be corrected or deleted. If you are a player and the club does not help, or you want to reach us directly, email hello@matchups.training and we will answer within a fortnight. If you are not satisfied, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.

Cookies

The app sets one cookie to keep a coach signed in, and one for the master administrator. There are no advertising or tracking cookies. Player links carry a private code instead of a login; anyone with a player’s link can see and change that player’s replies, so players should not forward it.

Security

The database is encrypted at rest and every connection is encrypted in transit; passwords are stored only as one-way hashes; every table is locked down so that only the app’s own connection can read it; player links carry a private code; and nightly backups are kept encrypted with a second provider. The detail, in plain words for a club secretary, a school or a parent, is on our security page. No system is perfect; if a breach ever affected personal information we would tell the clubs concerned and the Commissioner as the law requires.

Changes

When this policy changes, the date at the top changes and clubs are told by email. Questions go to hello@matchups.training.