Reference

Privacy Policy for Your kurama189 Account

Our Privacy Policy explains how kurama189 handles the details connected with your account, wallet activity and access from Indonesia.

Clear data purposesWallet record contextAccount access controlsIndonesia privacy requests
kurama189 Privacy Policy for Your kurama189 Account
PRIVACY CONTACT ROUTE

Get Privacy Help Through Your Account

A clear contact path helps you ask about personal data without explaining your whole account history again.

Account request Open the support path after login and state whether you want a copy, correction or removal request. We may ask you to complete phone verification before discussing account-linked details, so your private records are not disclosed to another person.
Wallet reference For a payment privacy question, provide the DANA, OVO, GoPay or QRIS reference shown in your receipt. We use the reference and status to find the relevant record while avoiding requests for your wallet PIN, password or full secret credentials.
Access concern If your privacy request follows a login problem, tell us the device path you used, such as a mobile browser or desktop browser. We can separate an account-security check from the privacy request and explain the next step through the same support route.
DATA CONTROL DETAILS

How kurama189 Protects Account Details

We treat privacy as an operating task: identify the record, confirm the requester, apply the requested change where permitted and keep an audit trail of the action.

Data handling

We use contact details to create and maintain your account, phone verification to confirm access, and payment references to reconcile DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. Each purpose is connected to an account or service action rather than a general data collection request.

Cookies

Cookies can remember a session, support basic account navigation and help us understand whether a page request completed. You can manage browser cookie settings, although removing required cookies may interrupt login or prevent the privacy request form from keeping its state.

Account security

Phone verification may be required before we reveal account-linked data or change sensitive details. Keep your password and wallet credentials private; our support route will not need those secrets to identify a DANA receipt or discuss a privacy request.

Retention

We keep account, support and transaction records only as long as needed for the stated service purpose, security checks, dispute handling or duties that depend on local law. When a retention period ends, records are removed, anonymised or restricted where that process applies.

Correction requests

If your name, phone detail or contact record is inaccurate, send a correction request from the account support path. We may verify the request before making changes, and we will explain if a record must remain unchanged for security or legal reasons.

Who to contact

Use the support route inside your account for access, correction, deletion, cookie or data-use questions. Include your account contact detail and a short description of the request; do not include a password, wallet PIN or complete payment secret in the message.

Privacy Policy Questions About kurama189

These Privacy Policy answers cover the questions we expect you to ask before opening an account or sending a data request. They explain the practical link between account access, local wallet records, cookies, device checks and support handling. If your situation is not covered, use the account contact route and describe the specific record or request you want us to check.

It covers account details, phone verification, device and browser signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains purposes, retention, security steps and how you can request access or correction.

Yes. The Privacy Policy explains that a QRIS flow may provide a reference, amount, time and status so we can match the payment to your account. We use that information for reconciliation, support and security checks, and we do not need your QRIS PIN.

Send a data access request through the support path after login, using the phone or email detail attached to your account. We may ask for phone verification before releasing account-linked records, and the response depends on local law and applicable exceptions.

You can request a correction through the account support route. State which contact or profile detail is inaccurate and provide the updated value. We verify the requester first, then make the change where permitted; some transaction records may need to remain unchanged for audit purposes.

On a mobile browser, cookies may keep your session active and preserve basic account navigation. You can change cookie settings in the browser, but required cookies may be needed for login or a privacy request form. The policy explains this functional use rather than treating cookies as wallet credentials.

We retain payment and support records for the period needed to reconcile a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, handle disputes, protect accounts and meet duties that depend on local law. The applicable period can vary by record type.

Use the logged-in account support path and request deletion of the relevant personal data. We may verify your identity before acting and will explain any records that must be retained for security, dispute handling or duties that depend on local law.