Mosswake Privacy Policy
Developer: Apzilon
Effective date:
Mosswake (the "Game") is a mobile game by Apzilon.
The Game and the Apzilon game service it connects to are run by Nattapon Suetrong (Apzilon), an independent developer in Thailand ("we", "us"), who decides how your personal data is used (the data controller under Thailand's PDPA). Contact: [email protected].
Information we collect
The Game connects to the Apzilon game service over the internet. The first time you tap the start button, 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. In Mosswake 1.0.0 (9), before the Game has reached our service, it offers Play as guest only. From Mosswake 1.0.0 (10), a first launch shows Connecting until the Game knows which service to use, then asks how you want to play. On iPhone, it offers Sign in with Google only beside Sign in with Apple. Nothing is created on our service until you choose. 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). If this phone already holds game data with no account, such as a setting you changed on the title screen or your earlier save file from before Mosswake had accounts, choosing Sign in with Google or Sign in with Apple first creates a guest account on our service and sends that game data to it as its cloud save, then opens the sign-in. If you cancel or the sign-in fails, that guest account stays, and after a cancel the Game starts with it. This does not happen while cloud saving is off after a deletion; see Deleting your account. A guest can link Google later in Settings > Account. On iPhone, Account also offers Continue with Apple, which ties your Apple account to the same account. 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; 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 played Mosswake before this version, our service's rule is to take the progress and settings already on your device as your first account's cloud save only if that account has no save for this game. Otherwise, the account's save is kept, and the Game takes the copy our service sends. While cloud saving is on, if the Game loses its connection while you play, your progress is saved on your device and waits to be sent when it connects again. What happens to a guest account when you uninstall the Game is described under Information stored on your device. A signed-in Mosswake player who looks up your Player ID through our service can receive your Player ID, player name, avatar identifier if set, level and a rough indication of when you last played. If no player name has been chosen, the card shows Player followed by your Player ID. The card does not show your account ID or email. The service also lets signed-in players block or report another player by Player ID. A player you block cannot look up your card; your own block list contains the cards of players you blocked. Mosswake has no screen to look up, block or report other players. In Mosswake 1.0.0 (14) and later, Settings also shows your player name if available, Google or Apple for a linked account or Guest otherwise, and your Player ID. Opening Settings can ask our service for your profile using your sign-in session. The line uses the account and profile details received; drawing it sends nothing further. It never shows your email.
You can also sign in with your Google account on Android or iPhone, or with Sign in with Apple on iPhone, or link it later, so that your account and the progress backed up to our service are tied to that sign-in. This is optional. If you sign in with it or link it, we receive and keep that service's account identifier and the profile it shares with us: your email address (only when the service says it is verified), whether it is verified, your name, the link to your profile picture (not the picture itself) and your language. Some of these may be missing.
On iPhone, Sign in with Google opens Google's own sign-in page in Apple's web sign-in window; the Game does not include Google's sign-in software. Google sends back a sign-in token with the details above, which the Game passes to our service. Neither the Game nor our service keeps any token from Google, and the Game keeps no Google email address or name on your iPhone. On iPhone, you can also link Google to an account that uses Sign in with Apple, so that you can sign in to it on Android too.
If you use Sign in with Apple, Apple shares your name with us only the first time you sign in, and only if you choose to share it. The email address may be a private relay address from Apple that forwards to your own email; we also keep whether it is one. We also keep a token from Apple, encrypted, only so that we can ask Apple to revoke the Game's access to your Apple account. We ask when your sign-in link is deleted (see Deleting your account), and we delete the token once Apple confirms, or after 30 days of trying.
When the Game starts a new sign-in session with our service, we keep a record of it: the game, the platform, the app build, your language, your device model and operating system version, the country and region that our hosting provider works out from the connection, and when the session was last used. When a new session starts, we also log your IP address with its country, region and network provider, for security and fraud prevention only.
The Game also keeps your whole game on our service as a cloud save, with up to 3 earlier versions of each part of it: your progress (your class, hero name and look, level and experience, party and companions, story and the scenes you have seen, cleared stages, collection, garden, gold, weapons and gear, class skills and loadouts, meal, mercenaries, shop and bounty state, play counters, the in-game day and time, best score and rounds) and your language, music and sound volumes, vibration, tutorial hints, auto battle and auto quest settings, with a short summary of your level and how many stages you have cleared. While cloud saving is on, saves and settings changes are queued for upload; while the Game cannot reach our service, they wait 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. You never have to choose. In Mosswake 1.0.0 (9) and (10), in rare cases, after this phone moved to another account, when you played offline with an account that had no cloud save yet, or when the Game changed which service it uses, the game on this phone or the save file from before this version could be uploaded as that other account's cloud save; Mosswake 1.0.0 (11) fixes this. From Mosswake 1.0.0 (9), Mail fetches notices and gifts of gold and existing items written by us or our service for your account. Opening an unread message sends its ID to mark it read; claiming rewards sends the message IDs or a request to claim all. Each letter's gifts can be claimed once. Our service keeps your inbox, its read and claimed marks, and the rewards 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 rewards from our active database at once. In this version, News and the announcement ticker on the title screen, before you tap the start button, fetch our public announcements, articles and their pictures from our service. Before and after you start or sign in, 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 keeps marks of the News articles you have read on this device, including before Start; once your account is ready, it keeps them in your settings and sends them with your cloud save. Opening Mail is also recorded with the screen records described below.
In Mosswake 1.0.0 (14) and later, you can choose a player name in Settings > Account > Set name, including for a guest account. Use 2 to 12 letters or digits, with no spaces or symbols. The name must be unique in Mosswake and pass a word filter. You choose it once and cannot rename it. One exception: when a guest account with Mosswake progress signs in with a Google or Apple account that has no Mosswake save, that account takes the guest's progress and the guest's player name in place of its own; if the guest had no player name, the account has none afterwards and you can choose one. When the name sheet opens, it sends the text already in the field, initially your hero name, to our service with your sign-in session for a check. While you type, a pause of 0.4 seconds sends the current text to our service with your sign-in session to check whether it is allowed and available. The check does not reserve the name or store the typed text; our service keeps a count of checks for your account. Save sends the name and whether this is your first choice. A taken name can bring back an available suggestion. The Game then puts it in the field and sends it to our service with your sign-in session for the same check. We store the chosen name, its matching key, the time it was set and its name-history entry with your account for this game. The Game keeps the profile answer in memory, and cached account details on your phone can also contain the name. Choosing this player name does not change your hero name or add it to your cloud save. Your hero name stays part of your progress and cloud save. Mosswake itself shows only your own player name, in Settings and on the Account page; our service allows the Player ID look-up described above.
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). It sends no gameplay records: nothing about your fights, quests, stages or items. 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 may offer optional purchases; when it does, such as a one-time, non-consumable unlock of hero classes, the purchase is made through Google Play on Android or the App Store on iPhone. The store shows the price and takes the payment; we never see your card details. The unlock belongs to the store account that paid for it: it comes back with the same Google account on Google Play or the same Apple ID on the App Store, and it never moves between the two stores. The Game reads ownership from the store at launch, on resume and on Restore purchase on the Unlock classes sheet, and keeps an unlock flag on this device. Our server's purchase record does not grant or remove the unlock.
After a purchase, the Game sends the product and Google Play purchase token on Android, or Apple's signed transaction on iPhone, to our service with your Apzilon account session. It also sends an owned purchase not yet recorded for that account when it reads ownership again, including at launch; a failed connection is retried later. Our service asks Google Play to check its purchase or verifies Apple's signed transaction. It records the purchase under the first Apzilon account that sends that receipt. For an older purchase recorded later, this can be the account in use then, rather than the account in use when it was bought. A later report from another account does not move the record; we keep both Player IDs in a purchase-conflict support record. The store receives no code derived from your Apzilon account for this unlock.
We keep a purchase record ID, the account and game IDs, the store, product, purchase kind and state, Google Play's purchase token and order number or Apple's transaction and original transaction IDs, a one-way receipt identifier, the purchase time when provided, check and acknowledgement times, any refund or revocation time, whether it is a test purchase, and whether it was recorded more than a day after purchase. The record also marks that it does not renew and when its account link is removed. Related account-event and usage records keep when it was recorded, the product and purchase IDs, and the price and currency when supplied by the store. Apple can supply a price; the Google Play check used here does not. We use these records for purchase support, refunds, fraud prevention and revenue reporting; test purchases and older purchases recorded later are counted separately from new sales.
For a refund, ask the store where you paid, or email [email protected] with your order or transaction ID for help. If the store reports that you no longer own the purchase, the Game locks those two classes for new characters; characters you already made keep their class. Our server marks a recorded purchase refunded or revoked: a Google Play refund through a daily check with Google Play, so it can take a day or more to appear in our record, and an App Store refund when Apple's verified notification reaches our service. The Game still reads the unlock from the store on the device.
The Game has no advertising 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.
Google Play handles payments under Google's own privacy policy. On iPhone, Apple handles payments under Apple's 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.
Purchase records are kept while your account exists. When you delete your Mosswake account, we remove your account ID from these records at once and keep the de-linked records for 90 days to handle refunds, chargebacks and fraud checks, then delete them in the daily clean-up, which can add up to one day. Keep your order or transaction ID so we can find a purchase if you ask for help. Related account-event and usage records follow the periods above and below. A separate Apple refund receipt marker, containing a hashed transaction identifier but no account ID or game progress, is kept without a time limit so that a refunded receipt cannot be used again.
Deletion covers your whole Mosswake account. Accounts in other Apzilon games are separate. Your cloud saves, progress, usage records and error reports leave our active database at once. In Mosswake 1.0.0 (14) and later, your player name and its history follow the limits under Deleting your account. Deletion records for accounts, game profiles, device sign-ins and ended sessions are removed after 30 days. Our clean-up runs once a day, so a record can remain up to about a day past its limit. Account-event records can remain linked to your account until that purge. Those records are kept for 180 days in total and can retain hashed sign-in identifiers or the account IDs involved in a merge. Copies may also remain in the database provider's recovery history until that history expires.
Deleting your account
In the Game, on the title screen, tap the gear to open Settings, choose Account, then Delete account, and hold Hold to delete for 2 seconds. In Mosswake 1.0.0 (9), Account may not open from Settings before you have started playing or if the first cloud sync fails. From Mosswake 1.0.0 (10), opening Settings > Account alone does not upload a waiting save, and you can close it with X. Once you are signed in, that version lets you reach Delete account even if cloud sync fails, with Sync now available. In both versions, if the Game cannot read your save or has not saved your latest changes on this device, in-game deletion is unavailable; use the web request steps below. 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 usage records (screens and sessions), 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 the links to your Google and Apple sign-ins, with the profiles they shared, are 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 save and records, deletes your progress, the recovery copies and any earlier save file with its backups from this device (your settings, the installation ID and the class unlock stay), and returns to the title screen with a new game. Cloud saving stays off until you choose how to play again. The next time you tap the start button, it asks again how you want to play: Play as guest turns cloud saving back on with a new account and a new game. Choosing Sign in with Google, or Sign in with Apple on iPhone, turns it back on directly; a cancelled or failed sign-in leaves it off. From Mosswake 1.0.0 (11), in a rare case where this phone is still signed in to an account while cloud saving is paused after a deletion, choosing Play as guest makes the Game ask before cloud saving goes back on: nothing is sent until you choose New cloud save from this phone, which turns cloud saving back on for the account this phone is signed in to, with the progress on this phone; on a phone where Mosswake 1.0.0 (9) started a guest account by itself as described below, that progress can be the save that request carried. Back or X sends nothing and leaves cloud saving off; choosing Sign in with Google or Sign in with Apple with that account instead brings back its own progress, and a cancelled or failed sign-in sends nothing and leaves cloud saving off. A Google or Apple account that already has its own progress in this game keeps that progress; the new game saved on this phone after deletion is kept as a backup on this phone instead. In Mosswake 1.0.0 (13) and earlier, Sign out, on the same Account page, is not deletion: the Game first sends any save still waiting, then signs you out on this device, creates a new guest account and starts a new game. A Google or Apple account keeps its progress on our service, 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, until it is deleted: to delete it then, email us with its Player ID, so note the Player ID in Settings > Account before you sign out, or delete the guest account in the Game first. Its game also stays on this device as a recovery copy. Without the Game, email [email protected], say Mosswake 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 and give your Player ID from Settings. A linked account requires verification of that Google or Apple identity; a Player ID alone cannot authorize its deletion. 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 Mosswake 1.0.0 (14) and later, deleting your account in the Game or through a verified email request deletes your name history at once and hides your profile from other players. The profile name, its matching key and the time it was set remain with the deletion record until the account is purged about 30 days later. The name stays taken for other players until that purge. A report made by or about you keeps a copy of the reported player's name even after the account is deleted, for up to 180 days after the report was made or 30 days after it is resolved, whichever comes first. Our clean-up runs once a day, so a record can remain up to about a day past its limit.
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, the Game on this device deletes your progress from this device in the same way as after a deletion in the Game, above, when it next reaches our service, including after the deleted account has been purged from our service. It returns to the title screen with a new game and, the next time you tap the start button, asks again how you want to play. If the saved account details on this device are missing or unreadable, recovery files of the deleted account's cloud save may remain on the device; they are never uploaded and stay until you clear the app's data or uninstall it. In Mosswake 1.0.0 (9), a request that was already on its way, or waiting to be tried again, when a deletion paused cloud saving can still be sent; in rare cases it starts a new guest account by itself and goes to that account, and such a request can carry a save that had not been sent yet. From Mosswake 1.0.0 (10), the Game never uploads the deleted account's progress to a new account: retries and late answers from before the deletion pause cannot start a guest account, send an old write or sign you in, and a sign-in or link still in progress is cancelled when the account is forgotten after deletion or sign-out. In Mosswake 1.0.0 (24) and later, after the deleted account has been purged from our service, 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, and the deleted account's progress, local save journal, recovery copies and the unsent usage 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. In Mosswake 1.0.0 (24) and later, when the sign-in key on this device is missing or cannot be read, the Game continues with a new guest account, and an earlier account's progress, local save journal and unsent usage records and error reports still on this phone stay there, separate from the new account, and are not uploaded under the new account. In both cases, usage 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. Deleting the new guest account in the Game later removes the recovery copies on this phone, but not the other account's local save journal; clearing the app's data or uninstalling the Game removes the files left on this phone.
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 Mosswake 1.0.0 (14) and later, Sign out is on the Account page, reached from the title screen gear through Settings. It is available only for a Google or Apple account; a guest has no Sign out button. The confirmation shows Cancel first. Cancel sends nothing. Sign out is refused if the Game is offline, cannot save your latest progress on this phone, or cannot upload it, including a failed write of claimed Mail gifts. You stay signed in. The Game sends the waiting save before asking our service to end this sign-in session. If the request was sent but its answer was lost, the Game keeps the account on this phone until a later connection confirms the outcome. Once confirmed, it clears the live account and progress, session token and cached account details, and replaces the secret sign-in key. On Android, it also asks Google sign-in software to clear the Game's local sign-in state; failure to clear it does not undo sign-out. The installation ID stays the same. The signed-out account's local save journal, backup copies, recovery copies and unsent usage records stay on this phone, separate from other accounts. They are not uploaded under another account or offered to restore into it. From Mosswake 1.0.0 (16), once an account has taken your earlier save file from before Mosswake had accounts, the Game never uses that file for another account. The test builds Mosswake 1.0.0 (14) and (15) had a rare fault here: if a Sign out was interrupted or lost the connection before its fresh guest account was created, and the Game next opened without a connection, that file could become the cloud save of the next account used on this phone. Mosswake 1.0.0 (16) fixes this. Signing in with the same account brings back its own progress and allows its waiting records to be sent. The next account starts a new play-session ID; queued records keep the IDs they were made with. Deleting that account in the Game on this phone removes its journal and queued records; an in-game deletion also removes the Game's recovery copies and earlier save files on this phone. Clearing app data or uninstalling removes files left on this phone; iPhone system backups may still contain game files as described under System backup. Your settings stay. Our service creates a fresh guest account before you choose again. The Game returns to the title screen, where the start button offers the first-run choice, and waits for that choice before entering a game. If you close and reopen the Game first, it boots that fresh guest. Your signed-out account and its progress stay on our service. Sign out is not deletion.
Information stored on your device
The Game saves your progress (story, level, items, garden, gold, the hero name you choose) and your settings (language, sound, vibration, touch controls, tutorial hints) in the app's own storage on your device. Your progress and these settings, except touch controls, are also copied to our service as your cloud save. When a cloud copy replaces the save on your device, the Game first keeps the replaced save as a recovery copy on your device. If you played before this version, your earlier save file and a one-time backup of it also stay on your device until you delete your account in the Game or clear the app's data. 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 usage records and error reports 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 you 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.
Vibration (VIBRATE): lets the Game vibrate your device as feedback while you play. You can turn it off in the Game's Settings › Vibration.
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 Mosswake and the email address of the Google or Apple account you signed in with, or tell us you played as a guest and give your Player ID from Settings. 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]