Reference

sbc toto Legal access for Indonesia

sbc toto Legal terms set out how you open an account, use QRIS for wallet activity and access titles such as Andar Bahar where local law permits.

Account termsData choicesLocal access
sbc toto sbc toto Legal access for Indonesia
REQUEST ROUTES

Where to raise a Legal request

A clear contact route matters when a policy question affects your account or wallet record. We keep support close to the account and cashier paths so you can identify the issue without explaining your full history repeatedly. Include your registered phone number, transaction reference and the policy point you want clarified.

Team online

Account access desk

Use the account support route when phone verification, sign-in status or local access wording needs clarification. We can direct your request to the policy team without asking you to create another account.

Wallet record desk

For DANA, OVO, GoPay or QRIS records, send the receipt reference shown near the cashier path. We use that detail to separate a payment-status question from a wider Legal request.

Policy contact route

Ask us to explain a clause, correct a personal detail or record an access concern through the policy contact route. We will tell you what account evidence is needed for the request.

RECORD HANDLING

How sbc toto handles account records

Legal handling is practical: we collect only what is needed to operate the account, answer a request and check wallet activity.

Account data

We use your registered phone details and account identifiers to connect access requests with the correct record. A clear phone verification step helps prevent changes being made against the wrong account.

Cookie choices

Cookies can support sign-in continuity and policy display across a mobile browser. You can ask the policy contact route what cookie information is used when a page behaves differently after settings change.

Wallet evidence

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be retained to match a transaction query. We use the receipt or reference supplied by you during a status check.

Account security

Do not share your verification code or account password through a support message. If access looks unfamiliar, tell the account desk and include the device path you used, such as mobile browser or desktop.

Retention questions

You may ask which account or transaction records relate to a Legal request and why they remain on file. We will use the registered account route to confirm the request belongs to you.

Change requests

To correct a phone detail, clarify a policy clause or ask about stored data, send the request through the policy contact route. Include the affected account field so we can review the right record.

Legal answers for Indonesian accounts

These Legal answers cover the questions we hear before account access, from local eligibility and data use to wallet records and policy changes. If your situation is specific, use the account or policy contact route with your registered details.

It explains account access, phone verification, data use, cookies, wallet records, security and policy requests. Access depends on local law, and you should read the wording before opening or using an account.

Access is available where local law permits. Your location and eligibility still apply, and we may ask for phone verification before account access. Check the Legal notice rather than relying on a payment method alone.

A DANA or QRIS reference can connect a wallet event to the correct account when you ask about a receipt, status or correction. We use the supplied reference for that specific policy request.

We use registered account details to provide access, verify requests, protect account security and answer policy questions. You can ask which record relates to your request through the policy contact route.

Send a correction request through the policy contact route using your registered phone details and the field that needs changing. We may request verification before updating the account record.

Stop sharing account codes, then contact the account access desk with the device path you used and any relevant time or reference. We can direct the matter to the security and policy route.

Use the policy contact route and name the cookie setting or account record you want clarified. We will explain the relevant handling purpose and confirm what account detail is needed to process your request.