Reference

kari4d Privacy Policy for Your Indonesia Account

Our Privacy Policy shows how we handle the account details you provide before you reach Super Sic Bo, Book of Dead or other lobby areas.

Account dataWallet recordsCookie choicesContact requests
kari4d kari4d Privacy Policy for Your Indonesia Account
ACCOUNT HELP ROUTES

Check Login Help And Privacy Contact

A clear contact path matters when a Privacy Policy question appears beside a login or wallet issue.

Account access Use the support path inside your account when phone verification or a sign-in record looks unfamiliar. We can connect the access question with the relevant Privacy Policy request.
Wallet records For DANA, OVO, GoPay or QRIS questions, include the payment reference and status shown in your account. We use that detail to locate the matching record without asking for a wallet PIN.
Data requests Ask through the listed contact route if you want to access, correct or question personal data held by us. We may verify account ownership before changing or disclosing account details.
DATA PRACTICES

Explore How We Handle Account Data

Privacy work follows the same account path you use to reach the lobby: sign in, complete the requested verification, then manage your records through the available support route.

What we collect

We handle account contact details, verification results, sign-in events, device signals and transaction references. These details support access checks and payment matching for activities such as QRIS receipt confirmation.

Cookies on devices

Cookies and similar device storage can remember an account session or help us understand an access error. You can adjust browser controls, though changing them may require another sign-in.

Account security

We use phone verification, sign-in monitoring and device checks to protect account access. If a device path looks unusual, support may ask you to confirm account ownership before discussing records.

Payment separation

DANA, OVO, GoPay, QRIS, bank transfer and virtual account entries are handled as transaction references and status records. We do not need your wallet PIN to investigate a receipt.

Retention choices

We retain records for the period needed for account security, payment matching, support history and legal duties. A request to remove eligible data can be assessed through our contact route.

Changing your details

Contact us when your phone detail, account record or consent choice needs correction. We may request a verification step so a change is made for the right account.

Browse kari4d Privacy Policy Questions

These Privacy Policy answers focus on the searches we hear around account access, local wallets, cookies and personal data. If your situation is not covered, use the support path connected to your account and describe the exact step that needs attention.

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

No. We use transaction references and payment status for DANA, OVO, GoPay and QRIS checks. Do not send a wallet PIN or password when contacting support about a receipt.

Phone verification helps us connect an account request to the correct account and identify unusual sign-in activity. We may repeat that check before discussing private records or changing details.

Yes, you can contact us through the account support route and ask for access to eligible personal data. We may verify account ownership before preparing or disclosing the requested records.

Send a correction request through the listed contact path, describe the affected account field and provide the relevant account step. We may ask for verification before applying the change.

Retention depends on account security, payment matching, support history and legal duties. The policy allows you to ask about an eligible record and request removal where applicable.

Account access and eligibility depends on local law. We apply the policy where local law permits, and support can clarify how a regional requirement affects your account data request.