Reference

kode4d Privacy Policy for Your Account

Your account details, wallet references and device signals stay tied to a clear Privacy Policy at kode4d.

Account dataWallet referencesCookie choicesContact requests

How Your Data Moves Through kode4d

kode4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers data supplied during account opening, including your contact details and phone verification status, plus records created when you sign in from a mobile browser or desktop device. Payment handling may create a reference for DANA, OVO, GoPay, QRIS, bank transfer or a

1
virtual account, while the payment provider processes the underlying transaction. We use these records to match account activity, investigate failed wallet status and protect the cashier path from misuse. Cookie and device data can help keep your session active and identify unusual sign-in patterns. Access to
2
our services depends on local law, and we apply this policy where local law permits. We retain records only for operational, security, dispute or legal needs, then remove or de-identify them when those needs end.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

ASK ABOUT YOUR DATA

Three Direct Routes For Policy Help

A clear contact path matters when you want to understand a Privacy Policy entry or correct an account record. Start from the support route linked near your account and include the email or phone detail used for verification. We can then locate the relevant sign-in, cookie or payment reference without asking you to send a wallet password or full banking credentials.

Team online

Account data request

Ask us to identify the account data connected with your verified phone detail. We use the account step to reduce mistaken disclosures and may request extra proof before responding.

Wallet reference query

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the date and visible reference code through support. Do not share your wallet PIN or full card credentials.

Cookie choice help

Contact support when a mobile browser keeps a cookie setting you do not expect. We can explain the session effect and point you to the browser path for clearing stored data.

OUR DATA PRACTICE

Six Practical Privacy Commitments

We handle this policy area through ordinary account controls rather than vague promises. Your data is separated by purpose: account access, payment matching, security checks, service measurement and support response.

Collection purpose

We collect contact and verification data to open and protect your account, not to request wallet passwords. Game activity such as Live Roulette or Bingo may create records linked to your account session.

Cookie controls

Essential cookies can keep a sign-in session and security check working. Optional measurement cookies may show how pages load on your device, and your browser settings can clear or restrict them.

Account protection

Phone verification helps us distinguish your account from an unauthorised sign-in. We may compare device and session signals when access changes or a payment status needs checking.

Payment separation

For DANA, QRIS, bank transfer and virtual account activity, we use transaction references and status data. We do not need your wallet PIN to match a receipt with your account.

Retention timing

We keep records while they support account operation, security, dispute handling or legal duties. When a purpose ends, we remove or de-identify the related data within our operating process.

Change requests

You can contact us to request access, correction or deletion of eligible account data. Include your verified contact detail and the specific record so we can assess the request accurately.

Privacy Policy Answers For kode4d

These Privacy Policy answers address the searches we hear most often before account opening. They cover account records, cookies, local wallets, device access and requests made through support, with each answer kept close to the practical step you can take.

It covers account and phone verification data, device and cookie signals, support messages, game-session records and payment references connected with DANA, OVO, GoPay, QRIS or bank transfer.

No. We use visible payment references and status details to match a transaction. Do not send a DANA, OVO, GoPay or QRIS PIN to support, even during a receipt check.

We may use browser, device and session signals to keep account access working, recognise unusual sign-ins and investigate a stalled payment status. These signals are handled for those stated purposes.

Yes, where applicable. Contact support using the verified phone or email linked to your account and name the records requested. We may ask for proof before releasing data to the correct person.

Send a correction request through the account support route, identify the inaccurate field and provide the updated detail. We check the account step before changing contact or verification records.

We retain data while it is needed for account operation, security, payment disputes or legal duties. After that purpose ends, we remove or de-identify records through our operating process.

Yes, it describes our handling of data for Indonesian account access where local law permits. Availability and eligibility depend on local law, so check the applicable rules before opening an account.

kode4d Privacy Policy for Your Account

Three Direct Routes For Policy Help

Account data request

Wallet reference query

Cookie choice help

Six Practical Privacy Commitments

Collection purpose

Cookie controls

Account protection

Payment separation

Retention timing

Change requests

Privacy Policy Answers For kode4d

01 What does the kode4d Privacy Policy cover?

02 Does the Privacy Policy store my wallet PIN?

03 How does kode4d use device data?

04 Can I request a copy of my account data?

05 How do I ask kode4d to correct my data?

06 How long does the Privacy Policy allow data retention?

07 Does this Privacy Policy apply to Indonesia access?

Related Pages