Privacy policy

App: Boyman (package uz.abdinazarov.boyman) on Google Play Developer: Abdinazarov, an independent developer based in Tashkent, Uzbekistan Contact: sh.sh.abdinazarov@gmail.com Effective date: 16 September 2026

The short version

Boyman is a single-player business simulation, and most of it still runs entirely on your phone: your progress is one file in the app's own private storage. Three things reach the outside world.

1. If you sign in with Google, the game creates an account on our own server at boyman.abdinazarov.uz and keeps a copy of your save there, so you can carry your empire to a new phone. That copy is uploaded roughly once a minute while you play.
2. The rich list is public. Your in-game name, emoji avatar, city label and fortune are served to anyone who asks for the leaderboard — no account needed on their side.
3. The game shows rewarded video ads from Google AdMob. The ads SDK reads your device's Advertising ID and sends it, with your IP address and device details, to Google. An ad only ever plays when you tap a "watch an ad" button — but the SDK loads one in advance every time you open the app, so data reaches Google even on a day you never watch one.

If you never sign in, nothing of yours is stored on our server — but the app still talks to the network: it asks our server for the time on launch, and it still requests ads.

The rest of this page explains all of that in detail: what is stored where, who can see it, how long it stays, and how to get rid of it.

1. What we collect

Here is the whole picture in one place. Everything in it is explained in the sections that follow.

On your device, always: your game save, and — after the first launch — a flag saying the sign-in invitation has been shown.

On your device, once you sign in: your Google display name, your Google email address, and a session token for our server.

On our server, only if you sign in: your Google account id, name, verified email address and profile picture URL; your full game save; your in-game name, emoji, city, fortune and lifetime earnings; a hashed copy of your session token; and, if you join or found a tapping company, that company and what your tapping has earned.

Public to everyone, only if you sign in: your in-game name, emoji, city and fortune, on the rich list.

Visible to other signed-in players, only if you join or found a tapping company: your Google display name and profile picture, as section 6 explains.

To Google, as the advertising network: your Advertising ID, IP address, device and app details, and what happened with each ad. We never see any of it.

To Google, at sign-in: the ID token from your Google account, which both your phone and our server hand to Google to be verified.

We never ask for and never receive your phone number, date of birth, GPS location, contacts, photos, microphone, camera or files. There are no in-app purchases, so we never see payment details of any kind.

The permissions the app declares

The app's own manifest declares three:

• android.permission.INTERNET — to reach our server and Google's;
• android.permission.ACCESS_NETWORK_STATE — to see whether you are online before trying;
• android.permission.POST_NOTIFICATIONS — asked at first launch, for the single local reminder described in section 2. Refusing it costs you nothing but the reminder.

The libraries the app is built with add a few more to the installed package without the app asking for them: com.google.android.gms.permission.AD_ID and the ACCESS_ADSERVICES_AD_ID / ACCESS_ADSERVICES_ATTRIBUTION / ACCESS_ADSERVICES_TOPICS permissions come with the Google Mobile Ads SDK; USE_BIOMETRIC and USE_FINGERPRINT come with the Google sign-in component; WAKE_LOCK and FOREGROUND_SERVICE come with Google Play services. The app declares no location permission of any kind — not fine, not coarse — so nothing in it, including the ads SDK, can read your GPS or network position.

2. What is stored on your device

The save file

Boyman keeps one save slot: a single JSON file named save.json, written in the app's own private storage at

/data/data/uz.abdinazarov.boyman/files/boyman/save.json

next to a backup copy save.json.bak and a short-lived save.json.tmp used while a save is being written. This folder is private to the app: other apps on the phone cannot read it, and it is removed when the app is uninstalled.

The save file contains your game progress only:

• your in-game name, emoji avatar and city label;
• your in-game balance, companies and their levels, holdings, merges, shares, cryptocurrencies, properties, vehicles, residence and collections;
• taxes due — one bill per company, one per holding and one for the dividends — and any company or holding the state has seized while you were away and not yet shown you;
• lifetime earnings, total taps, unlocked achievements, tap level;
• which tapping company you tap for, the terms you accepted, and what your tapping has earned its owner since your phone last reached the server — and, if you founded one, its name, its terms, how many people work for it and what it has paid you;
• your daily streak, best streak and the timestamps the game needs to calculate offline income when you come back.

The name, emoji and city are game labels, not identity fields. Today the app gives every player the same defaults — the name "Boyman", a neutral emoji and Toshkent as the city — and there is no screen anywhere in the app for changing them. They are not your Google name and not your real address. If a later version ever lets you edit them, whatever you type will be published on the rich list, so keep it a game label.

