Privacy Policy

Gully Cricket Scorer — published by K4 Technologies

Application ID: com.k4technologies.gullycricketscorer

Last updated: 6 November 2026

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:

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:

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_RECEIVER_NOT_EXPORTED_PERMISSION: 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_AUDIO 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_SERVICE 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_SERVICE_CAMERA 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_SERVICE_MICROPHONE Android 14 and newer, camera mode only The same, for the microphone.
WAKE_LOCK 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_NOTIFICATIONS 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_EXTERNAL_STORAGE 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://app.gullycricketscorer.k4tech.in/join/, and gullycricket://join/. 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:

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:

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:

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:

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:

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:

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

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, 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:

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