Reference

Open buncistoto Privacy Policy Before Account Access

buncistoto Privacy Policy explains how we collect, use and protect the account details connected with Sic Bo, Aviator and local wallet activity.

Clear data purposesWallet reference handlingPhone verification detailsIndonesia access wording

Browse Our Lobby Read FAQ

Explore How Wallet Data Fits Privacy

buncistoto Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers the details you submit when opening an account, the phone check used before account access, and technical records created when you move between the lobby and your device. When you use DANA or QRIS, we receive payment references and status details needed

1
to match an account action; OVO, GoPay, bank transfer and virtual account activity can create similar records. We do not describe these rails as a reason to collect unrelated details. We use the available data to confirm requests, investigate mismatched status and protect account access. Device
2
type, browser information and security events may be recorded when you open Sic Bo or Boxing Betting. Where local law permits, we provide the service to Indonesian account holders; eligibility depends on local law. The policy also explains storage, retention, disclosures and how to ask us
3
about your records.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT PATHS

Contact Us About Privacy Requests

A privacy question should not get lost beside a wallet issue, so we keep the contact route close to the account and cashier areas.

Account privacy route Open the support path from your signed-in account and select the privacy request option. We use the account phone check to connect the request with the correct record.

Wallet record question For a DANA, OVO, GoPay or QRIS reference, send the visible status and date through the secure contact form. Do not place a wallet PIN or secret code in your message.

Device access concern If a device you do not recognise appears in your account activity, contact us through the account support route and describe the login step. We can explain the security record linked to it.

DATA PRACTICE

Check How We Handle Your Records

Privacy work is tied to practical account events rather than broad statements. We separate identity details from payment references where our process allows, limit staff access by task, and use security checks…

Account details

We use your submitted account details to create and maintain access, complete the phone verification step and respond to a request about your own records.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match payment status. They are handled as transaction records, not as wallet passwords.

Cookies and devices

Cookies can preserve a signed-in session and remember basic device behaviour. Browser type, device signals and security events may be used to detect unusual account access.

Account security

Phone verification, session checks and access records help us respond when a login looks unusual. Keep your verification code private and contact us if a device seems unfamiliar.

Retention periods

We keep records only for the stated service, security or legal purpose, then remove or restrict them according to the applicable retention requirement and the request outcome.

Change requests

You may ask us to correct details, explain a record or address a deletion request through the account privacy route. We may verify ownership before making a change.

Find Answers About Privacy Policy

These Privacy Policy answers focus on the questions you may have before opening an account from Indonesia. We cover wallet references, device records, cookies, access requests and the ownership check used to protect your details. If your situation is not listed, use the privacy contact path beside your account area and include only the details needed to identify the request.

It covers account details, phone verification, device activity, cookies, payment references and support requests connected with your use of the service where local law permits.

No. Our policy concerns payment references and status details for DANA or QRIS activity. Never send a wallet PIN, password or verification code through a support message.

Device and browser signals help keep a session working and identify unusual access. If a record looks unfamiliar, contact us through the account privacy route for clarification.

Yes, you can submit a data access request through the signed-in support path. We may verify your phone or account ownership before releasing details connected to your record.

Send a correction request through the privacy contact route and identify the field that needs changing. We check the request against your account before updating the stored detail.

Retention depends on the purpose of the record, security needs and applicable legal requirements. The policy route can explain the category involved and whether restriction or deletion is available.

Yes. Contact us through the privacy route and mention your device or browser. We can explain which session files support account access and how they relate to your visit.

Open buncistoto Privacy Policy Before Account Access

Contact Us About Privacy Requests

Check How We Handle Your Records

Account details

Payment references

Cookies and devices

Account security

Retention periods

Change requests

Find Answers About Privacy Policy

01 What does the buncistoto Privacy Policy cover?

02 Does buncistoto store my DANA or QRIS PIN?

03 Why does buncistoto record my device information?

04 Can I request a copy of my account data?

05 How do I correct information in my account?

06 How long does buncistoto keep payment records?

07 Can I ask about cookies on my mobile device?

Related Pages