Privacy Policy
The short version
Gully Cricket Scorer works offline. It has no account system, no analytics, and makes no network requests — with three exceptions, all of which you switch on yourself. Share live sends one match, ball by ball, to a cloud service so people you give the link to can watch it. Publish puts one tournament on a public web page at a link you hand out, with players' and teams' names in full unless you choose initials. And a community shares a group's cricket between the phones that score it, so the table and the records agree. The app's website counts its visits, without cookies (section 8); the app itself does not.
The only ways copies leave the app's private storage are ones you start yourself: exporting a backup, saving or sharing a scorecard, sharing a roster or a tournament, turning on live sharing, publishing a tournament, or joining a community. If you have Android Backup switched on, your app data is also included in your own Google account backup.
The three are not the same promise, and the differences are the point. A live scorecard is deleted by itself about a week after its last update. A published tournament page is meant to last, and only the phone that published it can take it down — or, if it was published for a community, that community's admins. A community archive is meant to last too, and it belongs to the group rather than to you — leaving does not take back what you contributed.
1. Who we are
Gully Cricket Scorer is developed and published by K4 Technologies. For any question about this policy or your data, contact k4.technologies.dev@gmail.com.
For everything except live sharing, publishing and communities, the app transmits nothing to us: we hold no data and your match records exist only on devices you control.
Those three are the exceptions, and we would rather be plain about them than bury them. Each puts a copy of something into a Google Firebase database that we operate: a match, ball by ball, while you are sharing it live, the page of a tournament while it is published, and — if you join one — a community's roster and the cricket its members contribute.
For those copies we are the data controller and the responsibilities in this policy, including erasing them on request, fall to us. The community case is the largest of the three by some distance, because it is not one match or one season but a group's cricket, held for as long as the community exists. Everything you never choose to share, publish or contribute stays outside our reach entirely.
2. Information we collect
Nothing, unless you switch on live sharing, publish a tournament, or join a community. We never sell your information, and there is no analytics or advertising anywhere in the app. Specifically, the app does not:
- Ask you to create an account, sign in, or provide an email address
- Contain analytics, telemetry, advertising, or crash-reporting SDKs
- Read your contacts, location, camera, microphone, calendar, or accounts
- Send anything anywhere while live sharing is off, nothing is published, and you are in no community — in that state it makes no network requests at all, and works fully in aeroplane mode. The one exception finishes something you already asked for: if an Unpublish, or taking a live link off a page, could not get through at the time, the app tries again when it is next opened (sections 5a and 11). A live share whose deletion did not get through is not retried: it is left to its seven-day expiry (section 5a)
The three exceptions are Share live (section 5a), Publish (section 5b) and communities (section 5c). All three are off until you turn them on, and scoring works the same offline in all of them. Opening somebody else's live link or published page also makes a network request, for the obvious reason. And the web version of the app, at app.gullycricketscorer.k4tech.in, is a website: opening it loads the app from the company that hosts it (section 8), as opening any website does.
3. What the app stores on your device
Everything you enter while scoring is written to the app's private storage on your device:
- Team names, player names, and the venue you type in
- Ball-by-ball scoring data, scorecards, and any commentary you add
- Your saved player roster — the names and nicknames, and any notes you add to them, that you reuse from one match to the next
- Your saved teams, tournament squads, fixture schedules, competition rules and results
- Your theme preference
- Matches and tournaments you have deleted, for up to 30 days, so you can restore them (section 11)
- If you have ever used live sharing, or taken over a match from another phone: which match is being shared and its link, so sharing survives closing the app, plus the two identifiers described in section 5a. For a match you handed over to another phone: which match, the link it is now scored at, and the label that phone goes by in the community. And if the app has put a link to that match on a published tournament page, or has sent one and not heard whether it arrived (sections 5a and 5b): which page and which fixture, so that it can take the link away again. It notes this just before it sends the link, because a link sent as the signal drops can reach the page after the app has stopped waiting for it
- If you have ever published a tournament: the anonymous identifier described in section 5a, which tournaments are published, each page's link, what you chose to show on it, and any page you unpublished that the app has not yet been able to take down (section 11). For a page you published from your own phone this is the only thing that can update or unpublish it, so it is worth knowing it lives on this device and nowhere else, apart from your own Android backup if that is switched on (section 6). A page published for a community does not depend on it (section 5b)
- If you have opened a published tournament page in a browser: a copy of that page, and of the ball-by-ball detail of any match whose ball-by-ball or graphs you opened on it, kept by that browser so that opening the link again does not download it again. It holds what the page showed and nothing about you. Section 5b says how long it is kept and how to remove it
- If you are in a community: the anonymous identifier described in section 5a, which communities you belong to, your role in each and when you joined, which player you said you are, whether one has been closed, the name of any you were removed from until you dismiss that notice, a recovery code if you created one, and a copy of what the community has shared — its roster, the entries removed from it that can still be restored (section 5c), the cricket its members have contributed, and the link of any page the community has published with which admin's phone keeps that page up to date. That copy is what lets the app work at a ground with no signal
- A copy of each file you have sent through Android's share sheet — a scorecard, a tournament's PDF or its file — in the app's cache folder, which is how the file is handed to the app you chose. The app does not clear it: it stays until Android clears the cache, you clear it in Settings, or a file of the same name replaces it. It is not part of your Android backup
- Once you have used live sharing, publishing or a community: a short list kept by Google's Firebase code of the recent days on which it was used (section 5a)
- If you have used camera mode on Android: the YouTube stream key you last entered on this phone (never the community's, which is read each time and not kept), and the recordings it made, each with a small file beside it naming the live link it was of and when it started (section 5d)
This storage is sandboxed by Android and is not readable by other apps, with one exception: camera mode's recordings and the small file beside each (section 5d), which on Android 10 and older another app with permission to read the phone's storage can read. In the web version it is that browser's storage for the site, kept apart from other sites by the browser, and cleared with the browser's data for the site.
4. Permissions
The app declares nine permissions. None is used to gather information about you. A fifth entry can appear in a list of the app's permissions, ending DYNAMIC_: an Android library adds it, it is internal to the app, and it gives the app access to nothing.
| Permission | When it applies | Why |
|---|---|---|
INTERNET |
Always declared | Required by the Android System WebView the app is built on, and used by Share live, by publishing, and by a community's shared roster and cricket when you turn them on. With live sharing off, nothing published and no community joined, the app makes no network requests and functions fully in aeroplane mode. A community is the one of the three that keeps working on its own afterwards: while it is selected on the home screen, its roster and cricket sync when the app starts, when you select it, and a couple of seconds after the roster on the phone changes — which includes a new name being typed into a match — or after a match or tournament of the community's is finished or changed on it, and every five minutes while the app is on screen on a phone that has published a page of one of the community's tournaments (section 5c). |
CAMERA |
Android, camera mode only | Requested the first time a scorer opens camera mode (section 5d), and used only while that screen is open, to film the match for the stream and the recording. Never requested or used otherwise. |
RECORD_ |
Android, camera mode only | Requested with the camera, for the sound on the stream and the recording. Used only while camera mode is open. |
FOREGROUND_ |
Android, camera mode only | Lets camera mode carry on recording, and streaming, with the screen locked or the app behind another one (section 5d). Started when you tap Record or Go live and record, and stopped when recording stops. Not asked for: Android grants it with the app. |
FOREGROUND_ |
Android 14 and newer, camera mode only | The same, for the camera: Android 14 asks an app to say which kinds of thing it keeps doing in the background. |
FOREGROUND_ |
Android 14 and newer, camera mode only | The same, for the microphone. |
WAKE_ |
Android, camera mode only | Keeps the phone from going to sleep while camera mode is recording with the screen off, which would cut the stream and the recording. Released when recording stops. |
POST_ |
Android 13 and newer, camera mode only | Asked for with the camera, once. While camera mode is recording, a notification says so, on the lock screen too, and has a Stop button that ends the recording properly. Refuse it and camera mode works the same, without the notification. The app sends no other notifications. |
WRITE_ |
Android 9 and older only | Requested only at the moment you choose to save a file to your Downloads folder: a PDF scorecard, a backup, a roster file, or a tournament's PDF. On Android 10 and newer, no permission is needed or requested. |
Reading the clipboard needs no permission, so it is said here instead. The app reads it at one moment only: when you tap Paste in the Join a community dialog. What it finds is put in the invite box for you to see, is used for nothing else, and goes nowhere unless you then tap Join. The app never reads the clipboard on its own. It writes to the clipboard only when you tap a button: Copy beside a link, an invite or a recovery code, which says so; and Share beside a live link or a published page's link, and Share text for a tournament, wherever the app cannot open a share sheet, which copy the link, or the table and fixtures, instead and tell you they have.
The Android app also registers itself to open a community's invite links: addresses that begin
https://, and gullycricket://. When you open
one, the app reads the invite from the link, shows you the community's name, and waits:
nothing is sent until you tap Join. It opens no other kind of link; a live scorecard or a
published page opens in your browser. To confirm that the app may open those addresses,
Android itself fetches a small file from that website when the app is installed or updated,
whether or not you ever use a community. The app takes no part in that request and learns
nothing from it.
5. When data leaves your device
Only when you choose to create or share a copy. Nine actions can move data beyond the app's private storage, each started by you:
- Export data writes a JSON backup file to your device's Downloads folder, or in a browser to wherever that browser saves downloads
- Download PDF saves a scorecard to your device
- Share opens Android's share sheet so you can send a scorecard to another app or person
- Share this roster, on the Players screen. Save as file writes your own roster — never a community's, even while one is selected on the home screen — to a JSON file, for you to send to another phone. Nothing is uploaded anywhere: the file is saved to your Downloads folder and goes on only where you send it. For each player it carries the name, any nicknames or other names, any private note you added, and the record ids and merge history (which entries were merged into which, and when) that keep one person one record.
- Share a tournament, from a tournament's screen, in one of three forms. Nothing is
uploaded by any of them; each goes wherever you send it.
- Share PDF: the points table, where the format has one, and the fixture list, with each fixture's venue, its result, and the date and time of each fixture not yet played.
- Share text: the same table and fixture list as plain text, with results and the date and time of each fixture not yet played, but no venues.
- Share file: the tournament as data, for another phone to import. It carries everything: the fixtures with their dates, times and venues, every match the fixtures name, ball by ball, and the full roster entries of the players and teams in them — private notes and merge history included. Those entries come from the roster in use: your own, or the community's while one is selected on the home screen.
- Share live sends the match you are scoring to a cloud service while you have it switched on — see section 5a
- Publish puts one tournament on a public web page, and leaves it there — see section 5b
- Joining a community shares what you score with the other people in it — see section 5c
- Camera mode streams video of the match, with the score drawn on it, to your YouTube channel — see section 5d
These files can contain the match, player, team and tournament details you entered. Once you send a file somewhere, it is governed by the privacy policy of whichever service or app you sent it to. We have no access to it and no way to retrieve it.
5a. Live scorecard sharing
Share live is off by default and exists so friends who are not at the ground can watch the scorecard update ball by ball. When you turn it on for a match:
- The whole match is uploaded, not just the numbers on the scorecard, to a database we operate on Google Firebase, and updated after every ball while sharing is on. That is everything the app keeps about the match: the team and player names, the venue if you entered one, the toss and the match settings, every ball with the time it was bowled, any commentary, rain interruptions, the result and player of the match, and when the match was created and last changed. If the match belongs to a community (section 5c) or a tournament, it carries that community's and tournament's ids too. It travels encrypted (HTTPS). Google processes it on our instructions as our service provider, under Google's privacy policy.
- You get a link to hand out. Anyone who has the link can watch; the link's long random address is what protects it, like an unlisted video. We list it nowhere and there is no directory to find it in, and the page asks search engines not to index it — the only way to it is the link you send, with the exceptions in the next two points. A link you post somewhere public can be found there like anything else posted there. There is nothing for viewers to sign into, and holding the link does not let anybody change the score.
- A published tournament page that shows full names links to it. If the match is a fixture of a tournament with a published page (section 5b), and that page shows full names, as a new page does unless whoever published it turned them off, the app puts the live link on the page while you are sharing, so that anyone who has the page's link can open your live scorecard from it. The app does this by itself when sharing starts: for a page published for a community, from the phone of any scorer or admin of that community; for a page published from one phone, only when that same phone is the one sharing. It takes the link off the page when you stop sharing, when the match is finished, or when you delete the match; if it cannot reach the page at that moment it tries again, and when the app is next opened. On a community's page it can do that only while your phone scores for that community, so when you leave a community the app first takes your links off that community's pages, and only then gives up your place in it. If it cannot reach the page at that moment, leaving goes ahead anyway. The link is then still taken off when the app is next opened with a connection if your leaving did not reach the community either; once your place there has gone the app is no longer allowed to remove it, and the link stays on the page. It stays, too, if you are removed from the community or the community is closed, which the app only finds out afterwards. Section 5b says what a reader of the page then finds. A page that shows initials is never given the link, and neither is anything else: a match that is not a fixture of a published tournament is linked from nowhere.
- A community's members see a community match. If the match belongs to a community you score for, and you have not kept it off the community, the app also lists it in that community while you are sharing it and it is in play: the live link's id, your anonymous identifier and the time, so that the community's members see the match on the community's screen, and on their home screen while that community is selected, and can open the live scorecard from there. Nobody outside the community can read that list. Stopping sharing takes the match off it, as do finishing the match, keeping it off the community, deleting it and sharing another one instead; and if your phone cannot take it off, for instance because it was lost mid-match, the next phone of one of the community's scorers to find the live scorecard gone removes it.
- Where to watch it on YouTube, if anywhere. If the match is being streamed, the shared copy can say where: a YouTube video you link for this match in the Share live panel, or the YouTube channel of the match's community (section 5c). Anyone with the link sees a Watch on YouTube button that opens it, or, for a video, a Play the video here button that plays it on the page. Nothing is loaded from YouTube until somebody taps that button; when they do, YouTube's player loads in their browser or app, from youtube-nocookie.com, under YouTube's terms and Google's privacy policy. The page tells the player only the address of the site it is on, which says nothing about the match, and where in the video to play. The app stores the video's id or the channel's handle, never a link as typed.
- When the stream went live, if camera mode streams it. So that the match's wickets and boundaries can jump the video to the moment they happened, the camera phone adds to the shared copy the time it went live (its own clock, corrected to the server's), a correction a scorer of the match's community can make to line the moments up with the video, and the anonymous identifier (section 5c) of whichever of them set it last. It goes when the shared copy does.
- Whether the toss is still to come, for a match shared before it. A match can be shared, and filmed, before its toss is recorded. Until it is, the shared copy carries a mark saying the toss has not happened yet, and while it does nobody can take over the scoring from the phone that shared it, by a handover or as an admin. It holds nothing about anybody, and the phone takes it off with its first update after the toss.
- The video, kept with the match. The video's id, when its stream went live and how far its moments were lined up are kept on the match itself too, on the phone scoring it, so they last as long as the match does rather than the shared copy. A scorer can also give a match its video, or line its moments up, on the match's scorecard in the app, during the match or after it. From there they go wherever the match goes: into your backups, to the community's copy of it (section 5c), and onto a published page as section 5b describes. Who identified themselves by lining it up is not kept.
- Two identifiers go with it. The first time you share, the app asks Firebase for a random identity for that installation — the anonymous identifier — and also makes up a random id for the device, which ends in the time it was made. Both are stored on your device and written into the shared copy, beside the match, where anyone with the link can read them. Together they say which phone is scoring, which is what lets the database refuse an update from anywhere else. Neither is an account: they hold no name, email or password, they are not linked to your Google account, and on their own they say nothing about who you are. In a community that changes: the same anonymous identifier is what your member entry is filed under, beside the label you typed for your phone and the player you say you are (section 5c), so the other members, and we, can tell which member's phone is scoring a shared match. The app asks for that identity the first time you share live, publish a tournament, or create or join a community, whichever comes first, and uses the one identity for all three.
- Scoring can move to another phone, inside a community. You can hand over scoring to another member: for a match that belongs to a community you score for, to one of that community's scorers or admins; for a match that belongs to no community, to anybody in the community selected on the home screen. Their anonymous identifier is written into the shared copy as the one being offered the match, and when they take it, their phone becomes the scorer, with its own copy of the match, and yours can no longer change it. And if a community's match, shared from a phone that scores for that community, has had nothing sent for ten minutes — a phone that went flat, or was lost — any admin of that community can take it over the same way. Either way the new scorer's identifiers replace yours in the shared copy, and the viewers carry on at the same link. Outside those two, the phone scoring it is the only one that can change the score.
- Your network connection is visible to Google. As with any internet request, contacting Firebase reveals your device's IP address and connection details to Google. The same is true for anyone who opens the link, and because the link is a web address, opening it also sends a request to Vercel, the company that hosts the web version of the app, which sees the IP address and the address asked for (section 8). We do not receive, store or look at either. Firebase's own code also tells Google, with a request, which version of it the app contains and on which recent days it was used; it keeps that list on your device, and it starts only once you use one of the three features.
- When you stop sharing, the app asks Firebase to delete the cloud copy immediately. If that request cannot reach Firebase, the document is already marked to expire seven days after its last update and Firebase deletes it asynchronously. Until deletion actually happens, anyone who kept the link may still be able to open it. The match on your device is untouched either way, and stopping never costs you any scoring data.
- Deleting the match stops sharing it. If you delete a match from Match History while you are sharing it live, the app stops sharing it exactly as if you had pressed Stop: it asks Firebase to delete the cloud copy, with the same seven-day expiry behind that request if it cannot get through, and it takes the link off a published tournament page. Sharing stops in the same way if the match leaves your phone because you left the community it came from or were removed from it; what becomes of the link on that community's page is described above. A match you scored yourself stays on your phone when you leave, and stays shared. Putting the match back from Recently deleted does not start sharing again: the old link no longer works, and sharing the match again gives it a new one. The app says so before you confirm the delete.
- Nothing else on your device is uploaded — not your player roster, not your other matches, not your saved history. Everything outside the one shared match stays offline exactly as before.
Two things worth thinking about before you send a link. The people in the match are named on the page, so treat it like the scorecard itself and hand it to people you would show the scorecard to (see section 7). And anyone holding the link can pass it on, exactly as they could forward a photo of the scorebook — if that matters for a particular game, stop sharing when the match ends and the page goes with it.
5b. Publishing a tournament
Publishing is off by default and exists so that everyone who follows a competition — the players' families, the people who did not come this week, anyone sent the link — can see the table and the scorecards without installing anything or signing in anywhere. It is a publication, not a sync, and you choose it per tournament.
When you publish a tournament:
A page is created in a database we operate on Google Firebase, holding that tournament and nothing else: its name, its format and rules, its teams and their squads, its fixtures, its results, any awards and each match's player of the match, any points adjusted or fixture decided by hand with the reason given for each, and a scorecard for each match that has been played or is being played, with the toss and any overs lost to rain. It travels encrypted (HTTPS). As in section 5a, opening the page contacts Firebase, and the company that hosts the page's address (section 8), and shows each the reader's IP address. Google processes it on our instructions as our service provider, under Google's privacy policy.
A match's YouTube video, if it has one. For a match given a YouTube video (section 5a), the page holds the video's id and, for each wicket, four and six, the innings, the over, the batter as the page names them, and how many seconds into the video it happened, so a reader can play the video on the page and jump to them. It never holds when the stream started, or the time of any ball. YouTube itself may show when a live stream started, and with it the seconds give the time of each moment, even on a page that leaves out venues and times. There is no switch for it: a match with a video shows it, and taking the video off the match takes it off the page with the page's next update. Nothing is loaded from YouTube until a reader taps Play the video here (section 8). Who can watch the video itself is set on YouTube, but anybody who can read the page has its address.
Nothing else on your device is published. Not your other tournaments, not your casual matches, not your saved roster. The page is built fresh from the tournament you chose, so there is nothing in it that could carry the rest.
Players you have merged are shown as one player. If the roster says two records are the same person, because you merged them on the Players screen, the page counts them as one, as the app does: one row in its Player leaders and one entry on a side's list. Your phone uses the roster to work that out, and sends none of it: no name, nickname or note from the roster is on the page or in its ball-by-ball records, and no record id. The roster used is your own, or the community's for a tournament that belongs to a community you are in. Which of the two is decided by the tournament, not by which community is selected on the home screen, so a merge made in a community's roster does not change the page of a tournament that is not that community's unless it comes to be in your own roster as well. The app copies it there itself in two cases. When your phone stops being in the community, because you leave it, are removed from it or close it, the app keeps in your own roster the merges that join two records in matches you scored yourself or in your own roster, so that each stays one player in your app. And when a player you wrote a private note about leaves the community's roster, the note moves to your own roster (section 5c), and where you had no entry of your own for that player it takes the player's entry with it, merges included. From then on they are one player on such a page too, and the page is updated as it is for a merge you make yourself. What a reader can tell from it is that two rows they may have seen before were one person.
A player you rename in the roster is renamed in your tournaments' squads, and so on their pages. A page shows the names its tournament and its matches hold, and renaming a player in the roster, on the Players screen or from a match being scored, changes one of those: the app writes the new name into the squads of your tournaments that the player is picked in, finished ones included, on your phone. If such a tournament is published, its page is rewritten with the new name in its squads and its Player leaders: in full if the page shows full names, as initials otherwise. The roster a tournament follows is the one its merges come from, above: your own, or the community's for a tournament of a community you are in. So a rename any member makes in a community's roster reaches the squads of that community's tournaments on each member's phone when it syncs, and the community's page once the phone that keeps the page has synced. Squads your phone takes in with another copy of a tournament, from the community's sync or from a backup or file you import, are named the same way, as your phone's copy of that roster names their players, so a change another phone made to the tournament before it had the rename does not put the old name back. Matches already scored and awards already given keep the name they were entered with, and on a page of initials a player with two spellings is written as one. A nickname or a note is never on a page, renamed or not.
Player and team names are shown in full unless you turn that off. The publish screen has a switch, Show full names, and for a tournament that has no page yet it starts on. Turned off, names are shortened to initials: "R.S.", not "Rahul Sharma" — in the table, on the scorecards, in the results and in the dismissals. A published page is permanent, readable by anyone with the link, and names people who did not choose to publish anything, so before anything is sent the screen says what anybody with the link will be able to read as the switches stand, and says to turn both off if children are playing unless their parents have agreed (section 9). With full names on, the page also links to a match being shared live, described below.
Where and when the games are is shown unless you turn that off. Show venues and times is a second switch, and it starts on too. It is a switch of its own because, for a side of children, a permanent page saying where they will be on Saturday at four is a different disclosure from a scorecard. Turned off, the page says nothing of venues, or of the date and time of any fixture not yet played.
Both switches started off until October 2026, and a page keeps the choices it was published with. The change is to what a new page starts with. A page published earlier, or with a switch turned off, is not changed by it: it shows what it showed, until somebody who can update it changes a switch. A copy of the Android app from before the change still starts with both off.
The tournament's own name is never shortened. It is on the page as you typed it, whatever the switches say, so if it names a person, a school or a ground, the page does too.
The day each match was played is on the page whatever that switch says. The page lists its results newest first, and each one says the day it was played, which it could not do without knowing. It is the day only, with no time of day, and only for a match the page already shows: one that has been played, or is being played. It is taken from when the first ball was bowled, or from when the match was set up if no ball ever was, and worked out on your phone, in your phone's timezone. The switch still decides everything it did before: the venues, and the date and time of every fixture not yet played. A page published before this was added gains the days the next time your phone updates it, which it does by itself.
On a page of initials, names in commentary are shortened too, as far as we can recognise them. A player's name written in a remark, or in the reason typed for a decision or an adjustment, is replaced with their initials, whether you wrote it in full or wrote only a first name or a surname. Team names are matched in full.
Four kinds go out as you typed them. A nickname or a set of initials, and a spelling that differs from your squad, because the app has never been told those are names. A first name or a surname on its own that you typed without a capital — a name written in full is shortened however it is typed, but we only shorten a part of one where it is capitalised, because otherwise a squad containing an ordinary word as a name would have that word shortened all through your commentary. And a first name or surname of one or two letters written on its own — Jo, Li, Om — because that short it is as often an abbreviation as a name.
So: write people's names the way they appear in your squad, and start them with a capital, and they will be covered.
The link is unguessable and unlisted. It is a long random address, we list it nowhere, the page asks search engines not to index it, and nothing offers a directory of published tournaments. But anyone holding the link can pass it on, exactly as they could forward a photo of the scorebook, and a link posted somewhere public can be found there like anything else.
It uses the same anonymous identifier as live sharing (section 5a) to prove that later updates come from your phone. It is not an account and on its own says nothing about who you are. It is stored in the page and in each ball-by-ball record, where anyone with the link can read it, as in section 5a, and it is the same on every page and live scorecard from your phone, so somebody holding two of your links can tell that they came from one phone.
The page keeps itself up to date. When a result changes or a scorecard is corrected, the page is rewritten. So it is when two players on the page are merged, or separated again, in the roster, and when a player in its squads is renamed there. There is nothing to press.
Changing your mind about what is shown. You can turn either switch off after publishing, and the page is rewritten. That changes what a reader loads from then on — though a reader who has opened the page before may be shown the copy their own device kept for a while first (see "A reader's device keeps a copy" below). It cannot take back what people have already read, and it does not change the link, so the same audience keeps access. If what you need is for the existing link to stop working, that is Unpublish — publishing again afterwards gives a different address.
A page with full names on links to a match being shared live. While a fixture of the tournament is being shared live (section 5a), the phone scoring it writes that live scorecard's link onto the page, and the page shows the fixture as live, with the link, to everyone who opens it. What that means:
- The live scorecard has more in it than the page does. Behind it is the whole match as section 5a lists it: every player's full name, the venue of that match if one was entered, every ball and any commentary as it was typed. The live scorecard does not display the venue, but the shared copy it is drawn from holds it, where anyone who has the link can read it, whether or not the page shows venues and times. The publish screen says this where full names are switched on. There is no separate switch for the link: it comes with full names, and only with full names.
- A page that shows initials never links to a live scorecard. The link is kept in the page itself, where anyone holding the page's link could read it, so it is not enough for the page to leave it undrawn: it is never put there. The scoring phone checks what the page shows before it sends anything, our database refuses a live link on a page that does not say it shows full names, and turning full names off removes any link from the page in the same update that shortens the names. To make that possible the page records that it shows full names, as a yes beside the tournament, whenever it does.
- Who writes the link. On a page published for a community (below), the phone of any scorer or admin of that community that is sharing one of the tournament's fixtures. That link, and taking it away again, is the only thing a scorer's phone can change on the page. On a page published from one phone, only that phone, when it is the one sharing the match.
- When it goes. The scoring phone takes the link away when sharing stops, when the match is finished, when the match is deleted, and, on a community's page, when it leaves that community. If the match is handed over to another phone (section 5a) the link stays, and that phone takes it away at the end. A phone that goes flat or is lost mid-match leaves its link on the page, and so does a phone that could not take its link away before it stopped being in the community (section 5a). Once the page shows that fixture's result it no longer shows the link; until then the link leads to the live scorecard for as long as that exists (at most seven days after its last ball, section 5a), and after that to a note that the match is no longer live.
- Turning full names off takes the link off the page, not the live scorecard off the internet. Anyone who already opened the live scorecard, or kept its link, can go on opening it until sharing is stopped on the phone scoring the match.
How long it lasts, and who can remove it. A live scorecard expires by itself about a week after its last update. A published page does not: it has no expiry at all, deliberately, so that a season is still readable years later. That has a consequence worth being clear about — for a page you publish from your own phone, that phone is the only thing that can take it down. Press Unpublish and the page and its scorecards are deleted and the link stops working — except on a device that has opened the page before, which can go on showing its own saved copy for a while, as the next paragraph describes. If that phone is lost, wiped, or has the app reinstalled, the page stays readable and neither you nor the app can change or remove it; write to us at the address in section 14 with the link and we will delete it.
A reader's device keeps a copy. When somebody opens a published page, their browser saves a copy of it on their own device, and of the ball-by-ball detail of any match whose ball-by-ball or graphs they open on it, so that opening the link again shows the page without downloading it again. The copy is what the page showed, including the link to any match that was live when it was saved, and for a community's page the community's id that the page records, so that a live match opened from it can be checked as one of that community's. It is kept under the page's address. Nothing about the reader is stored with it beyond the time it was saved, and it is not sent anywhere. A page shown from a saved copy says so, and from when, beside a Refresh button that fetches the current one. There is one kind of page no copy is kept of: one that does not carry a valid date of when it was last written. A date more than a day ahead of the clock on the reader's device is not a valid one. Every page the app publishes carries that date, and it is added when the page reaches us: we accept no date that a phone chose for itself. So this is one of three things: a page written by something other than the app; a page opened on a device whose clock is more than a day slow; or your own page, opened in the same browser tab or app session you published or updated it from before we have confirmed that update. It is shown, without a "Last updated" line, and neither it nor the ball-by-ball detail of its matches is saved on the reader's device; a copy of that page saved earlier, when it had a date, is deleted.
What that means for you as the organiser is a delay, and it is worth being plain about. A device that has opened the page shows its saved copy, without checking with us, for up to 5 minutes while the tournament is still being played, and for up to 24 hours once you have marked the tournament completed and no match on the page is still in progress. So a correction, or a switch you turn off, can take that long to reach somebody who has opened the page before, and so can a match starting to be shared live, or stopping. And unpublishing deletes what we hold, but a reader's saved copy can outlive it by up to that long: a page you took down this morning can still open, from their own device, for a reader who looked at it yesterday evening. A device with no connection goes on showing its saved copy, labelled as one, until it can reach us.
A saved copy is deleted when that device next asks us for the page and finds it gone. Whatever happens, a device never shows a copy more than 7 days old, and deletes one that old the next time a published page is opened in that browser. It keeps copies of at most 8 pages and the ball-by-ball detail of at most 24 matches, the oldest going first. A reader can remove them at any time by clearing the browser's data for the site. Nobody else can: we cannot delete a copy on somebody else's device, and neither can you, any more than a screenshot they took. The one exception is a browser the app itself is used in: if you use the app on the web, publishing, updating or unpublishing a page removes that same browser's saved copy of it, so the next time you open the link there you see the page as it now is. That covers what the app in that browser sends itself, and nothing else. Updating includes taking a community's page over and moving a page into a community (both below), and for a page published for a community it holds for the browser of whichever admin does it. Three limits:
- The copy is removed once the change has been sent. An update cut off part way, by a lost connection or by closing the app, can have changed the page without removing the copy: it goes when the app next sends that page in full, and until then it lasts as any reader's does.
- Where an Unpublish that cannot be sent at the time turns the page off in the app, the copy is removed then, and the page itself is taken down when the app next has a connection (section 11). If you open the link in that browser in between, while the page is still up, the browser saves a copy again, and the app removes that one when it takes the page down. One case ends differently, for a community's page: if that phone stopped being an admin of the community before the takedown could be sent, the takedown is refused, the page stays up, and the copy removed when Unpublish was pressed is not put back. The app turns the page off without waiting for an update to that page that was itself still waiting for a connection: as Unpublish is pressed for a page published from that phone alone, and within ten seconds for a community's page that phone keeps up to date. If the app is closed in those seconds, the page has not been turned off, nothing has been taken down and the copy stays (section 11).
- An Unpublish that is stopped as it is pressed takes nothing down and leaves the copy: one that could not reach the page (section 11), or one that is refused there and then because that phone can no longer take the community's page down.
In every other case a browser the app is used in is a reader like any other, and its copy lasts as any reader's does, as described above. That includes every change to a community's page made from another admin's phone: an update, a takeover, an Unpublish. On news of such a change from the community the app removes the copy in some cases and not in others, and nothing here promises that it will. Putting a live link on a page, or taking one off, is not an update in this sense and removes no copy, on the phone that does it or anywhere else. A page published from the Android app and opened in the phone's browser is not covered by that exception either: the browser is a reader like any other, and Refresh is how you see a change at once.
Deleting a published tournament from the app takes its page down at the same time, because the tournament screen is the only place the Unpublish button lives. The exception is a page published for a community, below: deleting your copy of that tournament leaves the community's page up.
A page published for a community. If the tournament belongs to a community (section 5c) and you are an admin of it, Publish creates the page as the community's rather than as your phone's. What that changes:
- Any admin of that community can update the page, change what it shows, or unpublish it, from their own phone — including somebody who becomes an admin later. The page does not depend on the phone that published it, and it stays up if the admin who published it leaves the community or loses their phone.
- One admin's phone keeps the page up to date at a time, from the community's cricket as that phone last synced it: when a match or tournament of the community's changes on it, and every five minutes while the app is open on its screen (section 5c). A result another member scores is therefore on the page within a few minutes while that phone has the app open with the community selected, and otherwise the next time it is. If that admin leaves, is removed or stops being an admin, the next admin's phone to sync takes over. Another admin can also take it over from the publish screen, for a phone that is lost or no longer used.
- A phone that takes a page over keeps the choices already made about full names and about venues and times. It reads them from the page. They change only when an admin changes a switch on the publish screen.
- The page records which community it belongs to, as that community's id, beside the anonymous identifier of the phone keeping it up to date. Both are random strings that are not shown on the page and name nobody, though anyone with the link can read them in the page's data. The id opens nothing: what a community holds can be read by its members only. A link from the page to a match being shared live carries the same id in its address, so that the live scorecard can be checked as one of the community's, and goes wherever that link is copied to.
- Every member's phone is told where the page is. The link, and which admin's phone keeps the page up to date, are stored with the community's copy of the tournament, so the app can show the link to every member. Only an admin's phone ever writes to the page, with one exception: the link to a match being shared live, above, which the phone of a scorer who is sharing that match puts on the page and takes off again.
- A page you published from your own phone can be moved into the community, by that phone, if you are an admin. It keeps its link. From then on it is the community's, as above, and it cannot be moved back.
- If the community is closed, its pages stay online as they are, and nobody can update them or take them down from the app. The app says so before an admin closes a community. Unpublish first any page that should come down, or write to us at the address in section 14 with the link and we will delete it.
If you are in a community without being an admin, you can still publish one of its tournaments from your own phone when the community has not published it. That page is your phone's alone, and everything above about a page published from your own phone applies to it.
Two things worth thinking about before you publish. The people in the tournament are named on the page, initials or not, and a permanent page is a bigger step than sending a scorecard to a group chat — so treat it as publication and see sections 7 and 9. And publishing again after unpublishing gives a new link: the old address is retired for good and cannot be reused, by you or by anybody else.
5c. Communities
A community is a group of people who score the same cricket — a club, a league, a set of friends who take turns with the scorebook. Joining one means the phones in it share what they score, so the points table agrees, a player's record is complete rather than whatever happens to be on the phone you are looking at, and nobody has to email a file around.
You are in no community until you create or join one. If you never do, nothing in this section applies and the app behaves exactly as it did before.
What is shared
The community's roster and teams. For each player, the name, any nicknames or other names, when the entry was made, when it was removed if a member has removed it, and the record ids and merge history (which entries were merged into which, and when) that keep one person one record; for each team, the same without nicknames. Nothing else about a player — never your private note. A community starts empty: joining does not upload the players already on your phone, which is deliberate — the alternative is one tap that publishes forty names to a group some of them are not in.
Names added while the community is selected. While a community is selected on the home screen, the roster you are working on is the community's, not your own. So a name typed into a match that is not already on that roster is added to it — that is how a group that never opens the Players screen still ends up with a roster — and so is a player or team you add on the Players screen, or a new team you create for a tournament. This holds for a match you have kept off the community too: the setting below keeps the match back, not the names typed into it. If your role lets you score for the community, each of these is shared with every member at the next sync.
Deletions, for everyone — and restorable for 30 days. Removing a player or team from the Players screen while the community is selected removes it from the community's roster, and from every member's phone as it next syncs — if your role lets you score for the community. Otherwise the community's copy comes back at the next sync. The Players screen says which of the two will happen before you confirm. The community keeps a removed entry, marked with when it was removed, for at least 30 days: anyone whose role lets them score for the community can restore it, with its nicknames and merge history, from Removed from the community on the Players screen. Once 30 days and a day more have passed, an admin's phone deletes it for good the next time it syncs the roster; until one does, it can still be restored. A removed entry is off the roster every member sees, and it is not gone until then: it stays in the community's records, and in the copy on each member's phone, viewers' included.
Your private note stays yours when a player leaves the roster. If a player you wrote a note about leaves the community's roster — another member removes them, or merges them into an entry you had also written a note on — the note has nowhere left in the community's copy, so the app moves it, with that player, to your own roster on your phone and tells you. The note is still never shared.
A short label for your phone. You type it when you join — "Rahul's phone", "the club tablet" — and every member of that community can see it. It is free text about your device, so put in it whatever you are content for the group to see.
Which player you say you are, if you say, which a scorer or an admin can. Members can see that the phone labelled "Rahul's phone" is the player called Rahul. Somebody who said so as a scorer and was later made a viewer keeps it until they take it back.
Who has endorsed whom for admin. Scorers and admins can read the endorsements, and so can the person being endorsed. A viewer cannot read anybody else's.
When your phone last checked its clock, if you can add players. The app writes one timestamp, set by the server, and reads it straight back to learn how far your phone's clock is out, so that a merge or separation you make is dated by the server's clock rather than your phone's — once that check has worked, which is usually the first sync after you open the app. It is the only thing in that document, only you can read it, and it is deleted when you leave or are removed.
The community's tournaments, and the matches that decide them. A tournament you create while the community is selected on the home screen belongs to it, and is shared with its teams and their squads, fixtures, groups, results, awards and points adjusted by hand, with the reason given for each — and its schedule: the date, time and venue of every fixture that has them, and the pattern the dates were generated from. Every match played as one of its fixtures is shared with it, because a table with its matches missing is a wrong table.
Other matches scored for the community. A match you start while the community is selected is marked as the community's when it is created, and shared — scoring duty moves round, and a player's record is only complete if every phone's games are in it. Selecting something else later does not move it. The one thing that can mark a match afterwards is its tournament: a fixture of a community's tournament is that community's, however it was scored, and is marked so when it is created, or when the community's copy of it reaches your phone.
A match's YouTube video. Shared with the match, when it has one (section 5a): the video's id, when its stream went live and how far its moments were lined up. Any member holding the match can give it a video or line it up on its scorecard, which is shared as a correction to the match is. A phone on version 1.33.0 or earlier does not know the video, and a correction made there and synced shares the match without it.
A file an admin adds to the community. When you import a file — a backup, or a tournament somebody sent you — while a community you are an admin of is selected, the import screen offers Add to that community. It is off unless you turn it on. Turned on, every match and tournament in the file is marked as the community's and shared with it: the ones new to your phone, and any that were already on your phone as your own cricket and are in the file too. Before you confirm, the screen says how many matches and tournaments that is and how many players are named in them. This is the one way cricket from before a community existed, or scored on a phone that was never in it, becomes the community's, and only an admin's phone offers it. It does not move a match or tournament that belongs to another community, a match kept off the community stays off, and the match being scored on your phone is left alone, unless it is a fixture of a tournament being added, which brings every one of its fixtures with it. Where the file adds cricket that was already on your phone, a backup is saved to your device first. The file's saved players and teams go to the community's shared roster, which every member can see, and not to your own roster; the screen says how many before you confirm. A player or team the community has removed is not put back by this, and an earlier record of a player is linked to them only from the community's own matches. Imported without Add to turned on, they go to your own roster and are shared with nobody.
A file that is already a community's. A backup made on a phone that scores for a community carries that community's matches and tournaments marked as its own. Imported onto a phone that is in that community, they stay the community's and sync with it, and the import screen says how many. Imported onto a phone that is not in it, they are kept as they are and sent nowhere; they are shared only if that phone later joins that community.
Players and teams added in bulk. With the community selected, Add all to roster on the Stats screen adds everyone named in the community's matches who is not on its roster, and Save all on the Players screen saves the teams of its tournaments. Each says that the names join the shared roster, which every member can see. Records that share a name become one player or one team, and the Stats screen lists which before you add them.
The whole match, ball by ball. A shared match travels complete: every delivery with the time it was bowled, every player named in it (whether or not they are on the roster), any commentary you added, the venue and the result. It does not wait for the match to finish: a match still in progress is shared as it stands at each sync, and again as it goes on. A correction you make to it later is shared too.
Which of its matches are being shared live. While a scorer shares one of the community's matches live, the community holds its live link's id, the sharing phone's anonymous identifier and when sharing started, and its members see the match listed (section 5a). It goes when sharing stops.
Its YouTube stream key, if an admin sets one, for camera mode: readable by scorers and admins only (section 5d).
Its YouTube channel, if an admin sets one. The channel's handle, which is public on YouTube anyway, and which admin set it. Every member can see it on the community's screen. The live scorecard of each match the community shares then offers that channel's live stream to everybody watching (section 5a), unless the match's scorer gives it a link of its own. An admin can change or remove it.
To keep one match back, open it and use Keep this off the community in its advanced settings. If it has already been shared, that stops any further change being sent; it cannot take back the copies other members already have.
When it syncs
Only the community selected on the home screen syncs by itself, and only while it is selected: when the app starts, when you select it, and a couple of seconds after the roster on your phone changes — a name typed into a match is enough. Each sync sends the community what it does not have yet from your phone, including matches still in progress, and brings back what other members have shared.
It also syncs a couple of seconds after your phone comes to hold a match or tournament of the community's that the community does not have yet: a match you finish, abandon or correct, a fixture you start, a tournament you change. So a match you finish goes a couple of seconds after it ends, if the app is open and your role lets you score for the community. A ball bowled does not start a sync, and neither does a match that is not the community's or one you have kept off it. With no connection the match stays on your phone, and goes when the connection is back or the next time you open the app. Deleting a match from your phone sends nothing: the community keeps its copy.
A phone that has published a page of one of the community's tournaments (section 5b) also syncs every five minutes while the app is open on its screen, so that a result another member scores reaches the page without anybody opening the app again. It is the same sync, and it asks nothing while the app is in the background. A phone with no such page does not do this.
If your role does not let you score for the community, a sync brings back what other members have shared and sends the community none of your matches or tournaments: they stay on your phone. Your phone's record of your role can be out of date, because an admin changes it from their own phone, so before it sends nothing it reads your own membership record from the community, each time it syncs, and goes by what that says. A match you finish while your phone's record says you may not score starts a sync like any other, so that a role changed while the app was open is found when the match ends; if you still may not score, that sync sends nothing. If your membership record says you may now score, your phone keeps the new role and syncs once more, so that names you have added to the community's roster go with your matches.
A community you belong to but have not selected does not sync in the background; Sync now on its page syncs its roster, both ways, and nothing else.
What is not shared
Matches and tournaments you score with no community selected, and everything from before you joined — with two exceptions. A fixture of a community's tournament is shared with that tournament whenever and wherever it was scored (a league a member sent you as a file is the community's even before you join, and its fixtures are shared once you do). And what an admin adds to the community from a file is shared, as described above; importing a file without turning that on shares nothing. Everything else stays on your phone, exactly as section 4 says. A match you have kept off the community with the setting above. Your private note on a player, ever — a note is something you wrote about somebody else, it is yours rather than the group's, and it is left behind when a player is contributed. And nothing at all from a phone that is in no community.
Who can see it
Only members of that community, and only through the app. Nothing here is public and there is no directory: a community cannot be searched for or browsed to, and there is no way in that does not go through one of four doors.
- An invite, which an admin creates and hands out. It is good for one device: the first phone to use it binds the invite to itself, and nobody else can join on it afterwards. An admin can withdraw one at the moment they create it, if it has gone somewhere they did not intend — after that screen is closed the app no longer knows the code, and the invite is only usable by whoever gets to it first.
- A recovery code, for the case where every admin has lost their phone, shown once when the community is created and once each time an admin makes a new one. It binds to one device the same way. It is used up by the one recovery it makes, and the phone that used it makes a replacement in its own name and shows it, at once where it can; where it cannot, the community's screen says that phone has not made one and offers to. It works only while the admin who made it is still an admin, so one who is removed or demoted cannot come back on it. When that admin goes, the admins left are told the community has no working code and asked to make a new one; any admin can make one at any time.
- The community's link for viewers, if its admins have made one. This is the one way in that is not for a single device: an admin makes one link and can post it wherever the group talks, and everybody who opens it can join, including anybody it is passed on to, for as long as it stands. Whoever joins this way is a viewer. They can read what members can read — the roster, the member list, the community's tournaments and matches — and cannot score for the community or change its roster, tournaments or matches, and a viewer cannot help make anybody an admin. Like any member, they can name their own phone. Saying which player on the roster you are is for scorers and admins. The link is kept in the community's records, where only its admins can read it, with the identifier of the admin who made it. An admin can withdraw it, or replace it with a new one, at any time; either stops the old link for everybody who has not yet joined, and nobody who has already joined is removed. It also stops if the admin who made it stops being one.
- Two scorers, who can together promote another member to admin. Neither can do it alone, nobody can endorse themselves, a viewer's endorsement does not count, and an endorsement is spent when it is used. A community's admins can turn this off, and every member can see whether they have. They can do so only while there is another admin or a recovery code of their own, and the setting records which admin that was, where every member's app can read it.
An invite, a recovery code and the link for viewers each carry the community's name as well as the key that lets a phone in, so whoever is shown one can read the name before joining. An invite lets nobody read anything else of the community's without joining.
The community's records also keep, for each anonymous identifier that joined, which invite, recovery code or link for viewers it used, filed under that identifier; a later join under the same identifier replaces it. Joining again after clearing the app's data, or from another browser, is joining under a new identifier, which gets a record of its own, and the earlier one stays. No member can read these records and no phone can delete one, so each stays when its phone leaves or is removed, and when the community is closed, until we delete it on a request to erase you or the community's data (sections 11 and 12).
An admin can remove a member, and removal sticks. The invite they still have is bound to them and already used, so it will not let them back in — and neither will a fresh identity on the same invite, which is the thing that would otherwise have made removal pointless. The link for viewers is the exception, and the app says so when it matters: it is not used up, so somebody who was removed and still has it can join again as a viewer, as a phone the community has not seen before. Removing a member therefore offers to replace the link in the same step, which shuts the old one; an admin who leaves that unticked has left that door open.
Publishing a tournament (section 5b) is the separate, deliberate step that makes something public, and it stays entirely opt-in inside a community. When an admin publishes one for the community, the page belongs to the community: its admins, not one phone, can update it or take it down, and every member's phone is told its link.
Who you are in it
The same anonymous identifier live sharing uses, described in section 5a. It is not an account: no name, no email, no password, and nothing linking it to your Google account. What members see next to it is the label you typed for your phone, the player you say you are if you have said, your role, and a short code derived from the identifier so two people can check they are looking at the same device before removing or promoting anyone. Your member entry, which every member can read, also holds when you joined and when your role last changed. The app shows only the short code, but the identifier itself is what the entry is filed under, and every member's app can read it, a viewer's included. It is the same identifier that is beside a match you share live or a page you publish (sections 5a and 5b), so somebody who is a member and also holds one of those links could tell that they came from the same phone.
Other people's cricket, and other people's names
This is the part worth reading twice. A community archive contains names entered by other members, about people who are not members — the opposition, juniors, anybody who turned up. It is a group record rather than yours, and that has two consequences.
Leaving a community does not withdraw what you contributed. The players you added stay in the shared roster, and the matches and tournaments you shared stay in its archive, because they are the group's record of games other people played in. That is as true of a file an admin added to the community as of a match scored for it, and a file can hold hundreds of matches naming people who were never in the group: the import screen says how many before it is confirmed, and there is no button that takes an added file back out. What leaving does is stop your phone contributing anything further, and delete from your phone the community's roster and the matches and tournaments it received from other members — the copies you synced go, the group's copy does not. Matches you scored yourself stay on your phone as your own cricket.
One thing from the community's roster stays on your phone, so that your own cricket still adds up. Where the community's roster said that two or more records are one player, and at least two of those records are in matches you scored yourself or in your own roster, the app copies that link into your own roster before it deletes the community's. Without it the player would turn back into two people in your stats, with their matches split between them. If you already had an entry of your own for the player, the link is added to it and nothing else about it changes. If you had none, the app adds one: it holds the community's name for that player, the record id and creation date of the community's entry, and the link — no nickname, no note, and not when the records were merged. Nobody else on the community's roster is kept: not a player it had under a single record, and not one who is only in matches you received from other members. Closing a community takes its roster off your own phone in the same way, and keeps the same links.
Being removed is the same, from the other direction. An admin removing you ends your access to the shared roster and archive. The next time your phone tries to sync with the community, the app finds that its place there has gone, says so, and deletes from your phone what leaving would — the community's roster and the matches and tournaments it received from other members — keeping the matches you scored as your own cricket, and in your own roster the same links between records that leaving keeps, with the community's name for a player you had no entry for. It keeps the community's own name only to tell you, until you dismiss the notice. A removal cannot reach a phone that never syncs again, and the screen that does it says so rather than implying otherwise.
The archive has no expiry, by design. A club's history is meant to still be there next season. Nothing sweeps it up, so it lasts as long as the community does.
If you need something removed — what identifies you in the community, or a particular player's name — see section 12. It is a request we act on rather than a button, and section 12 says exactly what each one does.
Children
Everything section 9 says about junior cricket applies here with more force, because a community archive is durable and shared rather than a single link. If a community's cricket involves children, the people adding their names should be content that the whole group will see them — and that includes every name typed into a match scored while the community is selected, which joins the shared roster without a separate step (section 5c). It includes a file of earlier matches too: when an admin adds one to the community, every child named in those matches is named to the whole group, with the dates and venues of the games. Publishing any of it is a further, separate decision, and section 5b says what a page shows and how to keep names and venues off it.
A community's tournaments also carry their schedule: the date, time and venue of each fixture that has them. Section 5b treats exactly that as the disclosure that matters most for a junior side, and gives a published page a switch that leaves it off. There is no such switch inside a community — every member sees where and when the fixtures are — so before putting a junior side's fixtures in a community's tournament, think about who is in the group.
5d. Camera mode
Camera mode is in the Android app only. It lets a phone film a match, draw the score on the video, stream it live to YouTube and record it, so that people can watch the game with the scoreboard on screen.
Who can use it. It is offered only to a scorer or an admin of the community a match belongs to, from that match's live scorecard (section 5a), usually on a phone other than the one scoring. Anybody else who opens the live link sees the scorecard and nothing more. A match that belongs to no community cannot be streamed this way.
The camera and the microphone are asked for the first time camera mode is opened, and are used only while its screen is open or it is recording. While it records, locking the screen or leaving the app does not stop it: the stream and the recording carry on, and a notification says so, with a Stop button that ends them, on the lock screen too. Swiping the app away from the recent apps stops them as Stop does. When it is not recording, leaving the app lets the camera go.
Where the video goes. Straight from the phone to YouTube, to the channel whose stream key you enter, over YouTube's own streaming connection. It does not pass through any server of ours, and we never receive, see or keep it. Once it reaches YouTube it is governed by YouTube's terms and Google's privacy policy, and who can watch it is whatever that channel's settings say: public, unlisted or private is chosen in YouTube Studio, not in this app. With no stream key nothing is streamed: the phone only records. When it goes live, the camera phone notes the time in the match's shared copy, so that its live scorecard can jump the video to a wicket or a boundary (section 5a).
What is on the video besides the picture and the sound is the scoreboard: the teams' names, the score and the overs, the two batters and the bowler by name with their figures, the balls of the over, the run rates and the partnership, and for a few seconds after a wicket, a boundary or a milestone a line saying so, which for a wicket names the batter and how they were out. It is what the live scorecard already shows anybody with its link, drawn from the same live document; nothing is added to that document for it.
The stream key you type on the camera screen is kept on this phone only, so it does not have to be typed in every time. It is left out of Android Backup and device transfer (section 6), and the app sends it nowhere but to YouTube, as part of the address the stream goes to. Anybody who has a stream key can stream to that channel, so treat it as a password: YouTube Studio can reset it.
The community's stream key. Instead, an admin can give the community the channel's stream key on its screen, so that scorers can stream without being handed it. This one is stored in the cloud, in the community's records in Google Firebase (section 5c), with the anonymous identifier of the admin who set it and when. Only the community's scorers and admins can read it, and only its admins can change or remove it; a viewer cannot. The camera screen reads it from the server each time it opens and uses it for that stream only: it is not kept on the phone, not put in the copy of the community the phone keeps, and not in Android Backup. It is shown only by its last four characters. A scorer could still copy it while they can read it, and the app cannot take it back from somebody who has left or been removed: only YouTube Studio can stop a key, so removing a scorer or an admin, or making one a viewer, reminds the admin to reset it there and give the community the new one. Closing the community makes it unreadable to everybody.
The recording is saved on the phone, in the app's own folder on its shared storage, as an MPEG-TS video file, beside a small file with the live link's id, when the recording started and how far the phone's clock was from the server's (section 5a). Those are for finding the moments of the match in the video. The app uploads neither. They are removed when the app is uninstalled or its storage is cleared, and they are not in Android Backup. That folder is the app's alone on Android 11 and later. On Android 10 and older, any app the phone has given permission to read its storage can read it, as it can your photos; it is kept there so that the whole match can be copied off the phone over USB.
People on camera. A stream shows whoever is at the ground, and at a local match that can include children and people who never agreed to be filmed. Whether and what to film is the decision of the person streaming, and so is asking for permission where it is needed: the players, the parents or guardians of any child playing, and the ground. See sections 7 and 9.
Streaming uses a lot of mobile data: at the app's highest quality about 1.4 GB an hour, less when the connection is weak and the app lowers the quality to keep the stream going.
6. Android Backup
If Android's automatic backup is enabled on your device, everything section 3 lists except the cache of shared files and camera mode's stream key and recordings is included in your device backup to your own Google account, and in device-to-device transfer when you set up a new phone: your matches, roster and private notes, tournaments, the copy of any community you are in, a recovery code if you have one, the record of what you have published, and the two identifiers of section 5a. This means your data can survive uninstalling the app and can be restored onto a new device — and that a phone restored from your backup can come back, to a published page, a live match or a community, as the phone that was backed up, able to update or unpublish that phone's pages and holding its place in its communities. Do not count on that: Android decides what a restore brings back, which is why sections 5b and 11 treat a lost phone as lost.
That backup goes to your Google account, not to us, and is governed by Google's privacy policy. You can disable it in your device settings under System → Backup.
One limit worth knowing about. Android caps how much any one app may put in the backup to your Google account. If your saved matches ever grow past it — which takes hundreds of full games, more than most seasons — Android stops backing the app up, and it does so silently: Android itself does not tell you, and we are never told. Version 1.32.0 of the Android app and every later one has a notice for this; an earlier copy does not. In a copy that has it, Match History shows it by the export button when the room the app's data takes up is getting close to that cap, and a differently worded one once it looks to be past it. A copy of the app without the notice shows nothing. The notice is an estimate: the app can measure its own data, but it cannot see the backup itself, so it is set to appear early. For both reasons, not seeing a notice is never a promise that the backup is whole. You can put the notice off, and it comes back as the data grows.
Setting up a new phone directly from the old one is a different path, and Android does not put the same cap on it; its own guidance is that data too large for the cloud backup can still move in a direct transfer. So if you have years of cricket in here, transferring phone to phone is the more reliable way to carry it across — and either way, take an occasional export from Match History and keep the file somewhere. That is the copy nobody can take away.
7. Other people's information
When you score a match or organise a tournament you type in team and player names, and your saved pools can keep those names for reuse. Player names are personal information about other people, and they stay on your device under your control on the same terms as everything else in this policy. If you share a scorecard, a backup, your roster or a tournament, those names travel with it.
Two features make that a bigger step than keeping names on your own phone. A community (section 5c) shares them with a group and keeps them for as long as the community lasts. Publishing (section 5b) is the largest of all, because the page is public, permanent and about other people. That is why the publish screen says what the page will show before anything is sent, why names can be shortened to initials, and why we would ask you to think of it as publication rather than sharing: ask the people involved before you put their names on a page that is meant to outlast the season.
8. Third-party services
The app integrates no analytics, advertising, or crash-reporting SDKs. Camera mode streams to YouTube, a Google service, when a scorer enters a stream key and goes live (section 5d); the video goes to the channel that key belongs to. Somebody watching a live scorecard, a match's scorecard in the app or a match on a published page who taps Play the video here loads YouTube's player, from youtube-nocookie.com, on their own device (sections 5a and 5b). The app contacts YouTube for nothing else. Apart from that, one third-party service is used, and only when you use a feature that needs it: Google Firebase stores a live scorecard while you are sharing it (section 5a), a published tournament page while it is published (section 5b), and a community's shared cricket while you are in one (section 5c). The Firebase code in the app is not even loaded, and contacts nothing, until you turn sharing on, publish a tournament, join a community, or open somebody's live link or published page, or until the app retries a takedown it still owes (section 2).
A second company is involved whenever a link is opened in a browser. The web version of the app, at app.gullycricketscorer.k4tech.in, is hosted by Vercel, and a live link, a published page and a community's invite link are all addresses on it. Opening one sends a request to Vercel, which sees, as any web host does, the IP address it came from and the address asked for. That address contains the link's long random id, and for an invite the invite itself, with the community's name in it (section 5c). We run no analytics on the web version and set no cookies there. The installed Android app is not loaded from Vercel and sends it nothing.
Three more things sit outside the app and are worth knowing about. If you installed the app from Google Play, Google collects installation and, where you have enabled it at device level, crash and performance diagnostics, under Google's own privacy policy. And if you use Share, the app you share into receives whatever you send.
The third is the website, gullycricketscorer.k4tech.in — the page that describes the app, and this policy. It counts its visits with Vercel Web Analytics, run by Vercel, the company that hosts it. Each page view records the page, the address that linked to it, the time, the country, region and city the request appears to come from, and the kind of device, operating system and browser. It sets no cookies and stores nothing in your browser. To tell a second visitor from the same one reloading, Vercel derives a short-lived identifier from the request and discards it within 24 hours, so nobody can be followed from one day to the next or on to any other site, and the figures we see are totals that are not tied to a person or an IP address. The install links and the QR code on that site also tell Google Play that the visit came from the website, so that we can see how many installs it led to; Google handles that under its own privacy policy and nothing about it is passed to the app. None of that counting is in the app, or in the web version at app.gullycricketscorer.k4tech.in.
9. Children's privacy
The app has no accounts, does not ask anybody's age, and contains no advertising or in-app purchases. Outside a community it does not ask who you are; in a community it asks for a label for the phone and, of scorers and admins, which player they are, which is theirs to answer or not (section 5c). A parent should be aware that a scorer can type player names into a scorecard, roster or tournament; those names are stored on the device and included in anything the user chooses to share or export.
Junior cricket deserves a specific word about the three cloud features, because children are frequently the ones being scored and all three are off unless somebody deliberately turns them on.
A live link shows the names of everyone playing to whoever holds it. If a match involves children, please make sure the parents are content before sending the link round, and stop sharing once the game is over so deletion can begin immediately.
A community shares a child's name with everyone in the group and keeps it for as long as the group lasts. It is not public — no directory, no search, members only — but it is durable and it is other people's, so adding a junior side's names is a decision to make with the parents rather than on their behalf. A community starts empty for this reason — but once it is selected on the home screen, every new name typed into a match joins its roster, and an admin can add a file of earlier matches to it, with everyone named in them (section 5c). A community's tournaments also show every member where and when their fixtures are played, with no switch to leave that out.
Camera mode (section 5d) puts the match on YouTube, where who can watch is set by the channel, not by this app, and a recording of it stays on the camera phone. Before streaming a game that children are playing in, please ask their parents, and consider an unlisted stream shared only with them. A match's video is shown with it on a published page (section 5b), so an unlisted stream is no longer seen only by the people you sent it to once its match is on a page; take the video off the match to keep it off the page.
Publishing is the most serious of the three. A published page is permanent, and there is no equivalent of "stop sharing when the game ends" — a season is meant to stay readable. A new page shows names in full, and where the games are and when the ones still to come will be, unless the organiser turns those two switches off; for a junior side the second is the disclosure that matters most. So the publish screen says what the page will show before anything is sent, and says to turn both off if children are playing unless their parents have agreed. Turned off, the page shows initials rather than names and leaves venues and times out. It still says the day each match was played, once it has been, and it still shows the tournament's own name as it was typed (section 5b). Before publishing a competition involving children, please ask the parents, and turn both switches off unless they have said otherwise.
10. Security
Match data is held in the app's private, sandboxed storage, which Android prevents other applications from reading; in the web version, in that browser's storage for the site. With live sharing off, nothing published and no community joined, nothing is transmitted, so there is no data in transit to intercept and no server of ours to breach.
When any of the three is in use, what is sent travels over HTTPS to Google Firebase. Camera mode's stream goes to YouTube over RTMPS, which is encrypted in the same way, stream key and all. A live scorecard cannot be altered by a viewer: only the phone scoring it can change it, and scoring passes to another phone only by the handover and take-over section 5a describes. A published page cannot be altered, replaced or taken over by anybody but the phone that published it — or, for a page published for a community, an admin of that community — including after it has been unpublished, because a retired link can never be reused. The one thing a scorer of that community can change on it is the link to a match being shared live (section 5b), and only on a page that shows full names. A community's data is readable only by its members and writable only according to the role each member has, enforced by the database rather than by the app.
The security of the data therefore rests on the security of your device. We recommend keeping a screen lock, passcode, or biometric enabled, and keeping your device software up to date.
11. Keeping and deleting your data
Unless you are using live sharing, have published a tournament, or are in a community, we keep nothing, so there is no retention period on our side and no request to make of us. You control the data entirely:
- Delete a single match from the Match History screen, or a tournament from the Tournaments screen; deleting a tournament does not delete its completed matches
- Remove a player from the saved roster. While a community is selected, that roster is the community's, and if your role lets you score for it, removing a player removes them for every member — and any member who can score can restore them for 30 days, after which an admin's phone deletes the entry for good (section 5c)
- Remove everything by uninstalling the app, or through Settings → Apps → Gully Cricket Scorer → Storage → Clear data
- If Android Backup is enabled, also delete the app's backup from your Google account, or it may be restored later
A deleted match or tournament is not gone at once. It moves to Recently deleted, at the foot of the Match History or Tournaments screen, where you can restore it for up to 30 days — with Scoring for on the home screen set to the community it belongs to, or to Just this phone, if this phone is in a community, since those screens show the selected community's cricket or the phone's own — less if the bin fills up, since it keeps only the 15 most recent deletions and a limited amount of data. Delete for good there removes it from your phone straight away; otherwise it is removed when its time in the bin runs out, and a match's ball-by-ball record goes with it, at the latest the next time the app starts. Deleting a match or tournament on your phone does not remove a copy a community already has (section 5c). Deleting a match you are sharing live does stop sharing it, which asks us to delete the live copy (section 5a).
Three things are held by us rather than by you, and they have different retention.
A match you have shared live. Pressing Stop sharing, or deleting the match in the app, asks Firebase to delete the cloud copy immediately; if that request fails, its seven-day expiry is the fallback and deletion happens asynchronously. Uninstalling the app does not send a delete request — press Stop sharing first, or write to us at the address in section 14 with the link and we will remove it.
A tournament you have published. This one is kept indefinitely and on purpose: the page exists to be readable in years to come, so it has no expiry and nothing sweeps it up. Pressing Unpublish deletes the page and its scorecards; if that request cannot get through, the app keeps trying and completes it the next time the phone is online. That is so even when an update to the page was itself still waiting for a connection: the app notes the request on your phone without waiting for the update to be sent, and sends what it has noted each time it starts. There are four exceptions, all for a community's page. The first is a page that another admin's phone keeps up to date: your phone has to read that page before it can take it down, so with no connection the app tells you it could not reach the page, the page stays up and nothing is retried. Press Unpublish again when you are online. The second is a page your own phone keeps up to date, in the seconds after you press Unpublish. The app first asks whether your phone may still take the page down, and notes the request once it hears that it may, or after ten seconds at most with no answer. If the app is closed before then, nothing was noted: the page stays up, and the app still shows it as published when you open it again. Press Unpublish again. The third is a request still waiting to be sent when your phone stops being an admin of the page's community. The app tells the community that a page was taken down only once the page itself has been deleted, so a page that is still up is one every admin's phone still shows. If the page is still up, the request is refused once it can be sent, the page stays up as the community's, and the app stops trying. Any admin of the community can still unpublish it, which removes the page and its scorecards. If part of the request had already got through, the page can no longer be updated or taken over from another admin's phone, and some of its ball-by-ball records may already be gone; unpublishing it is what is left to do with it. None of that holds for a request made by an earlier version of the app, which told the community that the page was taken down first and deleted the page afterwards; a browser tab left open on that version still works that way. If such a request was still waiting to be sent when the phone stopped being an admin, the page is still up and the community has already been told that it was taken down. The request is refused and the app stops trying in the same way, but an admin's phone shows the page only until it next syncs with the community, and after that nothing in the app can take the page down. Write to us at the address in section 14 with the link and we will delete the page and everything under it. If the app had already deleted the page and only the ball-by-ball record of a scorecard on it was still waiting to be deleted, the page is gone and that record stays online: your phone can no longer delete it. Write to us at the address in section 14 with the link and we will delete it. The fourth is a page your phone published for a community when another admin's phone had published one for the same tournament and neither had heard of the other's. The community keeps one of the two, and the phone that published the other takes its own down. If your phone has stopped being an admin of the community by the time that request can be sent, the request is refused and your page stays online, known to no other phone. The same holds for a page your phone published that the community never heard of, when your phone stopped being an admin and stopped updating that page before another admin's phone published one for the tournament: once your phone hears of the other, it sends no request while it is not an admin, and your page stays online in the same way. The app keeps the request and shows that page's link on the tournament's Publish screen, with the reason, for as long as your phone is in the community and has the tournament. If your phone is made an admin again and the app has learnt of it, which it does when you open the community's screen, the app completes the request the next time it starts online. Otherwise write to us at the address in section 14 with that link and we will delete the page. Deleting the tournament in the app unpublishes it too, unless its page was published for a community (section 5b): deleting your copy of that tournament leaves the community's page up. If the community never heard of the page your phone kept, your phone takes it down once it hears that another admin's phone has published one for the tournament. If your phone is not an admin by then, the request is kept as in the fourth exception above, and the link is shown once you restore the tournament from Recently deleted. Unpublishing removes what we hold, but for a marker that the address has been used, with the time it was retired: nobody can read it, and it is what stops the address ever being used again. For a community's page, the community's copy of the tournament also keeps the retired address, marked as off. A device that had already opened the page keeps its own saved copy for a while longer — up to 24 hours while it is online, and never more than 7 days — as section 5b describes.
What has no fallback is a page published from your own phone, when that phone is lost, wiped or reinstalled before the page is unpublished. The page then stays readable and nothing on any device can remove it. Write to us at the address in section 14 with the link and we will delete it — that is the only remaining route, and it is why the app says so before you publish.
A page published for a community (section 5b) outlives the phone that published it: any admin of the community can unpublish it. What has no fallback there is a community with no admin left, or one that has been closed. Its pages stay readable, and the route is the same: write to us with the link.
A community you are in. This one is kept for as long as the community exists, on purpose: a club's history is meant to still be there next season, so there is no expiry and nothing sweeps it up. Leaving a community removes your copy from your phone, all but the links between records that section 5c says are kept in your own roster, and stops it contributing anything more; it does not withdraw what you already contributed, because that is the group's record of games other people played in. Nor does it delete your join record: the community's records keep, for each anonymous identifier that joined, which invite, recovery code or link for viewers it used. No member can read it, and it is kept for as long as the community's records are, which closing the community does not end, unless you ask us to erase you (section 12). An admin can remove a member. A page the community has published stays up when a member leaves or is removed, whoever published it.
An admin can also close a community, which ends it for everyone: nobody can read its roster after that, nobody can join it, and its address can never be used again. Be aware of what closing does not do. The stored documents are not erased by it — they are made unreachable, because a phone cannot be trusted to sweep a database and the invites are, by design, not even listable. If you need the data itself deleted rather than closed off, write to us at the address in section 14 and we will do it. Closing does not take down the pages the community published either: they stay online as they were, and after closing nobody can update or unpublish them from the app, so unpublish first or ask us (section 5b). What no button can do is take one person's name out of a group's history — see section 12.
12. Your rights
Privacy laws including the EU and UK GDPR and India's Digital Personal Data Protection Act give you rights to access, correct, export, and erase your personal data. For everything held on your device you can exercise all of them directly in the app, without asking us: view and correct any match, manage the saved roster, export everything as a JSON backup, delete individual matches or tournaments, or clear all app data through Android settings.
For a scorecard you have shared live and for a tournament you have published, the same rights apply to the cloud copy. Stop sharing and Unpublish each send a deletion request, and for a published page the app retries one that does not get through, with the four exceptions section 11 describes. There is no expiry fallback for a published page — it is meant to last — so if you cannot reach the app, lost the device, or need us to confirm removal, write to the address in section 14 with the link and we will delete it. There is still no account to close, because none was ever created.
For a community, the same rights apply and two of them need explaining, because a shared archive is not the same shape as a private one.
Erasing you. The community's copy of a match does not record which member or phone scored it, so there is no link from the cricket to you to strip. What does identify you in a community is your member entry — the label for your phone, the player you say you are, your role, and when you joined — and leaving deletes it, along with your claim to a player, your clock document and any endorsement for admin that other members had given you. Leaving with no connection takes the community off your phone at once, and the request to delete those waits for one; if the app is closed before it gets through, your member entry stays in the community, the app tells you so, and an admin has to remove the device, or you can write to us. A few records hold your anonymous identifier, beside nothing more about you than a date or the code you joined with, and leaving does not delete them, because they are what the database checks to keep membership honest: the invite or recovery code you joined with, marked as used by you; your join record, saying which invite, recovery code or link for viewers that was, which no member can read and no phone can delete; any invite or recovery code you created as an admin, and the note, readable by admins, that you made a recovery code; an endorsement for admin that you gave to another member, normally one that has not been used yet; the community's setting on whether members may promote an admin, if you were the admin it named when that was turned off; the community's link for viewers, if you were the admin who made it; the community's YouTube channel, if you were the admin who set it; the community's YouTube stream key, if you were the admin who set it; the record that you created the community, if you did, which every member's app can read; an entry listing a match you were sharing live (section 5a), which stays after you leave until the share has ended and a scorer's phone finds the match gone and removes it; and, if an admin removed you, the entry that keeps you out, with its date, which scorers and admins can read. If you ask us to erase you, we delete those as well, and the cricket stays. Three things outside the community's own records carry your identifier too. A match you are sharing live, until it is deleted (section 5a). A live match another member has offered to hand over to you, which names your identifier as the one it is offered to, until you take it or the match is deleted. And a tournament page your phone published or keeps up to date (section 5b): the page and its ball-by-ball records carry it, and for a community's page so does the community's copy of the tournament, where every member's app can read it, until another admin's phone takes the page over or the page is unpublished. Leaving does not change any of the three, and a request to be erased covers them.
That the cricket stays is deliberate, and it is worth saying why rather than leaving it to be inferred: the personal information in a scorecard is the players' names, and those belong to the people who played and to the group that keeps the record, not to whoever happened to be holding the phone. Removing the cricket would erase other people's history in order to erase your involvement in it.
Erasing a player. Taking one person's name out of a community's history is a request we act on rather than a button in the app, because no member owns the record and the person concerned may not be a member at all. Write to the address in section 14 saying which community and which player. We will remove that name from the shared copy; copies already downloaded to members' phones update when those phones next sync, and a phone that never opens the app again keeps what it had.
You can always leave a community, which removes your copy and stops any further contribution, without making a request of anyone.
13. Changes to this policy
We may update this policy as the app changes. Material changes will be reflected here with a revised "Last updated" date, and where the change affects how data is handled it will also be noted in the app's release notes. Please review this page from time to time.
14. Contact
Questions, concerns, or corrections about this policy:
k4.technologies.dev@gmail.com K4 Technologies