Reference

Privacy Policy For Your v87 apk Account

v87 apk Privacy Policy explains how we collect, use and protect the account details linked to your lobby access, including wallet records from DANA and QRIS.

Clear data purposesWallet record clarityAccount access controlsPolicy request path
v87 apk Privacy Policy For Your v87 apk Account
HELP CHANNELS

Get Privacy Help Near Account Access

A clear contact route matters when your personal data or wallet record needs attention. We ask you to start from the account help channel, where you can identify the registered phone number and describe the policy request without sending passwords. For a payment-related question, include the relevant receipt reference from DANA, OVO, GoPay or QRIS so we can locate the correct record.

Team online

Account data request

Use the account help channel to ask what personal details are linked to your account. We may ask for the registered phone number and an account step that confirms your identity before releasing or changing records.

Wallet record query

For a DANA, OVO, GoPay or QRIS record, send the payment reference and approximate transaction date through the cashier support path. We use those details to separate your receipt from another account before discussing the record.

Access concern

If a privacy request affects login or phone verification, tell us which device path you used, such as Android browser or desktop browser. We can then check the account event without asking you to share your password.

DATA PRACTICES

How We Handle Your Account Records

We handle policy requests through identifiable account records rather than open public messages. Phone verification helps us confirm that the person asking for access, correction or deletion is connected to the account…

Collection

We collect details you enter during account creation, including contact data needed for phone verification. Browser and device signals may also be recorded when you open the lobby, so we can maintain a session and detect unusual access.

Cookie use

Cookies and similar storage can keep your login state, language choice and device path available between pages. You can manage browser storage through your device settings, although clearing it may require phone verification again before account access.

Account security

We use the registered phone step to check identity before discussing sensitive account data. Never send a password in a support message; if access looks unfamiliar, tell us the device path and time shown in your account.

Payment matching

DANA, OVO, GoPay and QRIS references help us match a wallet event to the correct account. Bank transfer and virtual account records may be checked in the same way when you ask about a transaction status.

Retention

We keep records only for the operational, security or account purpose described in this policy, subject to the retention needs of that record. A deletion request can be assessed after we confirm your identity and any linked transaction.

Policy changes

When this Privacy Policy changes, we place the updated wording on this page and show the effective date. You can contact us through account help to ask what changed or request a copy of the version connected to your account.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers focus on the account, device and wallet questions you may have before opening access. We keep each response tied to the records we actually use, including phone verification, browser storage and payment references. If your question is not listed, use the account help path with your registered phone details.

The v87 apk Privacy Policy covers account details, phone verification, browser storage, device signals and payment references. It explains why we use those records for login security, wallet matching and account support, plus how you can ask for access, correction or deletion where local law permits.

The policy can apply to references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use a reference and transaction status to identify the correct account record; we do not need your wallet password in a support message.

Start through the account help channel and state that you want an account data request. Include your registered phone number and the device path used for access. We may complete phone verification before sharing records so another person cannot obtain your account details.

Yes. Our Privacy Policy explains that cookies or similar browser storage can retain session state, language choice and device preferences on mobile or desktop. Clearing storage through your browser settings may remove that state and require phone verification when you return.

You can request a correction through account help, using the registered phone number to identify the account. Describe the field that is wrong and the replacement detail. We verify the request first, then confirm whether the change can be applied under local requirements.

Retention varies by record type and its operational, security or account purpose. Payment references may need to remain linked to a transaction status, while other details can be assessed separately. Contact us for a record-specific answer rather than assuming every field has the same period.

Yes. Account access and any eligibility check depends on local law. Our Privacy Policy explains how related account and verification records are handled where local law permits. If your location or request creates a restriction, account help can explain the applicable next step.