Your save file stays on your phone. We run no servers, and nothing you do in the game — your keeper’s name, your progress, your results — is ever sent to us. We could not read it if we wanted to.
If you choose Sign in with Google in Settings, a copy of your save is also kept in your own Google account through Google Play Games, so you can carry your career to another phone. That copy belongs to your account, not to us; we cannot see it either.
The one exception is advertising. The game shows ads from Google AdMob, and fetching an ad means Google’s servers see your device: its advertising ID, its IP address, and basic model information. That happens between your phone and Google. It does not pass through us, and it carries nothing from your save.
We wrote the long version anyway, because Google Play requires one and because a policy that only says “we respect your privacy” tells you nothing.
All of it lives in the app’s private storage area, which only this app can read.
| What | Why it exists |
|---|---|
| The name you choose for your goalkeeper | It is shown in the game and spoken by the commentator |
| Career progress — chapter, matches played, match history, milestones, rank | So the game continues where you left it |
| Player statistics — reflexes, diving, positioning, experience, level | The progression system |
| Inventory — coins, gems, hearts, gloves, teammates, avatar and frame | What you own |
| Settings — music volume, sound volume, language, privacy switches | Your preferences |
That is the complete list. There is no hidden field.
These are statements of fact about the build you are running, not promises about intent:
INTERNET permission exists for one reason — the ad SDK
described below — and the app itself contains no HTTP client, no socket,
and no websocket code of its own. There is no address belonging to us for
anything to be sent to.The game is free, and ads are how it pays for itself. They come from Google AdMob. Google is an independent controller of the data it collects this way, not a processor acting for us — which means Google’s own privacy policy governs it, and we have no access to it.
What an ad request involves. To choose and deliver an ad, the SDK sends Google your device’s advertising ID (AAID), an app-set ID that identifies this app on this device, IP address, device model, operating system version, screen size, coarse region derived from the IP address, and which ad slot in the game was shown. It does not send your keeper’s name, your save file, or anything you typed. All of it travels encrypted.
Where ads appear. In seven places you choose to enter — extra gems, a heart refill, keeping a daily streak you missed, an extra Rank match, a second chance at a saved shot, the keeper’s instinct, and changing your keeper’s name — plus one that appears on its own: after a results screen, no more than once every three matches and never within three minutes of the last one, and never after a defeat. That is the complete list.
Your consent, and how to change your mind. In the European Economic Area, the United Kingdom, and Switzerland the app asks before any personalised ad is requested, using Google’s certified consent platform (UMP). Your answer is remembered. To change it later, open Settings → Ad privacy options inside the game. Where the law does not require the question, the form is not shown.
If you live in a US state with a privacy law. California, Virginia, Colorado, Connecticut, Texas and a number of other states give you the right to opt out of the “sale” or “sharing” of your personal information and of targeted advertising. When Google uses your advertising ID to show you personalised ads, those laws can treat that as sharing — even though the data never reaches us. You can opt out at any time in Settings → Ad privacy options inside the game; once you do, the ads you see are no longer personalised. Deleting your advertising ID on the device, described next, has the same effect for every app.
Opting out on the device itself. Android lets you delete your advertising ID entirely: Settings → Privacy → Ads. Ads still appear, but they stop being personalised, and the ID is no longer available to any app on the phone.
Google’s policy for this data: policies.google.com/technologies/ads
From version 0.3.71 the game can keep a copy of your save in your Google account, using Google Play Games Services. It is optional.
What Google Play Games does on its own. If your phone has a Google Play Games profile, Google may sign you in automatically when the game starts and show a short “welcome back” message. That is Google’s service recognising your account on your phone; the game receives your Play Games display name and an ID for your Play Games profile, and nothing else about you. It does not see your email address.
What the game sends, and when. Only when you press Sign in with Google in Settings does the game read or write its cloud save. The save — the same data listed above under What the app stores on your device — is stored in a hidden app folder in your own Google Drive, which only this game can read and which does not appear among your files. If the copy in your account and the one on your phone disagree, the game asks you which to keep; it never overwrites either without asking.
Removing it. You can delete the game’s saved data from your Google account in the Google Play Games app (Profile → Settings → Delete Play Games account and data, or the game’s own entry there), or by removing the app’s access in your Google Account under Data & privacy → Third-party apps & services. We cannot do it for you, because the data is in your account and never in ours.
Google’s privacy policy governs this data: policies.google.com/privacy
When you open the developer diagnostic screen, the app reads your device model, operating system version, graphics adapter name, screen size, and screen density, and displays them to you on that screen. These values are used to choose the right layout and are never stored and never transmitted. They exist only for as long as the screen is open.
Be a Goalkeeper is not directed at children, and it is not listed in Google Play’s Families programme. Its store listing declares a general audience.
The only thing a player types is a goalkeeper’s name, and that name stays in the app’s private storage on the phone — we never receive it and cannot read it.
Because the game does show ads, we say plainly what that means rather than claiming an exemption we no longer have: an ad request reaches Google whoever is holding the phone. If you are a parent and would rather your child’s device did not carry an advertising ID at all, Android can delete it — Settings → Privacy → Ads — and it applies to every app, not only this one.
We do not knowingly collect anything from a child, under GDPR Article 8, COPPA, or Indonesia’s Personal Data Protection Law (UU 27/2022); we hold no data about any player at all.
Your data never reaches us, so you do not need to ask us for it. If you use cloud saves, the copy in your Google account is yours to manage there (see Google sign-in and cloud saves).
We hold nothing about you, so there is nothing for us to correct, export, or delete on your behalf.
We hold nothing, so we have nothing to sell, rent, or disclose, and we do none of those things.
There is exactly one recipient to list, and it never receives anything from us: Google, which receives an ad request directly from your phone when an ad is shown, as described under Advertising — and, only if you sign in with Google, your cloud save, as described under Google sign-in and cloud saves.
We do not sell your data for money. Under some US state laws, Google’s use of your advertising ID for personalised ads may still count as “sharing”; how to opt out is explained under Advertising.
This policy describes the app as it is built today. If a future version adds analytics, accounts, cloud saves, or in-app purchases, this policy will be updated in the same release that adds them, the effective date will change, and the app will tell you inside Settings before the new behaviour begins. We will not quietly widen what we collect.
The 5 September 2026 revision is that promise being kept: advertising was listed in the previous version as planned and absent, and this version was published in the same release that added it.
The 29 September 2026 revision corrects the list of places where ads appear. Two of them — keeping a missed daily streak and an extra Rank match — were added to the app after the previous revision and left off the list, and the three-minute gap between automatic ads was not stated. Both use the same ad service described above; nothing new is collected.
The 18 October 2026 revision adds the rights of players in US states with a privacy law, and how to use them. The app itself did not change what it collects; the option to opt out now also appears for those players.
The 22 October 2026 revision adds optional Google sign-in with cloud saves, in the release that adds them (version 0.3.71). Nothing changes for players who do not sign in, except that Google Play Games may greet a player whose phone already has a Play Games profile.
Still planned and still not present: in-app purchases.
Questions about this policy: porogapitstudio@gmail.com