Reference

Open kode4 with clear Legal terms

kode4 puts Legal clarity beside your account path, covering access, payment records and requests about your personal data before you enter the lobby.

Account termsData requestsLocal-law access
kode4 Open kode4 with clear Legal terms
CONTACT PATHS

Reach support about a Legal request

A clear contact route helps when your question concerns account access, a payment record or the use of personal data. Start from the support area while signed in, include the email or phone number attached to your account, and describe the specific clause or record you need checked. We use those details to route the request without asking you to repeat the whole account history.

Team online

Account access

If phone verification or an access decision is unclear, send a support request from the account path. Include your registered contact detail and the country or region you are accessing from so we can assess the Legal question against local requirements.

Payment record

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, attach the receipt reference rather than sharing a wallet password. We can identify the transaction, explain the record held and direct you to the relevant Legal wording.

Policy request

For a data access, correction or deletion request, use our policy contact route and state exactly what you want changed. We may ask for account verification before discussing private details, protecting your account while the request is assessed.

DATA PRACTICE

Browse kode4 data and account duties

Legal handling is practical: we connect each request to the account details, payment reference or device session needed to assess it.

Data handling

We use account details, phone verification data and relevant payment references to operate access checks and answer Legal requests. We do not need your wallet PIN or password to identify a DANA, OVO, GoPay or QRIS receipt.

Cookies

Cookies can keep your sign-in state, language choice and security session working across the mobile browser and desktop path. If you ask what cookie data relates to your account, contact us with the device and account details needed to locate it.

Account security

Phone verification is an account step before access, and we may check ownership before releasing private records. Never send a password, wallet PIN or one-time code in a Legal request; our process is designed to work without those secrets.

Record retention

We retain account, access and transaction records for the period needed to operate the service, handle disputes and meet applicable obligations. A request about retention should identify the record type, such as a QRIS receipt or bank transfer reference.

Who to contact

Send policy questions through the support contact route connected to your account. Tell us whether the request concerns access, correction, deletion, cookies or a payment record so the right handling path can be used.

Request changes

You can ask us to correct account details or explain how a record is used. We may need phone verification and a matching account reference before making a change, and we will tell you if a Legal obligation prevents it.

Check common kode4 Legal questions

These answers address the policy points most often raised before an account is opened or when a record needs checking. They cover local access, identity steps, payment evidence, cookies and requests about personal data. If your situation does not fit one of these questions, contact us through the account support route with the smallest useful set of details.

The kode4 Legal terms cover account eligibility, phone verification, access decisions, personal data, cookies, payment records and contact requests. They apply to account activity connected with titles such as Live Blackjack Gold and Badminton Sudirman Cup Bet where access is available.

Access depends on local law. Where local law permits, you can follow the account path and complete phone verification, but you should read the applicable terms for your region before entering the lobby or submitting a DANA, OVO, GoPay or QRIS payment.

Phone verification helps us connect an account request to the person controlling the registered contact detail. It also protects private data and payment records from an unrelated request. We will not ask you to share a wallet PIN, password or one-time code.

Use the support contact route linked to your account and ask for a data access request. Include your registered phone or email and identify the records involved, such as account activity, cookies, a QRIS receipt or a virtual account reference.

Yes, you can request a correction through the policy contact route. State which account detail is wrong and what it should say. We may complete phone verification or ask for a matching record before changing information connected with your account.

Payment references may be linked to your account so we can identify status, receipts and disputes. This includes DANA, OVO, GoPay, QRIS, bank transfer and virtual account records. Do not send wallet credentials; a receipt reference is enough to begin.

Contact us through the policy support route and specify whether you want a cookie explanation, correction or deletion request. We may retain some account or transaction records when required for security, disputes or an applicable Legal obligation.