Reference

km789 Privacy Policy For Your Account Data

Our Privacy Policy explains how km789 handles the details connected with your account, from phone verification before access to wallet records for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice choicesPolicy requests
km789 km789 Privacy Policy For Your Account Data
CONTACT ROUTES

Policy Help For Login And Wallet Checks

A clear contact path matters when a privacy question appears beside a login or wallet issue.

Account contact Use the contact route inside your account when you need to ask how login records, phone verification or device signals are used under our Privacy Policy.
Wallet query For DANA, OVO, GoPay, QRIS or bank transfer records, provide the transaction reference and date so we can locate the relevant account entry.
Privacy request Ask for access, correction or removal through the same support route; we may request account details to confirm that the request comes from you.
DATA CONTROLS

Six Account And Device Privacy Controls

We apply the Privacy Policy through ordinary account operations rather than hidden settings. Phone verification helps us connect requests to the right account, while device signals can flag unusual login behaviour.

Collection

We collect contact, login, phone verification, device and transaction details when they are needed to open your account, protect access or answer a payment query.

Cookie use

Cookies and similar browser storage can remember sign-in preferences and help detect unusual sessions. You can manage browser permissions, though some account steps may then need repeating.

Account security

Phone verification and device checks help us identify an account session. Never share your password, wallet PIN or one-time code when asking about privacy.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match payment status without requiring the private login credentials of your wallet.

Retention

We retain account, activity and transaction records for service administration, security checks, dispute handling and legal duties, then assess whether continued storage remains necessary.

Your request

You may ask what data we hold, request a correction or ask about deletion through support. We verify your account before changing records tied to your identity.

Privacy Policy Questions About Your Account

These answers address the questions we hear before an Indonesian customer opens an account. Each response stays within the Privacy Policy, including account access, wallet references, cookies, device checks and requests made through our support route.

It covers account details, phone verification, login and device signals, cookies, game activity records, payment references and the ways we respond to access, correction or deletion requests.

Phone verification helps connect account access and privacy requests to the correct person. It also supports security checks when a login or wallet status appears unusual.

Yes. It explains how we may use DANA, OVO, GoPay, QRIS, bank transfer and virtual account references to match payment status with your account without requesting wallet passwords.

You can request access through the contact route in your account. We may ask for registered account details or phone verification so we do not disclose records to the wrong person.

Send a correction request through support and identify the account field that needs changing. We check the request against your account before updating contact, access or payment-linked records.

Retention depends on why a record exists. We may keep account, payment and security records for service administration, dispute handling and legal duties, then assess whether storage is still needed.

You can manage browser cookie permissions and device settings, but some login or verification steps may need to be repeated. The Privacy Policy explains why those signals support account security.