Reference

apk slot 777 Privacy Policy For Indonesia

apk slot 777 keeps this Privacy Policy focused on the details needed to open your account, verify your phone and handle wallet activity through DANA, OVO, GoPay or…

Account detailsWallet recordsDevice choicesYour privacy requests
apk slot 777 apk slot 777 Privacy Policy For Indonesia
HELP WITH REQUESTS

Privacy Help Beside Your Account Path

A clear contact route matters when a privacy question appears during phone verification or a wallet status check.

Account privacy request Use the signed-in support path to ask about phone verification records, login events or stored account details. We may confirm your identity through the account step before correcting a record or changing the way we contact you.
Wallet record question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the transaction date and reference through account support. We use the cashier record and account event together to locate the issue without asking for your wallet password.
Access and deletion request Ask us to provide eligible account records, correct inaccurate details or assess a deletion request through the same secured support route. We explain any records that must remain available because of an active account or legal requirement.
HANDLING YOUR DATA

What We Protect Across Mobile And Wallet Use

Our privacy handling follows the path your account actually takes: phone verification, mobile or desktop sign-in, lobby access, cashier activity and support contact.

Account security

Phone verification is checked before account access, and sign-in events can be used to identify an unusual device or session. We use these signals to protect your account rather than to request your wallet password or unrelated device content.

Cookies and sessions

Our mobile browser path may store cookies or similar session details so your sign-in and policy choices remain connected. You can manage browser storage through your device settings, though clearing it may require phone verification again.

Payment references

For DANA, OVO, GoPay and QRIS activity, we keep the reference and status needed to match a cashier request. Bank transfer and virtual account records are handled in the same limited way, without storing your external banking password.

Retention decisions

We retain account, support and transaction records only while they serve account security, reconciliation, dispute handling or a legal need. When a record no longer serves one of those purposes, we assess deletion or removal of direct identifiers.

Correction requests

If your phone detail or another account record is inaccurate, contact us through the signed-in support route. We compare the request with the account step, correct eligible fields and tell you when a record cannot be changed.

Policy contact

Questions about this Privacy Policy should include the account phone number and the specific request, submitted through secured support. We use that context to locate the relevant record and avoid exposing account details to an unauthorised person.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the questions you may have before opening an account or checking a wallet record. We keep the wording tied to the actual account path: phone verification, mobile browser access, cashier references and secured support. If your question is not listed, send it through the account support route so we can check the relevant record.

It covers account details, phone verification, sign-in events, device and cookie signals, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, correction, access and eligible deletion requests.

We use your phone number to create the account path and complete verification before access. It helps connect sign-in activity with the correct account and lets support check a request. We do not ask for your external wallet password through this process.

Yes. The Privacy Policy covers DANA, OVO, GoPay and QRIS references and status details used to match a cashier action. For bank transfer or virtual account activity, we may also retain the reference, amount and sending bank needed for reconciliation.

Use the secured support route inside your signed-in account and state that you want an eligible account-data request. Include the relevant date or record type. We may complete phone verification first, then explain which records can be provided and in what form.

Yes. Send a correction request through account support and identify the field that is inaccurate. We compare it with your account step and available records before changing it. If a field must remain for security or legal reasons, we explain that restriction.

We keep records while they are needed for account security, payment matching, support, dispute handling or a legal requirement. After that need ends, we assess deletion or removal of direct identifiers. The applicable period depends on local law and the record type.

Yes. It covers the mobile browser path from phone verification to account access and the lobby, including cookies, session details and device signals used for security. Browser storage can be managed in your device settings, although clearing it may require verification again.