Reference

koko4d Privacy Policy for Your Account

Auto Roulette, Mahjong Panda and Aviator sit behind one clear account path, while our Privacy Policy explains exactly how we handle your details.

Account dataWallet recordsCookie choicesPrivacy requests
koko4d koko4d Privacy Policy for Your Account
HELP CHANNELS

Reach Us About Privacy Requests

A privacy question should not get lost beside a wallet query, so we keep the request path close to account support. Sign in, open the support area, and describe whether you need a copy, correction or removal of personal data. If you cannot access the account, include the phone number used during registration and the relevant DANA, OVO, GoPay or QRIS reference without sending a password.

Team online

Account access route

Use the support area after signing in to ask about stored account details, phone verification records or a correction to your profile data.

Wallet status path

For a privacy question linked to DANA, OVO, GoPay or QRIS, share the transaction reference so we can locate the correct record.

Unavailable account help

If login stalls, send the registered phone number and request type through our available support route; never include your password or verification code.

ACCOUNT SAFETY

Six Practical Data Handling Commitments

Privacy works best when each account step has a clear reason. We separate sign-in checks from wallet reconciliation, record security events for account protection and keep policy changes visible on this page.

Purpose-based collection

We request phone and verification details for account access, wallet matching and support. We do not ask for unrelated personal details merely to let you reach the lobby.

Cookie controls

Cookies and similar session tools help keep you signed in and remember security choices. You can adjust browser controls, though some account functions may then require another sign-in.

Security records

We may log device type, browser version, sign-in time and failed attempts to identify unusual access. These records help us investigate account issues without exposing your password.

Retention periods

Account, payment reference and support records remain available only as long as needed for account administration, dispute checks, security work or applicable legal duties.

Your data choices

You can ask us to access, correct or delete eligible personal data. We may first confirm account ownership using the registered phone and a relevant account step.

Policy changes

When this Privacy Policy changes, we update the page and its revision wording. Please check it before using DANA, QRIS or another wallet through your account.

Privacy Policy Questions for koko4d

These answers focus on the searches we hear most often about the koko4d Privacy Policy. They explain what may be collected, why payment references appear, how to request a change and what happens when local access rules apply. If your question concerns a specific account record, use the support path rather than posting personal details publicly.

It covers account details, phone verification, device and session records, cookies, wallet references, support requests, retention and your available requests for access, correction or deletion.

A DANA, OVO, GoPay or QRIS reference helps us match a wallet event with the correct account and status. We use the reference for reconciliation, support and security checks.

Yes. Sign in, open the support area and request access to your stored details. We may confirm ownership through your registered phone before releasing account or transaction records.

Send a correction request through our account support route, identify the field that is wrong and provide the registered phone number. We check the request before changing account records.

We keep payment references and related account records only for the period needed for reconciliation, dispute handling, security and legal duties. The period can depend on the record type.

You may request deletion of eligible data through support. Some records may need to remain where required for security, account disputes or legal duties; we explain the reason in our response.

Yes. Mobile browser sessions can create device, cookie and sign-in records in the same way as desktop access. Account availability depends on local law, including for access from Indonesia.