Reference

virus4d Privacy Policy For Your Account

The virus4d Privacy Policy explains how we use account details, wallet records and device signals when you open an account or browse our lobby.

Account dataWallet recordsCookie choicesPhone verification
virus4d virus4d Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Policy Help Beside Your Account

A clear contact route helps when a privacy question sits beside a login or wallet question. We ask you to use the support path connected to your account so we can locate the right record without requesting unnecessary details. Include the email or phone used for your account, the device path you followed, and the request you want handled. We will use that context to direct the case to the appropriate privacy contact.

Team online

Account support

Open the account support route and describe whether your request concerns phone verification, a device record or a correction to your profile details.

Cashier context

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, include the payment reference and date so we can separate wallet data from account data.

Receipt check

If a receipt or status check is part of your privacy request, send the relevant reference rather than a full wallet screenshot; we use only what the case needs.

HANDLING PRACTICE

How We Handle Your Privacy Requests

Our privacy process follows the same account path you already use: identify the relevant record, confirm that the request comes from you, then apply the permitted change.

Account data

We may hold your account name, contact route, phone verification status and selected settings so we can maintain the account…

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be linked to account activity, while the payment provider…

Cookie controls

Cookies and similar device signals help retain session choices and measure basic site operation; you can adjust browser cookie settings…

Security checks

Phone verification and sign-in checks help us distinguish an account request from an unverified device.

Retention period

We retain account, support and payment references only as long as needed for the stated purpose, dispute handling, security review…

Change requests

Ask us to access, correct or delete eligible data through account support.

Privacy Policy Questions From Indonesia

These answers cover the requests we expect when you check the Privacy Policy before opening an account. They also explain what to send when your question involves a device, wallet reference or phone verification step.

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

Use the account support route and state that you want a copy of your personal account data. Add the phone or email connected to the account so we can verify the request.

Yes. The policy explains how we may use QRIS, DANA, OVO and GoPay references for account matching, receipt checks and status questions. Payment providers may keep separate records under their own terms.

Basic device and browser signals help retain a session, identify repeated sign-in problems and review unusual access. We use these signals for account operation and security checks, not unrelated profiling.

You can request a correction or deletion of eligible data through account support. We may retain records needed for security, dispute handling or legal duties, and access depends on local law.

Send the request through the account support path, using your account contact route and a short description of the issue. For wallet records, include the payment reference and date instead of a full screenshot.

The same Privacy Policy applies on mobile and desktop. Browser cookies, device signals and phone verification may work differently by device, while access remains where local law permits.