Chompist: Privacy Policy

Last updated: September 4, 2026

Chompist collects a small amount of anonymous usage data to help us understand how the game is played, nothing more. You never make an account with us, and nothing we collect identifies you personally. On Android you can choose to sign in to Google Play Games for achievements, leaderboards and a cloud backup: that account is Google's rather than ours, and it is described under Google Play Games below.

There is one optional ad, and you only ever see it if you ask for it. It is described under Ads below. There are also two optional purchases, which collect nothing at all; see In-app purchases.

What we collect

With analytics enabled (it is on by default), the game sends us a short stream of gameplay events:

• App interactions: when a run starts and ends, which realm it was in, which of the endings it reached, how far up the size ladder you got, how long it lasted, and whether it was a campaign run, the daily challenge, or an endless run.
• Diagnostics: if the game hits an error, the file name, line number, error message, and what kind of error it was, so we can fix crashes. Warnings are not reported, and the same fault repeating is sent once rather than over and over.

Each event is tagged with a randomly generated install identifier, a per-session random identifier, the app version, the platform name (e.g. “android”), and a timestamp. The install identifier is minted on your device, is not derived from your device or any account, and is deleted when you uninstall the game.

How the game closed last time

When the game opens, it asks the operating system how it closed the last time: whether it crashed, ran out of memory, or was simply closed by you, whether it was on your screen at the time, roughly how much memory it was using, when it happened, and which version of the game it was. We do this because a game that crashes cannot report its own crash, so the report has to come afterwards, from the system that watched it happen.

It is a single line about the app. It describes nothing you did, contains nothing about you, and is covered by the same opt-out as everything else on this page.

The session’s first event also carries two facts about the phone itself, and no more: roughly how much memory it has, and its operating system version. Those say which devices the game is too heavy for, and which ones can answer the question above at all. Neither is unique to you, and there are millions of phones that would answer both identically.

What we do NOT collect

• No names, email addresses, or accounts of ours. If you sign in to Google Play Games, the game reads your gamer tag so that Settings can show you which account is signed in. It is never written to your save file and never sent to us.
• No device serial numbers.
• No location. Our own server does not log or store IP addresses; Google's ad serving does receive your IP, which is why it is disclosed under Ads rather than denied here.
• No contacts, photos, files, microphone, or camera: the game never asks for those permissions.
• Nothing is ever sold. Our analytics goes to our own self-hosted service and stays there. The only data shared with anyone is what Google needs to serve the optional ad, and whatever you choose to send to your own Google account by signing in to Play Games.

How we use it

Aggregate analytics only: how many people play, whether they return, and (the question we actually built this to answer) which realm people stop in. Our analytics is not used for advertising, profiling, or any per-person decision, and it is encrypted in transit (HTTPS). The advertising data described below is separate from it and is not combined with it by us.

Ads

The game shows one kind of ad, and only when you ask for it. When something eats you, the game-over screen may offer a short video; watching it lets you carry on from where you died, once per run. There are no banners, nothing plays between runs, and if you never tap the offer you never see an ad at all.

The video is served by Google AdMob. To do that, Google reads your device's advertising ID and receives your IP address and basic app and device information, and uses them to serve and measure the ad and to prevent ad fraud. We do not receive your advertising ID ourselves, but it is read by software inside our app, so we disclose it as collected.

Where the law requires it (the EEA, the UK and Switzerland) you are asked for consent before any personalised ad is shown, and you can change that answer at any time from the privacy options in Settings. Your device's own “limit ad tracking” or “delete advertising ID” controls apply on top of anything we do. Google's handling of this data is covered by Google's privacy policy.

In-app purchases

The game offers two one-time purchases: "Remove Ads", which gives you the same continue the rewarded video offers without the video, and "Supporter Badge", which adds a badge to the realms screen and nothing else. Neither changes what you can eat or what can eat you.

Payment is handled entirely by Google Play. We never see your card, your billing address, or your Google account. What reaches the game is a yes-or-no answer about what you own, kept in the same local save file as your progress. A purchase sends us nothing. It produces no analytics event, so unlike a run or an ad, it leaves no trace on our server at all.

Restoring a purchase asks Google Play what your account owns. Google's handling of the transaction is covered by Google's privacy policy. The iOS version has no shop and offers no purchases.

Google Play Games (Android only)

On Android you can sign in to Google Play Games from Settings. The game never asks at launch and never asks twice, and it plays exactly the same if you never sign in: signed out, everything below is skipped rather than queued. There is no Game Center on iOS, so none of this exists there.

Signing in is handled entirely by Google. We do not receive your Google account, your name, or your email address. What the game sends is progress you have already earned in it: achievements (clearing each of the twelve arenas, finishing the ladder, daily streaks, and lifetime totals of prey eaten) and leaderboard scores (your best overall, your best in each arena, today's daily board, and endless). Nothing else is submitted, and no score carries anything but a number. Google's handling of it is covered by Google's privacy policy.

The game does read your gamer tag once you are signed in, so that the settings card can say who you signed in as. It is held for the session only, never written to your save file, and never sent to us.

You can sign out at any time from the Google Play Games app, which stops every submission above. Nothing in the game is lost or locked if you do: your progress lives in the save file on your device either way.

Your choices

• Turn it off: Settings. Turning it off stops collection immediately and discards anything queued but not yet sent.
• Reset your identity: a “Reset Analytics ID” control generates a fresh random identifier; data collected before the reset can no longer be associated with your device.
• Deletion requests: email us (below) and we will delete the server-side data for the install identifier you reset or describe.

The game itself never needs a connection. Events are queued on your device and sent later, so Chompist plays exactly the same offline.

Local saves, and the optional cloud backup

Your game progress is stored in a save file on your own device. Uninstalling the app deletes it, along with the install identifier.

Cloud backup is off unless you turn it on. With it enabled in Settings, and only while you are signed in to Play Games, a Back up now button copies that same save file into your own Google account, using Play Games' saved-games feature, so a new or reset phone can pick your ladder back up. Both the backup and the restore are buttons you press: nothing syncs on its own, and a restore takes effect the next time the game starts. This is the only circumstance in which your progress leaves your device, and it goes to Google rather than to us. We cannot read it.

Children

The game collects the same minimal anonymous data from everyone. Our own analytics is never used for advertising or profiling. The optional rewarded video is served by Google AdMob as described above; the game is not directed at children under 13.

Changes

If a future update changes any of the above, this policy is updated before that version ships, and the in-store data-safety section is revised to match. That happened as intended twice: the optional ad arrived in version 0.11.0 and the two purchases in version 0.11.2, and this page moved with each of them rather than after.

The Play Games section above is the exception, and it is recorded here rather than quietly backfilled. Sign-in, achievements, leaderboards and the opt-in cloud backup all shipped in version 0.11.2 as well, and this page did not move with them: it went on saying there were no accounts while the game was offering one. That was fixed on August 24, 2026. Nothing new was collected in the meantime, and nothing was ever sent to us that this page did not already describe, but the page understated what a signed-in player was sharing with Google, and it should not have.