Lantern Company Privacy Policy
Developer: Apzilon
Effective date:
Lantern Company (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 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. Before the Game has reached our service, it offers Play as Guest only. Nothing is created on our service until you choose, except for the fresh guest made after Sign out in Android 1.0.0 (3) and later and iPhone 1.0.0 (4) and later (see below). 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 Settings, 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 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. Progress already saved on your device, such as from an earlier version of the Game, is uploaded to the account you choose. In Android 1.0.0 (4) and later and iPhone 1.0.0 (5) and later, this happens only if that account has no save for this game; if it has one, the Game loads that account's save and keeps this phone's progress in a separate file on this phone, which is never uploaded and does not come back by itself. In Android 1.0.0 (3) and later and iPhone 1.0.0 (4) and later, progress belonging to a different signed-in account or a different service environment stays separate on this phone instead of being uploaded into the account you choose; the save rules below explain what happens when a guest signs in. What happens to a guest account when you uninstall the Game is described under Information stored on your device. In Android 1.0.0 (3) and later and iPhone 1.0.0 (4) and later, Settings > Account shows Guest account, Google account or Apple account and the Player ID with Copy once an account is available; it has no player-name entry. Play offline on the Connection lost notice lets you keep playing and saving on this phone. When the connection returns, queued progress and records can be sent for their own account; this does not turn cloud sync back on after a deletion.
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.
The Game also keeps your progress on our service as a cloud save, with up to 3 earlier versions of it: your coins, the floor you reached, your squad's recruits and supply levels, your weapon levels and the weapon you carry, and whether you finished the first run. Your best result, rounds played and language stay on your device. The Game uploads this progress each time it saves it, for example when a floor's run ends or you spend coins on an upgrade; while it cannot reach our service, the save waits on your device. 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. If the account has no save for this game, our service's rule is to take the guest's progress. In Android 1.0.0 (4) and later and iPhone 1.0.0 (5) and later, when a guest moves to an account that has a save, the Game loads that account's save and keeps the guest's local progress aside on this phone for its original account and service environment, with no automatic expiry. That guest set is not uploaded or offered back into the account you entered. If the account has no save, the Game can upload the guest's progress. When the guest's save is set aside and has progress, our service also stores an account notice about it for 30 days; these builds have no Mail screen. 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 when a floor's run starts, and when you lose it or leave it, with the floor and how long the run lasted. We use these to understand use of the Game, balance it 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, tap the gear to open Settings, choose Account, then Delete account, and hold Hold to delete for 2 seconds. The Delete account screen also has Delete on the web, which opens https://apzilon.com/delete-account/ in your browser, and for a guest account it shows this installation's Deletion code with a Copy 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 gameplay records (screens, sessions and floor runs), 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, deletes the active progress from this device (your language stays). In Android 1.0.0 (3) and later and iPhone 1.0.0 (4) and later, sets previously kept aside on this phone remain separate; a set from the deleted profile is not restored. The Game shows the message Account deleted. It then asks again how you want to play. Without the Game, email [email protected], say Lantern Company 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. 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/.
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.0.0 (3) and later and iPhone 1.0.0 (4) and later, when the Game learns that its account was deleted elsewhere, it keeps this phone's progress and pauses cloud sync, including when it reconnects after the 30-day deletion window. It shows Cloud save deleted and asks Turn cloud save back on? Not now keeps cloud sync paused and lets you play locally; the question returns on a later launch. New cloud save from this phone turns sync back on and uses this phone's progress for a guest account; if the phone still holds an account, the service checks that account first. You can instead choose an available Google or Apple sign-in, with the save rules above applying to the account you enter. Cancelling or a failed sign-in leaves the question open and keeps this phone's progress. If that Google or Apple account was deleted less than 30 days ago, the sign-in error shows its deletion date and the date you can start again with it; that attempt does not upload this phone's progress into the deleted 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.0.0 (3) and later and iPhone 1.0.0 (4) and later, Settings > Account offers Sign out for a Google or Apple account, but not for a guest. The confirmation shows Cancel first, then Sign out. You cannot sign out during a run or without a connection. With cloud sync on, the Game sends pending progress first; if it cannot send it, including while that save is held, you stay signed in. With cloud sync paused, it sends no save. The service then revokes this phone's session and device sign-in, and the Game clears its sign-in details and resets the active local progress and first-run choice. The account's progress stays with the account, and its progress set is kept aside on this phone for that account and service environment, as described under Information stored on your device. Queued gameplay records stay with that account on the phone and can be sent when it returns; the next account starts a separate records session. The service creates a fresh empty guest before you choose again. The Game returns to the first-run choice, or the title screen if no sign-in is available. Signing in to the same account again checks its kept set against the account's current data; a set from a deleted profile is not restored, and two copies of that account's save keep the one that went further. Sign out is not deletion.
Information stored on your device
The Game saves your progress (coins, the floor you reached, your squad's recruits and supply levels, your weapon levels and the weapon you carry, whether you finished the first run, your best result and rounds played) and your settings (language) in the app's own storage on your device, along with how you chose to play. Your coins, floor, squad, weapons and first-run progress are also copied to our service as your cloud save; your best result, rounds played and language stay on your device. If a cloud save comes from a newer version of the Game that this version cannot load, the Game keeps that one copy on your device, unloaded, until you update. 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 1.0.0 (3) and later and iPhone 1.0.0 (4) and later, the active progress set has a separate local owner record containing the account, service environment, sign-in state and profile date. Moving to another signed-in account or service environment, or signing out, keeps the old set in a separate file for its owner; if one is already there, the further set is kept. These files are not uploaded into another account or offered there for restore. They have no fixed expiry. When the same account returns in the same environment and the service confirms its current profile, its kept set can replace an empty or less advanced local set; a set from a deleted profile is discarded. That kept file is then removed. The Game also keeps account-specific save journals and recovery copies beside them. If it cannot read the cached account after a deletion elsewhere, it keeps the unread save journal as a recovery copy, without uploading or merging it. Clearing the app's data or uninstalling removes these local files.
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 Lantern Company 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 account 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
Apzilon | [email protected]