Apzilon

All Apzilon privacy policies

Drink Shop Privacy Policy

Developer: Apzilon
Effective date:

Drink Shop (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].

The Game's Licenses page has a button that opens the MiniMax H3 licence page on apzilon.com in your web browser. Your browser loads it as it would any website.

Information we collect

The Game connects to the Apzilon game service over the internet. The first time you tap to start, the Game asks how you want to play: on Android, Sign in with Google or Play as guest; on iPhone, Sign in with Apple, Sign in with Google (once the Game has reached our service) or Play as guest. 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). 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 once our service has created your account; 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 the Game cannot reach our service, it plays and saves on your device only. In Android 1.0.0 (5) and later and iPhone 1.0.0 (6) and later, progress the earlier offline version of the Game saved on your device is never uploaded (see Information stored on your device). Earlier builds must update before their cloud-save requests can proceed. 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 iPhone, or with Sign in with Apple on iPhone, or link it later, so that your account and the progress backed up to our service are tied to that sign-in. This is optional. If you sign in with it or link it, we receive and keep that service's account identifier and the profile it shares with us: your email address (only when the service says it is verified), whether it is verified, your name, the link to your profile picture (not the picture itself) and your language. Some of these may be missing.

On iPhone, Sign in with Google opens Google's own sign-in page in Apple's web sign-in window; the Game does not include Google's sign-in software. Google sends back a sign-in token with the details above, which the Game passes to our service. Neither the Game nor our service keeps any token from Google, and the Game keeps no Google email address or name on your iPhone.

If you use Sign in with Apple, Apple shares your name with us only the first time you sign in, and only if you choose to share it. The email address may be a private relay address from Apple that forwards to your own email; we also keep whether it is one. We also keep a token from Apple, encrypted, only so that we can ask Apple to revoke the Game's access to your Apple account. We ask when your sign-in link is deleted (see Deleting your account), and we delete the token once Apple confirms, or after 30 days of trying.

When the Game starts a new sign-in session with our service, we keep a record of it: the game, the platform, the app build, your language, your device model and operating system version, the country and region that our hosting provider works out from the connection, and when the session was last used. When a new session starts, we also log your IP address with its country, region and network provider, for security and fraud prevention only.

The Game also keeps your save on our service as a cloud save, with up to 3 earlier versions of it: the whole save the Game keeps on your device (listed under Information stored on your device), without your settings, which stay on your device. That includes your owner's name and your shop name exactly as you typed them (at most 12 and 16 characters), a short shop handle the Game makes from the shop name and, if you later change the names in Settings, also the names you had when you started the game. These names are only in your cloud save: other players never see them, and the Game puts them in no other record. The Game uploads your save each time it saves it on your device; while it cannot reach our service, the save waits on your device. When two saves from installations of the same account meet, the one that went further (a later new game, or in the same game a later day) 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. When the Game reaches our service, before and after you sign in, it can fetch our public news posts for this game. These requests send no account ID, sign-in token, installation ID or advertising ID; they carry the game, build, platform, language, kit protocol version, device model and operating system version. Our service writes no player record for these public reads.

