Reference

viv388 Privacy Policy For Your Account

The viv388 Privacy Policy explains what we collect, why we use it and how you can ask about your account data before opening an account.

Clear data purposesWallet record detailsAccount request pathIndonesia access terms
viv388 viv388 Privacy Policy For Your Account
CONTACT ROUTES

Ask About Your Privacy Policy Rights

A clear request helps us locate the right account record without exposing details to the wrong person.

Account access route If you cannot enter your account, use the access help path beside login. We first confirm the account details you provide, then explain which Privacy Policy request can be handled without revealing private records to an unverified person.
Wallet record query For a DANA, OVO, GoPay or QRIS receipt question, send the reference through the account support path. We use that reference to locate the related record and explain its status without asking you to share a wallet password.
Correction request When your phone number or account detail needs correction, tell us which field is wrong through support. We may request a phone verification step before changing it, helping keep the Privacy Policy request connected to the correct account.
DATA PRACTICES

How We Handle Account Data

We keep the Privacy Policy practical by linking each data practice to an account action you can recognise.

Account details

We use your account identifier and phone details to create the right account record and support login checks. Before changing a key detail, we may ask you to complete phone verification so another person cannot redirect account communication.

Device signals

When you move from a mobile browser into the lobby, we may record device type, browser details and access time. These signals help us compare a new login with normal activity; they are not a request for your device contents.

Cookies

Cookies can keep a session active and remember necessary page choices while you move between login and account areas. You can manage cookie settings in your browser, although turning off required cookies may interrupt access to parts of the Privacy Policy page.

Wallet references

A DANA, OVO, GoPay or QRIS reference can be retained to match a payment enquiry with the correct account. We do not ask for your wallet password through support, and you should never place that password in a message.

Retention checks

We retain records for the period needed for account support, transaction checking, security investigation or a legal requirement. When a purpose ends, our handling follows the applicable retention process rather than keeping every record without a reason.

Your requests

You can ask for access to your personal data, correction of an inaccurate field or an explanation of a processing purpose. Send the request through account support, identify the account clearly and complete any ownership check needed before we respond.

Privacy Policy Questions For viv388

These Privacy Policy answers focus on the account questions you are most likely to ask before using viv388 from Indonesia. We explain the records connected with login, phone verification, mobile access and local wallet references, along with the route for requesting access or correction. If your situation is not covered, use the support path inside the account area and describe the specific record or action you want us to check.

The viv388 Privacy Policy covers account identifiers, phone details, verification records, login activity, device signals, cookies and payment references. We use each category for a stated account, support, security or legal purpose, and you can ask us to explain a category connected with your account.

Phone verification helps us confirm that the person requesting account access or a data change controls the relevant account. It can be used before correcting a phone number, discussing a wallet reference or responding to a Privacy Policy request involving private account details.

Yes. The Privacy Policy covers payment references associated with DANA, OVO, GoPay and QRIS when those references help us match a receipt, account or status question. We do not ask for your wallet password, and you should send payment details only through the account support path.

When you use a mobile browser, we may record device type, browser details and approximate access time. These signals help us identify unusual login activity and keep a session working. We do not describe this as access to your photos, contacts or other unrelated device content.

Open the account support route and state whether you want to see a data category or correct an inaccurate field. Include your account identifier through that protected path, then complete any ownership check. Our ability to fulfil a request depends on local law and applicable retention duties.

Retention depends on why the record exists. Account support, transaction checking, unusual-login investigation and legal duties can require different periods. We do not promise one fixed period for every record; you can ask support why a particular account or wallet reference remains in our records.

Use the support route inside your account or the account-access path beside login. Describe the exact data or cookie question and avoid sending a wallet password. We can explain the relevant Privacy Policy section, confirm the request route and tell you what ownership check is needed.