Jameel Stuart Cricket Academy
This explains what the JSCA Player Development app holds about a player, who can see it, where it goes, and how to get a copy of it, correct it or have it deleted.
Last updated 4 October 2026
This app holds information about children. It is used by one coach, by parents and guardians, and by players themselves. We have written it in plain English because the people it is about — including the children — should be able to read it.
Where something protects you less than you might assume, we say so on this page rather than leave you to find out.
Jameel Stuart Cricket Academy Ltd is the data controller — we decide what is held and why. To reach us about anything on this page, email jameelstuartcricketacademy@gmail.com or call +44 7432 795503. We coach in Bolton and across Greater Manchester. If you would rather write to us by post, ask and we will give you the address.
| Profile | Name, date of birth, the teams they play for, how they bat and bowl, club, school, pathway and playing level. |
|---|---|
| Cricket record | Assessments and scores, four-week plans and homework, session notes, block reviews, match figures and post-match reflections. Some of this is about physical performance — how a player moves, strikes and holds up under pressure — which app stores classify as fitness information. |
| A rating we calculate | A single “Skill Index” number worked out from the assessment scores, used to track progress across a block. Families see a word rather than the number unless the coach turns scores on. |
| Notes | Anything a coach, a parent or a player writes to one another in the app. |
| Photos and video | Photographs and clips recorded in a session, only where photo permission has been recorded for that child. A profile headshot is the one exception — see below. |
| Account | Email address and a password, which is held by our hosting provider in a form we cannot read. We never see it. |
| Notification token | If notifications are switched on, an anonymous code identifying the handset, so a message can reach it. It is deleted when that person signs out. |
It is held in the academy's own database, hosted in London, United Kingdom by Supabase. A copy is also kept on the device so the app works without a signal. That on-device copy relies on the phone or tablet's own protection — we do not add a second lock of our own, so a shared device should have a passcode.
Under UK data protection law we have to name a lawful basis for each thing we do.
These limits are enforced by the database itself, not only by what each screen chooses to show.
The coach can create a shareable web page for a player. Anyone with that link can open it — there is no login. So it is worth being exact about what is on it, and we have checked a real card rather than described one from memory: the player's full name, their age, how they bat and bowl, their position, the club and team they play for, their pathway and playing level, their Skill Index number, the coach's one-line note of what they are currently working on, their scores in all five assessed areas, and their season record innings by innings — including the opposing club and the date of each match. A photograph appears only where photo permission has been given, and that is re-checked every time the page is opened — so withdrawing permission takes the photo off a card already shared, without the coach touching anything.
That is a lot about one child on a page with no password, so the protections around it matter: the address is a long random string nobody can guess, it stops working after 90 days, the page asks search engines not to index it and not to keep a copy, and the coach can switch it off at any time. A card exists only if he makes one. If you would rather no card existed for your child, say so and it will be turned off.
The app uses Google Gemini for two different jobs, and they send different things, so we describe them separately rather than give you one list that is only true of half of it.
When anyone asks the in-app assistant a question. Sent: the player's first name; their age in whole years; how they bat and bowl and their player type; the coach's two short notes on what the player is working on and what is holding them back; their Skill Index and assessment scores; and short summaries with dates of sessions, plans, matches, reviews and assessments. Titles go too — of homework tasks, programmes, milestones, drills and video clips — and the coach wrote those, so they are his words.
When the coach taps a "draft this for me" button. This is how he gets a first draft of a session note, a block review, a match analysis or drill ideas, which he then edits himself. It sends the same short player description as above, and it also sends the coach's own working notes for the thing being drafted — because that is the material the draft is made from. For a session note that is his shorthand, which may be most of the note. For a block review it includes the strengths and limiters he typed into the assessment. For a match it includes the figures and how the player got out. For a plan it also includes how the player best takes instruction.
Never sent, on either route: a surname. A date of birth. An email address or any account identifier. Club, school, teams or pathway — a school name beside a child's first name and age would locate them in the world. Photographs or clips. And the words a parent or a child writes: a parent's note of concern and a child's private reflection to their coach are never used as material for the model, on either route. The coach's own prose about his own coaching does go, as described above, and we would rather say that plainly than imply no writing ever leaves.
Requests go through the academy's own server, which passes them on without keeping them. We keep a count of how many questions each account has asked and when it last asked one, to cap costs — never the questions or the answers. Google processes what it receives under its own terms. The coach can also enter his own key for Google or for Groq; if he does, his drafting requests go to that provider directly rather than through our server, and are not screened by it on the way.
There is a microphone button beside the assistant. If it is used, the recording is transcribed by the device maker, not by us: on an iPhone or iPad that means Apple, which may do it on the device or may send the audio to Apple to do it; in a web browser it is normally Google. We never receive or store the audio — only the text it produces, and only once it is sent as a question. The button is optional and typing works everywhere.
Where notifications are switched on, the message on a lock screen carries a child's first name and a short fact such as "a new note from Coach Jameel". It never carries the contents of a note, a score or an assessment, because a lock screen can be read by anyone holding the phone.
The database and the files are in the United Kingdom. Some of the companies that help run the app are based in the United States, and data reaching them may be processed there: Google, Groq, Expo, and Apple or Google for notification delivery and voice transcription. Those transfers rely on the standard legal protections each provider offers for international transfers. If you want the detail for a particular provider, ask and we will point you to it.
The coaching record is kept while the player is at the academy, and for a period afterwards, because a player who returns should not start from nothing. We will be straight with you: there is no automatic deletion yet. Nothing is erased on a timer. If you want a record removed, ask and we will remove it — see the next section.
You can ask us to:
Email us and we will answer within one month, free of charge. A parent or guardian can make any of these requests for their child. A child can ask us directly too — they do not have to go through a grown-up to ask what we hold about them, and we will not be annoyed about it.
Two of these have buttons in the app:
It does more than remove that parent, so it should not be a surprise: it also switches off the child's own login and withdraws photo permission for that child, until a parent or guardian is linked again and gives it. The coach can hand the login straight back once that happens. If another parent or guardian is already linked to the child, none of that changes.
From the moment it is withdrawn, three things happen at once: no new photograph or clip of that child can be added, the ones already held stop showing to the family, and the child's photo drops off any player card link already shared.
What it does not do is delete anything. The files remain in storage and the coach can still see what he has already taken. A profile headshot also stays, though it stops appearing on a card. Deletion is a separate request — just ask, and we will.
There is one further limit we would rather state than have you discover. The coach can add a clip by pasting a link to it on another site, such as Google Drive, instead of uploading it here. A clip added that way follows that site's rules and not ours: the address does not stop working, and withdrawing photo permission does not reach it. It keeps working until someone removes the file where it actually lives. You can ask the coach which kind any clip of your child is.
When a photograph or clip is deleted it stops being reachable from the app at once, and the file itself is queued to be erased from storage. That queue is now emptied automatically every fifteen minutes, so the bytes normally follow within the hour. If you need confirmation that a particular file has actually gone, ask and we will check and tell you.
Everything travels encrypted. Photographs and clips are kept in private storage, not on the open internet: to show you one, the app requests a temporary address that stops working about an hour later. Access is enforced per account at the database level, so one family's device cannot request another family's records at all. As noted above, the copy held on your own device is protected by that device, so please keep a passcode on a shared phone or tablet.
We do not sell anything, we do not advertise, and there is no advertising or tracking technology in this app. The only counting we do is the usage meter described above, which exists to cap costs.
This app is built for school-age cricketers and the people who look after them. A child never signs themselves up: the coach creates a player's login, and the app will not create one at all unless a parent or guardian is already linked to that child — a child's private channel to an adult with no parent attached is not something we will build.
A parent can see what their child writes to the coach from 24 September 2026 onward, and children are told this on the privacy screen inside the app rather than left to assume otherwise.
If something in the app worries a child, they can tell the coach, tell their parent, or tell us by email. If they would rather tell somebody with no connection to the academy at all, Childline is free, confidential and open to under-19s on 0800 1111.
Everything above is about the app. The website you are reading this on collects nothing: it sets no cookies, carries no analytics and no tracking of any kind, and stores nothing you type.
The one place it takes any input is the enquiry form on the Contact page, and that form does not send us anything by itself — it opens WhatsApp with your message already written, and nothing leaves your device until you press send there. Once you do, it is an ordinary WhatsApp message: Meta carries it under their terms and we read it on the coach's phone. If you would rather not use WhatsApp, email or phone us instead and it never touches them.
If you are unhappy with how we have handled your information, please tell us — we would rather hear it and fix it. You do not have to come to us first, though: you can go straight to the Information Commissioner's Office, which regulates this in the UK.
ICO, Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF · helpline 0303 123 1113 · ico.org.uk