Reference

Privacy Policy for Your Account

Your account data, wallet records, cookie choices and device sessions sit under one Privacy Policy before you open the lobby at cilik4d.

Account data scopeDANA record contextOVO receipt checksGoPay and QRIS logs
cilik4d Privacy Policy for Your Account
PRIVACY CONTACT

Three Ways to Ask About Privacy

Fast answers matter when your request involves personal data, payment records or a device you no longer control.

Live chat privacy help Use live chat from 09:00 to 23:00 WIB when you need quick help with…
WhatsApp verification line Send WhatsApp support your account name and registered mobile number when asking about DANA…
Email data requests Email is better for correction, deletion or access requests because it gives you a…
DATA CONTROLS

Six Controls Behind Our Privacy Policy

Practical privacy controls protect the account journey from registration through wallet checks and game-session records.

Account setup records

When you open an account, we store the username, registered mobile number, password hash and sign-up time.

Payment reference handling

DANA, OVO, GoPay and QRIS activity creates payment references, timestamps and status codes.

Cookie and session use

Cookies keep you signed in, remember safe preferences and detect repeated failed login attempts.

Device access checks

Your mobile browser, IP address and device type may be logged when you sign in.

Activity data boundaries

We may record activity such as opening Live Football Odds, Leprechaun Riches or Crash Games.

Retention and changes

Some records stay while your account remains active, while payment and security records may be kept longer for dispute handling.

Privacy Policy Questions You May Ask

Privacy questions usually come up before account opening, after a payment check or when a device alert appears. We answer these requests through the same support channels used for account help, but we verify ownership before discussing personal data. The answers below explain what we collect, why we use it, how payment records are handled and how you can ask for changes under this Privacy Policy.

We collect account setup details such as username, registered mobile number, password hash, sign-up time and device data. If you add email or contact support, those records also become part of your account file.

Payment records help us match wallet activity to your account, check disputed transfers and answer support questions. We store references such as amount status, timestamp and payment channel, not your full wallet password.

Yes. Sign in, check your profile details, then contact live chat, WhatsApp or email with the record that needs correction. We verify account ownership before changing mobile numbers, email data or payment references.

Cookies keep your session active, remember preferences and help detect unusual login behaviour. You can clear cookies in your browser settings, but you may need to sign in again afterward.

Only support staff assigned to account, payment or security checks can view the data needed for your request. We limit access based on task type and do not share your data for unrelated promotion.

After signing in, go to Account > Security > Active Devices. If you see a phone, browser or location you do not recognise, contact support during 09:00 to 23:00 WIB.

Yes. Account access and eligibility depend on local law and are available only where local law permits. This Privacy Policy explains data handling, but it does not change local access rules.