The short version. Crease is used by adult cricket coaches. Coaches record information about the players they coach, some of whom are children. That information lives in a database in Sydney, is shared only with coaches at the same facility, and parts of it are sent to an AI provider to write a session plan. We do not sell it, we do not advertise, there are no tracking or analytics products in the app, and a coach can delete their account and everything in it from inside the app.
1. Who this is from, and who it is about
Crease is a cricket coaching app: coaches plan training sessions, run them, and track how players are developing. This policy covers the app and this website.
Two kinds of people appear in it. Coaches are our users: adults who create an account and use the app. Players do not use the app and do not have accounts; their coach records information about them so the app can plan their training. Players are often children, so section 7 is written for their parents and for the clubs they play at.
We have written this policy around the Australian Privacy Principles (the APPs) in the Privacy Act 1988 (Cth), and we intend to follow them whether or not the Act's small business exemption applies to us. Crease is operated from Australia. The legal entity behind it is being set up, and its registered name and address will be printed here before the app is available to the general public.
2. What we collect
From you, the coach
- Your email address and password. The password is handled by our authentication provider and stored only as a secure hash. We never see it.
- Your name, and the profile you fill in so the app can plan realistically: coaching level, years of experience, the equipment and space you have, any limitations on what you can demonstrate, and the facility you coach at.
- Anything you write in the app: session notes, feedback reports you send us about the app itself, and your answers in the Learn section.
About the players you coach (you enter all of this)
- Name, and a short player handle if your facility uses one.
- Birth month and year. Not a full date of birth. The app does not store, ask for, or have anywhere to put the day of the month. Month and year are enough to work out an age, and the age is what drives the junior bowling limits and the age gates.
- Cricket profile: batting, bowling and fielding levels, batting and bowling styles, competition grade, focus areas, goals, what motivates them, how they learn best, fitness level, maturation stage (a coaching judgement about growth, used for the junior workload rules) and any physical limitations you record.
- Session plans and the sessions you run from them: title, focus, length, intensity, equipment, the plan content itself, who took part, and how you rated the session afterwards.
- Check-ins. Before a session: a five tap answer to "compared with your usual, how are you today", whether anything is off today (tired, sore, flat, short on sleep, or nothing), and if sore, where it is, chosen from a fixed list of body areas. After a session: effort, enjoyment, whether they felt they improved, how many balls a bowler bowled, and any note you add.
- Skill test results: the test, the score, the units and the conditions you did it in.
- Development goals: targets you set for a player, the baseline, and the evidence you record against them.
- What happened during a session: notes you type while coaching, wickets, and the tap counts from the capture pads (for example how a batter met the ball). Free text here is capped at 80 characters by the database itself.
- A photo, only if you add one. A photo of a player is optional and is never asked for. If you add one, the app shrinks it, saves it again as a plain JPEG - which removes the hidden camera information a phone photo carries, including where and when it was taken - and stores that copy in a private area only your facility's coaches can reach. One photo per player; adding a new one replaces it, and removing it deletes it. For a player under 18, or a player whose birth month you have not recorded, the app requires you to tick "I have the parent's OK to add this photo" first, and it records that you ticked it and when.
- Your own notes about a player, filed under a date on that player's calendar. Capped at 1,000 characters by the database. These are private to you: see section 3.
- Bookings: the times you block out for a player and the one line steer you write for what that session should work on.
- If you tick "this player is me" on your own roster entry, the sessions you then create for yourself are marked as your own training rather than coaching, so our pilot numbers do not count them as coaching.
From the app, automatically
- Usage events: which screen was opened, which action was taken, your coach id, and record ids and counts. No names and no free text ever go into these events, which is checked by automated tests rather than left to care. There is no advertising id, no device fingerprint, no location and no IP address in them, and no third party sees them: they are rows in our own database.
- AI usage counters: how many generations you have run today, so we can hold the daily and per minute limits.
- Crash reports, through Sentry. These carry the error and the stack trace, the app and device version, and your account id as a bare identifier. Names, emails, screenshots, session replay and message text are stripped before anything leaves the phone. Nothing about a player is in them.
On this website
Nothing, unless you type it in. This site sets no cookies, runs no analytics and makes no request to any third party. Its typefaces are served from this site itself, not from Google Fonts or anyone else, so loading a page tells nobody but us that you were here. If you submit the waitlist form, your email address is sent to us and stored so we can email you back. While the waitlist is switched off, the page tells you so and asks you to email us instead.
3. Who can see what
Every read and write is checked in the database against the account making it, not just in the app.
- Shared with the coaches at your facility: player profiles, a player's photo if you added one, session plans, check-ins, skill tests, development goals and bookings. This is deliberate. If a colleague covers your session, they need the facts about the player in front of them.
- Private to you, and to nobody else: the dated notes you write on a player's calendar, and the notes you type during a live session. No other coach can read them, including a coach covering that same player, and including a facility administrator. The app tells you this on the screen where you write them.
- Us: we can reach the database as its operators, in order to run it, fix it and back it up. We do not read coaches' notes as a matter of course and we have no feature that surfaces them to us. If you send us a feedback report from inside the app, we read that report; it carries what you typed plus, if you attached it, the id of the session you were looking at, and never a player's name.
- Nobody else. We do not sell data, we do not share it for marketing, and there are no advertising or analytics companies in the app.
4. What we use it for
- Running the app: storing your players, plans, check-ins and results, and showing them back to you.
- Generating coaching content with AI (section 5).
- Safety rules that depend on age and workload, such as the junior bowling limits.
- Holding fair use limits on AI generation.
- Fixing crashes, and understanding whether coaches are actually using the app during the pilot.
- Answering you when you contact us.
5. AI processing
Crease uses Anthropic's Claude models to write session plans, drills, insights and report drafts. The app itself holds no AI key: every request goes through our own server, which authenticates you, holds the key, and enforces the limits.
What is sent when you generate a session: the player's first name only, their age as a number, their levels and styles, goals and focus areas, any limitations, maturation and fitness, recent session context, recent check-in readiness including where they said they were sore, and skill test lines. In a group session, if two players share a first name, one gets a surname initial to tell them apart.
Your own notes about the selected players go too, and this is worth reading twice. Up to five of your most recent notes per player, each shortened to 200 characters, up to about 900 characters per player, ride along with the rest of that session's information so the plan works on what you have actually been seeing. Before the app builds anything it shows you how many notes it will send and the exact words, and you can switch them off for that build. Only your own notes about the players in that session are ever used, and never another coach's.
What is never sent: surnames (other than a single initial in the group case above), the birth month and year (only the age number worked out from them ever travels), your notes about players who are not in that session, the notes typed during a live session, and anything at all from the crash or usage data.
Training. Anthropic's commercial terms state that "Anthropic may not train models on Customer Content from Services" (anthropic.com/legal/commercial-terms, section B), and their published API position is that inputs and outputs are deleted within 30 days of receipt, with exceptions for legal compliance and enforcement of their usage policy. We do not use your data, or your players' data, to train any model of our own, and we do not give it to anyone else to train theirs.
AI output is a suggestion, not instruction. The coach reviews every plan before using it. The app says so, and the terms of use say so.
6. Where your data lives, and what leaves Australia
- The database and your account: Sydney, Australia.
Our Supabase project runs in the
ap-southeast-2region. Connections are encrypted. - AI requests: the United States. The information listed in section 5 is sent to Anthropic in the US for the length of that one request, and the plan comes back. We store nothing there.
- Crash reports: the European Union. Sentry's EU region receives the scrubbed crash data described in section 2. It contains no player data.
- App updates are delivered by Expo. They carry no personal information.
Sending information overseas is a disclosure under APP 8, so we have set it out plainly here rather than burying it. Those three are the only places your data goes.
7. Junior players
This is the part of the app that matters most, so it gets its own section.
Children do not use Crease. There is no player login, no child account, and no way for a player to sign in. Everything about a player is entered by an adult coach. The one screen a player may ever touch is the pre-session check-in, when a coach hands them the phone for a few taps: how they feel compared with their usual day, whether anything is off, and where it is sore if it is. That screen has no keyboard on it and asks for no free text, on purpose.
Consent is obtained by the coach, before a child goes in. Coaches must have the right to record a child's details under their club's safeguarding and privacy arrangements, and parental or guardian consent where that is what the club requires. We ask coaches to do this offline, through the club, in the way clubs already handle consent for training records. The one thing the app records itself is the photo tick: before a coach can add a photo of anyone under 18 - or of a player whose birth month has not been recorded - they must confirm they have the parent's OK, and the app stores which coach confirmed it and when. That is a record that a coach answered a question; we hold nothing about the parent themselves.
We collect less than we could. No day of birth, only the month and year. No parent or guardian contact details, at all. No medical records. No video of players at all. A photo is optional, off unless a coach adds one, and never leaves the app: it is not published anywhere, not sent to the AI, and not included in the report a parent reads. A player's report for a parent is not emailed by the app: the coach copies it and shares it themselves, so we never hold a parent's address.
What coaches are told when they write a note. On the screen where a coach writes a dated note about a player, the app tells them: "Only you can read your notes. Nobody else sees them, not even another coach covering this player." Coaches are asked to keep notes about the player's cricket. Notes are capped at 1,000 characters, and the notes typed during a live session at 80 characters, and both caps are enforced by the database rather than only by the app, so there is no unbounded free text store about a child anywhere in this system.
If you are a parent or guardian and you want to know what is held about your child, want it corrected, or want it deleted: email hello@creasecricket.com and tell us the club, the coach and the player's name. Please also speak to the coach, because in most cases they can show you the record and delete it themselves in a few seconds, which is faster than we can. Deleting a player in the app removes that player's profile, sessions, check-ins, skill tests and every note about them. We will act on a request from a parent even where the coach is the one who entered the data, and we will tell you what we did.
8. How long we keep it, and deleting it
- Coach and player records are kept for as long as the coach's account exists. There is no automatic expiry, because a development record only means something over years.
- Usage events are kept for at most 12 months and then deleted.
- Crash reports expire on Sentry's own schedule, which is around 90 days.
- Waitlist emails are kept until the waitlist is closed or you ask us to remove yours.
Deleting a single player: open the player, edit, and delete. That takes their profile and everything hanging off it.
Deleting your whole account: in the app, tap your initials in the top right corner to open your Profile, scroll to Danger zone, tap "Delete account", and type DELETE to confirm. This is immediate and cannot be undone. It removes, explicitly: your player profiles, session plans and their participant records, pre and post session check-ins, skill tests, player goals, your private player notes, your in session stream events, your AI usage counters, your usage events, your Learn progress, your coach profile, and finally the login itself. You can also email us and ask us to do it.
Taking your data with you: your Profile has an "Export my data" option that produces a file of everything you own.
9. Getting at it, correcting it, complaining about it
Coaches can see and correct everything they hold, in the app. If you would rather ask us, email hello@creasecricket.com. We will answer within 30 days, and normally much sooner. If we cannot give you something, we will tell you why.
If you are unhappy with how we have handled your information, tell us first at the address above so we get the chance to fix it. If you are still unhappy, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.
10. Keeping it safe
- Every table is protected by row level security, so what an account can read is decided by the database, not by the app screen.
- The AI key never leaves our server. The app cannot reach the AI provider directly, and there is a switch that stops all AI use at once.
- Free text fields have hard caps in the database.
- Crash reporting is scrubbed before anything is sent.
- We take encrypted backups.
- If personal information is ever exposed in a way likely to cause serious harm, we will follow the Notifiable Data Breaches scheme: assess it, notify the OAIC and notify the people affected, and tell the coaches and clubs involved.
11. How we change this policy
When the app changes what it collects, this page changes in the same release, and the effective date at the top moves. For a change that materially affects players or coaches, such as photos, video, or sending anything to a new third party, we will update this page before the feature ships and tell coaches in the app or by email. Old versions are kept in our source history and we will send you one on request.