Reference

Privacy Policy for score288 Accounts

Our Privacy Policy explains how score288 handles the account details, device signals and wallet records connected with your access to the lobby.

Clear data purposesWallet record controlsContact for changesMobile and desktop access
score288 Privacy Policy for score288 Accounts
CONTACT ROUTES

Ask About Data or Wallet Records

A clear contact route helps when a Privacy Policy question involves a specific account event.

Support chat Use our support chat for a Privacy Policy question linked to login activity, phone verification, or a wallet status. Share the relevant date and rail, such as DANA or GoPay, without sending a password or full security code.
Account contact Contact us through the account-linked route when you want to change a detail or ask which records relate to your profile. We may confirm ownership before discussing information connected with your score288 access.
Receipt check For a payment record question, provide the receipt reference and choose the matching route, such as OVO, QRIS, bank transfer, or virtual account. We use those details to locate the relevant event without requesting unnecessary data.
DATA PRACTICES

How We Handle Your Account Data

Privacy Policy controls are most useful when they match the actual account path. We limit access to records according to operational need, use security checks around login and wallet reconciliation, and separate…

Account details

We use your account identifiers and phone-verification status to connect login activity with the correct profile. This helps us prevent an account change from being applied to the wrong person while keeping the request tied to your own access.

Device signals

Your browser, device type and session events can be recorded for security and troubleshooting. On mobile, these signals help us recognise the path from login to the lobby; on desktop, they support the same account check.

Cookie choices

Cookies may keep your session active, remember selected settings, and help us identify unusual access. You can manage browser cookie controls, although restricting them may require another login or limit parts of the account path.

Wallet matching

Payment references from DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account help us match a receipt with your account. We do not need your wallet password to investigate a payment record or status question.

Security checks

We may compare login, device, phone-verification and transaction signals when an account change or withdrawal record needs confirmation. These checks protect the profile and can require extra detail before we disclose or amend stored data.

Retention requests

We keep records only for service, dispute, security, or legal purposes that require them. Ask us to correct, restrict, or explain a record through an account-linked contact route; we will assess the request under local requirements.

Privacy Policy Questions About score288

These Privacy Policy answers address the account and payment questions we expect from Indonesian customers before they open an account. Each answer points to a practical step, from checking cookies on a mobile browser to requesting a correction through an account-linked contact route. If your situation depends on local law, we will apply the relevant rule when assessing the request.

The score288 Privacy Policy covers account details, phone verification, login and device events, support messages, cookie signals, and payment references. It explains why we use those records for account access, security, payment matching, service contact, dispute handling, and legal duties where local law permits.

No. Our Privacy Policy distinguishes a payment reference from a wallet credential. We may receive a transaction reference, amount status, or receipt detail for DANA, OVO, GoPay, or QRIS reconciliation, but you should never send us a wallet password, PIN, or full security code.

Contact us through the route connected with your account and identify the field you believe is wrong. Mention the relevant account step, such as phone verification or a bank-transfer receipt. We may confirm ownership before making a correction under the Privacy Policy.

Cookies can keep a mobile browser session connected to your account, remember settings, and help identify unusual access. You can adjust cookie controls in your browser. If you block necessary cookies, our Privacy Policy allows us to require another login or limit session functions.

We retain payment references for the period needed to reconcile DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity, handle disputes, protect accounts, and meet legal duties. The precise period can depend on the record and the rule that applies where local law permits.

Yes. Send an account-linked request asking us to explain the personal data connected with your profile. We may ask for an ownership check before responding, and some records may remain restricted when disclosure could expose another person, security controls, or a legal obligation.

Start with our support chat or account contact route and write that your request concerns the Privacy Policy. Include your account-linked contact detail and a short description, such as a cookie question, device event, or QRIS receipt query, while leaving passwords and PINs out.