Reference

Open 6svip apk Privacy Policy Before Account Access

6svip apk Privacy Policy shows how we handle your account, device and wallet details before you enter the lobby.

Clear data purposesWallet privacy contextRequest path included
6svip apk Open 6svip apk Privacy Policy Before Account Access
CONTACT ROUTES

Browse Support Paths For Privacy Requests

A clear support route helps when you want to ask about a record, correct an account detail or understand a wallet reference.

Account data request Send a request through account support when you want a copy of the personal…
Wallet reference check For DANA, OVO, GoPay or QRIS records, provide the payment reference and approximate date…
Correction request Tell our support route which account field is inaccurate and what should replace it.
DATA PRACTICES

Switch Through Privacy Controls With Clarity

We keep this policy practical by linking each data use to an account step, device action or support need.

Account details

We use your phone number and basic account fields to create access, complete clear phone verification and connect a support request to the right profile. Do not send wallet PINs or sign-in codes in a message.

Device signals

Browser type, operating system, session time and security events can help us identify unusual access or restore a mobile session. These signals support account protection; they are not a separate profile about your interests.

Cookies and storage

Cookies or local storage can remember a sign-in state, language setting and policy choice on your device. You can clear them through your browser settings, although clearing storage may require you to verify your phone again.

Wallet records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match payment status to the correct account. We do not ask for a wallet password, card PIN or one-time code through support.

Retention periods

We keep records only for the period needed for account operation, dispute handling, security checks or a legal duty. When a record is no longer needed, our process removes it or separates it from direct account identifiers.

Your requests

You can ask for access, correction, deletion or a clearer explanation of your personal details through account support. We confirm ownership first, then respond using the contact route attached to your account.

Explore Answers About 6svip apk Privacy Policy

These Privacy Policy answers address the questions we expect before you open an account: what we collect, why wallet references appear, how device records work and how to request a change. Read the relevant answer first, then use account support if your situation needs a record-specific response. We keep the wording focused on your data and access choices.

It covers account details, phone verification, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security steps, your request rights and policy changes.

A wallet or QRIS action can create a reference, status or timestamp that helps match a payment event to your account. We use that narrow transaction context for reconciliation and support, not to request your wallet password, PIN or private access code.

We may use your phone number for account creation and clear phone verification. We can also record browser, operating system, session and security signals when you access the site, including from a mobile device. These records support access and account protection.

Use the account support route and state that you want a copy of the personal details linked to your profile. Include your registered phone number and a clear request. We confirm ownership before sharing account records through the available contact path.

Yes. Tell support which field is wrong and what should replace it. We may ask you to complete phone verification before making the change. If the field comes from a payment reference, include the relevant DANA, OVO, GoPay or QRIS receipt detail.

The retention period depends on why the record exists. We keep account, security, support or payment references only as long as needed for operation, dispute handling, safety checks or a legal duty, then remove or separate them when no longer required.

You can clear cookies and local storage through your browser settings, and you can contact account support about a privacy request. We may need to confirm ownership before deletion or withdrawal of a request, especially when a legal or security record must remain.