ONE SHOT
Cascade
Last updated: 19 August 2026 · Applies to One Shot Cascade on Android and iOS.
One Shot Cascade has no sign-in: it never asks for your email, phone number, contacts, location, or photos, and there is no password to forget. It does have leaderboards and leagues, so that other players can see how they rank against you. To make that work, when you play, the game sends your scores, a short replay of the run so the score can be verified, a display name you choose, and a randomly generated player number to our leaderboard service. The game also sends an automatic crash report if it crashes. That is the whole list, and the rest of this page explains each item.
Most of what the game remembers never leaves the phone. It is stored locally, in the app's own private storage, and we cannot see it:
These stay on your device, are not sent to any server we operate, and are deleted when you uninstall the app. One caveat that belongs to your phone rather than to us: your device's own backup system (Android's backup to your Google account, an iPhone backup) may include the app's files along with everything else it backs up. Those backups are between your device and your Google or Apple account — we never see them.
The game's leaderboards and leagues run on Google Firebase (Cloud Firestore). So that other players can be ranked against you, when you finish a ranked run the game submits:
Alongside each run, the game keeps a single player row up to date on the server: your display name, Charge, league division, best run, and lifetime run count — the numbers the ladder is built from.
This is the information other players may see next to your rank: your display name, your score, and your league standing. It is stored so that the boards persist between sessions — run entries are stamped with an expiry when they are posted and deleted 90 days later, while your player row persists (so your league standing does) until you ask us to remove it. It is processed by Google as our service provider under Firebase's data processing terms.
Taking part is on by default, but you can turn league participation off at any time in the game's settings. When it is off, the game stops submitting your runs and your display name; runs queued but not yet sent are held on your device and go out only if you turn the switch back on. (The app still signs in to Firebase anonymously when it starts — that is where the player number comes from — but it submits nothing while the switch is off.) See Your choices and your rights below for how to also remove data already submitted.
If you report another player's name from the boards, the report sends their player number, the name as you saw it, the time, and your own player number — so that misuse of the report button can be spotted. Reports go into a store that no player can read and are used only for moderation.
The game uses Firebase Crashlytics, a Google service, to report crashes so they can be fixed. When the game crashes, Crashlytics sends:
These reports do not contain anything you typed. They are processed by Google as our service provider under Firebase's data processing terms, and Crashlytics retains them for 90 days.
Whenever the game talks to Firebase — submitting a run, fetching a board, reporting a crash — Google's servers see your device's IP address, the way any server sees the address of anything that connects to it. We never see or store it. Google processes it as our service provider, on servers that may be outside your country, under the data processing terms linked above, which include the EU's standard contractual clauses for international transfers.
Advertising is not active in the current release. The game shows no ads today and contains no ad network that requests one.
When advertising is enabled in a future update, the game will use Google AdMob. AdMob collects an advertising identifier (the Android Advertising ID or Apple's IDFA) and ad-interaction data (which ads were shown, tapped, and whether they led to an install) in order to serve and measure ads. We describe that here in advance so this policy does not need to change when ads are switched on; the store data-safety disclosures will be updated to match at that time, and where the law requires it you will be asked for consent before personalised ads are shown.
The share button hands a short block of text to your device's own share sheet. What happens next is entirely between you and whichever app you pick. The game does not see where you sent it. It does count that you shared — the counter behind the sharing achievement — but that count lives in your local career stats and stays on your device.
| Data | Collected? | Leaves your device? | Linked to you? |
|---|---|---|---|
| Email, phone, address | No | — | — |
| Location | No | — | — |
| Contacts, photos, files | No | — | — |
| Display name (chosen, or a neutral default) | Yes | Yes, to the leaderboard | To your player number |
| Scores, Charge & league stats (best run, run count, division) | Yes | Yes, to the leaderboard | To your player number |
| Run replay (taps & timings, for score verification) | Yes | Yes, to the leaderboard | To your player number |
| Player number (random) | Yes | Yes, to the leaderboard | Pseudonymous |
| Career stats, achievements, settings | Yes, on device | No | No |
| Crash diagnostics & recent game events | Yes | Yes, to Crashlytics | No |
| Advertising identifier | Not yet (see Advertising) | — | — |
One Shot Cascade is not directed at children under 13, and we do not knowingly collect personal information from them. The game has no chat and no way to send a message to another player; the only thing you can make public is a short display name, which is filtered and can be reported. If you believe a child has provided a display name or other personal information through the game, contact us and we will delete it.
If this policy changes, the date at the top changes with it, and we keep every previous version — email us for any of them. A change that widens what is collected will not be applied retroactively to a version of the app already installed — it takes effect with the release that makes the change.