Apzilon

All Apzilon privacy policies

Machine Tower Privacy Policy

Developer: Apzilon
Effective date:

Machine Tower (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].

Information we collect

The Game connects to the Apzilon game service over the internet. The first time you tap the title screen while the Game is connected, it asks how you want to play: on Android, Start as Guest or Sign in with Google; on iPhone, Start as Guest, Sign in with Apple or Sign in with Google. Nothing is created on our service until you choose; if you put the choice away, the next tap asks again. When you choose to start 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 Settings, Link account shows your Player ID with a Copy button; 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 the Game cannot reach our service, it plays on your device only. In earlier online builds, progress already saved on your device, such as from an earlier version of the Game, is uploaded to the account you choose. In Android 0.2.0 vc 6 and later and iPhone 0.2.0 build 5 and later, progress belonging to another account or service environment is not uploaded into the account you enter. An offline save not yet tied to an account can become its first save; if the account already has a cloud save, the offline save is kept aside on this device as described below. 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 progress on our service as a cloud save, with up to 3 earlier versions of each part of it: your best floor, the climbs you finished, your coins and your language, sound and music settings, with a short summary of them and when you last played. The Game uploads your progress at the end of each climb that ends in a win or a fall, and your settings each time you change the language, the sound or the music; a climb you quit from the pause menu uploads nothing. While the Game cannot reach our service, the save waits on your device. When two saves meet (from another installation, or when you sign in with or link a Google or Apple account that already has its own progress), the one with more finished climbs 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. 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 gameplay 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, until you finish your first climb, when you connect the guide's circuit and how long it took; when each floor starts, with the climb, your machine's health and the parts powered in it; when you clear a floor, fall or quit, with how long it took; the three parts offered after a floor and the one you pick; and when you change the language. We use these to understand how players progress, balance 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 gameplay 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.

Gameplay 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, 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 Home, open Settings, choose Delete data, then hold Hold for 2 seconds to delete. The Delete data screen also shows this installation's Deletion code, for the delete-account web page, and a button that opens https://apzilon.com/delete-account/ in your browser. 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 gameplay records, error reports, daily activity totals, running totals 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 and its copy of the cloud save, turns cloud saving off, deletes your progress from this device (your language, sound and music settings stay), checks that it is gone and returns to the title screen. It asks again how you want to play: a choice the next time you tap the title screen, or Start as Guest on the Delete data screen. A new guest account starts a new game; a Google or Apple account that already has its own progress in this game keeps that progress. The installation ID stays on this device, so the Deletion code does not change. If this device cannot clear your progress, for example when its storage is full, the Delete data screen shows "Deleted from the cloud. This device could not clear its own save. Free some storage space." with a Retry button, and the Game keeps cloud saving off; if it can save a reminder on the device, it remembers the unfinished deletion across restarts, retries at each launch and does not load or upload that progress while the deletion is unfinished. In Android 0.2.0 vc 6 and later and iPhone 0.2.0 build 5 and later, the device wipe also removes every offline save previously kept aside on this phone, and is unfinished until those files are confirmed gone. Without the Game, email [email protected], say Machine Tower and give the email address of the Google account you signed in with on Android or iPhone, or of the Apple account you signed in with on iPhone (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 data screen, which identifies the 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/.

