Apzilon

All Apzilon privacy policies

Arcane Idle Privacy Policy

Developer: Apzilon
Effective date:

Arcane Idle (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 the Game's Settings, Support opens our support page, apzilon.com/support/, in your web browser. Once your account has a Player ID, the Game adds your 9-digit Player ID to that page's address, so it appears in your browser and our hosting provider may keep it in its ordinary access logs; the page itself does not use it. In Credits, a button opens the MiniMax H3 licence page on apzilon.com. In Android 1.0.0 (5) and later and iPhone 1.0.0 (4) and later, Privacy policy, under Support, opens this page, with nothing added to its address. Your browser loads these pages as it would any website.

Information we collect

The Game connects to the Apzilon game service over the internet and supports a guest account without a sign-up form, email or password. A guest account is stored on our service, not only on your phone. It has a random account ID and a random 9-digit Player ID. To sign you in, the Game creates a random installation ID and a secret key on your device and sends them to our service; 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 or Android ID. On Android, if you have not linked Google, clearing the app's data, uninstalling it or moving to another phone prevents you from recovering that guest account. 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. Nothing is created on our service until you choose. When you choose Play as guest, the service creates this guest account; when you sign in with Google or Apple instead, it creates an account tied to that Google or Apple account, or signs you in to the one it already has (see the next paragraphs). If you choose Play as guest before the Game has reached our service, it plays and saves on your device only; in Android 1.0.0 (5) and later and iPhone 1.0.0 (4) and later, it then creates that guest account the next time it reaches our service and uploads your progress as that account's first save. Neither one is a password. In Android 1.0.0 (5) and later and iPhone 1.0.0 (4) and later, Settings, under Account, shows Guest, Google or Apple with your Player ID, never your email or the account ID; earlier builds show neither ID. On iPhone, none of these is your iPhone's advertising identifier either; what happens to the guest account when you delete the Game there 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, when the Game asks how you want to play, and a guest account can link Google later in Settings, under Account, so that your account and the progress backed up to our service are tied to that sign-in. In iPhone 1.0.0 (4) and later, a guest account can also link Sign in with Apple there. 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.

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.

We back up your idle run to our service, with up to 3 earlier versions of each part of the save. Link Google to get it back after you reinstall the Game. It is the same run file the Game saves on your device (listed under Information stored on your device), with a short summary of your stage, level, EXP and play time and the installation ID of the device that saved it. Your language, sound and music settings stay on your device. In Android 1.0.0 (4) and later and iPhone 1.0.0 (3) and later, a change of them is also sent in the gameplay records described below. When two saves from installations of the same account meet, the one that went further 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 with your Player ID. If the account has no save for this game, our service's rule is to take the guest's progress. You never have to choose. In Android 1.0.0 (5) and later and iPhone 1.0.0 (4) and later, after you sign in with or link Google or Apple, the Game loads the save our service keeps for that account, and the run it replaces on your device goes to the local backups described under Information stored on your device. Progress on your device that no account owns, such as progress made before your first account or after a deletion, goes up only as the first save of an account that has no save; with an account that has a save, it is not compared with that save and stays only in the local backups on your device. 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). In Android 1.0.0 (4) and later and iPhone 1.0.0 (3) and later, it also sends gameplay records: each tutorial step you finish and its place in the tutorial (tutorial_step); the start and the loss of each boss fight (stage_start, stage_fail), with the stage, which attempt at it this is since you last opened the Game, whether Auto-Summon was on, whether it would be your first clear of that stage, and each hero in your team with their level and stars, and for a loss also how long the fight lasted and how much HP the boss had left; each upgrade you buy (upgrade): the Growth stat, or the hero and whether it was a level, a star or a skill, with the level before and after; and each change of the language or of the sound or music volume (settings_change), from what to what. In earlier builds, it sends no gameplay records: nothing about your battles, stages, heroes or summons. 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.

