Reference

Open 62vip With Clear Privacy Terms

Your account details, wallet records and device activity are handled under the 62vip Privacy Policy, so you can understand what happens before opening an account.

Account accessWallet recordsCookie choicesContact requests
62vip Open 62vip With Clear Privacy Terms
REQUEST HELP

Contact Us About Privacy Policy

A clear support path helps you raise a Privacy Policy question without searching through unrelated pages.

Account support path Use the support route inside your account for a Privacy Policy request. Tell us whether your question concerns login records, phone verification, DANA, OVO, GoPay or QRIS activity, and we will direct it to the relevant handling step.
Receipt questions For a wallet or bank transfer query, attach the payment receipt reference rather than sending a full password or security code. We can use the reference to locate the relevant record while keeping unnecessary personal details out of the request.
Access changes If you want a copy, correction or removal of eligible personal records, state the request plainly and identify the account contact detail. We may verify your identity before making a change, where local law permits that process.
HANDLING YOUR RECORDS

Browse 62vip Privacy Controls

We keep the Privacy Policy practical by connecting each privacy question to a real account action.

Data collected

When you open an account, we may receive your contact details, phone verification result, login events and device information. When you use DANA, OVO, GoPay or QRIS, we may retain transaction references needed to match account activity with a payment status.

Cookie choices

Cookies can remember a sign-in state, language preference or security setting on your device. Our Privacy Policy explains their role, and you can ask support which cookie category relates to a particular page or account action.

Account security

We use phone verification and login signals to help protect account access. If a sign-in looks unusual, we may request an account step before discussing records or changing contact details, reducing the chance of disclosure to the wrong person.

Payment records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can help us check a receipt and wallet status. We do not need your wallet password for that check, so leave secret codes out of support messages.

Retention period

We keep personal records only while they serve account operation, security, dispute handling or applicable legal needs. The period can differ by record type, so ask us about a specific login event, receipt or contact message.

Change requests

You can ask for access, correction, restriction or removal of eligible records through the account support path. We will explain any identity check, exception or legal reason that affects the request where local law permits.

Find Privacy Policy Answers

These Privacy Policy answers focus on the account and wallet questions you are most likely to ask before opening an account or contacting support. They explain what we collect, why we retain it, how device activity and cookies fit into access, and how to request a change. If your situation is specific, use the account support path with the relevant receipt or account detail.

The 62vip Privacy Policy covers account details, phone verification, login events, device signals, cookies, support messages and payment references. It also explains use, security, retention and request options for records connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We may collect the contact details you provide during account opening, your phone verification result, login history, device signals and messages sent to support. Payment activity may add a transaction reference or wallet status, rather than your wallet password or secret security code.

DANA and QRIS references can help us match a receipt with the correct account and check a wallet status. OVO, GoPay, bank transfer and virtual account records may serve the same purpose. We use those references for account and payment handling, not unrelated profiling.

You can contact us through the account support path and ask for access to eligible records held about your account. Include the connected phone or email detail and the record type you need. We may verify your identity before responding, and access depends on local law.

Send a correction request through account support and identify the field that is wrong, such as a contact detail or account reference. We may ask you to complete phone verification or another account step before changing it, where local law permits.

Retention varies by record. Login and device events may support security checks, while payment references can help resolve receipt questions. We retain records while needed for account operation, security, disputes or legal duties, then assess whether continued storage is necessary.

Yes. Ask support which cookies relate to sign-in, page preferences or security on your mobile browser. We can explain the relevant category and available choices. Removing some cookies may affect access steps, and any request remains subject to local law.