Reference

vegas 6d Privacy Policy For Your Account

Our vegas 6d Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby and your wallet.

Clear data purposesWallet detail boundariesAccount request pathCookie choices

Explore Our Lobby Read FAQ

How DANA And QRIS Appear In Our Privacy Policy

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

Our Privacy Policy separates account data from payment references. When you choose DANA, OVO, GoPay or QRIS, we may record the selected rail, transaction reference, amount, status and time needed to match your account activity; we do not ask for wallet passwords through our account form.

1
Bank transfer and virtual account records can include the receiving bank reference, including BCA, BRI, Mandiri or BNI. We also process phone verification details before account access, browser and device signals used to protect sessions, and support messages you send about a receipt or wallet status.
2
We retain each category only for the stated operational, dispute and legal purposes, then review whether it is still needed. Your choices and any service access depend on local law, and where local law permits you can ask us to explain, correct or remove eligible data.

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

REQUEST HELP PATH

Contact Us About Privacy Policy Requests

A clear support route helps when you need a copy, correction or explanation under our Privacy Policy.

Account data request Ask the account support desk for the data linked to your profile. We may verify your phone before discussing account records or preparing a response.

Wallet record check Send the payment reference and selected rail when a Privacy Policy question involves OVO, DANA, QRIS or a virtual account status.

Correction or removal Tell us which detail needs changing or removal. We assess the request under local requirements and explain any record we must retain.

HANDLING YOUR DETAILS

What Our Privacy Policy Covers In Practice

We handle this policy area through defined account steps rather than a single broad data label.

Account data

We use your account details to create access, complete phone verification and respond to requests. We limit internal use to the purpose connected with that account step.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can leave matching references. These help us confirm status without requesting your private wallet password.

Mobile cookies

Cookies and similar browser data can remember session choices and help identify a returning device. You can manage browser cookie settings, though some account steps may then need repeating.

Session security

We examine sign-in and device signals when protecting an account session. If a session looks unusual, phone verification may be requested before account details are shown.

Retention decisions

We keep records for the purpose stated in the Privacy Policy, including account support, transaction matching or required disputes. When that purpose ends, we assess the record for removal.

Your requests

Use the support path connected to your account to ask for access, correction or eligible removal. Include a clear request so we can verify ownership and respond accurately.

Privacy Policy Questions For Indonesia Accounts

These Privacy Policy answers cover the searches we hear most often before an account is opened. We keep the scope on your data, wallet references, cookies, account security and contact choices, with access handled where local law permits.

It covers account details, phone verification, device and browser signals, cookies, payment references, support messages, retention and requests to access, correct or remove eligible data.

Our account form does not ask for a DANA or OVO wallet password. We may keep the chosen payment rail, transaction reference, status and time needed to match account activity.

Phone verification helps connect a request to the correct account and protects account details from being disclosed to the wrong person. It may also be requested after unusual session activity.

We may process browser, device and session signals from the mobile or desktop path you use. These details help maintain a session, remember choices and identify unusual access patterns.

Yes, where local law permits. Contact the support path shown in your account, describe the data request clearly and complete any ownership check needed before we discuss account records.

Retention depends on why the record exists, such as receipt matching, account support or a dispute. We assess whether it remains needed and apply local requirements before removal.

You can manage cookies through your browser settings and contact our support desk with a specific question. Turning some cookies off may require you to repeat a session or account step.

vegas 6d Privacy Policy For Your Account

Contact Us About Privacy Policy Requests

What Our Privacy Policy Covers In Practice

Account data

Payment references

Mobile cookies

Session security

Retention decisions

Your requests

Privacy Policy Questions For Indonesia Accounts

01 What does the vegas 6d Privacy Policy cover?

02 Does vegas 6d store my DANA or OVO password?

03 Why is phone verification used before account access?

04 What device data does the Privacy Policy mention?

05 Can I request a copy or correction of my data?

06 How long does vegas 6d keep payment records?

07 How do I ask about cookies in the Privacy Policy?

Related Pages