Screen, session and error records 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. In Android 1.0.0 (4) and later and iPhone 1.0.0 (3) and later, gameplay records are deleted after 180 days too.

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 battle 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 this game's cloud saves and progress, its screen, session and error records, and its daily activity totals, running totals and record receipts from our active database, and clears the device details and security IP log of its sessions. In Android 1.0.0 (4) and later and iPhone 1.0.0 (3) and later, it also deletes this game's gameplay records. It does not delete other Apzilon games. The Game then forgets the account on this device with its unsent records, deletes your run and its local backups from this device, starts a new run and opens the title screen. The next time you tap to start, the Game asks again how you want to play; cloud saving stays off until you choose, and Play as guest creates a new guest account. Without the Game, email [email protected], say Arcane Idle 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). 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, and say that you played as a guest. We must verify ownership and the deletion scope before carrying out an external request. Your sign-in link and provider profile are removed when no other game needs them, or when you ask to delete all your Apzilon game data. If you signed in with Apple, our service then also asks Apple to revoke the Game's access to your Apple account. 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, then in Android 1.0.0 (5) and later and iPhone 1.0.0 (4) and later, an installation of the Game that reaches our service after the deletion, within 30 days or later, is told so: it forgets the account, the progress stays on that installation in Android 1.0.0 (13) and earlier and iPhone 1.0.0 (12) and earlier, and when you next choose how to play, the Game first asks whether to turn cloud saving back on; it uploads nothing unless you agree. In earlier builds, 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.0.0 (13) and later and iPhone 1.0.0 (12) and later, if the Game on this device next reaches our service more than 30 days after your account was deleted another way, it treats our service's answer as a deletion only when its record on this device of which account its sign-in key opened names the deleted account. Otherwise, such as when that record is missing or cannot be read, it instead starts a new guest account by itself and uploads nothing of the deleted account to it: the Game moves your run into the local backups described under Information stored on your device and starts a new run, keeping your language, sound and music settings, and the new run goes up as the new account's first save; if that backup cannot be written, the Game keeps your run as it is, uploads none of it and tries again at the next launch. The deleted account's save data kept by our account software in the Game, with its copies, and the usage records, gameplay records and error reports already queued for that account also stay on this phone, separate from the new account, with no automatic expiry; none of them is uploaded. Usage records, gameplay records and error reports queued while the Game had not yet reached our service, such as during offline play, are sent with the new guest account. In Android 1.0.0 (14) and later and iPhone 1.0.0 (13) and later, when the Game learns that your account was deleted another way and the note beside your run names that account, it removes that run from the device and starts a new run, so only what you play after that can go up if you agree to turn cloud saving back on. When that note does not name the deleted account, is missing or cannot be read, the run stays on that installation. Copies of that run already in the local backups stay set aside on the device, never read back, shown or uploaded, until the backup rule described under Information stored on your device removes them. If the run cannot be removed, it stays on the device marked as the deleted account's, so that it is not uploaded to any other account; if you sign in to that same account again in the Game and agree to turn cloud saving back on, it can be uploaded again.

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.0.0 (5) and later and iPhone 1.0.0 (4) and later, the Account page in Settings (the account row) offers Sign out for an account signed in with or linked to Google or Apple, not for a guest; it is off while the Game's latest progress is not yet saved on this phone or queued to be sent. The confirmation shows Cancel first, then Sign out. The Game sends any unsent save first; offline, or if that save cannot be sent, nothing changes and you stay signed in. Our service then ends this device's session; on Android the Game also clears Google's sign-in state. The Game then forgets the account on this device, makes a new sign-in key for it and starts a new game; your language, sound and music settings stay. The signed-out account keeps its progress on our service, and its run on this phone goes to the local backups; that run and our account software's copy of its save stay on this phone for that account only and are never uploaded to another account; usage records still waiting stay with that account on this phone, and the next account starts a separate records session. Our service creates a fresh empty guest before you choose again, and the Game returns to the title screen; the next time you tap to start, it asks again how you want to play. Signing in to the same account again loads its save. Sign out is not deletion.

Information stored on your device

The Game saves your idle run (stage progress, account level and EXP, your heroes and team with their levels, stars, skills and gear, team upgrades, gold, gems and other in-game items, summon and quest progress, the camp chest, tutorial progress and how long you have played) and your settings (language, sound and music) in the app's own storage on your device. Your run is also copied to our service as a cloud save. In Android 1.0.0 (10) and later and iPhone 1.0.0 (9) and later, your run, and so its cloud save, also holds which story scenes you have seen. When a cloud copy replaces the run on your device, the Game first keeps the replaced run as a local backup; these backups stay on your device. In earlier builds it keeps at most 3 of them. In Android 1.0.0 (5) and later and iPhone 1.0.0 (4) and later, it also keeps a backup when you sign out, keeps every backup younger than 30 days (older ones only up to 3 backups in all) and never reads them back or uploads them; beside your run it keeps a note of the account and service environment the run belongs to, so that the run never goes up to another account, and our account software in the Game keeps, for 30 days and never uploaded, a copy of its own save data whenever a copy from our service replaces it or a sign-in sets it aside. On iPhone, your run and these backups 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 screen, session and error records there until it can send them. In Android 1.0.0 (4) and later and iPhone 1.0.0 (3) and later, gameplay records also wait 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 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 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 Arcane Idle and the email address of the Google or Apple account you signed in with, or tell us you played as a guest. 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