Reference

bujangtoto Privacy Policy For Your Account

Our Privacy Policy explains what we collect when you open an account, verify your phone, browse on mobile and request a wallet or bank transfer.

Clear data purposesPhone verification scopeIndonesia access terms

Explore Our Lobby Read FAQ

DANA And QRIS Data Under This Policy

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

This Privacy Policy covers details you provide during account creation, including your phone number, verification result and contact details, plus technical records from the browser or device used to reach the lobby. When you choose DANA, OVO, GoPay or QRIS, we use the transaction reference and

1
status needed to match a request to your account; bank transfer and virtual account references are handled for the same purpose. We do not treat a payment name as permission to collect unrelated content. Cookies and similar tools may remember a session or help us detect
2
unusual sign-in activity. Access and eligibility depend on local law, and we may limit processing when a request cannot be confirmed.

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

HELP PATHS

Where To Ask About Privacy

A clear contact route helps when you want to ask about stored account data, a phone check or a payment record. Start from the support path beside the account and cashier areas, then describe the request without sending your password or one-time code. We use the details already linked to your account to locate the matter, including a DANA or QRIS reference when your question concerns a wallet status.

Team online

Account data request

Use the account support route to ask what personal details are linked to your profile. We may request your verified phone step before discussing account-specific records.

Wallet record question

For DANA, OVO, GoPay or QRIS questions, include the transaction reference and approximate date. We use those details to separate your request from another account.

Privacy correction path

Tell us which field needs correction and why. Our support route can review a phone, contact or account record request without asking you to disclose a password.

DATA PRACTICE

How Account Data Stays In Scope

We keep this policy practical by connecting each data use to an account action you can recognise.

Collected account details

We may receive your phone number, account identifiers and verification result when you create or access an account. These fields help connect a request to the correct profile.

Device and session records

Our site may record browser type, device signals, session time and basic network details. These records help identify repeated sign-in failures and unusual account activity.

Cookies and preferences

Cookies can retain a session choice or support site operation. You can manage browser cookie settings, although removing them may require another account sign-in.

Account security steps

Phone verification is checked before account access is completed. Do not share your password or one-time code; support will not need either item to discuss policy requests.

Retention and removal

We retain records only while they support an account, payment trace or legal requirement. A removal request may be limited where a transaction record must remain available.

Requesting policy changes

Contact us through the account support route to request access, correction or deletion. Include the relevant profile detail, and we will use verification before changing records.

Privacy Policy Questions For Indonesia

These answers address the Privacy Policy searches we expect before an account is opened. They cover the records connected to your phone, device and payment choices, along with the practical route for asking us to check or change a record. If your circumstances are different, use the support path linked to your account.

It covers account details, phone verification, browser and device records, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us connect account access to the correct profile and investigate sign-in issues. We use the result as an account-security record, not as permission to read unrelated phone content.

We use transaction references and status details needed to match a request. You should never send a wallet password, account password or one-time code through a support message.

Yes. Use the account support route and describe the records you want checked. We may verify your phone or account details first so private records are not released to another person.

Send a correction request through support with the field that appears wrong and the replacement detail. We review the request against your verified account before making a change.

Retention depends on the record type and whether it supports account security, a payment trace or a legal requirement. You can ask support which retention reason applies to your request.

Yes. The policy applies when you use a mobile browser to sign in, open Lightning Roulette or check an account-linked wallet status. Device and session records may support access protection.

bujangtoto Privacy Policy For Your Account

Where To Ask About Privacy

Account data request

Wallet record question

Privacy correction path

How Account Data Stays In Scope

Collected account details

Device and session records

Cookies and preferences

Account security steps

Retention and removal

Requesting policy changes

Privacy Policy Questions For Indonesia

01 What does the bujangtoto Privacy Policy cover?

02 Why does the Privacy Policy mention phone verification?

03 Does bujangtoto store my DANA or QRIS password?

04 Can I ask for my personal data under this Privacy Policy?

05 How do I correct an account detail?

06 How long does bujangtoto keep account records?

07 Does this Privacy Policy apply on a mobile browser?

Related Pages