Reference

Open kaja66 Privacy Policy Details

kaja66 Privacy Policy explains how we collect, use and protect your account details while you access Live Roulette Diamond, wallet tools and the wider lobby.

Account clarityWallet data contextAccess request path
kaja66 Open kaja66 Privacy Policy Details
REACH OUR TEAM

Ask About Privacy From Your Account

A direct support path helps you resolve a privacy question without repeating your account story across unrelated channels.

Account route Use the support path connected to your account for access, correction or deletion requests. We may ask you to confirm the registered phone number before discussing personal records, so another person cannot receive account details by mistake.
Receipt details When your request concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, include the reference and date shown on your receipt. Those details help us locate the relevant record without asking for unrelated documents.
Access questions If you cannot sign in, explain the device path you used, such as mobile browser or desktop browser, and the exact message shown. We use that context to separate an access problem from a request about personal data.
DATA HANDLING

See How We Protect Policy Choices

Privacy controls work alongside the account steps you already use, rather than sitting apart from them.

Collected details

We may receive your contact details, phone verification result, sign-in events, device and browser signals, wallet references and support messages. We collect these details to provide account access, check payment status and respond to your privacy request.

Cookie use

Cookies can keep your signed-in session active and preserve practical settings between pages. You can manage cookies in your browser, although changing them may affect access to the account area or require you to sign in again.

Account security

Phone verification adds an account check before access to personal records. We also examine sign-in and wallet activity when a request appears unusual, helping us avoid sharing account data with an unverified person.

Retention choices

We keep personal and transaction records for the period needed to operate the account, resolve disputes, meet applicable requirements or protect security. When that need ends, we remove or de-identify the record where the process allows.

Your requests

You can ask us to access, correct or delete personal details, or ask how a particular record is used. Send the request through account support and include enough detail for us to identify the correct account safely.

Policy contact

For a Privacy Policy question, contact us through the account support route rather than sending payment credentials in an open message. We may request identity confirmation, then respond with the action we can take and its reason.

Browse kaja66 Privacy Policy Answers

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet is connected. They explain what happens to account data, how device access is treated and which details help us respond. If your situation involves a particular receipt or sign-in event, use the account support route with that reference. Access and eligibility depend on local law, including for Indonesian locations and devices used outside Indonesia.

The kaja66 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It explains why we use those records for account access, wallet matching, security checks and support, plus how you can request access, correction or deletion.

We use the payment reference, status and related account details needed to identify a deposit or receipt and answer a wallet question. We do not need unrelated wallet content for that task. Include the rail and transaction reference when you ask us to check a record.

Yes. Send a request through the account support route and identify the email or phone number linked to your account. We verify that you are the account holder before sharing personal records, then explain the available copy format and any detail that cannot be disclosed.

Cookies can retain a signed-in session and selected browser settings, which reduces repeated account steps on the same device. You can change cookie controls in your browser. If you block required cookies, the account area may ask you to sign in again or may not work as expected.

Ask through account support and state whether you want a correction or removal. Add the affected account detail, but do not send a password or full payment credentials. We verify the request, update or remove eligible records, and explain when a record must remain for security or legal reasons.

Yes. The same policy applies when you use a mobile browser to sign in, check QRIS status or open a lobby page. We may receive browser and device signals needed for session security. Those signals help us investigate access issues without replacing your account verification step.

Support can explain the next step, but we need to protect the account before discussing personal records. Tell us the device path and access message, then follow the identity check we provide. Where local law permits, we can continue the request after confirming the account safely.