Live / App
This policy explains what information jiliz collects when you use our platform, how we use it, and what choices you have over your own records. Access to our platform depends on local law and is available only where eligible under your region's rules.
When you open an account on jiliz, certain information is collected so the platform can work properly for you. This includes your registration details, the device and browser you use to access the lobby, and transaction context tied to your chosen payment method — whether that is GCash, Maya, GrabPay, PESONet, or Bank Transfer. We collect only what is needed to run your account, process wallet activity, and respond to support requests you raise. We do not sell your personal information to third parties. Data shared with payment processors — for example, when a GCash or PESONet transaction is initiated — is limited to what those processors require to complete the transfer. Each payment rail has its own terms, and we recommend reading them alongside this policy. Cookies and similar technologies help us remember your session so you can return to the lobby without repeating the login flow every time. You can adjust cookie preferences in your browser settings; doing so may affect how certain account features behave. Data we hold is kept for as long as your account is active and for any period required by applicable law in eligible regions. This policy applies to jiliz and any account-linked sub-paths under that domain.
Not every service connected to your jiliz account falls under this single policy document. The table below outlines what is inside our scope, what sits with a third-party service, and where to look for the relevant terms in each case.
Registration details, login activity, session history and device identifiers collected through jiliz are fully within this policy. You can request a summary of this data through the support channel listed on this page.
Transaction records initiated through GCash, Maya, GrabPay, PESONet or Bank Transfer appear in your account wallet history. The data jiliz holds on these is covered here; data held by the payment provider itself is governed by their own policy.
Game titles from studios available in the lobby — including content displayed in your session — do not carry separate user-data obligations beyond what this policy states. No personally identifying data is passed to a game engine.
Links or integrations that take you outside jiliz are not covered by this policy. Once you leave our domain, the privacy terms of the destination service apply. We do not control how external services handle your data.
Your account data is not locked away from you. Several actions are available without needing to escalate to a formal process. You can review the personal information attached to your account by logging in and opening the account settings page — the fields shown there reflect what we hold on file. If a detail is wrong, you can edit it directly in that view or submit a correction request through support. For questions about how a specific piece of data is used — for example, how a GCash top-up record is stored or how long a session log is retained — our support team can walk you through it. Requests to close an account and remove data where permitted by law are handled through the same channel. Response times are not guaranteed, but we aim to acknowledge every request and provide a clear next step. Availability of data-access rights may depend on local law in your eligible region.
Log in, open account settings and check the personal details we hold. The fields shown are your live record — what you see there is what we have on file for your account.
Update information directly in account settings or submit a correction through the support channel. Include the field name and the correct value in your message so the team can act without a follow-up.
If you want to know how a specific record — such as a GrabPay transaction log or a login event — is stored and for how long, contact support with the detail in question and we will respond with a clear answer.
Account closure and data removal requests are handled through the support channel. Where local law permits deletion, we process it within the scope allowed. Some records may be retained as required by applicable regulation in eligible regions.
Privacy questions can be directed to our support team through the channels below. For account-specific queries — such as verifying a data record or requesting a correction — include your registered account identifier so we can locate your file without delay.
Send privacy-related questions to our support address listed on the Contact page. Include the nature of your request and your account identifier for a faster response.
The live chat option in your account dashboard connects you to the support team. It is the quickest path for questions about a specific data field or a recent GCash or Maya transaction record.
For self-service corrections, open account settings after login. The editable fields shown there let you update most personal details without waiting for a support response.
Our approach to data handling is shaped by what your account actually needs to function. We store login credentials in encrypted form, and session tokens are invalidated when you log out or when a session expires from inactivity. Payment context — such as which method you used for a GCash or PESONet transfer — is kept in your transaction history and is not passed beyond what the payment processor requires to complete the action.
Session cookies keep you logged in across the lobby so you can move between games and your wallet without repeated sign-in steps. You control cookie preferences in your browser; turning off session cookies will require you to log in each visit.
Account records are held for as long as your account is active and for any period required by law in your eligible region. When an account is closed and deletion is permitted, we remove personal data from active systems within a reasonable period.
Transaction records for GCash, Maya, GrabPay, PESONet and Bank Transfer are visible in your account wallet history. We do not store full payment credentials — only the reference data needed to match a transaction to your account.
When this policy changes, we post the updated version at jiliz/privacy-policy/. Continued use of the platform after a change is posted indicates acceptance of the revised terms. Contact support if you have questions about a specific change.
These questions cover the situations that come up most often when you want to understand how your data is handled, what we keep, and how to act on your rights under this policy.
Registration collects the details you enter in the sign-up form — name, email address and contact information. After you log in, device identifiers and session data are also recorded. We keep only what is needed to run your account and respond to your requests.
When you initiate a transaction through GCash, Maya or GrabPay, we share only the data those processors need to complete the transfer. We do not send additional personal information. Each payment provider's own privacy terms govern how they handle data on their end.
After account closure, personal data is removed from active systems where local law permits. Some transaction records may be retained for the period required by applicable regulation in your eligible region. You can ask support for details specific to your account.
Yes. Contact support through the live chat in your account dashboard or via the support email on the Contact page. Include your account identifier and the nature of your request. We will confirm what data we hold and provide the relevant details in our response.
Log in and open account settings — most personal detail fields are editable there directly. If a field cannot be changed from settings, submit a correction request through support with the field name and the correct value you want on record.
We use session cookies to keep you logged in and to remember your lobby position. You can disable cookies in your browser settings. Doing so means you will need to log in each session and some account features may not work as expected between visits.