Last updated 11 October 2026
Fall of Shot is a naval strategy game made for families. This policy explains, in plain words, what the game stores, who can see it, and how to get rid of it. It is short because the game deliberately collects very little.
Game data, and a name chosen from a list we wrote. That is the whole list. No email address, no password, no name anybody typed, no date of birth, no age, and nothing they typed. We hold no identifier belonging to their device. Google's notification service keeps one of its own so that a turn alert can reach the handset — we never see it and never store it. See Children below.
No location. No contacts. No photos. No microphone. No advertising identifier. There are no adverts in this game and no third-party trackers of any kind. Nothing is sold or shared with anyone for marketing, because there is nobody to sell it to.
One thing we would rather state than have you find. Google's analytics library is present in the app, because the notification service depends on it and cannot be installed without it. We have switched its collection off and it reports nothing — no advertising identifier, no device identifier, no usage. We would remove it if Google let us, and we check every build to confirm it is still silent.
There is a feedback box in the game for telling us something is broken. It is the only place in Fall of Shot where anybody types words at all, and we would rather say so plainly than leave you to find it.
It is offered only to account holders — the person whose email address and licence the household runs on. An account you grant does not get it: the link is not shown, and our server refuses a report from a granted account even if something else asks. That is why the sentence under Children can say we collect nothing from a child without an exception hiding behind it.
When you send a report we store what you typed — a one-line summary and the longer description — together with the kind of problem, how badly it affected you, your device model, your Android version, the app version, and the game it happened in if you sent it from one.
It goes to us and to nobody else. No other player can read it. It is not a message channel — there is no reply inside the game, and nothing you write there can reach another player.
If you delete your account we keep the report and remove you from it: your account identifier and your name are stripped, and the words stay. A bug report is about the game rather than about a person, and deleting it would quietly un-report a fault somebody else is still hitting. If you would rather a report went altogether, write to us and say which one.
We collect nothing from a child. Not a name, not an email address, not a password, not a date of birth, not an age, and no identifier belonging to their device.
One qualification, stated here rather than left for somebody to find: delivering a “your turn” notification requires Google’s own notification service to recognise the handset, and it keeps an installation identifier of its own for that purpose. It is Google’s, it stays with Google, and it never reaches us. What we hold is a random subscription name we invented, which describes no device and no person. Turning notifications off in Android settings stops it being used.
An account owner creates the profile on their own device and hands the new account a one-time code. That second device is then given an identity generated by our server, containing nothing — no address to sign in with and no password to remember, because there is nothing for a child to type and nothing about them for us to hold.
An earlier version of this page said we asked for one and then threw it away. That was not accurate, and we would rather correct it plainly than quietly reword it. What the server actually kept was the date a restriction would end — which is a birthday shifted by a fixed number of years, and can be turned back into one exactly. Storing something a birthday can be recovered from is storing the birthday.
The question has been removed from the app and the field from our database. We do not ask for a date of birth, an age, or an age range, and we do not keep anything from which one could be worked out.
Because we never learn anyone's age, nothing in this game behaves differently for a child than it does for an adult, and nothing can lift on its own. There is no protected state to switch on, because the protections below are not a setting — they apply to every player, in every game, all the time.
There is no free-text field anywhere in this game that reaches another player. Not a chat message, not a nickname, not a team name, not a caption or a title. Every name in the game — players, ships, weapons and fleets — is chosen from lists we wrote and shipped in the app. A game whose names are not on our lists is refused, for everybody.
Players can send each other short phrases we wrote, such as "good game" or "bigger board please". There are 26 of them and nothing else can be sent — here is every one of them, so you can check that rather than take our word for it. That page is written out of the game's own table by the same build that ships the app, so it cannot fall behind what the game allows. Nobody can type anything of their own, to anyone, at any age.
This is why no child needs a special mode: there is nothing for one to switch on.
To tell an account we granted its turn is ready we use a random name we invent for that purpose, not an identifier taken from the handset. We do not store a device token for those accounts.
The record of a match — the one holding both fleets — cannot be read by any player, including the two people playing it. Only our server can open it. That is not a setting; it is enforced at the database, and it is what stops a modified copy of the game from simply reading where your ships are.
Your statistics cannot be written by anybody, including you. There is no leaderboard, and no way to look up another player.
On Google Firebase (Firestore, Authentication and Cloud Functions). Google processes it on our behalf. Passwords are handled entirely by Google — we never see one, and we could not tell you yours.
You can delete your account and its data at any time. See Delete your account for how, and exactly what happens.
You may ask us what we hold about you, ask for it to be corrected, or ask for it to be
deleted. Write to support@redmonlabs.com and we will act within 30 days.
If this policy changes materially we will update the date at the top and say so in the app.
11 October 2026 — the notification token, corrected again. We store a notification token for the account that owns the licence. The entry below, from 20 September, says we do not. That was wrong — it described how a child's granted account works and applied it to everybody. A child's account does work that way: a random topic name, no device token, exactly as described. The adult account that owns the licence has always had one token stored so its turn alerts can be delivered, and the correction we made in September removed a true sentence and replaced it with a false one.
20 September 2026 — notifications, and the analytics library. Three corrections. Two of them are this page describing the game as worse than it is, and the third is a piece of honesty we owed you.
14 September 2026 — the feedback box, and the phrase list. Two corrections, and both were this page describing the game less accurately than it should have.
26 August 2026 — the Children section was corrected. It previously described asking for a date of birth and discarding it. We no longer ask for one at all, and the paragraph above explains why the old description was wrong.