If your account is deleted another way, after an email request or in another installation of the Game signed in with the same Google or Apple account, when the Game on this device next reaches our service, whether within 30 days of the deletion or after those 30 days, it turns cloud saving off, deletes the old account's progress, its copy of the cloud save and its gameplay records and error reports not yet sent from this device, and returns to the title screen. If the Game cannot read its record of the signed-in account at that moment, it can keep the old account's copy of the cloud save on this phone as a backup file instead of deleting it; that file is never loaded or uploaded and can stay until you clear the Game's data or uninstall it. Your language, sound and music settings stay. The Game does not start a new account by itself or upload the deleted account's progress or queued data. The title screen does not ask you to sign in again; to start a new account with an empty game, choose Start as Guest on the Delete data screen after the device has cleared the old progress. If the device cannot clear that progress, the Delete data screen offers Retry instead. In Android 0.2.0 vc 6 and later and iPhone 0.2.0 build 5 and later, the device wipe also removes every offline save previously kept aside on this phone, and is unfinished until those files are confirmed gone. This also applies when a deletion is found while recovering an interrupted first sign-in at launch. If the cached account cannot be read, the unread cloud-save journal is kept separately as a recovery copy, never uploaded or merged, as described under Information stored on your device.

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 0.2.0 vc 6 and later and iPhone 0.2.0 build 5 and later, Settings offers Sign out below Link account for an account linked to Google or Apple, but not for a guest. The confirmation shows the sign-in provider and Player ID, with Cancel first as the prominent button, then Sign out. You cannot sign out during a climb or without a connection. With cloud saving on, the Game sends pending progress first; if it cannot send it, including while a pending save is held, you stay signed in. With cloud saving paused, it sends no save. Our service then revokes this phone's session and device sign-in. The Game clears the session and account details, replaces this device's sign-in key and resets the active local progress; your installation ID, language, sound and music settings stay. On Android it also asks Google to clear this app's saved sign-in state so the next sign-in shows the account chooser. The account and its progress stay on our service, and its cloud-save journal, recovery copies and queued gameplay records stay on this phone for that account only. Those records can be sent when the account returns; the next account starts a separate records session. Any offline save kept aside also stays, as described below. The service creates a fresh empty guest before you choose again; if that request cannot connect, the Game retries when it can. The Game returns to the title screen and opens the sign-in choice. Signing in to the same account again loads that account's save; two copies of that account's progress keep the one with more finished climbs. Sign out is not deletion.

Information stored on your device

The Game saves your progress (best floor reached, climbs finished and the coins you collected) and your settings (language, sound and music) in the app's own storage on your device. With your progress, the Game also notes which account it belongs to (the account ID only as a hash), so that a deletion found later clears that progress before anything is uploaded; the note goes with the progress. Your progress and settings are also copied to our service as your cloud save, and the app keeps a copy of that cloud save on your device with any changes still waiting to be sent. On iPhone, these files 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 gameplay records and error reports there until it can send them. In Android 0.2.0 vc 6 and later and iPhone 0.2.0 build 5 and later, the local owner record also holds the service environment, whether the account has a linked sign-in, and its profile and deletion dates. Cloud-save journals, recovery copies and unsent records are kept separately by account and service environment. Moving to another account or environment loads its own save and ends any climb in progress; the previous account's files stay separate and are not uploaded or offered for restore into another account. An offline save that has never belonged to an account can be kept whole in a separate dated file before a sign-in; the Game does not upload or offer that file for restore. If the first account takes that same offline save, the identical extra copy is removed. Otherwise these offline copies have no fixed expiry: signing out leaves them, while Delete data or a deletion learned from our service removes them all, including when finishing an interrupted first sign-in at launch. Clearing the app's data or uninstalling also removes these local files. If the Game cannot read its cached account when it learns of a deletion elsewhere, it keeps the unread cloud-save journal as a recovery copy, without uploading or merging it; this is separate from the offline copies just described.

The Game may also keep a recovery copy of your save data in the same app storage. This copy is not a cloud backup.

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's App Store and TestFlight may collect information when you download, test or use apps, under Apple's own privacy policy, which we do not control. Apart from what TestFlight shows us about testers (see Testers, support and contacting us), the statistics we see in App Store Connect are aggregated and do not identify you.

Children

The Game is intended for players aged 13 and over. We do not knowingly collect personal information from children under 13. If you believe a child under 13 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 or Apple TestFlight and to contact you about the test.

If you test the Game through TestFlight, Apple shows us the tester details TestFlight shares with developers (such as your name and email address if we invited you by email, your device and app version, and how many sessions and crashes you had) and crash reports, along with any feedback and screenshots you send through TestFlight. We use them only to run the test and fix the Game.

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 Machine Tower and the email address of the Google or Apple account you signed in with, or tell us you played as a guest and include your Player ID from Settings or the Deletion code from the Game's Delete data screen. 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