Reference

Open casiobet Privacy Policy Before Joining

casiobet Privacy Policy explains how we collect, use and protect the details connected to your account, wallet checks and support requests.

Clear data purposesWallet activity contextAccount access choicesSupport request path
casiobet Open casiobet Privacy Policy Before Joining
CONTACT DATA TEAM

Switch To Support When Privacy Questions Stall

A direct support route helps when you need to ask about a stored detail, an account access record or a wallet reference.

Account message Use the signed-in support message when you want to ask about your profile, phone…
Wallet query For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, share the…
Security concern If your account opens on an unfamiliar device or your contact detail changes unexpectedly…
DATA HANDLING

Browse Our Privacy Practices In Detail

We separate ordinary account operation from security investigation so each request has a clear reason.

Account details

We use your name, contact route and verification status to create and protect the account path. Before discussing personal records, we may compare the request with the registered phone or email so another person cannot obtain your account details.

Device signals

When you sign in from a phone, tablet or desktop browser, we may record device and session signals linked to security checks. These signals help us spot unusual access around the login step without reading unrelated files on your device.

Cookies

Cookies can remember sign-in preferences, language choices and security session details on the browser you use. You can manage cookies through browser controls, although disabling necessary cookies may affect account access and may require another verification step.

Wallet references

Payment records may show a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, amount and status. We use those fields to match account requests and investigate a receipt question, while wallet PINs remain outside our support process.

Retention checks

We keep account, support and security records for as long as needed for service operation, fraud checks, dispute handling or legal duties. After the relevant purpose ends, records are deleted or changed so they no longer identify you where practical.

Change requests

You can ask us to correct an inaccurate phone number, email address or profile detail through the signed-in support route. Tell us which field needs attention; we may request verification before changing it, then explain the outcome through your registered contact path.

Ask About Privacy Policy And Access

These Privacy Policy answers cover the searches we hear most often from Indonesian account holders. They explain what we collect around account access, why wallet references appear, how to request changes and what to do if a device or contact route looks unfamiliar. If your question is not listed, contact us through the support path above and include only the details needed to locate your account.

The casiobet Privacy Policy covers data connected to account creation, sign-in, device security, support messages, cookies and wallet transaction references. It also explains why we use those details, how long we retain them and how you can ask about access or correction where local law permits.

We may collect your contact details, account status, phone verification result, sign-in records, device signals, cookie choices and support history. If you request a wallet transaction check, we may also receive a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference.

No. Our Privacy Policy does not require you to send a DANA, OVO, GoPay or QRIS PIN to support. For a status check, provide the visible transaction reference and date only. Never share a password, PIN or one-time verification code in chat or email.

Sign in and contact support using the registered phone or email route, then name the field that needs correction. A request may involve an account check before we change it. This process can cover a phone number, email address or other profile detail.

Cookies can remember your security session, language choice and selected access settings on the browser. We use them to support the account path, not to read unrelated files on your phone. Browser controls let you remove or restrict cookies, though sign-in may then need extra checks.

We retain account, security, support and transaction records while they serve service, dispute, misuse-prevention or legal purposes. When a purpose ends, we delete or anonymise the relevant records where practical. The precise period can depend on the record type and applicable local law.

Contact support promptly through your registered phone or email route if a sign-in or contact change looks unfamiliar. Do not send your password or verification code. We may ask security questions, review the device event and help secure the account after confirming your identity.