Reference

Privacy Policy For Your vonis500 Account

Our Privacy Policy explains what account, device and wallet details we use when you open vonis500 in Indonesia.

Account dataWallet recordsDevice controlsPolicy requests
vonis500 Privacy Policy For Your vonis500 Account
CONTACT ROUTES

Get Help With Privacy Requests

A clear support path helps you ask what data we hold, why it was used or how an account record can be corrected.

Account privacy request Ask us to check the personal details connected with your vonis500 account, including the phone verification record. We may ask you to confirm account ownership before discussing or changing information, which prevents a request from exposing another person’s account data.
Wallet record check When a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the payment reference through the account support path. We use that reference to locate the relevant record and explain its status without asking you to share a wallet password or private security code.
Policy contact path For a question about collection, cookies, retention or deletion, contact us through the support channel connected to your account area. Describe the Privacy Policy section you mean, and we will route the request for a focused response rather than treating it as a general lobby question.
DATA HANDLING

What We Do With Your Account Data

We handle information by purpose: account details support sign-in, device signals help protect sessions, and payment references help reconcile wallet activity.

Account creation

When you open an account, we collect the details needed to create that account and connect it with the phone verification step. This lets us distinguish your session from another sign-in and gives our support team a specific record to investigate when access stalls.

Phone verification

Phone verification is an account security step before account access. We retain the verification result and related account reference so we can identify unusual sign-in questions, confirm that a request concerns the right account and avoid changing details on an unverified request.

Cookies and sessions

Cookies and similar session storage help remember the page state between sign-in and the lobby on your phone or desktop browser. They can also support security checks. Clearing browser storage may require you to repeat sign-in or phone verification, but it does not erase account records by itself.

Payment references

We use references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps to match an account payment record. We do not need your wallet password for that match. If a reference is incomplete, support may ask for the receipt number, not unrelated private details.

Device security

Device and browser signals can help us notice a session that differs from your normal account path. They support sign-in checks around the casino lobby, sportsbook pages and account area. These signals are used for security and troubleshooting, not as a replacement for your phone verification.

Retention and changes

We keep account, payment and support records for as long as needed for the stated purpose, security checks or applicable local requirements. You can ask us to correct inaccurate data or explain retention. A deletion request may be limited where a record is needed to resolve a payment or account issue.

Privacy Policy Questions For vonis500

These Privacy Policy answers address the account and access questions we hear most often before someone opens an account. They explain what happens around phone verification, wallet references, cookies, device sessions and requests for correction or deletion. When a situation depends on local rules, we state that directly so you know when our policy process may need an additional eligibility check.

The vonis500 Privacy Policy covers account details, phone verification, device and browser signals, cookies, payment references and support messages. It explains why we use each category, how it supports account security or payment matching, and how you can ask about correction, retention or deletion.

Our Privacy Policy concerns payment references, not your wallet password. For DANA, OVO, GoPay or QRIS activity, we may use a receipt or transaction reference to match the account record. Never send a wallet password or private security code through a support request.

Phone verification helps connect an account request to the right account holder before access or profile changes. We retain the verification result and related account reference for security and support checks. If you clear browser data, you may need to repeat this account step.

Cookies and session storage help keep your sign-in and page state consistent when you move between the account area and lobby on a phone or desktop browser. Clearing them can end a session or require another sign-in. The browser action does not itself delete account data.

Yes. Contact us through the account support path and identify the record you believe is inaccurate. We may ask you to confirm account ownership before making a change. For a wallet entry, include the DANA, OVO, GoPay or QRIS reference rather than unrelated personal details.

We retain account, payment and support records for the time needed for their stated purpose, security work or applicable local requirements. Our Privacy Policy does not promise one fixed period for every record. You can ask us to explain why a particular record remains stored.

Use the privacy contact path connected to your account area and name the Privacy Policy request, such as access, correction, retention or deletion. We may verify ownership before responding. Service access and eligibility depends on local law, so some requests may require an additional local-law check.