The Game also sends us gameplay records and error reports: which screens and pop-up windows you open, in what order and how long you stay on each (screen_view), the first time you open the Game (first_open), and when each play session starts and ends and how long it lasts (session_start, session_end). It also sends when each shop day starts and when it is counted, with the day, the number of the game you are playing and how long the day took; your first perfect pour; each item you buy with coins, with its coin price, and each recipe you unlock; and each change to the language, music, effects or sound setting, with the old and the new value. 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 owner's or shop name, 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 that 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, tap the gear on the title screen or at the cart to open Settings, choose Account, then Delete account, and hold Hold for 2 seconds to delete; letting go early cancels. The Delete account screen also has Delete on the web, which opens https://apzilon.com/delete-account/ in your browser, and for a guest account it shows this installation's Deletion code. 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 (screens, sessions, shop days, purchases with coins and setting changes), error reports, daily activity totals, running totals, first-clear records and record receipts leave our active database at once, the device details and security IP log of its sessions are cleared, and any link to your Google or Apple sign-in, with the profile that service shared, is removed. If you signed in with Apple, our service then also asks Apple to revoke the Game's access to your Apple account. It does not delete other Apzilon games. The Game then forgets the account on this device with its unsent records, deletes your progress and every copy of it from this device (your language, music and effects settings stay) and goes back to the title screen as on a first launch. In Android 1.0.0 (5) and later and iPhone 1.0.0 (6) and later, saves the Game set aside earlier on this device, including this account's own from a sign-out, stay (see Information stored on your device). The next time you tap to start, it asks again how you want to play; Play as guest then creates a new guest account and a new game. In Android 0.2.0 (4) and earlier, if the Game cannot remove a save file, progress still on this device can be uploaded as the new account's first save. Without the Game, email [email protected], say Drink Shop and give the email address of the Google or Apple account you signed in with (for Sign in with Apple, the address Apple shared with us, which may be a private relay address), or say that you played as a guest. A linked account requires verification of that Google or Apple identity; a deletion code alone cannot authorize its deletion. For a guest, include the Deletion code from the Delete account screen, which identifies the installation. We must verify ownership and the deletion scope before carrying out an external request. See the retention periods above and the full request steps at https://apzilon.com/delete-account/.

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, Android 1.0.0 (5) and later and iPhone 1.0.0 (6) and later treat the account as deleted when this installation next reaches our service, whether within 30 days of the deletion or after those 30 days. The Game forgets the account on this device, turns cloud saving off and removes its local cloud-save records and unsent gameplay records and error reports. It also deletes your progress and every copy of it from this device (your language, music and effects settings stay), forgets your saved choice of how to play and the album's seen marks, and returns to the title screen as on a first launch, without a deletion message. Saves the Game set aside earlier on this device stay (see Information stored on your device). After recognizing the deletion, it starts no new guest account by itself and uploads nothing until you choose to play again. The next time you tap to start, it asks again how you want to play, as on a first launch. If you then choose Sign in with Google or Apple, the Game first tells you that this account's cloud save was deleted elsewhere, and it signs in and turns cloud saving back on only if you choose Continue. If its saved account record on this device is missing or unreadable, the Game still treats the account as deleted and uploads nothing. If that happens after those 30 days, the Game moves the old progress aside on this device instead of deleting it: it is never loaded or uploaded, and it stays there until you clear the Game's data or uninstall it. In Android 0.2.0 (4) and earlier online builds, an installation that reaches our service within 30 days of the deletion also deletes your progress from this device and returns to the title screen. Play as guest then creates a new guest account and a new game. You can then link that guest account to Google in Settings > Account. If the Game cannot remove a save file in those Android builds, progress still on this device can be uploaded as the new account's first save. An installation of those Android builds that first reaches our service after those 30 days 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.

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 (6) and later, Settings, under Account, offers Sign out for an account signed in with or linked to Google or Apple, not for a guest; it works when you open Settings from the gear on the title screen and is off when you open it during play. The confirmation names Google or Apple with your Player ID, never your email or the account ID. 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. Nothing changes either while the save on this phone is one the Game does not upload to that account, such as progress from the earlier offline version. 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, makes a new sign-in key for it, forgets your saved choice of how to play and the album's seen marks and starts a new game; your language, music and effects 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. The save you were playing is moved into a separate folder on this phone, or removed if it cannot be moved, and is never loaded or uploaded again (see Information stored on your device). Queued gameplay records stay with that account on the phone and can be sent when it returns; the next account starts a separate records session. Our service creates a fresh empty guest before you choose again, and the Game returns to the title screen; the next time you tap to start, it asks again how you want 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 (season day, coins, stock, upgrades, regular customers and their stories, decorations, recipes, missions and followers, your owner's look, name and shop name) and your settings (language, music and sound effects) in the app's own storage on your device, along with how you chose to play and which album pictures you have seen. Your progress, with your owner's name and shop name, is also copied to our service as your cloud save; your settings stay on your device. The app also keeps a copy of that cloud save on your device with any changes still waiting to be sent. A cloud save that went further than the save on your device replaces it; one that is behind never does. If a cloud save comes from a newer version of the Game that this version cannot load, the Game keeps it on your device, unloaded (at most 3 such copies), and stops uploading until you update. In Android 1.0.0 (5) and later and iPhone 1.0.0 (6) 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 out, or sign in to or link an account other than the one the save belongs to, the Game moves the save whole, with any copies kept from a newer version of the Game, into a separate folder in the same storage; after a sign-in it then loads that account's save, or starts a new game if the account has none. A save this version finds on the device that no account holds, such as one from the earlier offline version of the Game, stays playable on this device but is never uploaded; it is moved into that folder too when an account's save is loaded in its place. Progress you make at an offline first launch, before your first account exists, becomes the first guest account's save; progress made after you delete your account, before the next account exists, is moved into that folder. The Game never loads, uploads or offers a save from that folder, and it keeps them there until you clear the Game's data or uninstall it; deleting your account does not remove them. 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.

