Privacy Policy
GUST
GUST has no account and no sign-in, and never asks for your email, phone number, contacts, photos or location. It has a world leaderboard, so that players can see how their runs compare. To make that work, the game sends your run results, a replay of each run so the score can be checked, a display name, and a randomly generated player number to our leaderboard service. It 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”). That is the whole list; the rest of this page explains each item.
GUST still plays fully offline. Everything above needs a connection and happens only while your phone is online; with no connection the game plays exactly the same, and nothing is sent.
This policy applies to GUST on iPhone and Android, from version 1.0.0. This revision brings the play statistics and Microsoft Clarity together in one section, Usage data; what the game collects has not changed. The previous revision added Microsoft Clarity and the “Help improve the game” switch, both new in version 1.1.1.
What stays on your device
Most of what the game remembers never leaves the phone. It is kept in the app's own private storage, and we cannot see it:
- Your career stats, personal bests and the achievements you have unlocked
- Your settings: the look (Gust or Lumen), sound, music, haptics, reduce motion, and your answer to “Help improve the game”
- A run in progress, so leaving the app does not cost you the run
- The most recent copy of the word list described below
Deleting the app deletes all of this. Your phone's own backup (an iCloud, Google or computer backup) may include the app's files along with everything else it backs up; that is between your device and your Apple or Google account, and we never see it.
The world leaderboard
The leaderboard runs on Google Firebase (Cloud Firestore). When you finish a run, the game submits:
- The run's result: the score, how deep you went, the pollen caught, your best combo, the petals lost and how long the run lasted.
- A replay of the run: the run's random seed and the touches you made, with their timings. The replay is how a score can be checked rather than taken on trust. It describes what happened inside the game and nothing outside it: no location, no device details, nothing typed.
- A display name. The game makes one up for you, and you can change it in Settings. It is free text, up to 16 characters, so it says something about you only if you put it there. Other players see it, so it is checked against a word filter when you set it, and other players can report it.
- A player number: a random identifier created the first time you open the game, using Firebase Anonymous Authentication. It keeps your runs together on the board. It is not linked to your real identity, your email or any account, because there is no account. You can see and copy it in Settings.
If you change your display name, the game also keeps one small record on the server holding that name, so your runs on the board show it.
Other players can see your display name and your runs' scores and depths. Each run entry is stamped with an expiry when it is posted and is deleted 90 days later. All of this is processed by Google as our service provider, under Firebase's data processing terms.
Taking part is on by default. You can turn it off with the Leaderboard switch in Settings. While it is off, the game submits no runs and no display name. It still signs in to Firebase anonymously when it starts, because that is where the player number comes from, but it sends nothing to the board. Crash reports and the usage data below are separate from this switch.
Reporting a display name
If you report another player's name from the leaderboard, the report contains 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). No player can read reports. They are used only for moderation.
Crash reports (Firebase Crashlytics)
The game uses Firebase Crashlytics, a Google service, so that crashes can be found and fixed. When the game crashes, Crashlytics sends:
- The stack trace: the line of code the crash happened on
- Your device model, operating system version and the app version
- The device's state at the moment of the crash: free memory and storage, orientation, and whether the device was jailbroken or rooted
- A randomly generated Crashlytics installation identifier. It is not linked to you and resets if you reinstall.
- A short log of the last game events before the crash, so the crash can be traced to what the game was doing. It describes gameplay only and never includes your name or anything you typed.
Crashlytics keeps these reports for 90 days.
Usage data
So we can see how the game is actually played, it sends anonymous usage data to two services: play events to Google Analytics for Firebase, and a replay of how you used the game’s screens to Microsoft Clarity. One switch turns both off, described at the end of this section.
Usage events (Firebase). The game counts anonymous play events through Google Analytics for Firebase: that the app was opened, that a run started, how a run ended (score, depth, pollen and how long it lasted), when a Drift began and ended and how long it lasted, which look you chose, and that a run was shared. It also records the standard session information that service collects. These describe the game being played, not the person playing it. We use them for one thing: to see how the game is actually played so it can be improved.
Advertising-identifier collection and ad personalisation are switched off in the app's configuration, and the events never include your display name or player number. Google derives a general location (country, sometimes region) from a masked IP address so that 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 ravine, the menus, what was tapped and when), rebuilt from what the game drew, so we can see where people get stuck or stop playing. Anything you type is hidden before it leaves your phone: the display-name box is masked, and so are your display name, your player number and the names on the leaderboard wherever the game shows them. 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.
Clarity’s part is captured and sent only while your phone is online. With no connection none of it is sent, and the game plays exactly the same.
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 and the leaderboard have their own rules, described above.)
The word list
So that player names can be checked for offensive words, GUST downloads a public list
of words from our website (bendigogames.com/moderation/name-filter.json)
when it starts. The request sends nothing from the game: no name, no score, no
identifier. As with any web page, the website's host, Cloudflare, sees the connection's
IP address in order to answer it. We do not use it to identify you.
The connection itself
Whenever the game talks to Firebase (submitting a run, fetching the board, sending a crash report), Google's servers see your device's IP address, and Microsoft's servers see it when usage data is sent to Clarity, as 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 their data processing terms, which include the EU's standard contractual clauses for international transfers.
Links, sharing and ratings
The Privacy, Support and App Store links in Settings open in your phone's browser or store, which have their own privacy policies. The share button hands a short line of text about your run to your phone's share sheet; the game does not see where you send it. After a new personal best the game may ask the store to show its standard rating card; the store decides whether it appears, and the game never sees whether or how you rated it.
What we do not do
- No account, no email, no phone number, no contacts, no photos, no files
- No location services, precise or approximate
- No advertising identifier and no cross-app tracking, so the game never shows a tracking prompt
- No in-app purchases
- No selling or sharing of data with anyone other than Google and Microsoft, acting as our service providers for the purposes above
Summary
- Display name: sent to the leaderboard (unless the Leaderboard switch is off), linked to your player number
- Run results and run replays: sent to the leaderboard (unless the switch is off), linked to your player number, deleted after 90 days
- Player number (random): sent; pseudonymous
- Crash diagnostics and recent game events: sent to Crashlytics; not linked to you
- Usage data (play events; taps, scrolls and screens visited, replayable; typed text, names and the player number hidden): sent to Analytics and Clarity while online (unless Help improve the game is off); not linked to you
- Approximate location (country or region, from the IP address): worked out by Analytics and Clarity; never precise
- Career stats, achievements, settings: on your device only
- Email, phone, contacts, photos, location: never collected
Children
GUST is not directed at children under 13, and we do not knowingly collect personal information from them. The display name is the only free-text field. If you believe a child has put personal information in it, email us with the player number shown in Settings and we will remove it.
Your choices and your rights
- Stop sending leaderboard data: turn off Leaderboard in Settings.
- Stop usage data: turn off Help improve the game in Settings. It stops straight away.
- Change your display name: Settings, Player name.
- Delete what the server holds: email support@bendigogames.com with the player number shown in Settings, and we will delete every run entry and record under it. We cannot find you by name, and we do not need to.
- Delete what the device holds: delete the app.
Data-protection laws such as the GDPR and the CCPA give you rights to access, correct and delete personal data about you. The address above is how to use them.
Changes to this policy
If a version of GUST changes what it collects, this page is updated, with a new date, before that version is released.
Contact
GUST is made by Bendigo Games. Questions about this policy or about privacy in the game: support@bendigogames.com.
Last updated: 18 November 2026