Reference

klik4d slot Privacy Policy for Your Account

Our Privacy Policy explains how we handle the account, device and wallet details connected with klik4d slot.

Account dataWallet recordsCookie choicesPolicy requests
klik4dslot.club page image
CONTACT ROUTES

Choose a Clear Privacy Contact Path

A direct request helps us locate the correct account record without guesswork. Use the support route shown in your account help area and include the phone number linked to your account, the…

Account help path Send a Privacy Policy request through the account help path, using your registered phone number so we can match the request with the correct login and verification record.
Payment record check For DANA, OVO, GoPay or QRIS questions, provide the payment reference and date. We use those details to locate the relevant wallet event without asking for your full wallet password.
Access concern If an unfamiliar device reaches your account, report it through support before changing other details. We may ask for account checks so a privacy request is handled by the account holder.
DATA PRACTICE

Browse How We Handle Your Data

Our privacy process follows the account journey rather than treating every record alike. Login events, wallet references, device signals and lobby activity serve different operational purposes, so we limit access to the…

Account details

We collect details needed to create and maintain your account, including contact data and verification status. Before account access, we may compare submitted details with the account record to prevent mistaken or unauthorised changes.

Device signals

A phone or desktop session can create technical records such as browser type, operating system, network indicators and login time. These signals help us investigate unusual access without reading unrelated device content.

Cookies

Cookies can keep your login session working and remember selected settings. You can manage cookie controls in your browser, although disabling necessary cookies may affect account access or the way a policy request is submitted.

Account security

We use verification steps, login records and device checks when an account change or wallet-status question needs confirmation. Never send us your password; our support route should not require it.

Retention period

We keep account, payment-reference and security records for the period needed for service operations, disputes, fraud checks and legal duties. When a record no longer serves those purposes, we remove or de-identify it.

Change requests

Ask us to access, correct or remove eligible personal data through the account help path. Include your registered phone number and request type; we may verify account ownership before making a change.

Find Answers About Privacy Policy

These Privacy Policy answers cover the questions we expect before an Indonesian customer opens an account. They explain the practical path for account data, wallet references, cookies, device records and requests sent through account support.

It covers account details, verification status, login events, device signals, cookies, lobby activity and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use the phone number to create and locate your account, support verification before access and match a Privacy Policy request with the correct account record. Do not send your password.

Yes. The Privacy Policy covers references connected with QRIS, DANA, OVO and GoPay, such as payment status, date and transaction reference. We do not need your full wallet password for a status check.

A phone or desktop visit may create records for browser type, operating system, approximate network details, login time and pages opened. These signals help us identify unusual access and resolve account requests.

Yes, where local law permits. Send a correction request through the account help path with your registered phone number and the field that needs changing. We may verify ownership before updating it.

Use the account help path and state that you want eligible data removed. We first check account ownership and any retention duty, because some payment, security or dispute records may need to remain.

The policy is written for supported Indonesia access, but account eligibility and related processing depends on local law. Where local law permits, contact us for a data-use explanation or rights request.