Reference

Privacy Policy For Your cahayaslot Account

cahayaslot Privacy Policy explains how we collect, use and protect details linked to your account, including login records, device signals and wallet references for DANA or QRIS.

Account dataCookie choicesWallet recordsAccess requests
cahayaslot Privacy Policy For Your cahayaslot Account
CONTACT YOUR WAY

Get Privacy Help Beside Account Support

A clear contact route matters when a privacy question appears during account access or a wallet check.

Account help Use the support contact displayed beside account help when you want to ask what…
Wallet questions For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, share the transaction…
Access requests To ask for a copy, correction or clarification, write the request through our account…
CONTROL YOUR DETAILS

What We Do With Your Account Data

We handle privacy as an account process rather than a broad promise. Login and device signals help us identify unusual access, while wallet references help us trace a DANA or QRIS status…

Collected details

We may receive your name or contact detail, account credentials in protected form, verification result, sign-in events, device path and support messages. Payment rails generally provide a reference and status for matching, not a request for your wallet password or one-time code.

Purpose of use

We use account and device records to let you sign in, protect the account, respond to a privacy request and investigate a disputed status. A game title such as Live Roulette Gold may appear in activity records only when needed to explain an account event.

Cookie control

Cookies can remember a session or a setting on your phone and desktop browser. You can remove or block them in browser settings. If you clear session cookies, we may ask you to complete the account sign-in step again before showing account-linked pages.

Account security

Keep your password, verification code and wallet credentials private. We use sign-in events, device signals and account checks to identify unusual access, but we will not ask you to post a DANA PIN, OVO PIN or full card-like credential in a support message.

Retention period

We retain each record for the period needed for its stated purpose, account support, security checks or applicable legal duties. When a record no longer serves those needs, our handling process is to remove it, anonymise it or restrict its use where appropriate.

Change requests

You can ask us to correct an inaccurate contact detail, explain a record, provide an available copy or discuss deletion where applicable. Send the request through the account support contact, and we may verify account ownership before making a change.

Privacy Policy Answers For cahayaslot

These Privacy Policy answers address the searches we expect when you are deciding whether to open an account or asking about an existing record. We keep each response tied to a real account step, device action, payment reference or contact request. If your situation is not covered, use the support contact shown in account help and describe the specific record you want us to check.

The cahayaslot Privacy Policy covers account details, sign-in and device events, cookies, support messages, security checks and payment references. It explains why we use those records, how long we may retain them and how you can request access, correction or clarification through account support.

We may collect contact details supplied during account opening, protected credential records, verification status, device and sign-in events, support correspondence and account activity needed for a query. We do not ask you to send a DANA PIN, OVO PIN or verification code in a support message.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account records. We use the reference, status and timing to match an account query; wallet credentials are not needed for us to check a receipt.

Use the support contact displayed in your account help area and state whether you want a copy, correction or explanation. Include the contact detail linked to your account and the record involved. We may verify ownership first so another person cannot request your account data.

Cookies can keep a sign-in session or remember a browser setting on your phone or desktop. You can block or remove them through browser controls. Clearing session cookies may require you to complete the account access step again before viewing account-linked pages.

Retention depends on the purpose of each record, the need to support your account, security checks and applicable legal duties. When continued storage is no longer needed, we may remove, anonymise or restrict the record according to our handling process.

You can ask us how the Privacy Policy applies to your account and request clarification through the stated support contact. Account access or eligibility depends on local law. Include your account contact detail and avoid sending wallet passwords, codes or unrelated personal material.