Reference

superliga168 Privacy Policy for Indonesia

superliga168 Privacy Policy gives you a clear account-level view of the data connected with login, wallet checks and lobby activity.

Account dataWallet recordsDevice detailsPolicy requests
superliga168 superliga168 Privacy Policy for Indonesia
CONTACT ROUTES

Ask About Wallet Records Privately

A clear contact path matters when a wallet status or login record looks unfamiliar. We ask you to use the support route shown inside your account and include the relevant transaction reference…

Account support path Use the support contact inside your account when you need to ask how login, verification or wallet details are used. Include your account identifier and avoid sending a password, PIN or complete wallet credentials.
Payment record check For DANA, OVO, GoPay or QRIS questions, provide the payment reference and status shown beside the cashier record. We use those details to trace the relevant entry without requesting your private wallet sign-in.
Access concern If a device sign-in or account change was not yours, contact us through the account support route promptly. We can review the account event, ask for verification and explain the next step under this Privacy Policy.
DATA PRACTICE

Device Cookies and Account Security

Our privacy process separates the data needed for account operation from the data used to understand a technical problem.

Account details

We use your submitted account and contact details to create the account record, send account-related messages and complete the verification step before access. Keeping these details current helps us match a privacy request to the correct account.

Device and browser

A mobile browser or desktop session may provide device, browser and sign-in event details. We use these signals to identify unusual access and investigate a session issue; they are not a request for your device password.

Cookies and sessions

Cookies can keep a session setting or account path available between pages. You can adjust browser controls, but removing session storage may require you to sign in again before reaching account or policy pages.

Payment matching

For DANA, QRIS, bank transfer and other listed rails, we use reference, amount and status details to connect a payment event with your account record. We do not ask for a wallet PIN or online-banking password.

Retention period

We keep each category only for the time needed to operate the account, resolve a stated issue, protect access or meet an applicable obligation. When the purpose ends, records are removed, anonymised or kept only where required.

Change request

You can ask what account data we hold, request a correction or ask about deletion through the support contact inside your account. We may verify your identity first, and available rights depend on local law.

Privacy Policy Questions for superliga168

These answers address the questions we expect you to have before opening an account or checking a wallet record. They focus on the data path behind login, payment matching, device sessions and contact requests. If your situation needs a record-level answer, use the support route inside your account and mention the relevant payment reference or sign-in event.

It covers account details, verification data, device and browser events, cookies, payment references, wallet status and records connected with account activity. It also explains why we use those records, how long we retain them and how to ask about correction or deletion.

We need account and contact details to create your account record, confirm the person requesting access and respond to account messages. A clear account step helps us connect a privacy request with the right record rather than exposing details to the wrong person.

Yes. The Privacy Policy covers the payment reference and status data needed to match DANA, OVO, GoPay or QRIS activity with your account. We do not need your wallet PIN, wallet password or online-banking password to check that record.

We may receive browser type, device details, session events and sign-in timing when you open an account page on mobile or desktop. We use these details to spot unusual access and investigate technical issues, not to request private device credentials.

Use the support contact shown inside your account and state whether you want access, correction or deletion. Include the account identifier that helps us locate your record, but do not send a password or full payment credential. Available requests depend on local law.

We retain payment and login records for as long as they are needed to operate the account, investigate a stated issue, protect access or meet an applicable requirement. After that purpose ends, we remove or anonymise them where permitted.

Yes. You can read this Privacy Policy before taking the account step and use it to understand data handling for login, device sessions and local payment references. Any access or eligibility question depends on local law and applies where local law permits.