Reference

virus88 Privacy Policy for Your Account

Our Privacy Policy explains how virus88 handles the details you provide when opening an account, signing in, using DANA or QRIS, and browsing titles such as Lightning Roulette.

Clear data purposesWallet record contextAccess request pathCookie choices
virus88 virus88 Privacy Policy for Your Account
PRIVATE HELP ROUTES

Wallet Receipt Privacy Support

A clear contact route helps you ask about personal data without exposing more than necessary.

Account access If you cannot sign in, use the account support route and share the registered contact detail you can safely confirm. We use it to locate the correct record before discussing private account data.
Payment references For DANA, OVO, GoPay, or QRIS questions, send the payment reference and date rather than a wallet password. This gives us enough context to check status while limiting sensitive information.
Policy requests Ask for a copy, correction, or deletion assessment through the same support route. We will explain the next account step and any identity check needed before releasing personal data.
COOKIE AND LOGIN CARE

How Cookies and Login Security Work

We treat Privacy Policy controls as part of the account flow, not as a hidden page. The browser may store cookies for sign-in continuity, language preferences, fraud checks, and page measurement; you…

Data collection

We collect account details, contact records, device and session signals, support messages, and payment references when they are needed for access, verification, payment matching, or a Privacy Policy request.

Cookie choices

Cookies can keep a browser session active, remember selected settings, and help identify unusual sign-in behaviour. Your browser controls let you remove or restrict them, though some account steps may then require another sign-in.

Account security

Before discussing private records, we may compare your sign-in details, device signals, or a verification step. Never place a password, wallet PIN, or one-time code in a support message.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references help us reconcile a transaction. We use the reference and status details for checking, not for collecting your wallet credentials.

Retention timing

We retain records only for the period needed for account operation, security checks, dispute handling, or a legal duty. A retention question can be sent through the account support route for assessment.

Change requests

You can ask us to access, correct, or assess deletion of personal data through support. Include the account contact detail and request type; we may verify ownership before making a change.

Privacy Policy Answers for Your Account

These Privacy Policy answers cover the questions you may have before opening an account or sending a wallet receipt. We keep each answer tied to the actual data path: browser cookies, login checks, payment references, support contact, and requests for access or correction. If your situation is not listed, use the account support route and describe the specific record involved.

It covers account details, contact information, login and device signals, cookies, support messages, verification records, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

We use account details to create access, confirm ownership, protect sign-in sessions, match payment references, answer support requests, and process a correction or access request where local law permits.

Yes. The policy includes transaction status, dates, reference numbers, and settlement details linked to DANA or QRIS. We do not need your wallet PIN to investigate a receipt or payment status.

Use the support route connected to your account and state that you want a Privacy Policy access request. Provide a safe account identifier; we may verify ownership before sharing records.

Yes. Send a correction request through account support with the inaccurate detail and the correct version. We will explain the verification step and assess the request under applicable local law.

Cookies can support sign-in continuity, selected settings, security checks, and page measurement. You can restrict them in your mobile browser, but a later login or account step may be required.

Use the account support route and identify the concern, such as login data, a QRIS receipt, cookie settings, retention, or correction. Do not include passwords, wallet PINs, or one-time codes.