Reference

live draw sgp Legal access starts with clarity

live draw sgp Legal details explain how account access, wallet records and policy requests work before you enter the lobby.

Account termsData requestsCookie choicesLocal-law access
live draw sgp live draw sgp Legal access starts with clarity
CONTACT ROUTES

Browse Legal help through three clear routes

A clear contact route matters when a Legal request affects your account or wallet record. We ask you to start from the signed-in support panel when possible, because it connects your message with the correct account details. If you cannot sign in, use the contact route on our site and include the phone number linked to your account. Where local law permits, we can explain the next verification step without asking you to send a password or payment PIN.

Team online

Account support panel

Use the signed-in support panel for a Legal question about your account terms, phone verification or access status. We can match the request to your account record more accurately when you send it from the verified account path.

Site contact route

If sign-in is unavailable, use the contact route on our site and include your registered phone number plus the subject of your Legal request. Never include a password, wallet PIN or full payment credential in the message.

Wallet record check

For a Legal question about DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, state the rail and transaction date. We use that detail to locate the relevant record before explaining what can be changed.

DATA PRACTICE

Check how Legal requests shape data handling

Our Legal process is tied to practical account controls rather than broad promises. We separate sign-in details from payment references, record policy requests against the verified phone path, and use device behaviour…

Account data

We use the account details you provide to maintain sign-in, phone verification and policy communication. When you ask us to correct a name or phone record, we compare the request with the verified account path before making a change.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries are handled as payment references linked to account activity. We do not need your wallet PIN to investigate a Legal request about a transaction record.

Cookie settings

Cookies help keep a signed-in session connected while you move between account pages. You can adjust cookie controls in your browser; blocking some cookies may end the session or require phone verification again.

Account security

Keep your password, phone verification code and wallet PIN private. We do not ask for those secrets in a Legal contact message, and a request may pause while we confirm that the account owner is contacting us.

Retention approach

We retain account and transaction records only as needed for account administration, dispute handling, security checks or a lawful requirement. If you ask what remains on file, we explain the applicable retention reason and available next step.

Change requests

Send a correction, deletion or access request through the support panel, or use the site contact route when sign-in is unavailable. Include the registered phone number, and we will describe the verification and response path.

Browse answers about Legal and access

These Legal answers cover the questions we receive before an account is opened and when a policy request is submitted. They explain the practical steps around identity checks, data records, cookies, payment references and contact routes. If your situation is unusual, use the support path with your registered phone number so we can address the specific account record.

Legal covers account access, phone verification, wallet and transaction records, cookies, data requests, security checks and policy changes. It also explains when we may need to confirm account ownership. Access or eligibility depends on local law, so the current page should be read before account use.

Access depends on local law. If access is available where you are, use the account path shown on the site and complete the requested phone verification. We may ask for a further check when the account record or a Legal request requires confirmation.

Send the request through the signed-in support panel, or use the site contact route if you cannot sign in. Include your registered phone number and ask for a data copy. We verify ownership first, then explain the response route where local law permits.

Yes, you can request a correction to account details through the support panel or site contact route. State which field is wrong and provide the registered phone number. We compare the request with the verified account path before changing the record.

DANA and QRIS references may be connected to your account activity so we can reconcile a payment-related request. We do not ask for your wallet PIN. Include the payment rail and date when contacting us, and we will explain what record can be checked.

Browser cookie controls can affect session continuity on account pages. If you block required cookies, you may be signed out or asked to complete phone verification again. The Legal terms still apply, and you can contact support if the change prevents a policy request.

Use the support panel while signed in, or the site contact route when sign-in is unavailable. Mention the clause or page wording you are asking about, along with your registered phone number. We can clarify the current text and identify its effective date.