Tidebreak Privacy Policy
Developer: Apzilon
Effective date:
Tidebreak (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 to start, the Game asks how you want to play: with Google on Android, with Apple on iPhone (and with Google too, once the Game has reached our service), or as a guest (Play as Guest). Nothing is created on our service until you choose, and a sign-in that cannot reach our service creates nothing there. 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 continue 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). Then you name your captain, unless your account already has one. 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, the Guest row (Linked once you link a sign-in) opens Link account, which shows your Player ID with a Copy button; 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 choose Play as Guest while the Game cannot reach our service, it plays and saves on your device only, and the guest account is created once the Game connects. If you already started playing in an earlier version of the Game on this device, it does not ask: the first time it reaches our service, it creates a guest account for you and uploads the progress saved on your device. 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 each part of it: everything the Game saves on your device (listed under Information stored on your device), with a short summary (your best result and voyages played) and the installation ID of the device that saved it. The Game uploads your save each time it saves, for example during and at the end of a voyage, and your language each time it changes; while the Game cannot reach our service, they wait on your device. When two saves from installations of the same account meet, the one with more voyages played 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 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 you open (the title screen, the harbour, a voyage, its result, Settings, the account screens that ask how you want to play, link a sign-in and delete 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 when you choose how to play and when you name your captain (the two steps, never the name), and the end of each voyage: whether you won or lost and how many voyages you have played. 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 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.
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, on the harbour screen, tap the gear at the top right to open Settings, choose Delete account, then hold Hold for 2 seconds to delete. The Delete account screen also shows this installation's Deletion code, for the delete-account web page, and a button that opens https://apzilon.com/delete-account/ in your browser. 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, the first-launch steps and voyages), error reports, daily activity totals, running totals, the record of when you first won a voyage 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 captain name from this device (your language setting stays) and goes back to the title screen with the first-launch choice; cloud saving stays off until you choose, and your deleted account does not come back. Without the Game, email [email protected], say Tidebreak and give the email address of the Google account you signed in with on Android 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, for a guest, your Player ID and the Deletion code from the Delete account screen. A linked account requires verification of that Google or Apple identity; a deletion code 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/. Link account also shows Unlink for a linked sign-in; our service removes a sign-in only while your account has another sign-in to open it with, so the only sign-in of an account stays until you delete the account.
A deletion made another way, after an email request or in another installation of the Game, does not delete the progress saved in the Game's other installations. When one of those installations next reaches our service, within 30 days of the deletion or later, it treats the account as deleted: it forgets the account on that device, turns cloud saving off, removes its local cloud-save records and unsent gameplay records, and uploads nothing; your progress and language setting stay on the device. 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 that device 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. In earlier builds, if you then choose Start as Guest there, in Settings under Delete account, before closing the Game, the new guest account starts a new game in place of that progress; if you close and reopen the Game first, the progress kept on that device is uploaded as the new guest account's save. In Android 1.0.0 (10) and later and iPhone 1.0.0 (6) and later, Delete account there offers New cloud save from this phone instead, with a line saying that the progress on this phone goes into it: choosing it turns cloud saving back on and uploads the progress kept on that device as the save it starts, whether or not you closed the Game first. To keep old progress out of a new account, 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 (10) and later and iPhone 1.0.0 (6) and later, Settings offers Sign out for an account signed in with or linked to Google or Apple, not for a guest; it is off while a duel is in progress or left unfinished. Its row shows 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. 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 and starts a new game; your language setting stays. The signed-out account keeps its progress on our service, and its copy on this phone is kept only for that account and never uploaded to another one. Queued gameplay records stay with that account on the phone and can be sent when it returns; the next account starts a separate records session. 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 (cards collected, best result, voyages played, a duel you left unfinished and whether you have finished the first-launch steps), the captain name you choose and your settings (language) in the app's own storage on your device. This save is 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. A cloud copy with as many voyages played as the save on your device or more replaces that save, and so does the save of an account you switch this device to; a copy that is behind never does. 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 (10) and later and iPhone 1.0.0 (6) 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. The save also names the account it belongs to: a save of another account found on this device, for example after a sign-out that was interrupted, is kept aside whole in a separate file and is never uploaded or loaded again. So is progress made on this device before any sign-in, for example at an offline first launch or after your account was deleted, when the account you then sign in to already has a save for this game: that account's save loads instead. An account with no save for this game takes that progress as its first save. Deleting your account does not remove a file kept for the other environment or a save kept aside; 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. 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 Tidebreak 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 Link account 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
Apzilon | [email protected]