Reference

kijangwin Privacy Policy For Your Account

The kijangwin Privacy Policy explains how we collect, use and protect details linked to your account, including phone verification, device activity and wallet records for DANA, OVO, GoPay…

Clear data purposesWallet record contextPhone access controlsCookie choices
kijangwin kijangwin Privacy Policy For Your Account
CONTACT PATHS

Three Ways To Ask About Privacy

A clear contact route helps you act on the Privacy Policy without searching through account screens. Use the support link attached to your account area for a data question, a correction request or a concern about a wallet reference. Include the phone number on your account and the relevant receipt or login date, while leaving out passwords and one-time codes. We use those details to locate the right record safely.

Team online

Account support link

Open the support path beside your account controls when you need to ask what personal details we hold, why a phone check was recorded or how to correct an account field.

Receipt and wallet query

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share the reference and date only. We can check the payment record without asking for your password.

Access concern

If a login alert or unfamiliar device appears, use the same support route and describe the device path. We may ask account checks before discussing personal details or changing access.

HANDLING PRACTICE

Six Privacy Controls Inside Your Account

The Privacy Policy is applied through ordinary account controls rather than vague promises. We separate identity details from payment references where practical, limit staff access to necessary records and use session checks…

Account details

We use your account name, phone contact and verification status to maintain access and answer account requests. Keeping your phone detail current helps us distinguish your request from an unknown person.

Device signals

Browser, device and session signals help us identify unusual access and protect the account. They may be compared with earlier login activity when a new mobile path or desktop session appears.

Cookie controls

Cookies can remember a language choice, session setting or page preference. You can manage cookies through your browser; reducing them may affect saved settings used during the account path.

Payment matching

DANA, OVO, GoPay and QRIS references help us connect a receipt or wallet status to the correct account. We do not need your wallet password or one-time code for that check.

Retention requests

We keep records only as long as needed for account operation, security, dispute handling or legal duties. Ask support what applies to a particular record and whether a change or removal request is available.

Policy changes

When a material Privacy Policy change affects how your details are used, we place the revised wording on the policy page. Check the page before opening a new account or updating your phone details.

Privacy Policy Questions For Indonesian Accounts

These Privacy Policy answers address the practical searches we expect before account creation or a wallet query. They explain what we collect, how device activity and cookies fit into account protection, and where to ask for access or correction. If your situation involves a local eligibility rule, access depends on local law and the support path can clarify the next account step.

It covers account details, phone verification, device and session signals, cookies, support messages and payment references. The Privacy Policy also explains purposes, retention, access requests, corrections and contact steps.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use them to match receipts, check wallet status and resolve account questions.

Device and browser details help us recognise a familiar session, investigate an unusual login and protect account access. They can include device type, browser type, session time and related technical signals.

Use the support link in your account area and ask for an access request under the Privacy Policy. Include your account phone number and a short description, but never send a password or one-time code.

You can ask us to correct an inaccurate account field or explain a payment reference. Contact support from the account path, identify the record clearly and complete any account check needed before changes are made.

Retention depends on the record and the reason it was collected. We may keep account, security or payment references for operation, dispute handling or legal duties; support can explain the applicable retention position.

Ask through the account support link if you need help with cookies, a policy wording change or a privacy choice. Your browser also provides controls for removing or restricting cookies used for saved settings.