Reference

Open the viv188 Privacy Policy

viv188 Privacy Policy explains what we collect when you open an account, verify your phone, browse Live Blackjack Prestige or use DANA, OVO, GoPay and QRIS.

Account data explainedWallet records clarifiedContact choices includedCookie controls outlined
viv188 Open the viv188 Privacy Policy
CONTACT ROUTES

Switch to account privacy support

When a privacy question affects your account, we keep the next step close to the login and cashier paths.

Account help Use the account help path when your phone verification, sign-in record or personal detail needs checking. We may ask for account identifiers already linked to your profile, but we do not ask you to send a password or wallet PIN.
Wallet status For a privacy question about DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, mention the payment rail and date shown in your account. This helps us separate a transaction reference from unrelated account activity.
Policy request Ask for a copy, correction or clarification through the available support contact shown on the site. Include your registered phone number and request type, then keep the reply reference so we can follow the same case without repeated disclosure.
HANDLING DETAILS

Browse how viv188 handles your data

Privacy Policy choices work best when you know what happens at each account step. We separate identity details from payment references, use access signals to investigate unusual sign-ins and keep cookie behaviour…

Account collection

We collect the details you provide when opening an account, including your phone number and verification result. Sign-in events and account changes can be linked to that profile so we can respond to a request about the correct record.

Payment references

A DANA, OVO, GoPay or QRIS payment can create a reference, status and time record in the account history. Bank transfer and virtual account entries are handled as transaction details; we do not need your banking password to identify them.

Cookie choices

Cookies can keep a session active, remember selected settings and help us detect repeated access attempts. You can review cookie controls in your browser, although removing required cookies may sign you out or interrupt the account path.

Device security

We may record device type, browser information and access timing when you sign in. These signals help us compare a normal phone session with an unusual request, including a sudden change before account or wallet details are opened.

Retention steps

We keep account, support and payment references for as long as needed for the stated account purpose, security checks and applicable legal duties. When a record no longer needs retention, our handling follows the removal process available under local requirements.

Change requests

You can ask us to correct inaccurate account details or explain the data connected to your profile. We may verify your phone or another account step first, then record the request and communicate the result through the available support route.

Ask about Privacy Policy and viv188

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet is connected. They cover the data linked to your phone, the records created by DANA and QRIS, browser cookies, correction requests and access wording for Indonesia. If your situation is more specific, use the policy contact route and describe the account step involved without sending a password or wallet PIN.

The viv188 Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It explains why we use each category, how we protect access and how you can request clarification or a correction through the available account support path.

Yes. A DANA or QRIS payment may create a reference, status and time entry connected with your account activity. The same approach applies to OVO, GoPay, bank transfer and virtual account records. We use these references to identify a transaction, not to collect your banking password.

Phone verification links an account request to the person controlling the registered number and helps us investigate unusual sign-in activity. It also lets us confirm which record you mean when you ask about the Privacy Policy, a wallet reference or a correction to account details.

You can contact us through the policy support route to ask what account information is connected to your profile or to request a correction. We may check your registered phone and request details first, so we do not disclose or change information for the wrong account.

Cookies can maintain your sign-in session, remember settings and help identify unusual access. Your browser controls let you remove or restrict them, but required cookies may be needed for account access. The Privacy Policy explains these uses without requiring you to share a password.

We retain account, support and payment references for the time needed for the stated account purpose, security checks and applicable legal duties. When retention is no longer needed, handling follows the removal process available under local requirements and the rights that apply to you.

Yes. Access and eligibility depend on local law. The Privacy Policy describes our data handling for the site, while local requirements can affect whether an account or particular account action is available. Contact support if you need the wording applied to your account location.