1. Overview and the current state of the website
This policy applies to the InfinityX Mobile website and to the services that will open through it. It sets out how personal data is collected, used and disclosed, as Thailand's Personal Data Protection Act B.E. 2562 (2019) requires.
In this policy, “we” means the operator of the InfinityX Mobile website and “you” means visitors to the website and players.
- The website has general content pages, such as the home page, news, the guide and the player ranking, and a registration page, a login page and a member area.
- The registration and login forms really work. What you type is sent to the website's server. Registration confirms your email address with a 6-digit code that we send to it, and no email the website sends contains a link.
- Registration also creates your game account, with the same username and password as your website account.
- Once logged in, you can change your password and your email address yourself in the member area. If you forget your password, you can set a new one from the login page. Every account must set a 6-digit transaction PIN.
- For now, accounts are open only for testing with invited people. Registration is not yet open to the public.
- There is no pre-registration and no top-up through the website yet, and the member area does not show characters or a Cash balance from the game yet.
- The website uses no visitor analytics, advertising or third-party tracking scripts. Every file that makes up the pages is served by this website itself.
The parts about pre-registration, top-up and game data in the member area take effect when each of those services actually opens. We will update this policy to match how each service really works before it opens.
2. Data controller
The data controller is the operator of the InfinityX Mobile website and server, which decides how personal data on this website is collected, used and disclosed (called “we” in this policy).
The data controller's name, address and contact channels have not been published yet. They will be published on this page before the website is opened to the public. Until then, accounts are open only for testing with invited people, and registration will not open to the public before those details are published.
3. What we collect at each step
We collect only what each service needs. The table below is arranged by the step you are using.
| Step | Data | Status |
|---|---|---|
| Visiting the website | Your language choice and display settings kept in your own browser (see the cookies section), and the technical data your browser sends when it requests a page, such as IP address, browser type, and date and time, which the server or the hosting provider may record in access logs | In use today |
| Asking for a registration code | The email address you enter, the language of the page you used, the date and time of the request, your IP address, and the versions of the Terms of Service and the Privacy Policy you accepted, with the date and time you accepted them. We send a 6-digit code to that address or, if the address already has an account, a notice instead of a code | In use today |
| 6-digit codes sent by email | Used for registration, for setting a new password when you forget it, for changing your email address and for setting a new PIN when you forget it. Each code is kept only as a hash computed with a secret key (HMAC), never as the code itself. Kept with it are the number of entries, the date and time it was issued and when it expires, the IP address of the request, the language, and what the code belongs to: the address being registered, or your account (for an email change, also the new address). A code works for 10 minutes and once, takes at most 5 entries, and a new code replaces the old one at once. When you enter a registration or password reset code correctly, the page receives a value for the next step, which works for 15 minutes and once. We keep that value only as a hash, with the same details as the code | In use today |
| Account | Email address, username, password (kept only as a hash that cannot be turned back into the password, never as readable text), the date and time your email was confirmed and the account was created, when the password was last changed, your language, the account's status, the document versions you accepted with the date and time, and the number of your game account | In use today |
| Creating your game account (at registration) | At the last step of registration, the website sends your username, password and email address to the game server's database, which is the game's own database on the game server's host, to create a game account with the same username and password as your website account. The game database stores the username, the password in the game server's own hashed format, the email address, and a random reference value that the website uses to confirm that the account was created. The website keeps the game account's number and the same reference value with your account. When you change your password or your email address on the website, the game database is updated to match. No other data of your website account, the PIN included, is stored in the game database | In use today |
| Logging in and using the member area | A login session record: the date and time you logged in, the date and time of last use, your IP address and your browser's identification (user agent); and records of successful logins, failed logins and logouts, with date and time, IP address and browser identification | In use today |
| Changing or forgetting your password | A password change in the member area needs your current password and your PIN. Forgot password uses the username or email address you type and a 6-digit code we send to the account's email address. Either way, the new password is set on the website and in your game account, the account's login sessions on other devices end (after setting a new password because you forgot it, every session ends), and we email you a notice that the password was changed | In use today |
| Changing your email address | Starting an email change needs your current password and your PIN. The request keeps your account, your current address, the new address, the language, the state of the request, the dates and times, and the IP address at the start, and lasts at most 60 minutes. You enter a 6-digit code sent to your current address, then one sent to the new address. The email to your current address names your username and shows the new address partly hidden. If another account already uses the new address, that address gets a notice instead of a code. After a completed change, the account keeps the new address, the number of completed changes and the time of the last one, which set the waiting time before the next change (7 days after the first change, 14 days after the second, and 30 days after the third and every later one). The old address gets a notice of the change, every other login session of the account ends, and the email address in your game account changes to the new one as well | In use today |
| Transaction PIN | Every account must set a 6-digit PIN, which confirms password changes, email changes and other transactions that open later. Setting the first PIN needs your current password. The PIN is kept only as a hash, never as readable digits. Kept with it are the dates and times it was set and changed, the number of wrong entries and whether it is locked. The PIN is separate from your password and is not sent to the game. After 5 wrong entries the PIN locks for 15 minutes the first time, 1 hour the second time, and 24 hours from the third time on. If you forget your PIN, you can set a new one with your current password and a 6-digit code we send to the account's email address. We email you when a PIN is set, changed or locked | In use today |
| Account event records | Records of registration, creation of the game account, password changes and new passwords, each step of an email change, setting, changing, locking and resetting the PIN, emails sent about the account, and each time a team member opens the account in the staff tool. Each record has the date and time, IP address, browser identification and a request number. Email addresses appear in these records only as hashes computed with a secret key, and no password, PIN or 6-digit code is ever in them | In use today |
| Protection against abuse | Counters of requests, kept as hashes computed with a secret key from an IP address, an email address, a username or the account, not as the values themselves, and security records of refused requests (date and time, IP address and browser identification). Before a form is sent, your browser works out a short puzzle that slows down automated mass requests. The puzzle uses and sends no personal data | In use today |
| Player ranking | The character name, class, nation, level and guild of the characters at the top of each board, with that board's figures: combat power (CP), the Alz a character holds, time spent online and whether the character is online now, war points and kills. The guild board shows the guild's name, its master, its number of members and its points. The website reads these from the game database from time to time and shows them to every visitor. The page shows no username, email address or other website account data | In use today |
| Game account UID on the profile page | The 16-digit UID of your game account. The website reads it from the game database when you open your own profile page and shows it to the account's owner only. The website keeps no copy of the UID in its own database and does not write it to its logs. | In use today |
| Item shop | What you put into the cart (the item, the chosen option and the quantity), your orders (the order number, the items, quantities, prices, the date and time, and the delivery status) and the history of your account's Point, Token and Coin balance changes. These are kept with your account in the website's database, not in your browser, and are shown to the account's owner only | The cart is in use today; buying is not open yet |
| Pre-registration | The email address you pre-register with, and the date and time of pre-registration | Not open yet |
| Top-up | Top-up records such as the reference number, the amount of Point, the date and time, and the payment result received from the payment provider | Not open yet; no payment provider has been chosen |
| Contacting the team | What you give us when you contact us, such as a way to reply to you and the details of your request | Contact channel not open yet |
| Game data in the member area | Game account data that the member area will display, such as character names, levels, last played date and Cash balance | Not open yet |
An email address, a username, a password and a PIN are needed to create and use an account. If you do not provide them, we cannot open an account for you, or you cannot use the member area, but you can still read the home page and the news without giving us anything.
We do not ask for sensitive personal data such as race, religion, political opinions, health data, criminal records or biometric data. Please do not send us data of this kind.
Apart from your game account's number, your game account's UID shown on your own profile page, and the character data on the ranking page, which the website reads from our own game database, we do not currently receive personal data about you from any other source. When top-up opens, we will receive the payment result from the payment provider so that Point can be added to your account.
4. Purposes and lawful bases
We use data only for the purposes listed in this table. If we want to use it for a new purpose, we will tell you first and ask for your consent where the law requires it.
| Data category | Purpose | Lawful basis |
|---|---|---|
| Technical data from your visit (IP address, browser type, date and time) | Delivering pages to you, keeping the website running, and detecting and preventing attacks or abnormal use | Our legitimate interests |
| Language and display settings in your browser | Remembering the language you chose and displaying pages properly | Our legitimate interests (needed for the website to work) |
| Email address used to ask for a registration code | Sending the code to continue registration, or telling the owner of the address that someone tried to register with an address that already has an account | Steps taken at your request before entering a contract, and our legitimate interests in protecting existing accounts |
| 6-digit codes and the value for the next step | Confirming that you can really read the email address before registering, setting a new password, changing your email address or setting a new PIN | Steps taken at your request before entering a contract, or performance of a contract, depending on the case |
| Pre-registration email address (when open) | Recording your pre-registration and sending rewards to the pre-registered account when the server opens | Performance of a contract, or steps taken at your request before entering one |
| Account data: email address, username, password | Creating and maintaining your account, verifying your email, letting you log in, and telling you about important account matters | Performance of a contract |
| Data sent to the game database: username, password, email address | Creating a game account with the same username and password as your website account, and keeping the password and email address in the game the same as on the website when you change them | Performance of a contract |
| Email change requests, the number of changes and the time of the last one | Changing your email address only after both the current and the new address have confirmed it, and setting the waiting time between changes, so that nobody else can take over your account | Performance of a contract, and our legitimate interests and yours |
| Transaction PIN (as a hash), wrong entries and lock state | Confirming that a password change, an email change or another transaction really comes from you, even if someone else has obtained your login session | Performance of a contract, and our legitimate interests and yours |
| The document versions you accepted, and the date and time | Keeping a record of which version of the Terms of Service you accepted and which version of the Privacy Policy you were shown | Performance of a contract, and our legitimate interests |
| Session and login records: date and time, IP address, browser identification | Keeping you logged in, keeping your account secure, preventing unauthorised access and fraud, and showing you the history so you can check it yourself | Performance of a contract, and our legitimate interests and yours |
| Account event records | Checking afterwards what happened to an account, detecting and investigating unauthorised access, and checking how team members look at account data | Our legitimate interests and yours |
| Request counters and security records | Limiting password guessing, mass registration and use of the website to send unwanted email to other people, and investigating security incidents | Our legitimate interests |
| Account data that team members look at in the staff tool | Helping with account problems you report, and checking abnormal use or security incidents | Performance of a contract, and our legitimate interests |
| Character data on the ranking page | Showing the ranking of players and guilds in the game | Our legitimate interests in showing rankings, which are part of the game |
| Top-up records (when open) | Adding Point to your account, checking and resolving problems with a transaction, and keeping the records the law requires | Performance of a contract, and compliance with the law where a law requires the records to be kept |
| Game data shown on the member page (when open) | Showing the characters and Cash balance of your account | Performance of a contract |
| Data from contacting the team (when open) | Answering questions, solving problems and following up on your request | Performance of a contract or our legitimate interests, depending on the case |
| Email address for news and promotions (if offered in the future) | Sending news, events and promotions | Your consent, asked for separately and withdrawable at any time |
| Cookies or tools not needed for the website to work, such as visitor statistics (none today) | Measuring and improving how the website is used | Your consent, asked for before they are used |
Your email address is used for account matters only. We do not send news or advertising to it.
6. Who we disclose data to
We do not sell your personal data. We disclose it only as far as necessary, and only to the following categories of recipients.
- Any hosting and infrastructure providers used to run the website and the game server, which would process data on our instructions
- Google, as our email delivery provider (Gmail SMTP): when we send you a 6-digit code or a notice about your account, your email address and the content of that message pass through Google's systems
- Every visitor to the website, for the character and guild data shown on the player ranking only
- Payment providers, once top-up opens and the providers have been chosen
- Government authorities or courts, when the law requires it or a lawful order is issued
The game server's database is our own system, so sending it your username, password and email address to create and keep your game account is not a disclosure to anyone else.
When you set a password, whether at registration, when changing it or when setting a new one because you forgot it, our server checks with the Have I Been Pwned service whether that password has appeared in leaked data. It sends only the first five characters of a hash of the password and compares the answer on our own server. Your password, email address, username and IP address are not sent, so no personal data is disclosed to that service.
No payment provider has been chosen yet. We will complete the list of recipient categories on this page before the related service opens.
7. Transfers outside Thailand
The email we send you goes through Google's Gmail service, which processes data on servers outside Thailand. Your email address and the content of that message are therefore sent abroad. This transfer is necessary to carry out your own requests, such as registering, setting a new password, changing your email address or setting a new PIN, and to tell you about important matters concerning your account.
The password check with Have I Been Pwned is also a connection to a server outside Thailand, but no personal data is sent, as described under Who we disclose data to.
The hosting or payment providers we come to use may store or process data on servers located outside Thailand.
If personal data is sent abroad, we will follow the rules set by personal data protection law, for example by sending it to a destination with an adequate standard of data protection, or by putting in place appropriate safeguards that still let you exercise your rights.
The hosting and payment providers, and their destination countries, have not been decided yet. We will state them on this page once they are.
8. How long we keep data
We keep data only as long as the stated purposes need it, using the following criteria.
- Account data (including the game account number, the PIN hash, and the number and time of email changes, which set the waiting time before the next change) and the data the website sent to your game account: for as long as the account exists, and for a further period after it is closed as far as needed to settle disputes or comply with the law
- 6-digit codes: a code works for 10 minutes from the time it was sent, works once and takes at most 5 entries, and an older code stops working at once when a new one is requested. We keep only a hash of the code, not the code itself. A code that is withdrawn or replaced by a new one is deleted at once
- The value for the next step after a correct code: works for 15 minutes and once. We keep only its hash
- Expired codes and values for the next step, used or not, with the email address, IP address and other details kept with them, including the email addresses of registrations that were not finished: deleted by an automatic clean-up within 24 hours after they expire
- Email change requests: last at most 60 minutes from the start. Requests that have ended (completed, cancelled or replaced by a new request) and expired requests are deleted by the automatic clean-up within 24 hours
- Login sessions: deleted at once when you log out. An expired session stops working at once, and the automatic clean-up deletes its record within 24 hours after the session's maximum lifetime ends (7 days after you logged in, or 30 days with “Remember me”)
- Request counters used for protection against abuse: deleted by the automatic clean-up within 24 hours after a counter expires
- Login records, account event records and security records: up to 12 months. The procedure that deletes these records once they are 12 months old is not in place yet; we will put it in place before the first record reaches that age
- Pre-registration data (when open): until the pre-registration rewards have been delivered, or until the data becomes part of a member account
- Top-up records (when open): for the period that the relevant laws, such as tax and accounting law, require them to be kept
- Technical visit logs: for a short time, as far as needed for security and troubleshooting, unless a longer period is needed to investigate a security incident or required by law
- Data from contacting the team: until your request is resolved, and for a further period in case of follow-up
- Data used on the basis of consent: until you withdraw your consent
When the period ends or the data is no longer needed, we will delete it, destroy it or make it unable to identify you. The exact retention period for technical visit logs has not been set yet and will be stated on this page before the website is opened to the public; for services that are not open yet, it will be stated before the service opens.
9. Keeping data secure
We keep passwords as hashes made with the Argon2id algorithm together with a secret key that is stored apart from the database. We never keep a password as readable text, and the team cannot see your password through the website. The PIN is kept the same way. The 6-digit codes we email are kept as hashes computed with a secret key, and the codes of login sessions and the values for the next step are kept as hashes.
The game server's database keeps its own copy of your password, in the game server's own hashed format, which is not the method the website uses. Because the same password works on the website and in the game, please do not use it for any other service.
The login cookies are sent over an encrypted connection only. The system limits the number of attempts to log in, to register, to enter a 6-digit code and to enter a PIN, checks a new password against lists of leaked passwords, and records security events for review. A password change and an email change need both your current password and your PIN, and an email change must be confirmed with codes from both the current and the new address. Access to data is limited to the team members who need it. These are part of our technical and organisational security measures, meeting the minimum standards the law sets.
Within the team, only members with the GM, administrator or owner role can look at account data, in the team's staff tool, which needs a password and a code from an authenticator app to sign in. They can see the username, the full email address, the account's status, language and key dates, the document versions you accepted, password and email change details, the PIN's state (whether it is set and whether it is locked), the game account number, live sessions with their IP addresses and browser identification, and the account's recent event records. In this tool the team cannot see your password, your PIN or any 6-digit code. The tool only shows data and cannot change an account, and every search and every account opened in it is recorded.
Even so, no system is one hundred per cent secure. You can help protect your account by using a password you do not use on any other service, by not sharing your password, your PIN or a 6-digit code with anyone, and by logging out on a device you share with others.
If a personal data breach happens that puts people's rights and freedoms at risk, we will notify the Office of the Personal Data Protection Committee without delay and, where feasible, within 72 hours of becoming aware of it. If the risk is high, we will also notify you without delay, together with the remedial measures.
10. Your rights
As the owner of your personal data, you have the following rights, subject to the conditions set by law.
- Withdraw a consent you have given, at any time. Withdrawal does not affect lawful use of the data before that point.
- Access your data and receive a copy of it, and ask how we obtained any of your data that we collected without your consent.
- Receive your data in a machine-readable format, or ask us to send it to another data controller.
- Object to the collection, use or disclosure of your data, including objecting to direct marketing at any time.
- Ask us to delete or destroy your data, or to make it unable to identify you.
- Ask us to restrict the use of your data.
- Ask us to correct your data so that it is accurate, up to date, complete and not misleading.
- Complain to the expert committee under the Personal Data Protection Act, as described in the complaints section below.
You can exercise these rights through the contact channels given in the contact section. We will respond without delay and within 30 days of receiving your request. Before acting on it, we may ask for more information to confirm that the data is really yours.
In the member area you can change your email address and your password yourself, and see your account's recent login history. A change of email address or password on the website also changes it in your game account. The member area does not yet let you close your account or get a copy of your data by yourself; the team carries out these requests when it receives them from you.
In some cases we may be unable to do what you ask, for example when the law requires us to keep the data, or when doing so would affect the rights of other people. In that case we will tell you the reason.
If you withdraw consent or ask us to delete data that your account needs in order to work, we may be unable to keep providing that part of the service. We will tell you the consequences before we act.
11. Minors and parental consent
If you are a minor under Thai law, which generally means you have not yet reached the age of 20, please talk to your parent or guardian and obtain their consent before registering or giving us personal data, where the law requires that consent.
For a minor aged 10 or under, consent must always be given by the parent or guardian.
A parent or guardian may exercise the rights in this policy on a minor's behalf. If we find that we have collected a minor's data without the parental consent the law requires, we will delete it. A parent or guardian who believes their child has given us data without permission can tell us through the contact channels.
12. Changes to this policy
We will update this policy when the website opens a new service, when we change how data is used, or when the law changes. The latest version is always on this page, with its version number and the date of the last update at the top. When you register, we record with your account the version number you were shown.
If a change is significant, we will announce it on the website in advance. If a change needs your consent, we will ask for it before the change takes effect.
13. Complaining to the regulator
If you think we have used your data wrongly, we would appreciate the chance to put it right first if you contact us directly. You always have the right to complain to the regulator, and you do not need to contact us first.
You may complain to the expert committee under the Personal Data Protection Act, through the Office of the Personal Data Protection Committee (PDPC), in Thai สำนักงานคณะกรรมการคุ้มครองข้อมูลส่วนบุคคล (สคส.). Its complaint channels and procedure are on the Office's website, www.pdpc.or.th.
14. Contact us
If you have a question about this policy or want to exercise your rights, you will be able to reach the InfinityX Mobile team through the official channels announced on this website.
This website has no contact page yet and no contact channel has been announced. We will publish the contact channel for personal data matters on this page before the website is opened to the public.

