Apzilon

All Apzilon privacy policies

Leasebreaker Privacy Policy

Developer: Apzilon
Effective date:

Leasebreaker (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].

The Game's Licenses page has two links that open pages on apzilon.com in your web browser: the MiniMax H3 licence page and our Terms of Use. Your browser loads them 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 opens Sign in, which asks how you want to play: on Android, Play as guest or Google; on iPhone, Play as guest, Google or Apple, with Google only when Apple is offered too. Google and Apple each appear only after our service has confirmed to the Game that it is available; until then, the Game offers Play as guest only. Nothing is created on our service until you choose. When you choose Play as guest, the service creates a guest account for you: no sign-up form, no email and no password. When you choose 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). The account has a random account ID and a random 9-digit Player ID. In Android 1.0.0 (9) and later and iPhone 1.0.0 (9) and later, Settings > Account shows the name you choose in Leasebreaker, then Guest, Google or Apple, then your Player ID; it never shows an email address or the account ID. The name on this line comes from the phone, and displaying it sends nothing new to our service. Earlier builds display neither ID. Neither one 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; 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 Play as guest while the Game cannot reach our service, it plays and saves on your device only, and the guest account is created later, after the Game reaches our service.

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.

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 keep your cloud save on our service, with up to 3 earlier versions of each part of the save. It includes your player name, story and stage progress, currencies, items, crew, teams and upgrades. In Android 1.0.0 (9) and later and iPhone 1.0.0 (9) and later, the Game follows the save our service chooses. When a guest signs in to or links a Google or Apple account, 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. When the account's save is kept, the guest's progress on this phone goes to a local support copy, never uploaded or restorable into that account. 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 our service is kept. You never have to choose. From Android 1.0.0 (8) and iPhone 1.0.0 (8), if the Game can identify this phone's progress as belonging to another account and the accounts were not merged, it takes the signed-in account's own save, or a new start if it has none, and keeps this phone's previous progress in a local support copy that is never uploaded to the other account or offered through Restore a save. In Android 1.0.0 (7) and earlier online builds and iPhone 1.0.0 (7) and earlier online builds, moving to another login account could instead upload this phone's progress to that account by the further-progress rule. Android 1.0.0 (8) and earlier online builds and iPhone 1.0.0 (8) and earlier online builds treat both sign-in answers as the same account and settle by the further-progress rule, so they can still upload the guest's further progress over the account's save even with our service's new rule. 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 name you choose in the Game is saved with your progress, so it is also part of your cloud save.

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). 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 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.

In the Game's Settings, tapping Privacy policy asks your browser to open this policy page, and tapping Support opens your email app with our address filled in. Neither one attaches your save data or any other information about you, and no email is sent unless you send it yourself. Your browser and your email service work under their own privacy policies.

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.

When you delete, the data described under Deleting your account leaves our active database at once. The records that only mark the deletion (account, game profile, device sign-in and ended sessions) are removed after 30 days. When you delete your account in a game, we may keep the date you did it, linked to your account ID, only so that an older copy of that game on another device cannot bring its data back into that account. It holds no game data, is never shown to other players, and is removed within 30 days after you have deleted your account in every Apzilon game you play, or asked us to delete everything. Account-event records are kept for 180 days in total. Deletion does not immediately remove their link to your account. The relevant records lose that link when the account or game-profile deletion markers are purged after 30 days; the daily clean-up can add up to one day. They can still keep a hashed sign-in identifier or the account IDs of a merge. After a deletion, copies can remain in our database provider's recovery history for up to 7 days, then roll off.

Deleting your account

In the Game, on Android or iPhone, from Home, open Settings, choose Delete account, then hold Hold to delete for 2 seconds. This option appears when the Game has an online account to delete. This deletes your account and progress in this Game: its cloud saves, progress, gameplay records, daily activity totals, running totals, any first-clear records and record receipts leave our active database at once, the device details and IP log of its sessions are cleared, and you are signed out. The Game also clears its unsent records, so deleted history is not uploaded again. Deleting in one Apzilon game does not touch your account or progress in another. Your sign-in link and the profile from your sign-in service are deleted at the latest when you have deleted your account in every Apzilon game you play, or when you ask us to delete everything. If you signed in with Apple, our service then also asks Apple to revoke the Game's access to your Apple account. Without the Game, email [email protected] and say Leasebreaker, which sign-in service you used (Google on Android or iPhone, or Apple on iPhone), and its email address, including Apple's private relay address if used. We need to verify that the account is yours before deleting it. If you played only as a guest, say so; we cannot delete an account we cannot identify and verify. In Android 1.0.0 (9) and later and iPhone 1.0.0 (9) and later, you can give the Player ID shown in Settings > Account with your email request, including if you play as a guest; a guest has no Sign out in these builds. The following applies only to Android 1.0.0 (8) and earlier online builds and iPhone 1.0.0 (8) and earlier online builds: Leasebreaker does not show a Player ID or deletion code. Sign out, in Settings, is not deletion: the Game first uploads your save, then signs you out, creates a new guest account and starts again from Sign in on this device. A linked Google or Apple account keeps its progress, and signing in with it again brings that progress back. A guest account you sign out of cannot be opened again. It stays on our service with its cloud save, with no time limit, and because Leasebreaker shows no Player ID or deletion code, we may not be able to identify it to delete it. To delete a guest account, use Delete account in the Game before you sign out. Full steps: https://apzilon.com/delete-account/. You can also ask us to delete your data in all Apzilon games.

