Downward privacy policy
Last updated: 8 November 2026
Summary
Downward is a puzzle game with no accounts, no sign-up and no server of its own. The developer does not receive your name, your email or your saved game.
The only data that leaves your phone is sent by the Google services the game uses:
- Google AdMob, to show the reward videos, which are always optional.
- Google Play, for the "Remove ads" purchase and for rating the game.
- Google Firebase (Analytics, Crashlytics and Remote Config), to learn which levels are hardest, detect crashes and tune in-game prices. Only if you agree in the privacy message (in the European Economic Area, the United Kingdom and Switzerland); without your consent it sends nothing.
Below is what each one collects and how to control it.
What is stored on your phone, and only there
Your progress and preferences are kept in the app's private storage, which no other app can read:
- Your saved game (
save.jsonand its backupsave.bak): levels completed, stars, coins, your daily challenge streak and the "Remove ads" purchase, if you made it. - Your preferences: volume, vibration, high contrast and whether you want the daily challenge reminder.
- The times you usually start playing (those of your last sessions, the hour only): to send the daily challenge reminder at your usual time (below). They never leave your phone.
- A local play log (
play_log.jsonl): which levels are played and how hard they are, so the difficulty can be tuned. The file never leaves your phone (unless you copy it out yourself with the hidden export option); with your consent, a reduced version of those same events is sent to Firebase (below). - The last price settings received (
remote_tuning.json): the prices of a hint and of skipping, the free-coin videos per day and the level where hints and the shop appear.
Android backup is disabled for this game, so none of this is uploaded to your Google account. Everything is deleted when you uninstall the app, or from Android Settings › Apps › Downward › Storage › "Clear data".
Ads (Google AdMob)
The game offers reward videos: coins, a hint, skipping a level, doubling a reward or saving your streak. Watching them is always optional and you always decide when. The game has no banners.
To show these videos, measure them and prevent fraud, Google's ads SDK (AdMob) collects and sends to Google, according to Google:
- Device identifiers: the Android advertising ID and other device and app identifiers.
- Approximate location, inferred from your IP address. Precise location is not used: the game has no location permission.
- App interactions: for example, which ads are shown and when they are tapped.
- Diagnostics: crash logs and performance data from the SDK itself.
This data is used to show and measure ads, for analytics and to prevent fraud. It is encrypted in transit and Google handles it under its privacy policy (https://policies.google.com/privacy) and its explanation of how it uses data from apps that use its services (https://policies.google.com/technologies/partner-sites).
Consent. In the European Economic Area, the United Kingdom and Switzerland, the game asks you at the start whether you accept personalised ads. You can change your answer at any time in Settings › "Privacy options". If you decline, the videos are still available, just not personalised.
Advertising ID. You can reset or delete it in Android Settings › Privacy › Ads.
Ads are requested with the content rating for all audiences.
Statistics and crashes (Google Firebase)
Starting with the version that includes this policy, the game may use three Google Firebase services:
- Firebase Analytics: the game's events, the same ones as the local play log: which level is played, how many attempts, turns and seconds it takes, whether a hint is used or the level is skipped, coins earned and spent, the daily challenge and its streak, reward videos offered and watched, purchases (only which product and whether it succeeded, never payment details) and visits to the shop and the Collection. Firebase adds an app instance identifier (random, deleted when you uninstall), the phone model, Android version, language, country derived from the IP address and session length.
- Firebase Crashlytics: if the game closes because of a crash, a technical crash report (where the code failed, phone model, Android version, free memory) with the level being played.
- Firebase Remote Config: the game occasionally asks for its prices and limits (hint, skip, videos per day, shop level) so they can be adjusted without releasing a new version. Always within fixed limits set in the game; without an answer, the usual values are used.
Not sent: your name, email, Google account, saved game, advertising ID (disabled for Firebase) or anything you type. Firebase is not used for ads or ad personalisation.
Consent. All of this is off when you install the game. In the European Economic Area, the United Kingdom and Switzerland it is only turned on if, in the privacy message, you accept storage on the device and measurement, with Google as a vendor; otherwise nothing is sent. In those regions you can withdraw consent at any time in Settings › "Privacy options", and the game stops sending data from then on; crash reports stored without your consent are deleted without being sent.
Outside those regions the privacy message does not appear and this data is sent without prior consent. In any country you can turn it off in Settings › "Stats and crash reports": from then on the game sends no statistics or crash reports and does not fetch remote configuration, and pending crash reports are deleted without being sent. Clearing the game's data (or uninstalling it) also deletes the instance identifier.
Google processes this data as a processor, encrypted in transit, under its Firebase terms (https://firebase.google.com/support/privacy). Analytics events are kept for 2 months and crash reports for 90 days; after that they are deleted automatically.
Test versions of the game (the Google Play closed test) send this data to the same Firebase project as the published version, under the same consent rules.
Daily challenge reminder
The game can send you a local notification at the time you usually play, if you have not played that day's daily challenge yet, and another one the next day if you still do not come back; after that, none until you play again. It is optional and off until you accept it: the game only asks after you win your first daily challenge, never when it opens, and on Android 13 or later Android also asks for the notifications permission. You can turn it off at any time in Settings › "Daily reminder" or in Android's notification settings.
The notification is scheduled by the phone itself: it does not go through any server and does not use Firebase or any messaging service. To choose the time, the game stores on the phone the times you started your last sessions (above); they are not sent anywhere.
Purchases (Google Play)
"Remove ads" is a one-time in-app purchase. Payment is handled entirely by Google Play: the developer does not receive, see or store your payment details. The game only receives from Google Play the confirmation that the purchase exists, to activate it and to restore it.
Ratings and sharing
- Rating the game: the game may open Google Play's rating window. What you write goes to Google Play, not to the game.
- Sharing the daily challenge: the result is shared through Android's share sheet, only if you tap the button and choose where. The text contains the challenge number, the turns and the link to the game's page; no personal data.
Permissions the app requests, and why
- Internet and network state (
INTERNET,ACCESS_NETWORK_STATE): to load the reward videos and for Google Play purchases. - Advertising ID (
AD_ID): used by AdMob, as explained above. - Google Play billing (
com.android.vending.BILLING): for "Remove ads". - Vibration (
VIBRATE): feedback when turning and scoring; it can be turned off in Settings. - Android Privacy Sandbox (
ACCESS_ADSERVICES_AD_ID,ACCESS_ADSERVICES_ATTRIBUTION,ACCESS_ADSERVICES_TOPICS), on Android versions that have it: Google's alternative to the advertising ID for showing and measuring ads. It is controlled in Android Settings › Privacy › Ads. - Notifications (
POST_NOTIFICATIONS, Android 13 or later): for the daily challenge reminder, only if you accept it (above). - Keep awake and start at boot (
WAKE_LOCK,RECEIVE_BOOT_COMPLETED): used by the Google libraries AdMob uses and by the daily challenge reminder (to schedule it again if you restart the phone). - Basic phone state and foreground service (
READ_BASIC_PHONE_STATE,FOREGROUND_SERVICE): added by the Google libraries AdMob uses for its internal operation.
None of these permissions give access to your calls, contacts or files.
- Install source (
BIND_GET_INSTALL_REFERRER_SERVICE): added by Firebase Analytics to know where the game was installed from (for example, the Google Play listing). Only used with your consent, like the rest of Firebase.
The game does not request location, camera, microphone, contacts, photos or files.
How to delete your data
The developer of Downward does not keep any of your data on a server of its own:
- On your phone: uninstall Downward, or go to Android Settings › Apps › Downward › Storage › "Clear data".
- Ads data: reset or delete your advertising ID (above). Whatever Google has collected is managed from your account at https://myaccount.google.com.
- Firebase data: it is not linked to any account or to your name, only to a random app instance identifier you never see, so the developer cannot find yours to delete it individually. It is deleted automatically (events after 2 months, crash reports after 90 days); the identifier is deleted when you uninstall or clear the app's data, and anything sent afterwards is no longer linked to what came before. In the European Economic Area, the United Kingdom and Switzerland, withdraw consent in Settings › "Privacy options" so nothing more is sent.
Children
Downward is intended for ages 13 and up and is not directed at children. It has no chat, no content from other players and no way for people to communicate with each other.
Changes
If a future version changes what is collected, this policy will be updated before that version is published.
Contact
For any question about this policy, write to downwardgame@proton.me.