Reference

buntoto Legal access starts with clear terms

buntoto Legal puts the rules behind account access, payment records and personal data in one place, so you can check them before completing phone verification.

Account rulesData choicesPayment recordsLocal-law access
buntoto buntoto Legal access starts with clear terms
POLICY CONTACT ROUTES

Get a direct path for Legal questions

A clear contact route matters when a policy question affects your account, wallet record or access request.

Account policy help Open the support route from your account when you need clarification about eligibility, phone…
Payment record check For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, keep the receipt…
Policy change request If a Legal record needs correction, use the account support route and state the…
DATA CONTROL DETAILS

See how our Legal controls work

We treat policy handling as an account process, not a vague promise. The Legal route covers what we collect during phone verification, how cookies support a signed-in session, how wallet records are…

Data used for access

Phone verification connects an account to the contact detail supplied during registration. We use that step to confirm an access request and may ask for matching account details before discussing private records through the support route.

Cookie choices

Cookies can keep a signed-in session and remember necessary page settings. Your browser controls cookie removal, while deleting required session data may sign you out and require another account check before Legal details appear.

Account security

Never share your password, wallet PIN or phone verification code in a support request. If a mobile browser changes device or session, we may request an additional account check before changing payment or contact details.

Payment data handling

A DANA, OVO, GoPay or QRIS entry can be linked to a transaction reference, status and account identity. Bank transfer and virtual account requests may need the same matching detail for a record correction.

Retention questions

If you want to ask how long a particular account, verification or payment record is kept, send the request through account support. Identify the record type and date so we can address the correct Legal category.

Requesting a correction

You can ask us to check inaccurate contact, identity or transaction details through the policy contact route. We may verify ownership first, then explain whether the requested change can be made under applicable rules.

Legal answers for your buntoto account

These Legal answers address the questions most often asked before account access: local eligibility, data use, cookies, payment records, corrections and contact steps. Read the relevant answer before completing phone verification, especially if you are checking access from Indonesia or changing a wallet-linked account detail.

buntoto Legal covers account eligibility, phone verification, personal data, cookies, payment records and policy contact requests. Access depends on local law, so check your local position before opening an account or entering any casino or sportsbook area.

Use the support route inside your account or near the sign-in and cashier areas. Describe the policy issue, account identifier and relevant date. Do not include your password, wallet PIN or phone verification code in the request.

Legal payment handling may connect a DANA, OVO, GoPay or QRIS entry with its reference, status, date and account identity. For a correction request, keep the receipt detail available and send only the information needed to locate that record.

Yes, you can ask us to check inaccurate contact, identity or transaction details through account support. We may complete phone verification or another ownership check before changing a record, and we will explain the applicable Legal outcome.

Yes. Our Legal wording explains that cookies can support a signed-in session and necessary settings. If you remove them or change device, the mobile browser may sign you out and request another account check.

We ask you not to share passwords, wallet PINs or verification codes in support messages. A device or session change can trigger an ownership check before private Legal, contact or payment details are discussed.

You can ask how long a specific account, verification or payment record is kept through the policy contact route. Name the record type and date, and we will direct the request to the relevant Legal process.