Reference

Privacy Policy for Your venus88 Account

Our Privacy Policy explains how venus88 handles the account details, device signals and wallet records connected with your access to the lobby.

Account dataWallet recordsCookie choicesPolicy requests
venus88 Privacy Policy for Your venus88 Account
CONTACT ROUTES

Get Help With a Privacy Request

A clear support route helps you ask about your data without repeating the whole account story. Start from the login or cashier help path and include the phone number linked to your account, the relevant date and the kind of request you are making. We may ask for an account check before discussing records, because a privacy request must reach the correct account holder. Keep payment references private and do not send wallet passwords or full security codes.

Team online

Account access

If you cannot complete phone verification or reach your account, use the support route beside login. Tell us whether the issue concerns a new device, a blocked session or a changed phone number so we can separate access data from a general account question.

Wallet records

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record, include the transaction reference and date. We can use that detail to locate the relevant cashier entry without asking you to disclose a wallet password or private security code.

Policy requests

For a copy, correction or deletion request, name the account email or phone number and describe the exact data involved. We review the request against account ownership and local requirements, then use the same support path to explain the next step.

DATA PRACTICES

How We Handle Your Account Data

The practical side of this Privacy Policy is visible in everyday account actions: phone verification before access, wallet matching after a cashier request, and device checks when a session changes.

Collection

We collect details you enter during account creation, including contact data used for phone verification. We also receive operational records from login, device and cashier actions, such as a QRIS reference or a bank transfer status, when those events relate to your account.

Use

Account data lets us confirm access, connect a payment reference to the correct account and answer a support request. Device and security signals help us investigate unusual sessions, while transaction records help us explain whether a DANA, OVO or GoPay status is pending.

Cookies

Cookies can keep a session active, remember selected settings and help us identify technical faults between login and the lobby. Your browser can block or remove them, but doing so may require fresh verification and can change how account pages load on mobile.

Account security

We use phone verification and session checks before discussing account details. If you change device or contact data, we may request another account check. Never place a wallet password, one-time code or complete payment credential in a support message.

Retention

We keep account, support and payment records for the period needed to operate the account, resolve disputes, detect misuse and meet legal duties. When a record is no longer needed for those purposes, our retention process removes it or separates it from direct account details.

Your requests

You can ask us to access, correct or delete eligible account data through the policy support route. We first confirm ownership, define the requested records and check any legal reason for keeping them, then tell you what action can be taken.

Privacy Policy Questions About venus88

These answers focus on the questions we expect you to ask before opening an account or sending a wallet payment. They explain what the Privacy Policy means for phone verification, device use, cookies, payment references and data requests. If your case involves a specific account record, use the support path described above and avoid sharing passwords or one-time codes.

It covers account details, phone verification, login and device events, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains why we use, retain and protect those records.

Phone verification helps connect account access to the correct contact detail and supports checks when a new device or changed phone number appears. We may use the result during account support, but you should never send the verification code in a message.

Yes. The policy covers transaction references, timestamps and status details created when you use DANA or QRIS, as well as OVO, GoPay, bank transfer and virtual account records. We use these details to match cashier activity and answer payment-status requests.

You can request a correction through the policy support route. Include the account phone number or email, identify the incorrect field and explain the requested change. We confirm account ownership first and may retain an earlier record when security or legal duties require it.

Cookies can remember a session and selected settings, while technical signals help us diagnose page or device issues. You may remove or block cookies in your browser. After that, login may ask for another check and some account pages may behave differently.

We keep payment and account records for the period needed for account operation, security checks, dispute handling and legal duties. The exact period can differ by record type and local requirement. When the purpose ends, we remove the record or separate it from direct identifiers.

Send a request through the support path connected with login or the cashier area. State that you want a data copy, provide the account contact detail and identify the date range if known. We verify ownership before locating and preparing eligible records.