Apzilon

All Apzilon privacy policies

Inkbound Archive Privacy Policy

Developer: Apzilon
Effective date:

Inkbound Archive (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 title screen, the Game asks how you want to play: on Android, Sign in with Google or Play as guest; on iPhone, Sign in with Apple 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. 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 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. Neither one is a password. In Android 1.0.0 (3) and later and iPhone 1.0.0 (3) and later, Settings, under Account, shows Guest, Google or Apple with your Player ID, never your email or the account ID; earlier builds show neither ID. 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 Inkbound Archive before this version, the progress already on your device is uploaded to the first account you choose. If you choose Play as guest while the Game cannot reach our service, it plays and saves on your device only; the next time you tap the title screen while the Game is connected, it asks again how you want to play, and the progress on your device is uploaded to the account you then choose. If that account already has a save, the one that went further is kept, as described below. What happens to a guest account when you uninstall the Game is described under Information stored on your device.

You can also sign in with your Google account on Android, 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.

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 save on our service as a cloud save, with up to 3 earlier versions of each part of it: the same progress the Game saves on your device (listed under Information stored on your device) and your language, sound and music settings, with a progress number made from the levels you have completed, and the installation ID of the device that saved it. The Game uploads your save as you play and your settings each time you change them; while the Game cannot reach our service, they wait on your device. When two saves meet (from another installation, or when you sign in with or link Google or Apple), the one that went further (more levels completed) 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. 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 you open (the title screen, the choice of how to play, the puzzle board, the Settings page that Account opens from the pause, the steps of signing in, linking and deleting your account, and the notices the Game shows when it needs an update, is closed for maintenance or cannot reach our service), 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 try at a level: when it starts, when its painting is completed (and whether that is the first time), when the board runs out of space and when you leave a try with Retry, with the level, the try's number on that visit and how long the try took; and, the first time you play, how long your first move on the first level took. These records never include your score, the board itself or anything you type. We use these to understand use of the Game and fix problems. Our service also records when your account is created, linked to Google or Apple, and deleted. 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, records of when you first completed each level, 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, during a level, tap the pause button, choose Account, then Delete account, and hold Hold to delete for 2 seconds. The confirmation also has Delete on the web, which opens https://apzilon.com/delete-account/ in your browser; when no account is signed in on this device, it offers only that. Without a connection, the in-game deletion cannot finish and nothing is changed. This in-game request deletes your account on our service: this game's cloud save, its earlier versions and any save kept from a conflict, its gameplay records, error reports, daily activity totals, running totals, records of when you first completed each level 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 and its copy of the cloud save, replaces your progress on this device with a new game (your language, sound and music settings stay) and shows the message Account deleted. It then asks again how you want to play (on Android at once, on iPhone the next time you tap the title screen): Play as guest creates a new guest account, and you can also sign in with Google or Apple there. Without the Game, email [email protected], say Inkbound Archive and give the email address of the Google or Apple account you signed in with (for Sign in with Apple, the address Apple shared with us, which may be a private relay address). A linked account requires verification of that Google or Apple identity. Inkbound Archive shows no deletion code. In Android 1.0.0 (3) and later and iPhone 1.0.0 (3) and later, if you played as a guest, include the Player ID shown in Settings, under Account, so we can find the account; with an earlier build we cannot find a guest account from an email, so use the in-game steps above. 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/.

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 also replaces your progress with a new game (your language, sound and music settings stay) when it next reaches our service within 30 days of the deletion, and asks again how you want to play. In earlier builds, an installation of the Game that does not reach our service within those 30 days 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 (3) and later, an installation that first reaches our service after those 30 days treats the account as deleted the same way: it replaces your progress with a new game and uploads nothing, and a Google or Apple sign-in from that screen first asks whether to turn cloud saving back on. If the Game cannot read its record of the signed-in account at that moment, it can keep a copy of that account's progress (its local cloud-save records) on that installation as a backup file instead of deleting it; that file is never loaded or uploaded and can stay until you clear the Game's data or uninstall 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 (3) and later and iPhone 1.0.0 (3) and later, Settings, under Account, offers Sign out for an account signed in with Google or Apple, not for a guest; it is unavailable while a level is open (from the pause), and you can sign out from Settings on Home. The confirmation shows Cancel first, then Sign out. The Game sends any unsent save first; offline, or if that save cannot be sent, nothing changes and you stay signed in. Our service then ends this device's session, and the Game forgets the account on this device and starts a new game; your language, sound and music settings stay. 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. Our service creates a fresh empty guest before you choose again, and the Game returns to the choice of how to play. Signing in to the same account again loads its save. Sign out is not deletion.

Information stored on your device

The Game saves your progress (the level you reached, the paintings you finished, your best score, which chapter notes you have seen) and your settings (language, sound, music) in the app's own storage on your device. Your progress and your language, sound and music settings are also copied to our service as your cloud save, and the app keeps a copy of that cloud save on your device with any changes still waiting to be sent. If the copy on our service went as far as or further than the save on your device, it replaces that save. 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 (3) and later, the Game keeps one save for each of our service environments (test and live): when this phone moves to the other one, the save of the one it left is kept whole on this phone in a separate file and comes back when the phone returns; it is never uploaded to the other environment. Deleting your account does not remove a file kept for the other environment; clearing the app's data or uninstalling does.

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: it stays on our service with its cloud save until it is deleted, so if you no longer want it, delete it in the Game first. 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 Inkbound Archive 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 (in Settings, under Account) if your build shows it. 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