Reference

k200m Privacy Policy: Your Account Data Path

k200m Privacy Policy shows what we collect when you open an account, move from login to the lobby, or check wallet status through DANA and QRIS.

Account dataDevice choicesWallet recordsPrivacy requests
k200m k200m Privacy Policy: Your Account Data Path
PRIVACY HELP DESK

Where to Ask About Your k200m Data

A clear contact route helps when a privacy question appears beside a login or wallet status issue. Use our support contact path from your account area and tell us the phone number linked to the account, the request you want handled, and the relevant DANA, OVO, GoPay or QRIS reference if one is involved. We use those details to locate the correct record without asking you to send a full password or security code.

Team online

Access request

Ask us to identify the account records connected with your phone verification, login history or wallet reference. We may ask for account details that confirm you are making the request for yourself.

Correction request

If your account detail is outdated or incorrect, send the field that needs changing through our support contact path. We check the account step and update eligible records after confirming the request.

Wallet privacy query

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account concern, include the transaction reference and date. We can trace the privacy side of the status without requesting your wallet password.

DATA HANDLING

What We Do With Account Records

Privacy depends on practical handling, not a promise hidden in fine print. We separate account access details from support context where the service allows, restrict internal access by…

Account details

We collect details needed to create and maintain your account, such as your phone number and verification result.

Wallet references

A DANA Instant Payout, QRIS, OVO or GoPay reference can be stored with account and status details.

Cookies and devices

Our mobile and desktop pages may use cookies or device signals for session continuity, fraud checks and language or region…

Security checks

Phone verification comes before account access, and sensitive changes may require another account check.

Retention approach

We keep records only as long as needed for the stated account, payment, security or legal purpose.

Your request route

You can contact us to ask what data is held, request a correction, question a use or ask about deletion.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account questions we expect when you come from an Indonesian phone, mobile browser or local wallet. They explain the practical route for checking records, changing details and asking why a payment reference or device signal appears in your account history. If your question concerns eligibility, access depends on local law.

The k200m Privacy Policy covers account details, phone verification, device and cookie signals, activity records, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains your access, correction and deletion request options.

We use phone verification to connect an account with the person requesting access and to reduce mistaken or unauthorised changes. When you ask about Privacy Policy data, we may use the same account step to confirm that the request belongs to you.

Yes. The Privacy Policy covers references and status details linked to QRIS, DANA, OVO and GoPay, along with bank transfer and virtual account records. We use these details to reconcile account activity, answer support questions and identify the relevant transaction.

You can contact our support path and request access to the account data we hold. Include your account phone number and describe the records you want, such as verification, device or wallet references. We confirm ownership before sending account-related details.

Send a correction request through our support contact path, naming the account field that is wrong and the replacement detail. We may ask for a phone verification step before changing it. A payment reference itself may need confirmation from the relevant wallet or bank rail.

You may ask about deletion through support, and we assess the request under applicable rules. Some records can remain when needed for payment reconciliation, account security or legal duties. Access and eligibility depends on local law, so the result may differ by request.

We may record browser type, device signals, login time and session activity to keep access working and detect unusual sign-ins. These details help protect your account on a phone or desktop; they do not give us access to your device password or private files.