Reference

Privacy Policy for Your Account Path

kapten 5000 Privacy Policy explains what we collect when you open an account, use the lobby and check wallet status, so your choices stay clear from the first…

Account dataCookie choicesWallet recordsPhone verification
Explore Our Lobby Read FAQ
kapten 5000 Privacy Policy for Your Account Path
CONTACT PATHS

Privacy Help Beside Your Wallet

A clear contact path matters when a privacy question appears beside a wallet status or login check. We keep policy requests close to the account and cashier areas, so you can identify the relevant transaction without sending unnecessary details. Use the support route shown after account access, include your registered phone number and describe whether you need a copy, correction, deletion request or cookie explanation. Where local law permits, we can also explain how the request affects access to the lobby.

Team online

Account request

Use the support path inside your account when you want to ask about personal data, phone verification or a stored login record. Include the registered phone number and the exact request so we can locate the correct account without asking you to resend unrelated wallet details.

Wallet record

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, refer to the payment receipt and status shown near the cashier path. We use the reference you provide to separate a privacy request from a transaction-status check.

Access concern

If a device or login concern raises a privacy question, tell us when it happened and which device path you used. We can check session signals and account-security records while keeping your request focused on the access event you identified.

DATA CONTROLS

Cookies, Security and Record Choices

We handle this policy area through practical account controls rather than broad promises. Your phone verification connects activity to the right account, while device and session checks help us investigate access concerns.

Data collected

We may collect your name, phone number, login credentials, device details, session activity, support messages and payment references. The specific fields depend on the account step you take, such as phone verification or checking a QRIS receipt.

Cookie handling

Cookies can keep your session open, remember a setting or help us understand which account page was used. If you ask about a cookie, we can explain its purpose and record your request for a change through the support path.

Account security

Phone verification and device signals help us distinguish your normal access from an unusual login. If you see an account event you do not recognise, contact support with the time and device path so we can check the related session record.

Payment references

We keep the references needed to connect a wallet or bank transaction with your account, including DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI details supplied during a payment step. We do not need unrelated wallet content.

Retention choices

We retain account, security and payment records for operational, dispute and legal reasons, then remove or anonymise them under our internal schedule. A deletion request can be submitted through support, although local requirements may affect what must remain.

Request changes

You can ask for access, correction or deletion of personal data by naming the account record concerned. Send the request from the account support path and include your registered phone number; we may need an account check before making a change.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain the data connected to phone verification, wallet records, cookies, device access and deletion requests. If your situation is different, use the account support path with the smallest amount of detail needed to identify your request. Access remains subject to local law.

The Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages and payment references. It also explains retention, security checks and how to request access, correction or deletion where local law permits.

We use your phone number to create and identify the account, complete phone verification and respond to an account request. It also helps us connect a support question with the correct wallet or login record without requesting unrelated personal details.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. These references help us check a receipt or status question, while the request should contain only the transaction detail needed for the check.

Use the support path inside your account and ask for a copy of the personal data connected with your registered phone number. State whether you want account, cookie, device or payment records, and we may complete an account check before responding.

You can request a correction or deletion through the same account support path. Tell us which record is wrong or no longer needed. We assess the request against operational, dispute and legal duties, so some records may need to remain.

On mobile, cookies may keep your login session active, remember a setting or help connect a page visit with a technical issue. Ask support which cookie is involved and what change you want; we will explain the available choice where local law permits.

Contact us through the account support path and provide the time, device type and account step involved. We can inspect session and device signals, then explain the relevant security record. Avoid sending a password, wallet PIN or unrelated payment details.

Related Pages

kapten 5000 Indonesia kapten 5000 Casino FAQ Andar Bahar Access guide