Reference

krx18 Privacy Policy for Your Account

Our krx18 Privacy Policy explains what we collect, why we use it and how you can ask us to change or remove eligible data.

Account clarityWallet recordsDevice choicesPolicy requests
krx18 krx18 Privacy Policy for Your Account
CONTACT ROUTES

Get Policy Help Beside Your Account

A clear support path matters when a Privacy Policy question concerns a login, wallet reference or old account record.

Account request Ask us to explain data connected with your krx18 account after phone verification. Include the account contact and the specific record you want checked, rather than sending a full wallet history.
Wallet question For DANA, OVO, GoPay or QRIS concerns, attach the payment reference and date through the account support path. We use those details to check status while limiting the personal data shared in the request.
Access concern If a mobile browser or desktop login shows an unexpected access message, tell us the device path and account step involved. We can review the relevant security record and explain what the Privacy Policy allows.
DATA PRACTICES

Six Practical Privacy Controls At krx18

Our privacy work follows the same account path you use: identify the account, understand the event and limit the data needed to resolve it.

Account data

We may hold the contact details you enter, phone verification status and account activity needed to operate access. Ask us which categories relate to your account, and we will explain the purpose connected with each category.

Cookies and sessions

Cookies or similar session tools can keep a mobile browser signed into the right flow and remember selected settings. You can clear browser data, though doing so may require another phone verification step before account access.

Wallet references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may be stored to reconcile an account action. It is used for that operational purpose, not as a request for unrelated wallet activity.

Account security

We use sign-in details, device signals and phone verification events to identify unusual account changes. If a login pattern looks unfamiliar, support may ask for a focused account detail before discussing private records.

Retention timing

We keep records for as long as they serve account operation, dispute handling, security checks or legal duties. When a record no longer needs retention, our process can remove or de-identify it where applicable.

Change requests

You can request correction, access or clarification through the account support path. State the requested action and the relevant account step; where local law permits, we will assess the request and explain any necessary limits.

Privacy Policy Questions For krx18

These Privacy Policy answers address the account, device and payment questions you are most likely to have before opening access. Each answer points back to a practical step, so you know what to prepare when contacting us from Indonesia.

The krx18 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It explains why we use each category, how long records may remain and how you can ask about data linked to your account.

Yes. Privacy Policy treatment includes references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account actions. We use those references to reconcile an account event or investigate a receipt question, not to request unrelated financial activity.

Open the support path from your account area and request access to the categories linked with your account. Include your account contact and the specific period or action, such as phone verification or a QRIS receipt, so we can narrow the search.

You can ask us to correct inaccurate account details through support. Identify the field that needs attention and provide the replacement value through the account path. Where local law permits, we assess the request and explain any reason a record must remain unchanged.

Device and cookie data help maintain a consistent mobile or desktop session, recognise unusual sign-in activity and remember necessary account choices. Clearing cookies can end the current session and may send you through phone verification again before access continues.

Retention depends on the purpose of the record. We may keep account, payment-reference, support and security data while it supports account operation, dispute handling, fraud checks or legal duties, then remove or de-identify it when applicable.

Use the support route inside your account and describe the Privacy Policy request in plain terms. Mention whether it concerns login data, a wallet reference, cookies, correction or deletion. If access is discussed, it depends on local law.