Reference

koora4live Privacy Policy For Your Account

koora4live Privacy Policy explains what we collect when you create an account, verify your phone, browse from a mobile browser, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
koora4live koora4live Privacy Policy For Your Account
CONTACT YOUR WAY

Use Support For Privacy Policy Questions

A clear contact route matters when you want to ask what we hold or correct an account detail.

Account support path Open the support route after signing in and select the Privacy Policy subject.
Receipt and status check For a DANA, OVO, GoPay, or QRIS privacy question, attach only the relevant receipt…
Access request route Ask us to provide, correct, or remove eligible account data through the same support…
DATA HANDLING

Check How Our Privacy Policy Works

We keep this policy practical by connecting each data use to an account action you recognise. Phone verification supports account recovery, device signals help us spot unusual sign-ins, and payment references help…

Account records

We collect the account details you submit, such as contact credentials and the verified phone detail used during access. We use them to identify your account, respond to policy requests, and maintain a clear record of changes rather than asking for unrelated personal data.

Payment references

A DANA, OVO, GoPay, or QRIS reference can show that a wallet event belongs to your account. Bank transfer and virtual account records serve the same matching purpose. We handle the reference and status needed for reconciliation, not your wallet password.

Cookies and devices

Cookies may remember a session or support account protection when you return on a phone or desktop browser. Device signals can indicate an unusual sign-in pattern. You can manage browser cookie settings, although some account functions may not work as intended without session cookies.

Account protection

We use phone verification and account checks before discussing private records or changing access details. If a request arrives from an unfamiliar device, we may ask for additional confirmation. Never place a password, PIN, or complete wallet credential in a support message.

Retention choices

We retain account, support, and transaction references only while they serve an account, operational, or legal purpose. When a record no longer needs to be kept, we remove it or separate it from direct account identifiers, subject to duties that may still apply under local law.

Your data request

You may contact us to ask what personal data is held, request a correction, ask about deletion, or question cookie use. Send the request through the account support path, identify the relevant account, and allow us to confirm control before we disclose or change records.

Browse Privacy Policy Answers For koora4live

These Privacy Policy answers cover the questions we expect you to ask before opening an account from Indonesia. They explain the practical route for account data, wallet references, cookies, corrections, deletion, and access requests. If your situation is not listed, use the support path in your account and describe the specific record you want us to check.

The koora4live Privacy Policy covers account details, phone verification, device signals, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. It also explains retention, access requests, corrections, and contact steps where local law permits.

We may keep a transaction reference, amount status, date, and payment route needed to match an account event. This can involve DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. We do not need your wallet password or PIN for that record check.

Your phone number can support account creation, verification, recovery, and a response to a Privacy Policy request. We use the verified detail to connect you with the correct record. If you contact support, do not include your password, PIN, or complete wallet credentials.

Yes. Send a correction request through the support path in your account and identify the field that is wrong. We may confirm control using your verified phone step before changing the record. Whether a change can be made depends on local law and the record's purpose.

Use the account support route to request deletion and name the account records involved. We first confirm the request is yours, then assess whether any account, transaction, support, or legal retention need remains. Records that must be kept cannot be removed immediately where local law requires retention.

Yes. The Privacy Policy applies when you access the account from a mobile browser or desktop browser. Session cookies may remember your sign-in state, while device signals can help identify unusual access. You can adjust browser cookie settings, though some account functions may then be limited.

After signing in, open the support link and choose the Privacy Policy subject. Include the account contact detail connected with your request and explain whether you want access, correction, deletion, retention, or cookie help. We may verify account control before discussing personal records, where local law permits.