Reference

cacurbet Privacy Policy for your Indonesia account

Our Privacy Policy explains what cacurbet collects when you open an account, sign in from a mobile browser, browse casino or sports sections, and use DANA, OVO, GoPay…

Clear data purposesMobile account accessWallet context explainedPrivacy request path

Explore Our Lobby Read FAQ

What DANA and QRIS reveal to us

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

This Privacy Policy applies to the account details, device signals, payment references and support messages you provide while using cacurbet. We use these details to create your account, complete phone verification, show the correct wallet status and investigate an access or payment question. A DANA, OVO,

1
GoPay or QRIS reference may identify a transaction without giving us your wallet password. Bank transfer and virtual account records can also appear when you choose those routes. We retain records only for the operational, security and legal purposes described in this policy, then remove or
2
anonymise them when they are no longer needed, subject to local requirements. Access to the service depends on local law, and our policy may apply differently where local law permits a particular account activity. You can ask us to explain a data use through the privacy
3
contact path linked in your account settings.

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

PRIVACY CONTACT ROUTE

Where to ask about your stored data

A direct privacy request helps us match the question to the right account record without asking you to repeat sensitive details in a public channel.

DATA HANDLING PRACTICE

Six ways we handle account data

Privacy at cacurbet is managed through ordinary account controls rather than hidden settings. We separate sign-in details from payment references, record consent where cookies require it, and use security checks when a…

Account creation

When you open an account, we collect the details needed for account setup and phone verification. We use them to recognise your account, respond to requests and prevent another person from changing its records.

Device signals

A mobile browser may send device, browser and connection signals during login. These help us detect unusual access and protect your account, but they are not used to read your wallet password or private phone content.

Cookies

Cookies can keep a session active, remember selected settings and help us understand whether a page loads correctly. Your browser controls cookie removal, while our policy explains when a cookie supports security or account access.

Payment references

We handle transaction references for DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use these records to match status questions, not to request or store your wallet PIN.

Retention period

We keep account, security and payment records for the time needed for the stated service, dispute and legal purposes. When a record is no longer needed, we remove it or make it less identifiable.

Your changes

You can ask us to correct an inaccurate account detail, explain a data use or request removal where applicable. Send the request through account settings so we can confirm ownership before making a change.

Privacy Policy questions before account access

These answers cover the questions we expect you to have before opening an account from Indonesia. They explain the practical route for checking data, cookies, wallet references and account security. If your situation is specific, use the privacy contact path in account settings and tell us which account step or device path produced the question.

It covers account details, phone verification, device signals, cookies, support messages, security records and payment references connected with your use of cacurbet, including activity where local law permits.

Phone verification helps link account access to the detail you submitted and helps us respond safely to account changes. We may request it before discussing private records or restoring a sign-in path.

Yes. We may handle visible transaction references and status details for DANA and QRIS, along with OVO, GoPay, bank transfer and virtual account routes, without requesting your wallet PIN.

You can ask for access to personal data linked to your account through the privacy contact path in account settings. We first confirm account ownership, then explain what can be provided.

Send a correction request from your signed-in account and identify the detail that is wrong. Include your registered phone or email so we can verify the request before editing the record.

Cookies can support sign-in sessions, security checks and selected settings when you use a mobile browser. Your browser can remove them, though removing required cookies may interrupt account access.

We retain each category only for its stated account, security, dispute or legal purpose. When that purpose ends, we remove or anonymise the record, subject to requirements that still apply.

cacurbet Privacy Policy for your Indonesia account

Where to ask about your stored data

Six ways we handle account data

Account creation

Device signals

Cookies

Payment references

Retention period

Your changes

Privacy Policy questions before account access

01 What does the cacurbet Privacy Policy cover?

02 Why does cacurbet need phone verification?

03 Does the Privacy Policy cover DANA and QRIS data?

04 Can I request a copy of my cacurbet account data?

05 How do I correct an error in my Privacy Policy records?

06 How does cacurbet use cookies on mobile?

07 How long does cacurbet keep my personal data?

Related Pages