Reference

Privacy Policy For Your km717 Account

Our Privacy Policy explains what we collect when you open a km717 account, use the mobile lobby, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesContact requests

Browse Our Lobby Read FAQ

How Privacy Policy Applies To Wallet Records

km717 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers details you provide during account creation, including your phone number and verification response, plus technical details from the device and browser used to reach the lobby. When you use DANA, OVO, GoPay or QRIS, we record the payment reference, amount status and

1
time needed to match the transaction; bank transfer and virtual account records are handled for the same account check. We use this information to process access requests, investigate mismatched receipts, protect the account from unusual activity, and meet requests required where local law permits. We do
2
not describe payment data as a public profile. If you stop using the account, retention follows the operational and legal need explained in this policy. Questions about a record can be sent through the contact path shown below.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT THE TEAM

Privacy Help Beside Your Account Path

A clear contact route helps you act on the Privacy Policy without guessing which account screen to use.

Account privacy request Ask us to check, correct, or explain personal data connected with your account. Use the support route beside the account or cashier area, describe the request clearly, and we will ask for account confirmation before discussing private records.

Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, include the payment reference and date rather than sending a full wallet password. We use those details to trace status while keeping unrelated account data out of the request.

Access and correction If a login or phone verification step prevents you from reaching your privacy settings, tell us what appears on your device. We can guide the account check, explain the next step, and route a correction request to the right record.

DATA HANDLING

Six Privacy Checks We Keep Visible

Privacy work is easier to understand when each handling step has a clear purpose. We separate account access details from payment references, use cookies to remember practical settings, and limit internal access…

Account details

We collect the details needed to create and maintain your account, such as your phone number and verification result. We use them for account access and support rather than presenting them as public profile content. You may ask us to check their accuracy.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, status, value and timestamp in our records. Bank transfer and virtual account entries follow the same purpose: matching your account activity and resolving a receipt question without requesting your wallet password.

Cookies and devices

Cookies can remember a practical setting and help us understand whether a session belongs to the expected browser. Your device path may change from mobile to desktop, so a new login or phone check can appear when account protection requires it.

Account security

We use account checks to reduce the chance that an unfamiliar device or person receives private account details. If access stalls after a phone verification step, contact support through the account route; we will confirm ownership before changing sensitive access data.

Record retention

We retain records only for the operational, dispute, security or legal purpose described by this Privacy Policy. Payment references may remain after a session ends when they are needed to reconcile a receipt or answer a valid request where local law permits.

Your requests

You can ask us to access, correct, explain or delete eligible personal data. Send the request through the privacy contact route with enough detail to locate it. We may request identity confirmation, and some records may need to remain for a legal or security reason.

Privacy Policy Answers For km717

These Privacy Policy answers focus on the questions you may have before opening or using an account from Indonesia. We keep the wording practical: what is collected, why wallet references appear, how cookies behave, and where to send a request. If your situation is not covered, use the account privacy route and include the device step or payment reference that caused the question.

It covers account details, phone verification, device and browser data, cookies, payment references, support requests and retention. We explain how each category supports account access, payment matching, security or legal duties. Access or eligibility depends on local law and the region connected with your account.

We use the phone number and verification result to create an account path and check that a sensitive access request comes from the account holder. If the verification screen fails, contact support through the account route. We will not change private access details without an ownership check.

Yes. The Privacy Policy covers DANA, OVO, GoPay and QRIS references, including status, value and transaction time. We use these details to match account activity and investigate a receipt question. We do not need your wallet password to trace a payment reference.

Cookies may remember a session setting or help identify whether the browser matches an expected account path. Moving from a phone to a desktop can trigger a fresh login or verification check. You can ask us about a cookie record through the privacy contact route.

You can ask us to access, correct or explain eligible personal data linked to your account. Send the request through the account privacy route and describe the record, such as a phone detail or payment reference. We may confirm ownership before responding where local law permits.

We keep payment references for the operational, dispute, security or legal purpose stated in the Privacy Policy. A DANA, QRIS, bank transfer or virtual account record may remain after use when needed to reconcile a receipt or answer a valid account request.

Use the privacy contact path beside your account or cashier area and explain the issue in clear terms. Mention whether it concerns cookies, phone verification, wallet status or a correction. Do not send a wallet password. We may request account confirmation before sharing private details.

Privacy Policy For Your km717 Account

Privacy Help Beside Your Account Path

Six Privacy Checks We Keep Visible

Account details

Payment references

Cookies and devices

Account security

Record retention

Your requests

Privacy Policy Answers For km717

01 What does the km717 Privacy Policy cover?

02 Why does km717 collect my phone verification data?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How do cookies affect my km717 account?

05 Can I request a copy or correction of my data?

06 How long does km717 keep payment information?

07 Where should I send a Privacy Policy question?

Related Pages