Reference

Open Your Privacy Policy Path

kapital4d's Privacy Policy explains how we use account details, phone verification, device signals and wallet records when you access our lobby.

Account dataWallet recordsDevice accessPolicy requests
Browse the lobby Read FAQ
kapital4d Open Your Privacy Policy Path
CONTACT ROUTES

Reach Us About Account Data

A direct support route helps you resolve a Privacy Policy question without sharing more than needed. Sign in first where possible, open the account support path near the cashier area, and describe whether your request concerns access, correction, deletion or wallet records. We may ask for a matching account detail before discussing private data, and we keep payment receipts out of public messages.

Team online

Account support

Use the support path inside your account when you need to ask how your phone number, sign-in record or profile details are handled. We can match your request to the correct account without asking for a DANA, OVO, GoPay or QRIS wallet password.

Payment query

If your question concerns a QRIS scan, DANA receipt or bank transfer reference, send the transaction date and account identifier through the private support route. We use those details to locate the record and avoid requesting unrelated personal data.

Access help

When a phone verification step or mobile sign-in stalls, tell us the device type and the exact screen where access stops. We use that narrow description to investigate session data while keeping your account credentials and wallet PIN private.

DATA PRACTICES

Browse How We Handle Your Data

We apply the Privacy Policy to the account journey rather than treating every visit the same way.

Account collection

We collect details you provide during account creation and phone verification, such as contact information and account identifiers. These details help us recognise your profile when you move from the lobby to account settings or ask support to locate a privacy request.

Session signals

A mobile browser opening asoy4d or a desktop session entering the live lobby may produce device and session signals. We use them to keep access functioning, identify unusual sign-in patterns and connect your request to the right account activity.

Cookie controls

Cookies and similar browser storage can remember sign-in preferences and help pages load in the expected account state. You can manage browser permissions on your device, although changing them may require another sign-in or limit parts of the account path.

Wallet records

Payment references can remain linked to your account when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use the reference to check status and answer a receipt question, not to request your wallet password or PIN.

Security steps

Phone verification, sign-in checks and restricted support handling help us protect account data. If your access changes after a device switch, contact us from the account route and share the screen detail rather than sending a password or private wallet credential.

Retention requests

We retain records only for stated account, security, transaction or legal purposes, subject to the period that applies to the request. Ask us to explain a record, correct a detail or remove eligible data through the private support path.

Ask About Privacy Policy Access

These Privacy Policy answers cover the account questions we expect from Indonesian customers before they open an account. You can check how data connects to phone verification, mobile access, game sessions and local wallet references, then use the private support route if your situation needs a specific answer.

The Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages and payment references. It explains why we use each category when you access the lobby, open Dragon Tiger or check a DANA, OVO, GoPay or QRIS transaction.

Phone verification helps us connect account access with the contact detail you supplied and investigate unusual sign-in activity. We may use the verification record when support handles a Privacy Policy request, but you should never send your verification code or wallet PIN in a message.

Yes. The Privacy Policy covers mobile browser sessions, device signals and cookies used while you sign in, browse lgbola or move between account pages. Browser settings can affect saved preferences, so changing them may require a fresh sign-in or another verification step.

We keep transaction references needed to check account status, match a receipt or answer a payment question. The Privacy Policy does not require your DANA or QRIS wallet password. Send only the account identifier, date and relevant reference through the private support path.

You can ask us to correct an inaccurate eligible detail through account support. Include the profile identifier and explain the change clearly; we may verify that you control the account before making an update. The request remains subject to local requirements and the Privacy Policy.

Start a removal request through the private support route and identify the account you want us to assess. We first check whether records must remain for security, transaction or legal reasons. Any available action depends on local law and the retention need described in the Privacy Policy.

Use the support path inside your account and state that your message concerns the Privacy Policy. For a wallet record, add the payment type such as GoPay or bank transfer, the date and account identifier. Do not include a password, wallet PIN or full verification code.

Related Pages

kapital4d Indonesia kapital4d Casino About Us Account information Dragon Tiger