In Android 1.0.0 (18) and later and iPhone 1.0.0 (15) and later, after you delete your account in the Game, this phone starts again as a new player and nothing of the deleted account's progress is uploaded. Some copies of your progress stay on this phone: the backup kept for Restore a save and one earlier copy of it, until later backups replace them; the local support copy and one earlier copy of it, until later sign-outs, account changes or a deletion made another way replace them; the separate copy kept when an account is deleted another way, described in the next paragraph; and the previous version of the save file, until the Game next saves, usually in the same session. None of them is uploaded by the Game on its own or offered through Restore a save to any other account. In Android 1.0.0 (18) and iPhone 1.0.0 (15), if you play another Apzilon game with the same Google or Apple account and sign in to Leasebreaker with it again on this phone, Restore a save can still offer that backup, and choosing it uploads that progress to the account. They are removed when you clear the app's data or uninstall the Game. On iPhone, they are also part of the app's data in your own iCloud or computer backups when you use them; we never receive those backups. In Android 1.0.0 (19) and later and iPhone 1.0.0 (16) and later, before our service is asked to delete your account, the Game records the deletion on this phone with the progress being deleted. Once the Game has received our service's answer that the account is deleted, that record stays on this phone, separate from the copies above, until you clear the app's data or uninstall the Game; on iPhone, it is part of your own backups in the same way. From then on, nothing of the deleted account's progress is uploaded or offered through Restore a save to any account, including the same account if you sign in to it again. If the Game is closed or loses its connection after the request is sent and before that answer arrives, our service may have deleted the account while this phone still holds its progress; the Game then learns of the deletion when it next reaches our service and treats it as a deletion made another way, described in the next paragraph. If the Game cannot record the deletion, for example when the phone's storage is full or the save cannot be read, it does not delete your account: it shows that it could not save the game, and nothing is deleted.

