Black Monsoon Privacy Policy
Developer: Apzilon
Effective date:
Black Monsoon (the "Game") is a mobile game by Apzilon.
The Game and the Apzilon game service it connects to are run by Nattapon Suetrong (Apzilon), an independent developer in Thailand ("we", "us"), who decides how your personal data is used (the data controller under Thailand's PDPA). Contact: [email protected].
In Android 1.3.1 (11) and later and iPhone 1.3.1 (10) and later, Settings > Licenses and credits has a button that opens the MiniMax H3 licence page on apzilon.com in your web browser. Your browser loads it as it would any website.
Information we collect
The Game connects to the Apzilon game service over the internet. The first time you tap to start, the Game asks how you want to play: on Android, Sign in with Google or Play as guest; on iPhone, Sign in with Apple, Sign in with Google or Play as guest. On iPhone, before the Game has reached our service, it offers Play as Guest only. Nothing is created on our service until you choose. When you choose to play as a guest, the service creates a guest account for you: no sign-up form, no email and no password. When you sign in with Google or Apple instead, the service creates an account tied to that Google or Apple account, or signs you in to the one it already has (see the next paragraphs). Your account is stored on our service, not only on your phone. It has a random account ID and a random 9-digit Player ID. In earlier online builds, the Game's screens show neither the account ID nor the Player ID. In Android 1.2.0 (8) and later and iPhone 1.2.0 (7) and later, Settings > Account shows Google or Apple for a linked account, Guest otherwise, and your 9-digit Player ID; it shows no player name or email. Showing it sends nothing further to our service. Neither ID is a password. To sign you in, the Game also creates a random installation ID and a secret key on your device and sends them to our service. On Android, the secret key and the session token are kept encrypted with a key held in the Android Keystore; on iPhone, they are kept in the iPhone's Keychain. We keep the installation ID and only a hash of the key, and a hash of the session token that keeps you signed in. None of these is your device's advertising ID, its Android ID or your iPhone's advertising identifier. If you choose to play as a guest while the Game cannot reach our service, it plays and saves on your device only, and the guest account is created once the Game connects. What happens to a guest account when you uninstall the Game is described under Information stored on your device.
You can also sign in with your Google account on Android or iPhone, or with Sign in with Apple on iPhone, or link it later, so that your account and the progress backed up to our service are tied to that sign-in. This is optional. If you sign in with it or link it, we receive and keep that service's account identifier and the profile it shares with us: your email address (only when the service says it is verified), whether it is verified, your name, the link to your profile picture (not the picture itself) and your language. Some of these may be missing.
On iPhone, Sign in with Google opens Google's own sign-in page in Apple's web sign-in window; the Game does not include Google's sign-in software. Google sends back a sign-in token with the details above, which the Game passes to our service. Neither the Game nor our service keeps any token from Google, and the Game keeps no Google email address or name on your iPhone. On iPhone, you can also link Google to an account that uses Sign in with Apple, so that you can sign in to it on Android too.
If you use Sign in with Apple, Apple shares your name with us only the first time you sign in, and only if you choose to share it. The email address may be a private relay address from Apple that forwards to your own email; we also keep whether it is one. We also keep a token from Apple, encrypted, only so that we can ask Apple to revoke the Game's access to your Apple account. We ask when your sign-in link is deleted (see Deleting your account), and we delete the token once Apple confirms, or after 30 days of trying.
When the Game starts a new sign-in session with our service, we keep a record of it: the game, the platform, the app build, your language, your device model and operating system version, the country and region that our hosting provider works out from the connection, and when the session was last used. When a new session starts, we also log your IP address with its country, region and network provider, for security and fraud prevention only.
The Game also keeps your story save on our service as a cloud save, with up to 3 earlier versions of each part of it; nothing is uploaded before you play. It is the same story progress and story choices the Game saves on your device (listed under Information stored on your device), with the installation ID of the device that saved it; your language, touch-control, sound and music settings stay on your device. In Android 1.2.0 (8) and later and iPhone 1.2.0 (7) and later, the following save rules apply. The Game follows the save our service chooses. When two saves from installations of the same account meet, the one that went further in the story is kept whole; if they are equal, the save already on the account is kept. The other save is kept for 30 days so support can recover it. When a guest signs in with or links Google or Apple, our service's rule is to keep the account's save if it already has one for this game, whatever the progress; the guest's save does not replace it. In that conflict, the rule is to keep the guest's save on our service for 30 days, restorable only by support if you email [email protected] within those 30 days. If the account has no save for this game, our service's rule is to take the guest's progress. In Android 1.3.0 (10) and later and iPhone 1.3.0 (9) and later, when you sign in to an account that already has a save for this game, the Game loads that save even if this phone holds a save of that account that went further; this phone's different save and any progress not yet sent stay on this phone and are never uploaded. In earlier online builds, when two saves meet (from another installation, or when you sign in with Google or Apple), the one that went further in the story is kept whole; if they are equal, the save already on the account is kept. The other save is kept for 30 days so support can recover it. You never have to choose. Our service also receives the room and chapter usage records described below, linked to your account. When the Game reaches our service, before and after you sign in, it can fetch our public news posts for this game. These requests send no account ID, sign-in token, installation ID or advertising ID; they carry the game, build, platform, language, kit protocol version, device model and operating system version. Our service writes no player record for these public reads.
The Game also sends us usage records and error reports: which screens and pop-up windows you open, in what order and how long you stay on each (screen_view), the first time you open the Game (first_open), and when each play session starts and ends and how long it lasts (session_start, session_end). It also sends which room of a chapter you enter, which room Thar dies in or you leave for Home before finishing it, and how many times you have entered that room on this installation. It sends when you start chapter 2 and when you finish chapter 1 or chapter 2. These records never include the choices you make in the story (your choice to kill or spare or your answers in conversations; those are part of your save, described above) or any other details of your fights. We use these to understand use of the Game and fix problems. Our service also records account creation, sign-ins, linking and deletion. An error report holds a fixed message, the part of the Game's code where the error happened and the app build, at most 20 per session. Each record is linked to your account and the game; the ones the Game sends also carry a random installation ID, event and session IDs, the time and order of the event, your device model, operating system and language, and our service adds the app build, platform and your country. They never include your email address, your IP address or your advertising ID.
The Game sends these usage records and error reports from an iPhone too. The Game itself has no crash reporting: it sends no crash logs.
The Game has no advertising, in-app purchases or analytics and tracking software from other companies. Our service never receives your device's advertising ID, and the Game never asks for your phone number, contacts or location. On iPhone, it has none at all, and it never asks to track you across other companies' apps and websites.
How we use it and who processes it
We use this data to run your account and the Game, back up your progress to our service, keep the service secure and stop cheating and fraud, answer you when you ask for help, and understand and improve the Game. We do not sell it and we do not use it for advertising. Other players never see your email address, your IP address, or the name and picture from your sign-in account.
Our service runs on Cloudflare (servers and network, worldwide) and Neon (our database, hosted by Amazon Web Services in Singapore), so your data is stored and processed outside Thailand. They receive the data they need to provide those services to us. If you link Google or Apple, that company handles the sign-in under its own privacy policy.
How long we keep it
We keep your account, its sign-in links and your game data until you delete them (see Deleting your account). The security log of IP addresses is kept for 90 days after the last new session from that address. Session records and their device details are deleted after 180 days without use, or 30 days after the session ends. Records of account events, such as sign-ins, links and deletions, are kept for 180 days. Our clean-up runs once a day, so a record can stay up to a day past its limit.
Usage records and error reports are deleted after 180 days. We keep the following, linked to your account, until this game's data is deleted: daily activity totals, running totals of each kind of record (such as how many times Thar has died), records of when you first finished each chapter, and a receipt for each record we received. A receipt holds only the record's ID and time, so that a record sent twice is not counted twice.
The game data described under Deleting your account leaves our active database at once. Deletion markers for accounts, game profiles, device sign-ins and ended sessions are removed after 30 days. Account-event records can remain linked to your account until that purge; the daily clean-up can add up to one day. Those records are kept for 180 days in total and can retain hashed sign-in identifiers or the account IDs involved in a merge. A record of when you deleted this game's profile can remain while you still use another Apzilon game, to stop an older device from restoring deleted game data to your account; it is removed within 30 days after all your Apzilon game data is deleted. Copies may also remain in the database provider's recovery history until that history expires.
Deleting your account
In the Game, on the title screen, tap the gear to open Settings, tap the account row (it shows Guest, Google or Apple), choose Delete account, then hold Hold to delete for 2 seconds. The Delete account screen also shows this installation's Deletion code with a Copy code button. This in-game request deletes your account on our service: this game's cloud saves, their earlier versions and any save kept from a conflict, its usage records (screens, sessions, rooms and chapters), error reports, daily activity totals, running totals, records of when you first finished each chapter and record receipts leave our active database at once, the device details and security IP log of its sessions are cleared, and any link to your Google or Apple sign-in, with the profile that service shared, is removed. If you signed in with Apple, our service then also asks Apple to revoke the Game's access to your Apple account. It does not delete other Apzilon games. The Game then forgets the account on this device with its unsent records, opens the title screen with the message Account deleted. In earlier online builds, it deletes the single save and its local backups from this device. In Android 1.2.0 (8) and later and iPhone 1.2.0 (7) and later, it deletes that account's save file, local backups and recovery copies in the current service environment; other accounts' files, older single save files and their support copies stay on the phone. In Android 1.3.0 (10) and later and iPhone 1.3.0 (9) and later, it deletes that account's save file, local backups, recovery copies, save journals and the journal copies kept with them in the current service environment, and this installation's room attempt counts. Progress made as a guest before any account existed, the files of other accounts or other service environments, older single save files, their support copies and your settings stay on the phone with no automatic expiry, and so do a file that cannot be removed and a journal copy the Game cannot read. A journal copy kept with another account's files that also holds some of the deleted account's progress stays until that other account's save on this phone is next replaced by its save from our service (as at a sign-in) at least 30 days after the copy was made, with no end date if that never happens or if the Game had not yet reached our service since it was opened when it made the copy; it is never uploaded. The next time you tap to start, the Game asks again how you want to play. Without the Game, email [email protected], say Black Monsoon and give the email address of the Google or Apple account you signed in with (for Sign in with Apple, the address Apple shared with us, which may be a private relay address), or say that you played as a guest. A linked account requires verification of that Google or Apple identity; a deletion code alone cannot authorize its deletion. For a guest, include the Deletion code from the Delete account screen, which identifies the installation; earlier online builds do not show a public Player ID. In Android 1.2.0 (8) and later and iPhone 1.2.0 (7) and later, you can also give the Player ID shown in Settings > Account; the Deletion code still identifies this installation. We must verify ownership and the deletion scope before carrying out an external request. See the retention periods above and the full request steps at https://apzilon.com/delete-account/. On iPhone, if your account uses both Sign in with Apple and Google, the account row also offers Unlink Google: it removes only the Google link, with the profile Google shared, from our service, and your account, its progress and its Sign in with Apple stay.
In earlier online builds: If your account is deleted another way, after an email request or in another installation of the Game, an installation of the Game that does not reach our service within 30 days of the deletion is no longer told that the account was deleted: it starts a new guest account by itself and uploads the progress still on it as that account's first save. To prevent this, clear the Game's data or uninstall it wherever you no longer play it. In Android 1.2.0 (8) and later and iPhone 1.2.0 (7) and later, if the Game is told that the account was deleted elsewhere, cloud saving stays paused until you answer the question about turning it back on. Not now leaves it paused. Turn on allows the Game to start a new guest account and copy the deleted account's local progress into it only when the saved source is unchanged and that guest has no progress of its own. A Google or Apple sign-in does not bypass this question. If this device still holds an account, Turn on first checks and resumes that account instead. After the 30-day notice window, a new guest does not inherit another owner's save file. The old file stays separate on this phone. In Android 1.3.3 (13) and later and iPhone 1.3.3 (12) and later, when our service answers this phone's sign-in with a new guest account instead of the account the phone held, the Game treats that as a deletion only when its record on this device of which account its sign-in key opened names the account it held. Otherwise, such as when the sign-in key or that record is missing or cannot be read, it starts a new guest account by itself instead, and the previous account's save files, local backups, save journals and the unsent usage records and error reports already queued for it stay on this phone, separate from the new account, with no automatic expiry; none of them goes to the new account. If that account was not deleted, it and its progress stay on our service, and for an account linked to Google or Apple, signing in to it again loads its own save. Usage records and error reports the Game queued before it reached our service, such as during offline play, can be sent with the new guest account.
If you delete your account in the Game and then sign in again with the same Google account, or Apple account on iPhone, your deleted account and its progress do not come back; the sign-in can create a new account or link to the guest account you are playing on.
In Android 1.2.0 (8) and later and iPhone 1.2.0 (7) and later, Settings > Account offers Sign out for an account linked to Google or Apple, from the title screen or Home; it is not offered to a guest and is unavailable while a run is open. The confirmation shows Cancel first as the prominent button, then Sign out. When you confirm, the Game saves the latest checkpoint and sends any waiting save before asking our service to revoke this device's session. If the save cannot be sent or the service cannot be reached, it shows an error and does not complete sign-out; if the reply is lost, the Game keeps a record to settle the request later. In Android 1.3.0 (10) and later and iPhone 1.3.0 (9) and later, if you sign out while the Game is still waiting for our service's copy of that account's save (for example right after you signed in), progress made in the meantime is not sent and that does not stop the sign-out; that progress stays on this phone for that account only, with no automatic expiry. After a confirmed sign-out, the Game clears the session and account details here, replaces this device's sign-in key, ends the current run and clears its local room-attempt counts. The installation ID and your settings stay. That account's save files and backups stay on this phone for that account only; they are not uploaded or offered to restore into another account. Its account and progress stay on our service, and signing in to that account again loads its own save. Our service creates a fresh empty guest account before you choose again. If that guest request cannot connect, the Game retries when it can. The Game returns to the title screen and asks how you want to play again. If you close the Game before choosing, opening it again resumes that guest account and still asks how you want to play when you tap to start. Sign out is not deletion.
Information stored on your device
The Game saves your story progress (the chapters and rooms you have reached, whether you finished a chapter and won its boss fight, and how far the story has gone), your story choices (your choice to kill or spare and your answers in conversations) and your settings (language, touch controls, sound and music) in the app's own storage on your device. Your story progress and story choices are also copied to our service as your cloud save. In Android 1.2.0 (8) and later and iPhone 1.2.0 (7) and later, the Game keeps a separate save file and up to 3 local backup copies for each account in each service environment, including a guest account; progress made as a guest before an account exists has its own file. Only the active owner's file is loaded or uploaded for that owner. Signing in to another account does not upload the previous account's progress or offer it to restore into that account. An older single save file is copied into an owner's file only when the Game can identify its owner from the local save journals; otherwise it stays on the phone without being uploaded. The older files, migration record and local support copies stay on the phone. In earlier online builds, the Game uses one story save file and keeps at most 3 local backups when a cloud copy replaces it. These local backups have no fixed day limit and are never uploaded as backups. In Android 1.3.0 (10) and later and iPhone 1.3.0 (9) and later, the Game also keeps a copy of an account's save journal before replacing what it holds, for example when it loads that account's save at a sign-in. These journal copies are never uploaded. Each stays at least 30 days and is removed only when that account's save on this phone is next replaced by its save from our service after that, with no end date if that never happens or if the Game had not yet reached our service since it was opened when it made the copy. Local support copies, older single save files, progress made as a guest before any account existed and the files of an account deleted another way have no automatic expiry; deleting an account in the Game removes that account's own copies. On iPhone, the save files and these copies are also part of your iPhone's own iCloud and computer backups when you use them; we never receive those backups. To keep you signed in, the app keeps its installation ID, sign-in key, session token and account details on your device. It also keeps usage records and error reports there until it can send them.
Clearing the app's data or uninstalling the Game removes only the copy on your device. On Android, if you have not linked a sign-in account, you cannot get that guest account back afterwards. On iPhone, the installation ID, sign-in key and session token are kept in the iPhone's Keychain: deleting the Game does not remove them, so if you install it again on the same iPhone, the Game is designed to come back to the same account. They stay on that iPhone only: they are not synced to iCloud Keychain and never restored to another device. To delete the data on our service, see Deleting your account.
App permissions
The Game asks Android for these permissions:
Internet access (INTERNET): to connect to our service.
Biometric and fingerprint (USE_BIOMETRIC, USE_FINGERPRINT): come with Android's sign-in system (Credential Manager), which Google sign-in uses. Android may use them when it asks you to confirm with your fingerprint or face. The Game never receives your fingerprint or face data.
One permission the Game declares for itself (DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION), which Android uses to keep the Game's internal messages private.
None of these give the Game access to your camera, microphone, contacts, location or files. On iPhone, the Game asks for no permissions: not for your camera, microphone, photos, contacts or location, and not to track you.
System backup
The Game turns off Android's automatic backup, so the save on your device is not backed up to your Google account. Your progress is backed up to our service instead. On iPhone, your sign-in details stay on that iPhone, and your progress is backed up to our service.
Google Play
Google Play may collect information when you download or use apps, under Google's own privacy policy, which we do not control. The statistics we see in Google Play Console are aggregated and do not identify you.
App Store
Apple may collect information when you download or use apps from the App Store, under Apple's own privacy policy, which we do not control.
Children
The Game is intended for players aged 16 and over. We do not knowingly collect personal information from children under 16. If you believe a child under 16 has given us personal information, contact us and we will delete it.
Testers, support and contacting us
If you send us your email address to join a test of a game, we use it only to add you to the tester list on Google Play and to contact you about the test.
If you send us feedback or a support request, we use your message only to reply and to improve the game. We never sell or share it, and you can ask us to delete it at any time (see Contact below).
Your rights under Thailand's Personal Data Protection Act B.E. 2562 (PDPA)
Under Thailand's Personal Data Protection Act B.E. 2562 (PDPA), you can ask to see or get a copy of your personal data, to have it corrected or deleted, to restrict or object to how we use it, and to withdraw consent you gave. Email [email protected], say Black Monsoon and the email address of the Google or Apple account you signed in with, or tell us you played as a guest and include the Deletion code from the Game's Delete account screen if you have it. We need to identify your account and verify that it is yours. You can also complain to Thailand's Personal Data Protection Committee.
Changes to this policy
If we change what a game collects or how we use it, we update that game's page before the change takes effect and show the new effective date.
Contact
Apzilon | [email protected]