Reference

vegasgg Privacy Policy For Your Account

Our Privacy Policy shows what we collect when you open a vegasgg account, sign in from a phone, or check wallet status for DANA, OVO, GoPay and QRIS.

Account clarityWallet dataCookie choicesSupport requests
vegasgg vegasgg Privacy Policy For Your Account
HELP WITH PRIVACY

Where To Ask About Your Data

A clear contact path matters when a phone check, wallet reference, or account record needs attention.

Account request Ask about data linked to your account through the signed-in support path.
Wallet record For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, share the transaction…
Device question If a phone or browser keeps a session record after sign-out, tell us the…
DATA CONTROL POINTS

What We Keep And Why

Privacy choices are easier when each record has a clear purpose. We separate account, device, cookie, and payment-reference details so a request can be directed to the right…

Account details

When you open an account, we use the contact details and phone verification result needed to connect you with the…

Device signals

A phone or desktop browser may send device type, session time, and basic connection details.

Cookies

Cookies can keep a sign-in flow, remember a selected setting, or measure page activity.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference can be stored with account activity.

Account protection

Phone verification and sign-in checks help prevent an account record from being disclosed to the wrong person.

Retention requests

Some records remain while needed for account operation, dispute handling, security checks, or duties that apply where local law permits.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the searches we expect before you open an account. They explain account access, local wallets, cookies, device records, correction requests, and the support path in practical terms. If your situation is not listed, use the account support route and identify the specific record you want us to check.

It covers account details, phone verification, device and session records, cookies, payment references, support messages, and retention. It also explains how we use those records when you access the lobby where local law permits.

Yes. The Privacy Policy explains that DANA, OVO, GoPay, and QRIS references may connect a cashier status with your account. We use the reference for checking and support, not your wallet password.

Use the signed-in support path and state whether you want a correction, access request, or permitted deletion. Include the account contact detail needed to verify ownership, and avoid sending full wallet credentials.

Device type, session time, and basic connection details help us protect sign-in access and investigate a session that remains open. We use those signals for account security, not to inspect unrelated content on your device.

You can clear cookies through your browser controls. Removing a session cookie may sign you out or reset a setting, while some records already held for account or legal purposes may remain under the Privacy Policy.

Retention depends on why the record exists, such as account operation, payment status, security, dispute handling, or a duty that applies where local law permits. Ask support which category applies to your record.

Start from the support route inside your account and describe the exact data concern. For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account matter, include its reference without sharing a wallet PIN.