If your account is deleted another way, after an email request or in another installation of the Game, Android 1.0.0 (8) and later and iPhone 1.0.0 (8) and later recognize the deletion when this installation next reaches our service, whether within 30 days of the deletion or after those 30 days. The Game forgets the account on this device and pauses cloud saving, but keeps your progress on this phone. In Android 1.0.0 (16) and later and iPhone 1.0.0 (13) and later, after those 30 days the Game 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, without pausing cloud saving. If the Game can identify this phone's progress as the deleted account's, the new account starts from a new start and that progress goes to the local support copy, never uploaded or offered through Restore a save; if it cannot, that progress can upload to the new guest account as its first save. The deleted account's cloud-save journal and the gameplay records and error reports already queued for that account stay on this phone, separate from the new account, with no automatic expiry; none of them is uploaded. 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 (12) and later and iPhone 1.0.0 (10) and later, if the same account has already started this game again elsewhere when this installation next reaches our service, the Game does not forget the account or pause cloud saving: it moves this phone's previous progress to the local support copy in Android 1.0.0 (18) and earlier and iPhone 1.0.0 (15) and earlier, never uploaded or offered through Restore a save, stops offering any earlier backup of that account through Restore a save while keeping it on this phone, and continues with the account's new save, or a new start if it has none. In Android 1.0.0 (19) and later and iPhone 1.0.0 (16) and later, that previous progress goes instead to a separate local copy kept for that case, never uploaded or offered through Restore a save, and the local support copy is not replaced; each such copy stays on this phone until you clear the app's data or uninstall the Game. The exception is when the Game learns of the new start only because our service refuses an upload from a session that was already running: that progress can then go to the local support copy, as in earlier builds. Android 1.0.0 (8) and (9) and iPhone 1.0.0 (8) and (9) do not recognize that case and can upload this phone's previous progress to that account, as its first save or over a new save that went less far. At Home, and again at each launch while cloud saving remains paused, the Game asks whether to turn cloud saving back on and upload this device's progress, with Upload and Not now. If the deleted account was forgotten on this device, only Upload does that: at Home, it creates a new guest account with this device's progress as its first save, even if the deleted account used Google or Apple. If you have not yet chosen how to play on Sign in, choosing Play as guest, Google or Apple asks the same question first. After the Game has forgotten the deleted account, with Upload, Play as guest creates a new guest account with this device's progress, and Google or Apple signs straight into that account. In Android 1.0.0 (9) and later and iPhone 1.0.0 (9) and later, the Game takes the account's save if it has one and puts this phone's previous progress in a local support copy, never uploaded or restorable into that account; if the account has no save, our service's rule is to take this phone's progress. Android 1.0.0 (8) and iPhone 1.0.0 (8) instead settle the copies by the further-progress rule and can upload this phone's further progress over the account's save. In Android 1.0.0 (16) and later and iPhone 1.0.0 (13) and later, before the account's save replaces this phone's progress in that case, the Game also copies that progress to a separate file on this phone that later sign-outs and account changes do not replace. Like the support copy, it is never uploaded or offered through Restore a save, and deleting the account in the Game does not remove it; it stays until two later copies of the same kind have replaced it, or until you clear the app's data or uninstall the Game. On iPhone, this copy is also part of the app's data in your own iCloud or computer backups when you use them; we never receive those backups. Not now, Android Back, or a cancelled or failed sign-in uploads nothing and leaves cloud saving paused. In these new builds, in a rare case where this phone is still signed in to an account while cloud saving is paused after a deletion, Upload at Home, or Upload after choosing Play as guest on Sign in, turns cloud saving back on for that account with its logins kept, and allows this phone's progress to upload to that same account by the same-account progress rule above instead of creating a new guest account. On Sign in, Upload followed by a successful Google or Apple sign-in to that held account also turns cloud saving back on for it; Not now, Android Back or a cancelled or failed sign-in leaves it paused and sends no progress. A missing or unreadable saved account record or cloud-save journal does not by itself let the old progress upload: the Game also checks the remaining account ownership and cloud-save records. If the sign-in key must be recreated and no save revision or account-linked file remains, the Game cannot tell this from a new installation, and progress still on the phone can upload to a new guest account. While cloud saving is paused, your progress stays on this phone until you replace or delete it, clear the Game's data or uninstall the Game; a deletion made elsewhere does not erase your own iCloud or computer backups. After an in-game deletion in these new builds, choosing Google on Android or iPhone, or Apple on iPhone, signs straight into that account without creating a guest account first. In Android 1.0.0 (7) and earlier online builds and iPhone 1.0.0 (7) and earlier online builds, an installation 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.

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 (18) and iPhone 1.0.0 (15), the exception is the backup that Restore a save can still offer, described above.

In Android 1.0.0 (9) and later and iPhone 1.0.0 (9) and later, Sign out is in Settings > Account, opened from the title screen gear or Home's Settings, only for a Google or Apple account; a guest has no Sign out. It is disabled while a run is open, from entering a stage until that run is settled; Settings cannot be opened during a battle. The confirmation sheet puts Cancel first; Cancel, a tap outside the sheet, Back and X send nothing. Sign out first uploads this phone's progress to the account's cloud save. If the Game is offline or that upload fails, it refuses and shows a message; nothing changes and you stay signed in. You are then signed out on this phone, its progress is moved to a local support copy under that account, our service creates a fresh guest account, and the Game starts a new game and returns to the title screen. On Android, the Game also clears its Google sign-in on this device. Gameplay records and error reports not yet sent stay on this phone for that account, with their own play-session ID, and go up only if that account signs in on this phone again; none goes up under the new guest. The next account's records start a new play-session ID; the installation ID stays the same, and the sign-in secret key on this device is replaced. The local support copy is never uploaded or offered through Restore a save; it is replaced by the next sign-out, by the Game taking another account's copy, or by a purge after account deletion. In Android 1.0.0 (12) to (18) and iPhone 1.0.0 (10) to (15), it is also replaced when the same account has started this game again elsewhere. Deleting the account in the Game does not remove that support copy; clearing the app's data or uninstalling it does. On iPhone, this copy is also part of the app's data in your own iCloud or computer backups when you use them; we never receive those backups. The account and its progress stay on our service; signing in with that account again loads its save. Sign out is not deletion.

Information stored on your device

The Game saves your progress (story and stages, currencies and items, crew, teams and upgrades, tutorial and mission progress, inbox letters and rewards with their read and claimed marks, shop stock and recruits), the name you choose and your settings (language, sound) in the app's own storage on your device. Your progress is also copied to our service as a cloud save. 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, and may keep a local recovery copy of your progress. On iPhone, the save and any recovery copy are also part of your iPhone's own iCloud and computer backups when you use them; we never receive those backups.

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 Leasebreaker and which sign-in service and email address you used, 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