Reference

Privacy Policy for balap kuda Accounts

Your account details, wallet records and device signals are handled under the balap kuda Privacy Policy, so you can see what we collect and why.

Account clarityWallet checksDevice controlsPolicy access

Explore Our Lobby Read FAQ

How Wallet Data Fits This Policy

balap kuda Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect only the account and transaction details needed to provide access, verify activity and respond to your requests. A phone number is checked before account access, while payment references help us match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity with the correct

1
account. If you use BCA, BRI, Mandiri or BNI, the related transfer record may be retained for reconciliation and security checks. Device details can help us recognise a returning browser or mobile session and investigate unusual sign-ins. We do not describe access as universal: eligibility depends
2
on local law, and our handling follows the purpose stated at collection. For a policy question, use the account help route beside the cashier area and include your registered phone number without sending a password or wallet PIN.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT DATA HELP

Reach Us About Your Account Data

A clear contact path matters when a wallet record or account detail looks unfamiliar. Start from your signed-in account help area and choose the route connected to the relevant payment or verification…

Account access If phone verification blocks your account, use the signed-in help route and describe the step shown on your device. We use the account record to check the request.

Wallet status For DANA, OVO, GoPay or QRIS questions, send the payment reference and selected rail. We can compare the receipt record with the wallet status without needing your PIN.

Data requests To ask for a copy, correction or deletion review, state the request clearly from your account help route. We may verify account ownership before changing any stored detail.

SECURITY AND RETENTION

Data Care Across Your balap kuda Account

Our privacy work follows the same account steps you see in the lobby: identify the account, check the relevant record, then apply the requested action where permitted.

Account records

We use your phone number and verification result to connect you with the correct account. If you request a correction, we compare the submitted detail with the existing account record before applying a change.

Payment references

DANA, OVO, GoPay and QRIS references help us identify a transaction, while bank transfer details support reconciliation. We do not ask for your wallet PIN as part of a privacy request.

Cookies and sessions

Cookies and similar device signals can keep a signed-in session working and help us detect unusual access. You can clear browser data, although this may require phone verification again.

Mobile protection

When you move from a mobile login to the lobby, device and session details may be recorded for security checks. Closing the browser ends the local session according to your device settings.

Retention purpose

We retain account and transaction records only for stated operational, security, dispute and legal needs. When a record is no longer needed for those purposes, we assess it for removal.

Change requests

You can ask us to correct account details or explain how a record is used through account help. We may request phone verification before releasing, changing or removing data.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account, wallet and device questions you are most likely to have before opening an account. They also explain the practical route for asking us about stored records, with access handled where local law permits and eligibility depending on local law.

It covers account details, phone verification, payment references, device signals, cookies, security checks, retention and requests to access or correct your stored data.

We use your phone number to identify the account and complete verification before account access. It also helps us connect a data request with the correct account record.

Yes. The Privacy Policy covers payment references from DANA, OVO, GoPay and QRIS, along with bank transfer or virtual account records used for reconciliation.

You can request a copy through the signed-in account help route. We may verify ownership first, then explain which account, payment and device records can be provided.

Send a clear correction request through account help and identify the detail that needs changing. We compare it with your account record and may ask for phone verification.

Cookies and session signals help keep your mobile browser connected and support unusual-access checks. Clearing them can sign you out and trigger phone verification at the next login.

We keep payment records for operational reconciliation, security, disputes and legal needs. Retention depends on the purpose and applicable local requirements, followed by a removal assessment.

Privacy Policy for balap kuda Accounts

Reach Us About Your Account Data

Data Care Across Your balap kuda Account

Account records

Payment references

Cookies and sessions

Mobile protection

Retention purpose

Change requests

Privacy Policy Questions From Indonesia

01 What does the balap kuda Privacy Policy cover?

02 Why does balap kuda need my phone number?

03 Does the Privacy Policy cover DANA and QRIS records?

04 Can I request a copy of my balap kuda data?

05 How do I correct an account detail?

06 How are cookies used on my mobile device?

07 How long does balap kuda keep payment data?

Related Pages