Witch Apothecary Privacy Policy
Developer: Apzilon
Effective date:
Witch Apothecary (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. The Game creates this guest account when you choose Play as Guest. If the first launch is offline, your progress is saved only on your device; the next time you open the Game while it is connected, it asks again how you want to play. In earlier online builds, your save goes to the account you then choose, unless that account already has a save that went as far or further, which then replaces the one on your device. In Android 1.0.0 (5) and later and iPhone 1.0.0 (9) and later, a run with no recorded owner can be uploaded only as the first save of this device's own guest account when that guest has no cloud save. It is never uploaded to a Google or Apple account: the Game loads that account's save, or starts a new game for it if it has none. A replaced run with no owner is kept only on this phone, as described below. In Settings, Account shows your 9-digit Player ID, for guest, Google and Apple accounts alike. It is not a password, and it is not the deletion code described under Deleting your account.
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. 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, Sign in with Google or Play as guest. A guest can link Google later in Settings, under Account; on iPhone, a guest can also use Sign in with Apple there. 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 back up your profile to our service, with up to 3 earlier versions of each part of the save. Sign in with Google, or Apple on iPhone, to get it back after you reinstall the Game. It includes your chosen player name and appearances, school and exam progress, garden, brewing and recipes, quests, shop, decorations, in-game items and currencies, day and room position, earlier puzzle progress and play counters. Sound, music, vibration and language settings stay on your device. The save also includes a progress summary: exams passed, days played and potions brewed. 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. Give Witch Apothecary and the Player ID shown in Settings > Account so support can find the account. 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. In Android 1.0.0 (5) and later and iPhone 1.0.0 (9) and later, the Game loads and shows the save our service chooses. The previous guest's cloud-save journal and a local backup of the replaced run can remain on this phone, separate from the signed-in account; they are not uploaded over its save. A run that has never had an owner follows the device-only rules above, instead of being uploaded to a login account. When two saves from installations of the same account meet, the one that went further is kept whole; if they are equal or a progress score is missing, the save already on our service is kept. You never have to choose. In Android 1.0.0 (5) and later and iPhone 1.0.0 (9) and later, switching from one signed-in account to another loads the new account's own save, or starts a new game for it if it has none. The previous account keeps its progress on our service; the Game does not upload one account's run into another account. When the Game reaches our service, before and after you sign in, it can fetch our public news posts for this game. These requests send no account ID, sign-in token, installation ID or advertising ID; they carry the game, build, platform, language, kit protocol version, device model and operating system version. Our service writes no player record for these public reads.
The name you choose in the Game is saved with your progress, so it is also part of your cloud save.
The Game also sends us gameplay records and error reports: which screens and pop-up windows you open, in what order and how long you stay on each (screen_view), the first time you open the Game (first_open), and when each play session starts and ends and how long it lasts (session_start, session_end). It also sends when you pass an exam (stage_clear), with the exam, whether it is your first pass of it and, when they rose, its stars; each upgrade or garden plot you buy (upgrade), with what it is, the level before and after and its price in coins or copper; each story quest you finish (tutorial_step), with its step and order; and each change of the language, sound or music setting (settings_change), with the old and new value. We use these to understand use of the Game and fix problems. Our service also records account creation, sign-ins, linking and deletion. An error report holds a fixed message, the part of the Game's code where the error happened and the app build, at most 20 per session. Each record is linked to your account and the game; the ones the Game sends also carry a random installation ID, event and session IDs, the time and order of the event, your device model, operating system and language, and our service adds the app build, platform and your country. They never include your email address, your IP address or your advertising ID.
The Game sends gameplay records and error reports from an iPhone too. The Game itself has no crash reporting: it sends no crash logs.
The Game has no advertising, in-app purchases or analytics and tracking software from other companies. Our service never receives your device's advertising ID, and the Game never asks for your phone number, contacts or location. On iPhone, it has none at all, and it never asks to track you across other companies' apps and websites.
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, first-clear records, 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, in a school room, tap the gear at the top right, below the day counter, to open Settings, choose Account, then Delete account and hold Hold to delete for 2 seconds. The in-game request is limited to this game; the whole account is deleted with it only when no other Apzilon game still uses your account. Deletion removes this game's cloud saves, progress, gameplay records, daily activity totals, running totals, first-clear records and record receipts from our active database, clears its session device details and security IP log, and ends its sessions. The Game then starts a new game on this device and asks again 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; cloud saving stays off until you choose. In earlier online builds, Sign out, on the same Account page for Google and Apple accounts, is not deletion: the Game first uploads any save still waiting, then signs you out, creates a new guest account and starts a new game on this device. Your Google or Apple account keeps its progress, and signing in with it again brings that progress back. To request deletion without the Game, email [email protected], say Witch Apothecary and give the email address of the Google account you linked, or of the Apple account you signed in with on iPhone (the address Apple shared with us, which may be a private relay address), or say that you played as a guest. For a guest account, include the deletion code that the Delete account popup shows to guests, if you have it. It identifies the installation and is not the Player ID. We need to identify your account and verify that it is yours before acting. A Google- or Apple-linked request requires verification of that Google or Apple identity; a Player ID or deletion code alone cannot authorize it. Guest requests made outside the Game require verification of the account and the deletion scope before they can be carried out. Your sign-in link and provider profile are removed when no other game needs them, or when you request deletion of 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. The retention periods above explain what remains. Clearing app data or uninstalling alone does not delete the account on our service. Full request steps: https://apzilon.com/delete-account/.
If your account is deleted another way, after an email request or in another installation of the Game, 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, turns cloud saving off, replaces your progress and player name with a new game, removes the local backup copies of that progress, its local cloud-save records and unsent gameplay records and error reports, and returns to the title screen. 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. Your language, sound, music and vibration settings stay. The Game does not start a new account by itself or upload the deleted account's progress or queued records. The title screen asks again how you want to play: Sign in with Google or Play as guest on Android; Sign in with Apple, Sign in with Google or Play as guest on iPhone. If you choose Play as guest, a new guest account starts with the new game, both before closing the Game and after reopening it. On iPhone, versions before 1.0.0 (8) instead start a new guest account by themselves when they first reach our service after those 30 days, and keep the progress still on them only on that device, without uploading it. In Android 1.0.0 (11) and later and iPhone 1.0.0 (15) and later, after those 30 days the Game treats our service's answer as a deletion only when its record on this device of which account its sign-in key opened names the deleted account. Otherwise, such as when that record is missing or cannot be read, it instead starts a new guest account by itself, and the deleted account's progress, cloud-save journal, local recovery copies and the unsent usage records already queued for that account stay on this phone, separate from the new account, with no automatic expiry; none of them is uploaded. Usage records queued while the Game had not yet reached our service, such as during offline play, are sent with the new guest account. In Android 1.0.0 (5) and later and iPhone 1.0.0 (9) and later, after a deletion in the Game or elsewhere, the title screen's choice sheet says cloud saving is paused. Choosing Google, or Apple on iPhone, there signs in directly without first making a guest; after a deletion elsewhere, only a choice from the sheet showing that notice consents to turn cloud saving back on. The old local run is cleared before this can happen; if it cannot be cleared, cloud saving stays paused. Cancelling or failing sign-in leaves it paused, and retries, timers and late answers cannot turn it back on by themselves. Parked files belonging to the deleted owner in the current service environment are also removed. If local account records cannot be read, cloud-save recovery files may remain on this phone, as described under Information stored on your device. In Android 1.0.0 (7) and later and iPhone 1.0.0 (11) and later, if by the time this device next reaches our service the game has been started again on the same account after such a deletion, the Game keeps the account instead: the progress this device had from before goes into a dated file on this phone, as described under Information stored on your device, and is never uploaded into the account; the Game loads the account's new save, or a new game if it has none, and if this device had progress, it says "This account's progress was reset elsewhere. This device now shows 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 (5) and later and iPhone 1.0.0 (9) and later, Sign out is in Settings > Account, reached from the gear in a school room, and is shown only for Google or Apple accounts. In Android 1.0.0 (5) and iPhone 1.0.0 (9), tapping Sign out signs out with no second confirmation sheet. In Android 1.0.0 (6) and later and iPhone 1.0.0 (10) and later, a confirmation shows Cancel first, then Sign out, and Sign out is unavailable while a board attempt is open. It is unavailable while an account action is busy or cloud saving is paused, and refused offline or if the waiting save cannot be sent, including a save whose upload is held. The Game sends that save first, then asks our service to end this sign-in session. After the service confirms sign-out, the Game clears the session token and cached account details and replaces the secret sign-in key. On Android, it also asks Google's sign-in software to clear its local sign-in state so the next sign-in can show the account chooser; a failure to clear that state does not undo sign-out. The signed-out account's cloud-save journal, local recovery copies and unsent usage records stay on this phone, separate from the next account, and are used only for their own account if you sign in again. In Android 1.0.0 (7) and later and iPhone 1.0.0 (11) and later, a separate copy of the active run is made for Sign out only when the Game cannot confirm the run is already in the account's cloud save, as described under Information stored on your device; in earlier versions, none is made just for Sign out. The active run and its backup are replaced by a new game; your settings and installation ID stay. Leaving the account starts a new play-session ID; queued records keep the IDs they were made with. A fresh guest account is created before you choose again. The Game returns to the title screen and asks how you want to play. Your signed-out account and its progress stay on our service, and signing in with it again brings its progress back under the save rules above. Sign out is not deletion.
Information stored on your device
The Game saves your chosen player name and character and cat appearances, school and exam progress, garden, brewing and recipes, quests, shop, decorations, in-game items and currencies, day and room position, earlier puzzle progress and play counters, plus your sound, music, vibration and language settings in the app's own storage. Your profile is also copied to our service as a cloud save. The app keeps its installation ID, sign-in key, session token and account details on your device, and queues screen, session and error records until they can be sent. 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. In Android 1.0.0 (5) and later and iPhone 1.0.0 (9) and later, the Game keeps separate saves for the test and live service environments. When the phone moves to another environment, the previous environment's run and its backup stay in separate files on this phone, and can return when the phone returns to that environment; they are never uploaded to the other environment. In Android 1.0.0 (7) and later and iPhone 1.0.0 (11) and later, this also holds for a run with no recorded owner once the Game has recorded its environment; in earlier versions, it holds only for a run with a recorded owner. In Android 1.0.0 (7) and later and iPhone 1.0.0 (11) and later, when the environment of a run with no recorded owner that holds progress cannot be written into the save, or cloud saving is off, the Game keeps it in a small file beside the save that holds only that environment and a hash identifying the run, no progress; this file is never uploaded, is removed when a later try writes the environment into the save, and otherwise can stay on this phone, even after account deletion. A run with no recorded owner that an account's copy replaces is kept in a separate dated file on this phone, never uploaded, with no in-game way to restore it. In Android 1.0.0 (7) and later and iPhone 1.0.0 (11) and later, such dated files also keep a run with progress that a Sign out would replace when the Game cannot confirm the run is already in the signed-out account's cloud save, such as play after a Sign out that the Game could finish only at a later launch, and the progress this phone had from before when your account's progress was reset elsewhere, as described under Deleting your account. In Android 1.0.0 (14) and later and iPhone 1.0.0 (18) and later, such dated files also keep your account's progress that was still waiting to be saved or that the Game could not add to its cloud-save journal, such as play in the last moment before an answer from our service, when the Game replaces it with another save, for example one that went further in another installation of the Game, or another account's save. These dated files have no automatic expiry. In Android 1.0.0 (7) and later and iPhone 1.0.0 (11) and later, deleting an account in the Game, or learning that it was deleted elsewhere even when the local account record cannot be read, removes every one of these dated files on this phone, except when the game has already been started again on the same account after a deletion elsewhere (see Deleting your account). If one cannot be removed, cloud saving stays off while it remains: the Game tries again each time it starts and at each title screen choice that would turn cloud saving back on. In earlier versions, account deletion does not remove them. The first sign-in can also set aside an unbound autosave as a local recovery copy instead of uploading it. Local cloud-save recovery copies are normally removed after 30 days when that account's save is used and the service supplies a time; a copy that is no longer used can stay longer. Deleting an account in the Game, or learning that it was deleted elsewhere with its local account record readable, removes that account's cloud-save journal and recovery copies and its parked files in the current environment. Other owners' files and other environments' files stay. If the local account record cannot be read when a deletion elsewhere is detected, the old journal can instead be set aside as a local recovery copy that is never uploaded and can remain without expiry. Clearing app data or uninstalling removes the remaining app files; the iPhone system backups described above may still hold copies.
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.
In Android 1.0.0 (12) and later, the Game also asks for Vibration (VIBRATE), which lets it vibrate your device as feedback while you play. You can turn it off in the Game's Settings > Vibration.
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, have it corrected or deleted, restrict or object to its use, and withdraw consent you gave. Email [email protected], name Witch Apothecary and tell us how you signed in. We need to identify your account and verify ownership. 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]