All the money, companies, banks, brands, coins, paintings and billionaires in Boyman are invented. The save file holds no real financial data, no payment details and no real money of any kind.

The account preferences, once you sign in

Signing in adds a second, separate store: the private preferences file boyman-account, also inside the app's private storage. It holds:

• token — the session token our server issued, in plain text. It is not a password and it cannot be turned back into one; it is what lets the app upload your save without asking you to sign in again. It is removed when you sign out, and rejected by our server if it is ever revoked.
• name and email — your Google display name and email address, shown on the profile screen so you can see which account you are signed in as. Both are removed when you sign out.
• synced-at — when the last upload succeeded, to show "last backed up". Removed on sign-out.
• invitation-shown — a yes/no flag so the sign-in invitation is never offered twice. This one deliberately survives signing out.
• offer-payload, offer-version, offer-fortune — if the server held a richer run than the one on your phone and you chose to keep the phone's, the app holds on to that other save so you can change your mind. It is your own save from another device, it stays on this phone, and it is not removed by signing out. Clearing the app's storage removes it.

Your Google ID token — the signed proof of who you are that Google hands the app at sign-in — is never written to disk. It exists in memory for the seconds it takes to send it to our server, and then it is gone.

Ad consent, if you are in a region that requires it

If Google determines you are in the EEA, the UK, or another region where a consent form is required, Google's User Messaging Platform writes your answer into the app's default preferences on the device (the IABTCF_* and IABGPP_* entries and Google's own consent keys). The app never reads or writes those values itself; the ads SDK reads them to know whether it may ask for a personalised ad. See section 7.1.

The upgrade reminder

If you allow notifications, the app can schedule one local reminder for the minute your idle income covers your next upgrade. The company name, level and price sit in an alarm on your phone and are posted as a local notification. There is no push service, no Firebase Cloud Messaging, and nothing about the reminder leaves the device.

Diagnostic messages

When something goes wrong while reading or writing the save file, the app writes a short message to the Android system log on the device. These messages stay on the device, are not collected by us, and are overwritten by the system over time.

If you have chosen in your Google account to share crash and diagnostic data with Google, Android may report crashes of any app to Google Play. That is an Android platform feature under your own control and Google's privacy policy — not something Boyman does or receives. The app contains no crash-reporting SDK, no analytics SDK, no Firebase and no Google Analytics.

3. Android's own backup — copies that leave your phone

Boyman's manifest has android:allowBackup="true", which is Android's default and which keeps your progress when you replace or reset your phone. The app sets no exclusion rules, so Android's "back up everything" default applies. This means the Android operating system may copy the whole of the app's private storage:

• to your own Google account backup (Android Auto Backup / Google One device backup), and
• to a new device during a device-to-device transfer, when you set up a new phone.

Be aware of what "everything" includes: not only save.json and save.json.bak, but also the boyman-account preferences file described in section 2 — which holds your session token, your Google display name, your email address and any stored save from another device — and the ad-consent entries.

This copy is made by the Android operating system under your Google account, not by us. We receive nothing from it, we have no access to it and we cannot read it. It is handled under Google's own privacy policy and your Google account settings.

You can turn this off at any time: Settings → Google → Backup on your phone (the exact path varies by manufacturer), or by switching off backup for this app in your Google account's backup settings. Turning it off means this data stays on the device only.

4. Our server — what is sent, and when

We run our own back end at https://boyman.abdinazarov.uz/api. It is a Laravel application with a PostgreSQL database, on a server rented by the developer. There is no other company involved, no analytics service, no third-party log service.

Even before you sign in

Every time the app starts, it makes one request to our server and reads the date from the response headers. The game uses that as a trusted clock, so that moving your phone's calendar forward does not conjure up years of idle income. The request carries no account data — but like any web request it necessarily carries your IP address and a standard user-agent string, which our web server may record in its access log.

The ads SDK also runs at this point; see section 7.

Once you sign in with Google

Sign-in goes through Android's own Credential Manager, so the app never sees your Google password. Google gives the app a signed ID token, which the app sends to our server. Our server hands that token to Google (https://oauth2.googleapis.com/tokeninfo) to verify it is genuine, then reads these claims out of it and stores them in the users table:

• your Google account id (the sub claim) — the only value your account is looked up by, so renaming your Gmail does not lose your empire;
• your name;
• your email address, and only if Google says it is verified — an unverified address is discarded and stored as nothing;
• your profile picture URL (the link only; we never download or store the image).

Alongside that we store the row's own id and timestamps. The updated_at timestamp moves on every sign-in, so in effect it records when you last signed in. We keep a last_seen_at stamp beside it, written at sign-in and at most once an hour while your phone is using its token: it is what the automatic 90-day deletion in section 10 counts from. None of these fields is ever shown to another player; the leaderboard does not contain them. We do not use your email address to write to you — the server has no mail configured at all.

The server then issues a session token for your phone. We store only a SHA-256 hash of it, never the token itself, in the personal_access_tokens table, with the label "android" (a fixed word — not your device model), the time it was created and the time it was last used. A token does not expire on a timer: it lives until you sign out, or until you sign in again from the same device, which replaces it.

The cloud save

While you are signed in, the app uploads your whole save to our server. It does this about once a minute while the game is open, and once more when you leave the app — and only when your fortune has actually changed. The upload is stored in the players table:

• payload — your save file, verbatim, exactly as described in section 2, up to 256 KB;
• name, emoji, city — your in-game labels;
• fortune and lifetime_earned — your in-game figures;
• save_version and synced_at — which format the save is in, and when it last arrived.

There is one row per account, overwritten on every sync. There is no history and no second copy. The payload is stored as plain text in the database; it is reachable only through your own signed-in session, and no request from another player can name your row.

We keep all of this until you ask us to delete it — see section 10 — or until the account has gone 90 days unused, at which point the server deletes it on its own. Uninstalling the app does not remove it.

Server logs

Our web server keeps a standard access log — client IP address, the request line, the status, the user agent — as web servers do. It lives inside the application container and is destroyed every time we deploy a new version; it is not on a backup volume and is not sent anywhere. The TLS proxy in front of it keeps its own access log under the host system's normal rotation. We do not store IP addresses in the database, and we do not build any profile from these logs; they exist for keeping the server running.

The application's own error log can, when something fails in an unusual way, contain technical detail from a failed sign-in attempt. That log is also inside the container and is destroyed on each deploy. It is never shipped to any outside service.

We take manual database backups before risky changes; those dumps contain every row described above and are kept by the developer only.

Who on our side can read it

One person: the developer. There is an admin panel at boyman.abdinazarov.uz/admin, open only to the developer's own signed-in Google account and a plain 404 to everybody else. It lists the accounts with their Google name and email address next to their in-game figures, and it has a button that deletes one outright — running the same code as the delete page and the 90-day sweep. Nothing in it is shared with anyone, and there is no other way into the database than the server itself.

The website

The site at boyman.abdinazarov.uz sets one cookie, site_locale, to remember whether you chose English, Uzbek or Russian. There is no analytics, no tag manager, no advertising script and no external web font on it.

5. The rich list is public

The in-game rich list ("Forbes") is exactly what it looks like: a public ranking. Once you are signed in and your fortune is above zero, these five fields about you are served to anyone who asks:

• your rank,
• your in-game name,
• your emoji avatar,
• your city label,
• your fortune,

plus a numeric player id used to highlight your own row. The list covers the top 200 players by fortune. It requires no account and no token to read: any player, and in fact anyone on the internet who knows the address, can fetch it. Treat those four labels as published.

What is not on the list: your Google name, your email address, your profile picture, your Google account id, your lifetime earnings and your save file. Those never appear in it.

As section 2 explains, the app currently gives everyone the same default name and city, so today the list reveals nothing you chose. The city default is a real city name (Toshkent) — it is a label, not a claim about where you live, and nothing in the app asks where you live.

If you do not want to appear at all, do not sign in. Your progress then stays entirely on your phone.

6. Tapping companies — what other players see

A tapping company is the one part of Boyman where two accounts meet. One player founds it; others choose to tap for it, and a share of what each tap is worth goes to the owner. Because money moves between two people, the terms and the ledger are kept on our server rather than on either phone.

If you join somebody's company, the owner sees, on their own workers screen: your Google display name, your profile picture, the terms you accepted, the date you joined, and the total your tapping has earned them. They do not see your email address, your save, your fortune, or anything else about you.

If you found one, every signed-in player browsing the list sees its name, its level, the share it offers, how many people work for it, and your Google display name as the owner. Not your email address.

Your phone reports how much plain tap money it earned for the company since it last reached the server. That figure is a number, not a record of when or how you played, and the split is worked out here from the terms on record rather than taken from the phone.

Leaving a company stops all of it. Deleting your account removes your company, its payroll and your membership of anybody else's along with everything else, and the owners of companies you worked for keep only the money already collected — no name, no row, nothing that points back to you.

If you never sign in, none of this exists for you: the whole feature needs an account.

7. Advertising

Boyman shows rewarded video ads only — the kind you start yourself by tapping a "watch an ad" button. There are no banners, no interstitials, no ads that interrupt you and no ads that appear without you asking for one. Skipping every ad in the game costs you nothing but the bonus.

The ads come from Google AdMob, through Google's Mobile Ads SDK. We do not run an ad server, we receive no data about you from Google, and we cannot see who you are from the advertising side. We see only anonymous totals: how many ads were shown and what they earned.

Be clear about the timing. The SDK does not sit dormant until you tap. Every time you open Boyman, the app initialises the SDK and fetches one rewarded video in advance so that a tap plays instantly, refreshing it while the app stays open. That means the data below reaches Google on every launch, even on a day when you never watch an ad.

What Google receives

The SDK gathers and sends this itself; our code passes it no targeting data at all — no keywords, no interests, no content about you:

• your Advertising ID (the resettable identifier Android gives to advertisers). The app itself never reads or stores it;
• your IP address, from which Google derives an approximate location — country, region, roughly city. The app has no location permission, so nothing more precise than that is available to anyone;
• device and app details: device model and manufacturer, screen size, Android version, language, connection type, the app's package name and version, and our AdMob ad unit id;
• ad events: that an ad was requested, filled, shown, watched to the reward point, clicked, dismissed or failed;
• your consent signals, where a consent form applies (section 7.1).

The Mobile Ads SDK is also wired for Android's Privacy Sandbox (Topics and Attribution Reporting) on devices that support it, so interest signals of that kind may be used by Google where the device and Google's own rollout enable them.

Google uses this to choose and deliver an ad, cap how often you see it, measure it, detect fraudulent traffic, and — only where you have consented or the law otherwise allows it — personalise what you are shown. Where personalisation is refused, ads are still served, but non-personalised (chosen from context, not from you).

Google's role

For this advertising data Google acts as an independent controller, not as a processor working on our behalf: Google decides its own purposes for what it collects through the ads SDK, under its own policies. We cannot access it, correct it or delete it for you. The authoritative descriptions are Google's:

• Google Privacy Policy
• How Google uses information from sites or apps that use our services
• Google Ads services where Google is a controller
• What AdMob collects
• Google's data retention
• Your own controls: My Ad Center

7.1 Consent in the EEA and the UK

If Google determines from your IP address that you are in the EEA, the UK, or another region where consent is required, Google's User Messaging Platform shows you a consent form before any personalised ad request is made. Your answer is stored on your device as described in section 2 and read by the ads SDK. Google's explanation of that mechanism is here.

How to change your mind. Being honest about a gap: this version of the app has no "Privacy options" button for reopening that form. Until we add one, there are two ways to change your answer:

• Clear the app's storage (Settings → Apps → Boyman → Storage & cache → Clear storage). The consent choice is forgotten and the form is shown again next time. Note this also erases the local save — if you are signed in, your progress is on our server and comes back when you sign in again; if you are not, it is gone.
• Use the device-level controls in section 7.2, which stop personalised advertising regardless of what the consent form was told.

We will add an in-app way to revisit the choice; this policy will be updated when it exists.

7.2 Turning off personalised ads on your phone

This works for every app on your device, Boyman included, and does not depend on us:

• Android 12 and newer: Settings → Privacy → Ads → Delete advertising ID. Apps then receive no advertising ID at all and can no longer use one to build a profile of you.
• Older Android: Settings → Google → Ads → Opt out of Ads Personalisation, and Reset advertising ID to break the link with everything gathered so far.

The exact path varies by manufacturer; Google's instructions are here. Ads in Boyman will keep working after you do this — they simply stop being personalised.

8. No purchases, no real money

Boyman has no in-app purchases and no subscriptions. There is nothing to buy, at any point, and the app never asks for a card, a wallet or any payment detail — we could not charge you if we wanted to.

There are ads, as section 7 describes, and they are the only way the app earns anything. What a rewarded ad gives you is in-game only: a stretch of accelerated or offline game time, paid in the invented money of the game. Nothing in Boyman can be exchanged, transferred, cashed out or sold. The fortunes on the rich list are points, not currency.

Boyman is not a financial service, not investment advice, and not gambling. All the companies, banks, brands, coins and billionaires in it are invented.

9. Children

Boyman is not directed at children, and this section has to be plain about why.

The game shows ads served by Google using an advertising identifier, offers a Google sign-in, and publishes a rich list of other players. That combination means it is not a "child-directed" app: it is not part of the Google Play Families programme, the app does not set the child-directed or under-age-of-consent flags on its ad requests, and we do not treat its audience as children. It is intended for a general audience of teenagers and adults.

Signing in requires a Google account, which is subject to Google's own age rules for your country. Signing in is optional — the whole game is playable without it, and without an account nothing of yours is stored on our server or shown to other players.

We do not knowingly collect personal data from children under 13 (or under the higher age of consent that applies where you live). If you are a parent or guardian and believe a child in your care has signed in and that we hold their data, write to sh.sh.abdinazarov@gmail.com and we will delete the account and everything attached to it. To stop the advertising identifier being used at all on a child's device, use the device-level control in section 7.2.

There is no chat in Boyman, no messaging, no friend list, no photo upload and no way for one player to write anything to another. What players see of each other is the rich list described in section 5 and, inside a tapping company, the Google display name and profile picture described in section 6.

10. How to delete your data

There are two copies to think about: the one on your phone, and — if you ever signed in — the one on our server.

On your phone

• Uninstall Boyman. Android deletes the app's private storage with it: save.json, its backup, the boyman-account preferences and the stored consent values. Nothing of the app is left behind on the device.
• Or clear the app's storage: Settings → Apps → Boyman → Storage & cache → Clear storage. This erases the same things while keeping the app installed, and starts you from zero.

If Android backup was switched on (section 3), a copy may still exist in your own Google account backup. You can remove it from your Google account's backup settings, or on the web under your Google One device backups.

On our server

Uninstalling does not delete the server copy. Signing out does not delete it either — signing out only revokes the session token on your phone. Your account row, your save and your rich-list entry stay until they are deleted by hand.

There is a delete button, and you do not have to ask anybody. Open boyman.abdinazarov.uz/delete in any browser, sign in with the same Google account, and press delete. It removes your users row, the players row holding your save and your rich-list figures, every session token any device of yours still holds, and the cached copy of the rich list. Your entry disappears from the list with it. Nothing is kept, and it cannot be undone.

An account nobody has used for 90 days is deleted automatically, by the same code the button runs, without anybody asking for it. If you stop playing, your data does not sit on our server forever.

You can also write to sh.sh.abdinazarov@gmail.com from the address your Google account uses and we will do it for you, but the page is faster and needs nobody's help.

Advertising data

Data Google collected through the ads SDK is held by Google, not by us, and we cannot delete it for you. Use My Ad Center and the device controls in section 7.2.

11. Your rights

Data protection law gives you rights over the personal data held about you: to know what is held, to get a copy, to have it corrected, and to have it erased.

If you have never signed in, we hold nothing about you and there is nothing to ask for: the only copy of your game data is on your own device.

If you have signed in, we hold what section 4 lists — your Google account id, name, verified email, picture URL, your save and your in-game figures. Write to sh.sh.abdinazarov@gmail.com and we will send you a copy of everything in those rows, correct anything wrong, or delete the lot. It is one person reading that address, so allow a few days.

Advertising data is Google's, and Google's own tools, linked in section 7, are where those rights are exercised.

12. Changes to this policy

If this policy changes, we update this page and the effective date at the top.

The 14 September 2026 version was a substantial rewrite. Earlier versions of this policy described Boyman as an entirely offline game that collected nothing, declared no Android permissions and had no server. That stopped being true when Google sign-in, the cloud save, the public rich list and rewarded video ads were added. Everything that changed is described above. If a future version of Boyman changes what it stores or where it sends it, this policy will be updated before that version is released, and the change will be noted in the release notes on Google Play.

This revision, 16 September 2026. The contact address, left as a placeholder in the version before it, is now written out everywhere it was promised. The delete-account page at boyman.abdinazarov.uz/delete and the automatic deletion of an account nobody has used for 90 days are now described as they actually work — the earlier text said this version of the app had no delete button, which had stopped being true. Section 6 is new: the game now lets one player's tapping earn money for another, so what the two of them see of each other is written down. The same pass added the admin panel the developer uses, and the tax accounts, seizures and tapping membership the save file now carries.

13. Contact

Questions about this policy, requests for a copy of your data, or requests to delete your account:

sh.sh.abdinazarov@gmail.com Abdinazarov, an independent developer, Tashkent, Uzbekistan