Reference

Open kode4 Privacy Policy With Clarity

kode4 Privacy Policy explains what we collect when you create an account, sign in from a phone, browse Live Blackjack Gold or use DANA and QRIS.

Account dataDevice controlsWallet recordsPolicy requests

Explore Our Lobby Read FAQ

Browse How Privacy Works With QRIS

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

Our Privacy Policy covers details you provide during account creation, such as your phone number and verification information, along with records created when you sign in, open a game page or check a wallet route. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or a

1
virtual account may be used to match a receipt with your account and resolve a status question. We also explain cookie use, device signals, retention and account-security checks in plain terms. Access depends on local law; where local law permits, you can use the contact path
2
below to ask what we hold, request a correction or raise a privacy concern.

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

CONTACT ROUTES

Reach Support About Your Privacy Policy

A clear contact path helps when your account record or wallet reference needs attention. Use the support route shown on kode4 to ask about personal data, a phone-verification record, cookie choices or a payment receipt connected with DANA, OVO, GoPay or QRIS. Include your account phone number and a short description, but do not send a password or full wallet credentials. We use the account details you provide to locate the request and keep the conversation focused on your Privacy Policy rights.

Team online

Account privacy request

Ask us to locate the personal data linked to your account. Include the phone number used for access and mention whether your question concerns sign-in, phone verification or a profile correction.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears in an account conversation, send the receipt reference rather than your wallet password. We can use that detail to trace the relevant payment record.

Security concern

Tell us promptly if a device, phone number or account action does not look familiar. We may ask account questions before discussing records, helping keep private details away from an unverified requester.

DATA PRACTICES

Explore kode4 Data Handling Step By Step

We handle this policy area around the actions you take, not around broad claims. A sign-in can create device and security records; a QRIS receipt can create a payment reference; and opening…

Account collection

We collect account details you submit, including contact and phone-verification data, so we can create the correct account path. You can ask support which fields are associated with your account.

Device signals

When you sign in on a mobile browser or desktop, technical signals can help identify a session and flag unusual access. These signals support account security and are not a substitute for your password.

Cookie choices

Cookies can keep a session active, remember selected settings and help us understand page errors. Your browser controls can remove or restrict them, although some account steps may then need to be repeated.

Wallet matching

A DANA, OVO, GoPay or QRIS reference may be matched with your account when we check a receipt or wallet status. We do not need your wallet password to investigate that reference.

Retention checks

We keep records only for the operational, security or legal purpose connected to them, subject to applicable rules. Ask support about a particular record rather than assuming every account detail has the same retention period.

Change requests

You can ask us to correct inaccurate account details or explain how a record is used. We may verify your account first, then respond through the available support route with the next required step.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers address the questions we expect before an Indonesian account is opened or used on a phone. They cover account data, cookies, wallet references, device access and requests for correction. If your situation is different, contact support with the account phone number and a narrow description so we can direct the request without asking for unnecessary credentials.

The kode4 Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, game-session activity, wallet references and support conversations. It also explains retention, security checks and how you can ask about, correct or challenge data connected with your account.

We use the phone number you submit to create and identify your account, complete phone verification and help prevent an unverified person from receiving private account details. If the number is wrong, contact support and ask for an account-data correction.

Yes. The Privacy Policy covers payment references created when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We may use a receipt reference to match a wallet status or resolve an account question, without requesting your wallet password.

A mobile browser or desktop session can create technical signals such as browser, device and access details. We use them to keep sessions working, investigate errors and identify unusual account activity. You can ask support which device-related records are linked to your account.

You can contact us to ask whether account data is inaccurate or incomplete and request a correction. Include the phone number used for access, identify the field or record in question and avoid sending passwords. We may verify ownership before making a change.

Retention depends on the type of record and the reason it was created, such as account operation, security, receipt matching or legal duties. The Privacy Policy does not treat every record alike. Ask support about a specific data category for a more useful response.

Where local law permits, use the support route on kode4 and state that your request concerns the Privacy Policy. Add your account phone number, the data category involved and the action you want, such as access, correction or an explanation of use.

Open kode4 Privacy Policy With Clarity

Reach Support About Your Privacy Policy

Account privacy request

Wallet record question

Security concern

Explore kode4 Data Handling Step By Step

Account collection

Device signals

Cookie choices

Wallet matching

Retention checks

Change requests

Check Privacy Policy Answers Before Opening

01 What does the kode4 Privacy Policy cover?

02 Why does kode4 need my phone number?

03 Does the Privacy Policy cover DANA and QRIS records?

04 What device data is collected when I sign in?

05 Can I request a correction under the Privacy Policy?

06 How long does kode4 keep my personal data?

07 Where local law permits, how do I raise a privacy concern?

Related Pages