Reference

km7777 Privacy Policy for Indonesia

This km7777 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsCookie choicesSecure access
km7777 km7777 Privacy Policy for Indonesia
HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support request can help when you cannot identify a payment record, sign-in device or account message.

Account data request Ask us what personal data is linked to your account and why it is being used. We may request your verified phone detail or another account step before releasing account-specific information through the support channel.
Wallet record check If a DANA, OVO, GoPay or QRIS status looks unfamiliar, send the payment reference and approximate time. We compare that reference with the cashier record without asking you to share a wallet PIN or password.
Policy contact route For corrections, deletion questions or cookie concerns, label your message Privacy Policy and describe the requested action. We will use the account details supplied to confirm the request belongs to you before proceeding.
DATA HANDLING

What We Do With Account Information

We separate practical account needs from optional browsing signals. Phone verification supports account access, while device and session details help us recognise unusual sign-in activity.

Account security

Phone verification helps us connect a sign-in to the correct account. Device and session signals may be checked when access appears unusual, and we can ask you to confirm account details before discussing private records.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a cashier event. We do not need your wallet PIN or banking password to investigate that status.

Cookies

Cookies can retain a session setting or help us understand movement between the Privacy Policy and account pages. Your browser controls can limit or remove cookies, although some account functions may then need to be repeated.

Device records

When you sign in from a mobile browser, we may record technical signals such as session time and device type. These records help protect account access and are handled for the purposes described in this Privacy Policy.

Retention

We retain personal data for account operation, payment reconciliation, security checks and applicable legal duties. When a record is no longer needed for those purposes, our handling process removes it or separates it from direct account identity where practical.

Changes and contact

You can ask us to correct account details, explain a data use, or assess a deletion request. Send the request through support with your account identifier; we may verify your phone before making a change.

Privacy Policy Questions for km7777

These Privacy Policy answers focus on the account actions Indonesian customers ask about most: phone verification, mobile access, wallet records, cookies, retention and contact requests. The exact handling of an account or payment record can depend on the details supplied, and access remains where local law permits. Use the support route when your question concerns a specific account.

It covers data connected with account creation, phone verification, sign-in sessions, device signals, cookies, support requests and payment references. This includes records related to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when those details are used to identify a cashier event.

Phone verification helps us connect account access to the correct person and reduce confusion when a mobile session or payment status needs checking. We may use the verified phone detail to confirm an account-specific request before discussing personal data.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account routes. We use those references to reconcile the account event, not to request your wallet PIN.

You can contact support with your account identifier and describe the correction needed. We may ask you to complete a phone or account verification step. If the detail is tied to a payment or security record, we will explain any handling restriction before making a change.

Send a deletion request through the support route and label it Privacy Policy. We will assess which data can be removed and which records must remain for payment reconciliation, account security or a legal duty. Access and eligibility depend on local law.

Cookies may remember a basic session setting or support movement between account and policy pages. You can manage them through your browser controls. Removing cookies may require you to repeat a sign-in step, and some account functions may not work as expected.

We keep information while it is needed for account access, security checks, payment reconciliation or a lawful recordkeeping requirement. The period can differ by record type. You can ask support about a particular account or payment reference and we will explain the applicable handling.