Glass Station Privacy Policy
Developer: Apzilon
Effective date:
Glass Station (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 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. 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. In Settings, Account shows your 9-digit Player ID. It is not a password.
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. Link Google, or Apple on iPhone, to get your progress back after you reinstall the Game. It includes your level progress, best Classic score, which story lines you have seen and play counters. In Android 1.0.0 (11) and later and iPhone 1.0.0 (12) and later, the save on your device and the cloud save also hold the cases you have solved, the tickets you have taken, your glass shards and the repairs you have bought. In Android 1.0.0 (11) and later and iPhone 1.0.0 (12) and later, when this device's save of your own account and your account's cloud save have the same progress score, the Game keeps the one with more changes to your cases, tickets, glass shards and repairs, and uploads it if it is the one on this device; earlier versions of the cloud save are kept as described above. When the Game loads a cloud save of your account written by an earlier build over this device's save of that account, and this device's save holds glass shards or repairs, the Game adds them to it and uploads it. When a guest signs in to or links a Google account, or an Apple account on iPhone, 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. There is no in-game way to restore that archived save. If the account has no save for this game, our service's rule is to take the guest's progress. When two saves from installations of the same account meet, the one with further progress is kept whole; a tie or missing progress score keeps the server copy. The other copy is kept for 30 days so support can recover it. You never have to choose. Earlier builds must update before their cloud-save requests can proceed. 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. In Android 1.0.0 (12) and later and iPhone 1.0.0 (13) and later, the save on your device and the cloud save also hold your play statistics: for each level, your tries, your clears and your tries since your last clear, and once you clear it, your fastest active play time and your fewest tries for a clear; for each case, the tries and active play time it took, how many answers you gave and how many were wrong, whether your first answer was right and whether you solved it; your total tries, clears, losses and quits across all levels; and how many Classic games you have ended. In Android 1.0.0 (12) and later and iPhone 1.0.0 (13) and later, News on Home shows our posts from our service while the Game is connected, and otherwise the notes for this version that come inside the Game. After an update, those notes open once by themselves on Home, but not on a new installation; to know which notes you have seen, the Game keeps the build number of the last notes you have seen in its settings file on this device, never sends it, and keeps it, even after you delete your account or sign out, until you clear the Game's data or uninstall it. Opening a post from our service saves its ID and the news revision on this device and includes them in your cloud save. A post can carry a link to our website; tapping it asks your browser to open it. In Android 1.0.0 (12) and later and iPhone 1.0.0 (13) and later, while the Game is connected to our service, Mail on Home fetches notices and gifts of glass shards written by us or our service for your account. Opening an unread message sends its ID to mark it read; claiming gifts sends the message IDs or a request to claim all; Delete read sends the IDs of read messages with nothing left to claim, and our service removes them from your inbox. Each letter's gifts can be claimed once. Claimed glass shards are kept in your cloud save and its copy on this device, and Repair can spend them. Our service keeps your inbox, its read and claimed marks, and the gifts it gives you, linked to your account. A letter usually stays in your inbox for 7 days. These are game messages, not email or messages written by other players. Deleting your account removes its inbox and gifts from our active database at once. Opening News or Mail is also recorded with the screen records described below.
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 each run of a level or of Classic: when it starts, and when you clear it, run out of space or quit it from Pause (stage_start, stage_clear, stage_fail, stage_quit), with the level or Classic, a run ID made from the time the run started, the attempt number and, when the run ends, how long it lasted; a cleared level also says whether it was your first clear of it. On the first launch it also sends when the opening story ends, how long it took and whether you skipped it, and your first move on level 1 with the time it took (tutorial_step). In Android 1.0.0 (11) and later and iPhone 1.0.0 (12) and later, until you first win level 1 it also sends your first cleared line, your next move after the Game points at the level's goal and that first win, each with the time since the run began (tutorial_step). In Android 1.0.0 (12) and later and iPhone 1.0.0 (13) and later, each run also says whether you started it with Retry after running out of space, whether it replays a level you had already cleared, whether level 1's guide was on and how many soot panes the level asks you to clear; when it ends, it also says how long you actively played (time paused or with the Game in the background left out), how many pieces you placed, how many rows and columns you cleared and how many soot panes were left. A cleared level also says how many glass shards it earned, and the end of a Classic game, when you run out of space or quit, says your score, your best score and whether it is a new best. The Game also sends when you start a case, with the case, the level and how many clues you had found (case_start); each clue you find, with the case, the clue, its number in the case and the level (clue_found); each answer you give, with the case, the suspect you chose, whether it was right and which answer it was (accuse_answer); when you solve a case, with the case, how many answers you gave, whether your first answer was right, how many were wrong, the number of levels in a case, and the tries and active time it took (case_solved); each step of level 1's guide whose pointing hand shows, with the step, the level and the attempt number, and each time the Game explains a wrong answer, with the case, the suspect and the clue it points to (help_shown); and each repair you buy, with the part of the station, the repair, its cost and the glass shards you have left (repair_buy). 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.
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.
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, while the account is on this device, from Home open Settings with the gear, choose Account, then Delete account and hold Hold to delete for 2 seconds. In Android 1.0.0 (13) and later and iPhone 1.0.0 (14) and later, Settings is in the Menu that the button at the top left of Home opens. This in-game request deletes this game's cloud saves, progress, gameplay records, daily activity totals, running totals and record receipts from our active database, clears the device details and security IP log of its sessions, and signs you out. Its unsent records and its local copies of your progress are cleared too: the Game starts a new game on this device and keeps only your sound, music and language settings. In Android 1.0.0 (9) and later and iPhone 1.0.0 (10) and later, saves the Game set aside earlier in separate files on this device, including this account's own from a sign-out, stay (see Information stored on your device). If it cannot write the new save, it tells you that the old save is still on this device. The in-game request does not delete other Apzilon games. Cloud saving then stays off until you choose Play as guest, Sign in with Google on Android or iPhone, or Sign in with Apple on iPhone. Play as guest starts a new guest account with a new game; you can then link Google, or Apple on iPhone, in Settings > Account. Signing in turns cloud saving on without creating a guest account first. In Android 1.0.0 (9) and later and iPhone 1.0.0 (10) and later, the Game then loads the save of the account you sign in to, or starts a new game for it if it has none, whatever the progress on this device, and never uploads that progress into it (see Information stored on your device). In earlier versions, if the account you sign in to already has progress in this Game, the save with further progress is kept; a tie keeps the account's copy. A cancelled or failed sign-in changes nothing and cloud saving stays off. The Game does not upload the deleted account's old progress or removed records. Without the Game, email [email protected], say Glass Station and give the email address of the Google account you linked 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). A linked account requires verification of that Google or Apple identity; a Player ID alone cannot authorize its deletion. For a guest, give the Player ID that Settings > Account shows 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 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 forgets the account on this device, turns cloud saving off and removes its local cloud-save records and unsent gameplay records and error reports. If the Game cannot read its record of the signed-in account at that moment, it can keep that account's local cloud-save records on this phone as a backup file instead of removing them; that file is never loaded or uploaded and can stay until you clear the Game's data or uninstall it. It also starts a new game and clears your saved sign-in choice; your sound, music and language settings stay. In Android 1.0.0 (12) and iPhone 1.0.0 (13), before starting that new game, the Game first moves the game on this device whole into a file of its own on this device (see Information stored on your device), unless it is still a new game, and then shows "Account deleted. Your earlier progress (Level n) is still kept on this device.", with that game's level as n, instead of "Account deleted."; if that file cannot be written, the Game leaves that game on this device as it was and starts no new game, tells you that the old save is still on this device and uploads none of it before the next launch; from then on the rules under Information stored on your device apply to that save again. It shows "Account deleted." and offers Play as guest, Sign in with Google on Android or iPhone, or Sign in with Apple on iPhone through the sign-in sheet where Google is offered, or Play as guest through Tap to Start on the title screen otherwise. Cloud saving stays off until you choose one of these ways to start again. Play as guest starts a new guest account with a new game and cloud saving on; you can then link Google, or Apple on iPhone, in Settings > Account. Signing in turns cloud saving on without creating a guest account first. In Android 1.0.0 (9) and later and iPhone 1.0.0 (10) and later, the Game then loads the save of the account you sign in to, or starts a new game for it if it has none, whatever the progress on this device, and never uploads that progress into it (see Information stored on your device). In earlier versions, if the account you sign in to already has progress in this Game, the save with further progress is kept; a tie keeps the account's copy. A cancelled or failed sign-in changes nothing and cloud saving stays off. The Game does not upload the deleted account's old progress or removed records, or start a new guest account by itself. While the account is in this deleted state, Settings > Account hides Delete account and offers Start again: it asks for confirmation before starting a new game in the same way. If the Game cannot write the new save, it tells you that the old save is still on this device. In Android 1.0.0 (13) and later and iPhone 1.0.0 (14) 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: unless the game on this device is still a new game, the Game moves that game whole into a file of its own on this device (see Information stored on your device) and starts a new game for the new account, keeping your sound, music and language settings; if that file cannot be written, it keeps that game as it is and tries again at the next launch. The deleted account's local cloud-save records and the unsent 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. 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.
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 (9) and later and iPhone 1.0.0 (10) and later, Settings > Account, opened with the gear on Home, offers Sign out for an account signed in with or linked to Google or Apple, not for a guest. In Android 1.0.0 (13) and later and iPhone 1.0.0 (14) and later, Settings is in the Menu that the button at the top left of Home opens. It is not offered during a level or a Classic run: the Pause menu there has no Account page. Sign out asks first, with Cancel first and Sign out below it; Cancel, Back or tapping outside it changes nothing. In Android 1.0.0 (13) and later and iPhone 1.0.0 (14) and later, the button above Sign out reads Back instead of Cancel. The Game sends any unsent save first; offline, or if that save cannot be sent, nothing changes and you stay signed in. Nothing changes either while the save on this device belongs to no account or to another account. 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 and makes a new sign-in key for this device. It moves the save you were playing whole into a file of its own on this device, where it is never loaded or uploaded again (see Information stored on your device), clears your saved sign-in choice and starts a new game; your sound, music and language settings stay. If that file cannot be written, the Game keeps the save as it was, never uploads it to another account and tries again at the next launch. Our service then creates a new guest account for this device, and the new game becomes its cloud save. The Game returns to the title screen; the next time you tap it, it asks again how you want to play. The signed-out account keeps its progress on our service, and its copy on this phone is kept only for that account and never uploaded to another one. 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. Signing in to the same account again loads its save; if you played as the new guest in the meantime, the rule above for a guest that links an account decides which save is kept. Sign out is not deletion.
Information stored on your device
The Game saves your level progress, best Classic score, which story lines you have seen, play counters and settings (sound, music and language) in the app's own storage on your device. Your progress is also copied to our service as a cloud save. In Android 1.0.0 (9) and later and iPhone 1.0.0 (10) and later, the save also records which account it belongs to and which of our services (test or live) that account is on, and the Game uploads it only to that account. When you sign in to or link a Google or Apple account while this device holds a save that is not that account's own, the Game loads the save our service holds for that account, or starts a new game for it if there is none, whatever the progress on this device; the save that was on this device is first moved whole into a file of its own on this device. Progress made with no account, such as at an offline first launch or after you delete your account, can become the first save of a guest account this device starts, if that guest has no save yet; the Game never uploads it straight into a Google or Apple account you sign in to, but once it is a guest's save, the rule for a guest that links an account decides what happens to it (see Information we collect). When you sign out, the save you were playing is moved into a file of its own the same way. In Android 1.0.0 (11) and later and iPhone 1.0.0 (12) and later, the same happens to this device's save of your own account when the Game loads your account's cloud save over it and that cloud save lacks a change to your cases, tickets, glass shards or repairs made on this device; if that file cannot be written, the Game loads nothing over this device's save and tries again at the next launch. In Android 1.0.0 (12) and iPhone 1.0.0 (13), the save you were playing is also moved into a file of its own this way when the Game learns that your account was deleted another way, unless it is still a new game (see Deleting your account). In Android 1.0.0 (13) and later and iPhone 1.0.0 (14) and later, the save you were playing is moved into a file of its own this way when the Game starts a new guest account by itself after your account was deleted another way, unless it is still a new game (see Deleting your account). If the Game on this device moves between our test service and our live service, the save of an account on the service it leaves is kept whole in a file of its own, is never uploaded to the other service and comes back if the Game returns to that service; the other service starts with a new game or the save of the account you use there. Apart from bringing back a save kept for the other service, the Game never loads, uploads or offers a save from these files, and keeps them until you clear the Game's data or uninstall it; deleting your account does not remove them. In Android 1.0.0 (11) and later and iPhone 1.0.0 (12) and later, if the save on this device can be opened but not read when the Game starts, the Game moves it whole into a file of its own beside it and starts as a new installation would, so the cloud save of an account you are signed in to comes back when the Game reaches our service. The Game never loads, uploads or offers that file. Like the files above, it stays until you clear the Game's data or uninstall it, and deleting your account does not remove it, except that when the Game sets aside another unreadable save, it deletes those set aside more than 30 days before the new one. If the save cannot be opened or moved, the Game leaves it as it is and reads it again at the next launch. 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 the app's other files 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'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 Glass Station and the email address of the Google account (on Android or iPhone) or Apple account (on iPhone) 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
Apzilon | [email protected]