← Bendigo Games

ONE SHOT

Cascade

Privacy Policy

Last updated: 18 November 2026 · Applies to One Shot Cascade on Android and iOS. This revision brings the usage analytics and Microsoft Clarity together in one section, Usage data; what the game collects has not changed. The previous revision (16 November 2026) added Microsoft Clarity and the “Help improve the game” switch, both introduced in version 1.0.4.

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, sends anonymous usage data so we can see how it is played (it can be turned off in Settings, under “Help improve the game”), and — only if you allow notifications — registers a push token so it can tell you when your rank changes. That is the whole list, and the rest of this page explains each item.

What stays on your device

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.

What leaves your device

Leaderboards and leagues

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.

Reporting a display name

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.

Crash reports (Firebase Crashlytics)

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.

Rank notifications (new in version 1.0.2)

The game can tell you when something happens to your standing — when another player passes you on the leaderboard, or when you have been away and your position has moved. This only happens if you allow notifications when your phone asks; decline, and nothing in this section applies to you.

If you do allow them, the game registers a push token with Firebase Cloud Messaging and stores it with your player number, so the server knows which device to notify. A push token is a long random string issued by Apple or Google that identifies an installation of this app on one device. It is not your phone number, not your account, and not an advertising identifier. It changes if you reinstall the app, and it is useless to anyone who cannot send through Google's or Apple's notification service.

You can turn notifications off at any time in your phone's settings, and the token stops being used the moment you do. Uninstalling the app has the same effect.

Usage data

So we can see how the game is actually played, it sends anonymous usage data to two services: usage events to Google Analytics for Firebase (since version 1.0.2), and a replay of how you used the game’s screens to Microsoft Clarity (since version 1.0.4). Both are controlled by one switch, described at the end of this section.

Usage events (Firebase). The game counts anonymous events through Google Analytics for Firebase: that the app was opened, that a run started, that a run ended and how it went, and the standard session information that service records. These describe the game being played, not the person playing it.

Advertising-identifier collection is switched off in the app's configuration on both platforms, the events are not linked to your name or email (the game has neither), and they are used for one thing only — understanding how the game is actually played so it can be improved. Google also derives a general location from a masked IP address — country, sometimes region — so the counts can be broken down by place; that approximate figure is all we see. The game never uses your device's location services and never asks for location permission.

Taps, scrolls and screens (Clarity). The game uses Microsoft Clarity, as our processor, to capture taps, scrolls and the screens you visit, which can be replayed: a replay of how you used the game’s own screens — the board, the menus, what was tapped and when — rebuilt from what the game drew, so we can see where people get stuck or give up. Anything you type is hidden before it leaves your device: the display-name box is masked. Clarity also notes your device model, operating-system version, the app version and the length of the session.

Sent with it is a random identifier Clarity creates for this installation, so that one person’s sessions count once. It is not your advertising identifier, it is replaced if you reinstall the app, and the game never links it to your player number, your display name or anything else about you. Like Google, Microsoft works out an approximate location (country, sometimes region) from your IP address; never a precise one. This usage data is used only to understand and improve the game, never for advertising or tracking. Microsoft keeps the replays for 30 days and the aggregate figures (such as how many sessions reached the results screen) for up to 13 months. Nothing is sent to Clarity while you play offline.

Turning it off. Settings → Help improve the game. Off, the game sends no usage data to either service, from that moment and on every later launch, until you turn it back on. It is on by default. The game plays exactly the same either way. (Crash reports, the leaderboards and notifications have their own controls, described above.)

The connection itself

Whenever the game talks to Firebase — submitting a run, fetching a board, reporting a crash — Google's servers see your device's IP address, and Microsoft's servers see it when usage data is sent to Clarity, the way any server sees the address of anything that connects to it. We never see or store it. Google and Microsoft process it as our service providers, 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

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.

Sharing your score

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.

Summary

DataCollected?Leaves your device?Linked to you?
Email, phone, addressNo——
LocationNo——
Contacts, photos, filesNo——
Display name (chosen, or a neutral default)YesYes, to the leaderboardTo your player number
Scores, Charge & league stats (best run, run count, division)YesYes, to the leaderboardTo your player number
Run replay (taps & timings, for score verification)YesYes, to the leaderboardTo your player number
Player number (random)YesYes, to the leaderboardPseudonymous
Career stats, achievements, settingsYes, on deviceNoNo
Crash diagnostics & recent game eventsYesYes, to CrashlyticsNo
Usage data (app opened, run started, run ended; taps, scrolls and screens visited, replayable; typed text hidden; switch in Settings)YesYes, to Analytics and ClarityNo
Approximate location (country/region, from the IP address)YesYes, to Analytics and ClarityNo
Push token (only if you allow notifications)YesYes, to Cloud MessagingTo your player number
Advertising identifierNot yet (see Advertising)——

Children

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.

Your choices and your rights

Changes to this policy

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.

Contact

Get in touch

Email: support@bendigogames.com

Developer: Bendigo Games