Reference

vi555 Privacy Policy for Indonesia Accounts

Our vi555 Privacy Policy explains what we collect when you open an account, use a mobile browser, check a wallet status or contact support.

Account clarityWallet data contextMobile accessPolicy requests
vi555 vi555 Privacy Policy for Indonesia Accounts
CONTACT ROUTE

Where to Ask About Account Data

A clear contact path matters when a wallet reference or account detail looks unfamiliar. We keep privacy questions close to the account-help route so you can identify the record, explain the issue…

Account access Use the support path attached to your account when you need to ask how an email, phone number or verification record is used. We may request enough account detail to locate the correct record, but you should keep passwords and full wallet credentials out of the message.
Wallet reference For a DANA, OVO, GoPay or QRIS question, share the visible reference, date and status rather than private wallet credentials. We use those details to locate the matching transaction record and explain whether the data is held for account, payment or security purposes.
Correction request If your contact detail or account record is inaccurate, tell us which field needs attention and why. We may verify that you control the account before changing it, helping us avoid altering the wrong profile or exposing another person’s data.
ACCOUNT SAFETY

How vi555 Protects Account Details

Privacy is applied during ordinary account actions, not only when you read this page. We limit internal access to records needed for account support, payment matching or security checks, and we keep…

Account records

We use the details you submit during account creation to identify your profile, support sign-in and complete phone verification before account access where that step is required. Keeping these fields accurate helps us respond to a privacy request without confusing your record with another account.

Payment references

A DANA, OVO, GoPay or QRIS record can show a reference, status and amount linked to an account action. We use this limited context to match the request and investigate an account question, rather than asking you to send a wallet password or private security code.

Device signals

When you move from login to the lobby on a mobile browser, technical signals such as browser type, connection details and session events may be recorded for access protection. These signals help us examine unusual sign-ins without treating a device label as your identity by itself.

Cookies

Cookies and similar session tools can keep your account path working between pages and help us understand whether a sign-in session is active. Your browser settings control some cookie behaviour, although restricting necessary session tools may affect access to the policy or account area.

Retention periods

We retain account, support and payment-linked records only for the period needed for the stated purpose, account security and applicable legal duties. The exact period can differ by record type, so your request should name the account field or transaction reference you want us to assess.

Policy changes

If we change this Privacy Policy, we will place the updated wording on this page and show the effective date. Check the page before opening an account or using a new wallet path, then contact support if a change affects a request you already submitted.

Privacy Policy Answers for Your Account

These Privacy Policy answers address the account and wallet questions you may search before opening access. We keep the wording tied to actual actions: phone verification, mobile-browser sessions, payment references and requests through account support. If your situation involves a legal access condition, it depends on local law; the support route can help you identify the right request without asking you to post private credentials in a message.

The vi555 Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains access, correction, deletion and retention requests where local law permits.

We use your submitted phone or contact detail to create and locate your account, support sign-in and complete verification before account access when required. It also helps us confirm that a privacy request comes from the person connected with the record, rather than changing another account.

Our policy describes payment references, status and matching details for DANA, OVO, GoPay and QRIS, not your private wallet password. When you contact us about a transaction, send the visible reference and date only. Never include a password, PIN or full security credential.

Use the account support path and state whether you want access to a record, a correction or another request allowed where local law permits. Include the account contact detail and the specific field or payment reference. We may verify account control before responding or making a change.

Yes. The Privacy Policy covers technical signals created when you sign in or move through the account path on a mobile browser, such as browser type, connection details and session events. We use them for session operation and access protection, not as a substitute for your account identity.

Retention varies by record type and the purpose for holding it. Account, support and payment-linked records may be kept for account security, service handling and legal duties. Ask through account support with the record type you mean, and we will explain the applicable retention basis where local law permits.

The current Privacy Policy appears on this page with its effective wording. If a change affects your account, wallet reference or earlier request, use the support path connected with your account and identify the section or date. We can then direct your question to the relevant privacy handling route.