Reference

vp555 Privacy Policy For Your Account

vp555 Privacy Policy explains what we collect when you open an account, use the lobby, or check a wallet status, and why each detail is needed.

Clear data purposesWallet record contextDirect request pathIndonesia access terms
vp555 vp555 Privacy Policy For Your Account
CONTACT ROUTES

Three Ways To Ask About Privacy

Your privacy request should reach the team handling the related account record. We keep the route practical: identify the account, state the change or question, and include the relevant payment or device detail only when it helps us locate the record. If you are in Medan, Semarang, or elsewhere in Indonesia, the same request path applies. We may ask for a phone verification step before releasing account data or changing contact details.

Team online

Account privacy request

Use the privacy contact path to ask what account data we hold, why we use it, or which detail needs correction. Include your registered phone number and a short request so we can locate the right record without asking you to resend unrelated personal data.

Wallet record question

For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference, tell us the date and status shown in your account. We use that limited context to find the transaction record and respond without requesting your wallet password or full banking credentials.

Access and deletion request

Ask us to review, correct, or remove eligible personal data through the same support route. We first verify that you control the account, explain any record we must retain for a lawful purpose, and confirm the action or reason for keeping it.

DATA HANDLING

Six Controls Behind Our Privacy Policy

We handle privacy as an account operation, not as a statement placed apart from daily use. Registration, phone verification, sign-in, wallet status, and support activity each create different records with different purposes.

Account data

We may collect your name, phone number, account identifiers, sign-in events, and verification status. These fields help us create the correct profile and distinguish your request from another account. We do not need your wallet password to discuss a DANA, OVO, GoPay, or QRIS reference.

Cookies and devices

Cookies and device signals can remember a session, identify unusual sign-in behaviour, and keep your selected account path available on mobile or desktop. You can manage browser cookies through your device settings, although removing them may require you to verify the account again.

Payment references

A payment record can include the rail used, a reference number, amount status, and matching account details. For bank transfer or virtual account checks involving BCA, BRI, Mandiri, or BNI, we use the reference needed to reconcile the request rather than collecting unrelated banking data.

Account security

Phone verification before account access helps us confirm control of the registered number. We may compare sign-in time, device context, and account changes when a session appears unusual. This can pause a request while we check ownership, protecting your data from an unauthorised change.

Retention periods

We retain personal data only for the period needed for account operation, security checks, dispute handling, or a lawful record requirement. When a retention reason ends, we remove, anonymise, or restrict the record according to our internal handling process and the request details.

Policy changes

When this Privacy Policy changes, we update the page so you can compare the current purpose and contact path before using your account. A material change may require a fresh acknowledgement or account step, with access still handled where local law permits.

Privacy Policy Answers For vp555

Most privacy questions come down to three points: what we collect, why we need it, and how you can ask us to act. The answers below use the account steps and payment references you are likely to see when accessing vp555 from Indonesia. They also explain why identity checks may come before a data request, even when the request concerns only a phone number or wallet status.

The vp555 Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages, and payment references. It explains how we use, protect, retain, correct, or remove those records when you access the service where local law permits.

We use your phone number to create the account identity, complete the phone verification step, and help protect access when a sign-in or account change appears unusual. It also lets us locate your privacy request without asking you to provide unnecessary personal data.

Yes. The Privacy Policy covers the payment references connected with DANA and QRIS, including the rail used, account match, reference, and status needed for reconciliation. We do not ask for your wallet password, and we use only the payment context needed for the request.

You can ask us to correct eligible account data through the privacy contact path. State which field is wrong and provide the registered phone number. We verify account control first, then confirm the correction or explain why a particular record must remain unchanged.

Send a data access request through the support route shown on this page, using your registered account details. We may complete phone verification before sharing a copy. The response can cover account, device, support, and payment-reference records that we are permitted to provide.

We keep personal data for the time needed to operate the account, protect access, resolve a payment or support dispute, or meet a lawful record requirement. After that purpose ends, we remove, anonymise, or restrict the record under our retention process.

You may request removal of eligible account data through the privacy contact path. We first verify ownership and check whether a security, dispute, payment, or local-law reason requires retention. We then remove or restrict what can be changed and explain any remaining record.