App / Sports
This policy covers how jili48 collects, uses and protects the information linked to your account — from the moment you log in to every transaction you make through GCash, Maya or GrabPay. Access to our platform depends on local law and is available only where permitted in your eligible region.
When you create an account on jili48, we collect the details you submit — your name, contact information, login credentials and any wallet identifiers you connect for transactions. This includes payment context from GCash, Maya, GrabPay, InstaPay and PESONet when you initiate a deposit or withdrawal through those rails. We also gather session data: device type, browser session identifiers, IP address and in-app navigation events. This data serves three purposes. First, it lets us verify your account and keep your session continuous across devices. Second, it helps us detect unusual activity on your wallet so your balance stays under your control. Third, it allows us to respond accurately when you raise a support question about a specific transaction or account state. We do not sell your personal information to third parties. Where we engage processors — for example, a payment gateway handling your GCash transfer — those processors receive only what is needed to complete the transaction and are bound by data-handling terms. Your account dashboard after login shows the wallet and session activity tied to your profile. Availability of this service depends on local law and the region you access from.
Not every interaction with jili48 falls under the same data rules. Understanding the scope helps you know exactly which parts of your activity this policy governs and which sit outside it.
Login sessions, device identifiers and authentication events on jili48 are covered. This includes account creation, password changes and session continuity across mobile and browser. These records are held under the terms of this policy.
Wallet actions you initiate — deposits via GCash or Maya, withdrawals through InstaPay or PESONet — generate records we hold. The payment processor handling the transfer operates under its own terms; we receive only the confirmation and amount.
Pages, game lobbies and content you browse on jili48 generate session analytics. These help us understand navigation patterns. No personally identifying data is attached to anonymous browse events unless you are logged in.
Links or services outside jili48 — including your GCash or Maya app, external verification tools or any linked third-party page — operate under their own privacy terms. We do not control or accept responsibility for those external data practices.
You have concrete options when it comes to the data we hold on your account. Reviewing your records is straightforward: log in and open the account dashboard, where your transaction history, wallet entries and session log are visible. If a detail is incorrect — a contact number, an e-wallet identifier or a name field — you can update it directly from the account settings page without needing to contact support first. For any correction that requires our side to act, such as a transaction record discrepancy or a data removal request, raise it through the support contact path listed in this policy. We aim to acknowledge data queries within a reasonable period and will confirm what action was taken. If you want to understand what specific information we hold or how long a record is retained, send your question to our support channel with your account reference number included so we can respond accurately.
Log in and go to your account dashboard. Transaction history, wallet activity and session data linked to your profile are shown there. No additional request is needed to view this information.
Name, contact and e-wallet identifier fields can be updated from account settings after login. For fields that require verification before a change takes effect, the instructions are shown in the settings screen.
If you want to know what we hold, how long we keep it, or need a record corrected on our side, contact support with your account reference. We confirm the action taken after reviewing your request.
Data retention periods vary by record type. Ask support directly for the retention schedule that applies to your account or a specific transaction log. Include your account reference so we can respond with the correct detail.
For any question about how your data is handled, a correction to your account record, or a concern about a specific transaction entry, use the contact paths below. Include your account reference number when you write so we can locate your record and respond accurately.
Open the chat widget from any page on jili48 while logged in. State that your query is a privacy or data matter so the agent picks up the correct case type.
Send your data or policy question to our support email address shown in the Help section of your account dashboard. Attach your account reference and describe the specific record in question.
The Help section inside your logged-in account lists current contact options and the expected response path for data queries. Check there first for the most current contact details.
Security and retention practices are part of how we operate, not an afterthought. Here is what we apply to your account data on jili48.
We use session cookies to keep your login active across page loads and to remember your preferences within the lobby. You can review cookie settings through your browser. Clearing cookies ends your current session but does not delete account records held on our side.
Your account credentials are stored using standard hashing practices. We do not store your GCash, Maya or GrabPay PIN or full card numbers. Payment processors handle sensitive credential data directly under their own security standards.
Transaction logs and account records are kept for a period required by applicable regulations in eligible regions. If you want to know the retention period that applies to a specific record type on your account, contact support with your account reference.
When this policy changes, the updated version is published at jili48/privacy-policy/ with the revision date shown at the top of the page. Continuing to use your account after a revision takes effect means you have reviewed the updated terms.
These are the questions we hear most often about how your data is handled on jili48. If your question is not here, contact support through the path shown in your account dashboard.
We collect the details you submit at registration — name, contact information and login credentials — plus wallet identifiers you connect for GCash, Maya or GrabPay transactions. Session data such as device type and IP address is also recorded when you log in.
We do not sell your personal information. Payment processors — for example, the gateway handling your GCash or InstaPay transfer — receive only the minimum needed to complete a transaction and are bound by their own data-handling terms. No broader sharing occurs.
Log in and go to account settings. Most contact and profile fields can be edited directly there. For changes that need verification on our side — such as a transaction record correction — raise the issue through live chat or email support with your account reference included.
Retention periods vary by record type and depend on applicable regulations in your eligible region. The current retention schedule for your account type is not shown in the dashboard by default. Contact support with your account reference to get the specific period that applies to you.
Records linked to your account are retained for the period required under applicable local regulations, even after your last login. If you want to request removal of a specific record or understand what is held after inactivity, contact support with your account reference and the detail you are asking about.
The current version of this policy is always at jili48/privacy-policy/ with the revision date at the top. We do not guarantee a separate notification for every update, so checking the page directly after any significant account activity is the most reliable approach.