The Game may also keep a recovery copy of your save data in the same app storage. This copy is not a cloud backup.

Clearing the app's data or uninstalling the Game removes only the copy on your device. On Android, if you have not linked a sign-in account, you cannot get that guest account back afterwards. On iPhone, the installation ID, sign-in key and session token are kept in the iPhone's Keychain: deleting the Game does not remove them, so if you install it again on the same iPhone, the Game is designed to come back to the same account. They stay on that iPhone only: they are not synced to iCloud Keychain and never restored to another device. To delete the data on our service, see Deleting your account.

App permissions

The Game asks Android for these permissions:

Internet access (INTERNET): to connect to our service.

Biometric and fingerprint (USE_BIOMETRIC, USE_FINGERPRINT): come with Android's sign-in system (Credential Manager), which Google sign-in uses. Android may use them when it asks you to confirm with your fingerprint or face. The Game never receives your fingerprint or face data.

One permission the Game declares for itself (DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION), which Android uses to keep the Game's internal messages private.

None of these give the Game access to your camera, microphone, contacts, location or files. On iPhone, the Game asks for no permissions: not for your camera, microphone, photos, contacts or location, and not to track you.

System backup

The Game turns off Android's automatic backup, so the save on your device is not backed up to your Google account. Your progress is backed up to our service instead. On iPhone, your sign-in details stay on that iPhone, and your progress is backed up to our service.

Google Play

Google Play may collect information when you download or use apps, under Google's own privacy policy, which we do not control. The statistics we see in Google Play Console are aggregated and do not identify you.

App Store

Apple's App Store and TestFlight may collect information when you download, test or use apps, under Apple's own privacy policy, which we do not control. Apart from what TestFlight shows us about testers (see Testers, support and contacting us), the statistics we see in App Store Connect are aggregated and do not identify you.

Children

The Game is intended for players aged 13 and over. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has given us personal information, contact us and we will delete it.

Testers, support and contacting us

If you send us your email address to join a test of a game, we use it only to add you to the tester list on Google Play or Apple TestFlight and to contact you about the test.

If you test the Game through TestFlight, Apple shows us the tester details TestFlight shares with developers (such as your name and email address if we invited you by email, your device and app version, and how many sessions and crashes you had) and crash reports, along with any feedback and screenshots you send through TestFlight. We use them only to run the test and fix the Game.

If you send us feedback or a support request, we use your message only to reply and to improve the game. We never sell or share it, and you can ask us to delete it at any time (see Contact below).

Your rights under Thailand's Personal Data Protection Act B.E. 2562 (PDPA)

Under Thailand's Personal Data Protection Act B.E. 2562 (PDPA), you can ask to see or get a copy of your personal data, to have it corrected or deleted, to restrict or object to how we use it, and to withdraw consent you gave. Email [email protected], say Drink Shop and the email address of the Google or Apple account you signed in with, or tell us you played as a guest and include your Player ID from Settings or the Deletion code from the Game's Delete account screen. We need to identify your account and verify that it is yours. You can also complain to Thailand's Personal Data Protection Committee.

Changes to this policy

If we change what a game collects or how we use it, we update that game's page before the change takes effect and show the new effective date.

Contact