Reference

Privacy Policy For Your vegawin Account

Our Privacy Policy explains how vegawin handles the details connected with your account, including phone verification, DANA, OVO, GoPay and QRIS activity.

Account detailsWallet recordsCookie choicesPrivacy requests
vegawin Privacy Policy For Your vegawin Account
REQUEST HELP

Three Privacy Support Routes

A clear contact route helps when your account details, wallet receipt or device session needs attention.

Account access If phone verification or sign-in exposes an incorrect detail, use account help to ask for a correction. We may request the verified phone reference and a short description, while avoiding unnecessary wallet or game activity.
Wallet receipt For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, use the cashier help path and attach the relevant receipt reference. We check the payment record against your account before discussing transaction details.
Privacy request To ask about stored details, cookie choices, access or deletion, send a privacy request through account help. We first confirm that you control the account, then explain what can be changed under local requirements.
DATA HANDLING

Six Practical Privacy Commitments

Privacy decisions are easier to understand when they match real account actions. We connect each commitment to a step you can recognise: opening an account, signing in on mobile, checking a QRIS…

Account collection

We collect details needed to create and protect your account, including contact details and the phone verification step. We use those details to recognise your account during sign-in rather than asking for unrelated personal records.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a payment status with the correct account. Bank transfer and virtual account records follow the same matching purpose, so a receipt question can be checked without exposing another account.

Device sessions

When you move from a mobile browser to desktop, session and security details can help us detect an unusual sign-in. We use device signals for account protection and do not treat a device change as permission to collect unrelated content.

Cookie choices

Cookies can keep a selected session available and help us understand whether a page request is working. You can adjust cookie settings in your browser; changing them may affect sign-in continuity or the way policy pages load.

Retention checks

We retain account, payment and security records for the period needed for account administration, dispute handling and applicable legal duties. When a record no longer serves those purposes, our handling follows the deletion and retention controls attached to it.

Change requests

You can ask us to correct, access or remove eligible personal details through the privacy request path. We verify account control before making a change, and we explain when a record must remain available under local law.

Privacy Policy Questions From Indonesia

These answers address the searches we hear most often about the vegawin Privacy Policy. They focus on account creation, local wallet references, mobile access, cookies and requests for changes, so you can decide what to send before contacting us. Where access or a request is restricted, the outcome depends on local law.

The vegawin Privacy Policy covers account details, phone verification, device sessions, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. It also explains retention, security checks and the ways you can request access or correction.

Phone verification helps us confirm that you control the account before access is granted or a privacy change is made. It also helps separate your records from another account. We use the verification detail for account protection and related support checks, not for unrelated requests.

Yes. The Privacy Policy includes payment references connected with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account records. We use those references to match status questions, investigate receipt differences and protect account details when a payment query is raised.

You can request a correction through the account help or privacy request path. Tell us which detail is wrong and provide the verified account reference requested by our team. We check account control first, then confirm the change or explain why a record must remain unchanged.

On a mobile browser, cookies may keep your session available and help us identify whether a policy page or sign-in request works correctly. You can change cookie settings in your browser. Some choices may require another sign-in or affect session continuity on that device.

We keep account, payment and security records for the period needed to operate account controls, resolve disputes and meet applicable legal duties. Retention differs by record type. You can ask which category applies to your request, although deletion depends on local law and required records.

Use the account help path for access, correction, deletion or cookie questions. For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account receipt, use the cashier help path. Include the smallest useful reference, and we will confirm account control before discussing details.