Privacy Policy — Pro Football Agency
Read this first. This policy describes what the Android version of Pro Football Agency does today. The app is available on Google Play. The game itself runs offline and never sends your saves anywhere; separately from that, the app contains Google's advertising and ad-consent tools, and if you have shared a birth year that meets the ad age threshold, those connect to Google every time the app opens. Separately from both, the app offers products that can be bought through Google Play, and it asks Google Play a set of store questions at every launch — that path does not depend on the birth year declaration. These are three different things and they are described separately below. In addition, the app may occasionally ask Google Play to show its rating window; that has a section of its own.
Short version
Pro Football Agency is a single-player football agent game. There is no account, no sign-in, and the developer runs no server for it. Your careers, your agency name and your settings are written to the app's own storage on your phone.
Four separate things follow, and they should not be merged. First: the game does not send your saves or anything you typed to the developer or anywhere else. Second: if you write to us, your support message and your email address reach the developer. Third: because the app is distributed through Google Play, the store's own reports and the reviews written on the store are visible to the developer. As for the rewarded ad in the app, you start it yourself and get in-game money back; apart from that, a full-screen ad can open on its own once every ten played weeks. The advertising is run by Google, so ad-related data goes to Google rather than to the developer. Fourth: the app offers products that can be bought through Google Play; Google Play takes the payment, your card details never reach the app, and all the app receives is the record of the purchase.
What the game stores on your device
The following is kept on your phone, in the app's own storage. The game does not send any of it anywhere on its own. There is one exception, written out below: when you start a purchase, that career's identifier and that attempt's number are handed to Google Play. Apart from that, if Android backup is enabled on your device, your operating system can include this data in a backup — that is done by Android, not by the game, and is described under Android backup.
- Your career saves. Up to three career slots. A save holds the game world and your progress in it: the agency and manager name you typed, your clients, your money, your reputation, the leagues you have discovered, match history and in-game messages. The app never asks for your real name, email address, phone number or location. The agency and manager name is free text; whatever you type there stays on your device like the rest of the save.
- Your settings. Theme, language and sound preference.
- Your birth year — only if you share it. We ask for your birth year before any ad can be shown: when the app opens, and when you tap the + button next to your money (What happens when the app opens). Only the year is stored; the month and day are not asked for. If you do not share it, nothing is written and the game works exactly the same. It is not part of a career save but of your device preferences — deleting a career does not delete it. It is not sent to the developer and is not attached to ad requests.
- Your daily reward record. Which career used today's ad reward, and whether a showing was interrupted. It exists so the same reward is never credited twice.
- Rating request record. How many times the app has asked Google Play for its rating window, when it last did, and whether you opened the store page from Settings, kept in your device preferences. It exists to keep those requests rare. Whether you rated, and what you wrote, is not in it — the app does not know.
- Ad break marker. The played week of a career's most recent automatic ad break is kept in the career save. It exists so a second ad never opens at the same break, and so the next break can be worked out.
- Your purchase records. Nothing is written before a payment starts — picking a pack on the store screen creates no record on its own, and a failed or abandoned payment leaves no trace in that career. Even so, these records are not created only by a completed purchase; two separate things are kept:
- The record of the entitlement granted. The purchase token issued by Google Play and which product it belongs to. Capacity packs sit in the career save they belong to; ad removal sits in your device preferences.
- A transaction queue. Unfinished transactions, and ones whose state is not settled, are kept in a queue held for the device as a whole: payments still pending, entitlements granted whose closure could not be verified, and transactions whose target career no longer exists. This queue does not belong to any single career.
- Prices are not stored, but they do reach the app. The app gets the localized price of each product from Google Play and shows it on the store screen; it does not write it to the device and asks again at every launch. Card and billing details are a separate matter entirely: they never reach the app and are stored nowhere.
- Local identifiers. Each career gets a randomly generated identifier when it is created, and each reward request and each purchase attempt gets a randomly generated number. They are used to match career, reward and purchase records to each other. They are not generated for the purpose of tracking across apps, they are not attached to ad requests, and they are not sent to the developer. When you start a purchase, the career's identifier and that attempt's number are handed to Google Play together — so that the entitlement can be written to the right career once the payment completes (Purchases and Google Play). Because they are part of your saves, they can be included in an Android backup if backup is enabled.
What the game does not do on its own
- The game does not send your saves, your settings or anything you typed to the developer or to any server.
- The game has no analytics, crash reporting or usage tracking of its own.
- The game never starts a purchase on its own. A real-money payment happens only when you pick a product on the store screen and confirm Google Play's payment sheet; your card details do not pass through the app (Purchases and Google Play).
- There are no banner ads and no app-open ads. The rewarded ad opens only when you ask for one; apart from that, the only ad that opens on its own is the full-screen ad that can come once every ten played weeks (Automatic ad every ten weeks).
- The game does not sync your saves to a cloud account. Backup can only happen through Android's own feature, described below.
- The game gives nothing in return for a rating or a review. The rating window is never placed behind a question such as "do you like the game?", and the rating you give changes nothing in the game (Rating requests).
What happens when the app opens
The birth year question. On Android, if no birth year has been shared on the device yet, a short screen asking for it opens over the menu once the menu has been drawn. It says that the game shows ads and that the birth year is asked before any can be shown; it does not mention any reward. You can continue without sharing — the whole game, your careers and your saves stay available. Skipping writes nothing, so the question comes back the next time the app opens, until you share a year. Once a year has been shared — whether it meets the threshold or not — it is not asked again; you can change or delete it from Settings. The screen itself is drawn by the game and connects to nothing. In a web browser the question does not appear at all.
The steps below run only if you have shared your birth year and your declaration meets the ad age threshold. If you have not shared it, or it is below the threshold, the app does not start the ad path on its own: at startup your consent information is not read, no consent screen is attempted, and the advertising library is not initialised.
The limit of that statement belongs here too. Measurements were taken on a test device, and what was verified is this: with no birth year shared, the app made no call to the advertising component, and no connection to any advertising address appeared in the logs.
On the other hand, when the app was opened for the first time, some network traffic was recorded against the app's own account even though the ad path was closed. What produced that traffic was not determined. On a later launch on the same device, again with the ad path closed, no traffic was measured during the observation window. The advertising library is installed on the device together with the app and carries its own startup component; whether the measured traffic came from that component, from the browser component inside the app, or from something else was not established.
So we do not claim that "no network connection is made while the ad path is closed". What we say is narrower: the app does not start the ad path on its own.
The store side is separate from all of this and does not depend on the birth year declaration: on Android, at every launch, the app asks the Google Play app on your device a set of store questions. What those are is described under Purchases and Google Play. The measurement above concerned calls made to the advertising component and does not cover this store path.
If your declaration meets the threshold, then every time you open the app, the menu is drawn first and then these steps run in the background:
- The app connects to Google's ad-consent tool and refreshes your consent information.
- If a consent screen is required for your region, Google's tool draws it. What is asked and which options are offered is decided by Google's tool; the game does not control that content.
- If the result allows ad requests, Google's advertising library is started. Starting it also connects to Google.
- If the result does not allow ad requests, the advertising library is never started and the + button does not appear in the game.
- If the result allows ad requests, the full-screen ad for the next ad break is loaded in the background beforehand. That load never makes the screen wait, and it does not happen at all if you bought the ad removal product. In a long session a loaded ad is treated as stale after about 50 minutes and a new one is loaded in its place, because Google does not allow an ad older than an hour to be shown.
These steps run even if you never tap the ad button. The menu, your saves and the rest of the game do not wait for this flow: if your device is offline the flow does not complete, the game still opens at normal speed, and only the + button is missing.
The result of the consent flow determines one thing: whether an ad may be requested. It is not a measurement of what data was actually collected.
Ad privacy options are a separate path. When you tap that row in Settings, Google's consent tool is contacted even if you never shared a birth year or have deleted it: managing the consent you gave earlier needs current information. That connection starts from your tap, not at startup, and it does not initialise the advertising library.
You start the ad yourself
On the career screen there is a small + button next to your money. Tapping it does not start an ad; it only opens a window.
If you have not shared your birth year yet, the window does not open at all: + takes you straight to the declaration screen. The reward amount is not shown there, and the screen does not tell you which answer opens the feature; you can continue without sharing. If your declaration is below the threshold, the window that opens says so neutrally, still does not show the amount, and does not invite you to change your answer.
If your declaration meets the threshold, the window shows the reward amount, the state of your daily allowance, and a button clearly labelled "Watch an ad". The ad starts only when you press that button. The button can be pressed only while today's reward is available; if it has been used, or another ad or consent step is running at that moment, the window says so and the button stays disabled.
The + button itself is not always there either: it is not drawn at all if the advertising component has not been started on the device, or if the consent result does not allow ad requests.
- An ad opens only when you press the "Watch an ad" button in that window.
- The reward is separate for each career and available once a day. The day is calculated from your device's local calendar; when the local day turns over, the reward becomes available again. Two careers do not consume each other's reward.
- The reward is in-game money — not real money, not a gift card, not store credit.
The reward is credited when the advertising component reports that the reward condition has been met. That report can arrive before the ad screen closes — what determines the reward is the report, not the screen closing. If no such report arrives, no reward is credited and the day's reward is not treated as used.
These are real ads: they come from Google AdMob through the app's own ad units. There is no ad mediation network; ads are served only through Google AdMob.
Automatic ad every ten weeks
Separately from the rewarded ad, a full-screen ad can open on its own once every ten played weeks of a career. The count is the career's total played weeks; it does not reset when a season ends, so the interval carries straight on from one season into the next. In a new career the first break comes in week 10.
- Each break is worth one ad and is marked in the career save. The mark is written before the week is saved, so redrawing the screen, reloading the save or closing and reopening the app cannot produce a second ad at the same break.
- The game never waits for the ad. If no ad happens to be loaded at that moment, nothing opens and the week advances normally; that break is then used up, and the ad does not open later on some other screen. Closing the ad, or an error, does not touch game state.
- The interval is counted in played weeks, not in minutes. If you advance weeks quickly, two breaks can come within a few minutes of each other.
- These ads also depend on the birth year declaration and the consent result. If you have not shared a declaration, if it is below the threshold, or if the consent result does not allow ad requests, nothing is loaded and nothing is shown.
- If you bought the ad removal product in the store, these ads are not shown and are not loaded either. That product does not switch off the rewarded ad: you start that one yourself and are paid for it.
- There are no banner ads, no app-open ads, and no ad that opens on its own anywhere else in the game.
These ads come from the same Google advertising library; what goes to Google is described in the section below. They are real ads too: they come from Google AdMob through the app's own ad unit, and here as well there is no ad mediation network.
What goes to Google with the ads
This section applies to both kinds of ad: the rewarded ad you start yourself, and the automatic ad every ten weeks. The advertising side is run by Google and that data does not reach the developer. Google publishes its own account of what the advertising library collects for the version used in this app. According to Google's own data disclosure, the library collects and shares:
- IP address — which may be used to estimate your general location.
- App and ad interactions — app launches, taps, video views.
- Diagnostic information — performance data such as launch time, hang rate and energy usage.
- Device and account identifiers — the Android advertising ID, the app set ID, and, if applicable, other identifiers related to signed-in accounts on the device.
Google states that this data is encrypted in transit using Transport Layer Security. The list above is Google's own statement, not a measurement made by the developer, and Google may update it over time — the current version is always on Google's data disclosure page.
How Google generally uses information coming from apps is described on Google's page about sites and apps that use its services and in the Google Privacy Policy.
The app declares the permissions the advertising library requires as part of its installation, including access to the advertising ID. You can see them in the permission list on your device's app info screen.
Controlling your ad preferences
- From inside the app: in Settings, next to the Privacy Policy row, an "Ad privacy options" row appears. It is shown only when Google's consent tool says such an entry point is required for your region; tapping it lets you review and change the consent you gave earlier. This path is independent of the birth-year declaration: you can manage the consent you gave even if you never shared a birth year or have deleted it, because deleting the declaration is not withdrawing consent.
- From your device: you can reset Android's advertising ID and turn off ad personalization. According to Google's advertising ID documentation, the path on Android 6.0 and above is Settings → Google → Ads; the naming can differ by version.
- From your Google account: you can manage personalization through Google's own ad settings. Details are in the Google Privacy Policy.
Purchases and Google Play
The app offers five products: four capacity packs (raising the number of clients a career can carry by +1, +3, +5 or +10) and one ad removal product. Payment runs through Google Play's billing system.
Your card details never reach the app. Google Play draws the payment sheet and collects card, billing and payment information directly. The app never sees, stores or processes any of it, and that information is handled under Google Play's own terms.
What the app gives to Google Play: the identifier of the product you want to buy, and a randomly generated pair of identifiers — the career's random identifier and a random number generated for that purchase attempt. The pair exists so the entitlement can be written to the right career once the payment completes. It contains no name, no email address, no device identifier and no account information; nothing you typed into your career is sent either.
What Google Play gives back to the app: the state of the purchase, the product identifier, the purchase token issued by Google Play, and the same pair of identifiers. The app writes these into its own storage — that record is what says which entitlement was granted. Capacity packs are written to the career save, ad removal to your device preferences. These records are not sent to the developer; the developer runs no server.
What is asked at every launch. On Android, while the app opens, it asks the Google Play app on your device three things: is billing available on this device, what are the product details and localized prices, and is there a purchase still standing on your account. These questions do not depend on the birth year declaration — they are asked even while the ad path is closed. Buying does not work until the products are opened on the store side; in that case the app says that purchasing is unavailable.
Capacity packs belong to one career. The capacity you buy applies only to that career, and a career can hold at most +10. Deleting that career deletes that capacity with it. On the Google Play side these packs are "consumable" products: once delivered, Google Play no longer returns them among the purchases standing on your account. So if you uninstall and reinstall, or move to another device, a capacity pack that has been consumed cannot be restored by asking Google Play; and the developer holds no record of it either, because there is no server. Because the capacity lives inside the career save, it can come back with that save if Android backup is enabled and the backup is restored — but we cannot promise that a backup was taken or that restoring it will succeed; that is Android's doing (Android backup).
The +10 ceiling is applied at delivery. A career can be granted at most +10 capacity, and that limit is checked at the moment the entitlement is written, after the payment has completed. If two purchases are started over each other and the second does not fit the limit, that purchase is not partially delivered: no entitlement is granted, the transaction is not acknowledged and not consumed, and its record stays in the device-wide queue as undelivered. Google Play may refund such a transaction under its own rules; the app cannot verify that — there is no server — so it never says "refunded" on screen, only that the entitlement was not granted and the transaction was not acknowledged. You can see the state of your orders through Google Play's own tools, and contact Google Play support about a refund.
Deleting a career does not delete the purchase record. When the career goes, its capacity goes with it; but the record of a paid transaction for that career stays in the device-wide queue and is marked as having no target. Deleting the record of a paid transaction would destroy the only trace you have. The entitlement is not moved to another career on its own.
Ad removal can be restored. That product is "non-consumable" and is kept in your device preferences. When you are signed in with the same Google Play account, the app sees the product again when it asks Google Play, and the entitlement comes back. The record on the device is only a local copy; what the entitlement actually rests on is your Google Play account. This product switches off only the automatic ad every ten weeks.
Rating requests
The app may occasionally ask Google Play to show its rating and review window inside the game. Google Play draws that window; your rating and review go straight to Google Play through your Google Play account and never pass through the app.
- When it asks. At the earliest at the end of your first season, when you close the season summary — never while the summary is on screen. At most three times per device, and at least 30 days apart. It does not ask while your career is in debt, in a week that is an ad break, or while an ad or consent step is in progress.
- Google Play decides whether to show it. Google Play may show nothing at all, for instance when its own limit has been reached or when you have already rated the app. The app cannot learn whether the window was shown, whether you rated, or what you wrote.
- The "Rate the game" row in Settings does not open that window; it opens the game's page in the Play Store app. Once you have opened that page, the app no longer asks on its own.
- No reward. Nothing is given for a rating or a review, and nothing in the game changes.
- Independent of your birth year. This request is not part of the ad path and does not depend on the birth year declaration.
The only thing the app keeps for this is a short counter in your device preferences: how many times it has asked, when it last did, and whether the store page was opened from Settings. It is not sent to the developer. A store review you write is public text, and, as described under "What the developer sees in reports", it is visible to the developer as well.
What the internet connection is used for
The app declares the internet permission and, on Android, genuinely uses it. The uses we know of are four: the ad consent flow, the ads, the store questions asked of Google Play, and the rating window requested from Google Play. The last two run through the Google Play app on your device; the app itself does not connect to a store server. We do not, however, limit the app's total network usage to those four — at first launch some traffic of undetermined origin was also measured (What happens when the app opens). The game itself makes no request to any external address at any point during play. Everything the game displays comes from inside the installed app, and the game is fully playable offline.
Tapping the Privacy Policy row in Settings is not an exception but an address: the link is handed to your device's browser and the browser loads the page. The game does not open that page inside itself.
This policy describes the Android version of the app. The consent flow and the ads run through the native advertising component on the device; when the game is opened in a web browser that component is not present, so no consent request and no ad request is made. Page and file downloads by the browser version are a separate matter.
Android backup
The app allows Android's standard Auto Backup for Apps feature and does not exclude its own files from it. If backup is enabled on your device, your operating system can back up the app's data — including your career saves — to a private folder in your Google Drive account, and restore it when you set up a new device.
According to Google's Auto Backup documentation:
- The backup is limited to 25 MB per app and does not count against your personal Drive quota.
- Backups run when the device is idle, at least 24 hours have passed, and normally while connected to Wi-Fi.
- On Android 9 and later the backup is end-to-end encrypted using your device's screen lock — meaning this protection depends on your device actually having a PIN, pattern or password set.
- The backup cannot be read by users or by other apps.
The backup is performed by Android and Google, not by the game or the developer, and the developer has no access to it. The feature is entirely under your control: you can turn it off in your device's backup settings.
Deleting your data
Because game data lives on your device, you do the deleting. Each of the following removes the data held on that device:
- Delete a single career: from the slot card in the main menu, or from Settings inside a career with "Delete career". This also deletes the capacity bought for that career. The device-wide transaction queue is not deleted: the record of a paid transaction for that career stays, marked as having no target (Purchases and Google Play).
- Delete everything: in Android settings, Apps → Pro Football Agent (the app's name on the device) → Storage → "Clear storage". This also deletes the transaction queue and the ad removal record in your device preferences; the ad removal product can be restored with the same Google Play account.
- Delete your birth year: you can delete or change it from the birth year row in Settings. Deleting it closes the ad path; it does not withdraw the advertising consent you gave — you manage that from the ad privacy options.
- Uninstalling the app also removes your local data.
These actions do not reach backup copies. If Android backup is enabled, a copy may remain in your Google Drive backup after you clear storage or uninstall. That copy is managed by your Google account and is deleted separately: from your device's backup settings or from the Google Drive app.
Your purchase records on Google Play are not deleted by any of this: your orders are held by your Google Play account and you view them through Google's own tools.
The data that goes to Google with the ads is separate from all of this: Google holds it and it is managed through Google's own tools. Because no copy of your game saves exists with the developer, there is no game data the developer can delete on your behalf. Your support correspondence is separate: you can ask for it to be deleted by writing to the address below. If you write a review on the store — including through the rating window inside the game — you can edit or delete that review yourself through Google Play.
Retention
Game data, and your birth year if you shared it, stay on your device until you delete them; since the developer holds no copy, there is no server-side retention period for them. How long the Android backup is kept is determined by Google and your device settings. Retention of ad-related data is determined by Google. Your purchase records also stay on your device: the capacity record until the career it belongs to is deleted; the ad removal record and the device-wide transaction queue until storage is cleared or the app is uninstalled — deleting a career does not affect the queue. The rating request counter also stays in your device preferences until storage is cleared or the app is uninstalled. How long Google Play keeps its own order records is determined by Google.
The data whose retention period the developer sets is support correspondence. Its period is below.
If you write to support
Support is a plain email address: xahkeee@gmail.com. The game has no contact form and sends nothing on your behalf — an email exists only if you write one.
If you write, your email address and the contents of your message are received and read by the developer. That includes your name as it appears in your mail account and anything you choose to put in the message: a description of the problem, your device model, your Android version, or a screenshot you attach. We suggest you do not send information you would not want to share.
Support emails are used only to reply to you and to resolve the problem you reported. They are not used for marketing and are not passed to third parties for their own purposes. The developer is not the only party processing the message, though: the mailbox is a Gmail account, so Google receives your message as the email provider and processes it under the Google Privacy Policy.
Retention period: support correspondence is deleted within 30 days after the request is closed — the incoming message, the reply and any attachments together. You can ask for it to be deleted sooner by writing to the same address.
What the developer sees in reports
The developer receives no data directly from the game. Because the app is distributed through Google Play, three things on the store side are visible to the developer:
- Store statistics. Aggregate figures such as installs, uninstalls, crashes and ratings, broken down by country, device and app version. These are aggregate statistics and contain no records about individual people.
- Store reviews. The review text, along with the name shown on your Play profile, plus language and device information. A store review is public text to begin with. A review written through the rating window inside the game is the same store review; the app sees nothing more.
- Sales reports. Sales and order information for transactions made through Google Play can be made available to the developer in the reports Google Play provides. These come from Google Play, not from the app: the app sends the developer no purchase information at all.
On the advertising side, the app shows real ads through Google AdMob, and Google provides aggregate ad reports about this app in the developer's AdMob account: counts of ad requests, impressions and clicks, and estimated earnings, broken down by things like country and ad unit. These are aggregate figures and contain no records about individual people. AdMob is the only source of these reports; the app contains no separate analytics tool.
Support emails are the only route by which personal information reaches the developer directly, and they are described in their own section above.
Exercising your rights
By writing to the developer at xahkeee@gmail.com you can ask for a copy of your support correspondence, ask for incorrect information to be corrected, or ask for it to be deleted. You can also send any question about your data to that address — if the answer depends on another company, pointing you to them is the developer's job too.
The developer is based in Türkiye. Turkish law grants a person whose personal data is processed rights such as learning whether their data is processed, requesting information about it, having it corrected, requesting its deletion, and learning to whom it has been transferred; the applicable time limit and the route for complaining to the Personal Data Protection Board are described on the Authority's data subject rights page.
If you live in the European Union, data protection law grants rights such as being informed, access, rectification, erasure, restriction of processing and data portability; the conditions under which each right applies and the response times are set out on the European Commission's information page for individuals. If you live in the United Kingdom, the same rights are governed by UK law; the response time is normally one calendar month and can be longer for complex or multiple requests — see the ICO's page on time limits and the ICO's page on making a complaint.
The data that goes to Google with the ads is not held by the developer and the developer cannot access it. You can raise requests about it through Google's privacy tools; the routes are described in the Google Privacy Policy. You can also reset your device's advertising ID yourself, as described above. If you are unsure where to go, you can write to the address above.
Age
Pro Football Agency is designed for players aged 13 and over. This is the developer's own decision about the intended audience.
The ads have a separate threshold of their own: 18. It covers both the rewarded ad and the automatic ad every ten weeks; it is not the game's audience, it only decides whether the ad path opens. A player below it, or one who does not share a birth year, keeps the whole game, their careers and their saves; only the ads and the rewarded ad's daily reward stay closed, and nothing replaces that reward. The store is separate from this threshold: buying does not depend on the birth year declaration and runs through your Google Play account.
The declaration is your own statement and is not verified. Because only the year is stored, it is not known whether your birthday has passed and the younger age is assumed — so reaching the threshold can appear up to a year late, depending on your date of birth.
Apart from the birth year, the game asks no player for personal information and sends nothing about any player to the developer on its own. If you are a parent or guardian and there is a problem with the game — or you want a support message that was sent deleted — you can write to xahkeee@gmail.com.
This website
This site consists of static pages hosted on GitHub Pages. There are no analytics, no ads, no tracking pixels, no cookie banner, no contact form and no third-party fonts or scripts. The site sets no cookies of its own.
As the host, GitHub logs visitors' IP addresses for security purposes when a GitHub Pages site is visited. That logging belongs to GitHub, is entirely separate from the game, and falls under the GitHub Privacy Statement. The developer does not receive those logs.
Changes to this policy
When this policy changes, the "Last updated" date at the top of the page changes with it. The current version always lives at:
https://xahke.github.io/privacy/pro-football-agent/en.html
If the app's advertising behaviour changes, this policy will be updated before that version is published. Today the app shows real ads through Google AdMob and uses no ad mediation network. The same applies to the purchase side: if the scope of the products or the way they work changes, this policy is updated before that version too.
Contact
For any question about this policy or your data: xahkeee@gmail.com.
This document is also available in Türkçe. The two versions say the same thing; if they ever contradict each other that is a mistake — please report it to the address above.