Reference

kode388 Privacy Policy For Your Account

kode388 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
Explore Our Lobby Read FAQ
kode388 kode388 Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Help Beside Account Support

A clear contact path matters when a privacy question appears during sign-in or wallet checking. We ask you to use the support route linked from your account area and include the email or phone detail connected to your profile, without sending a password or full payment credentials. That lets us identify the right account, check the request safely and explain the next step for you.

Team online

Account privacy request

Use the account support route to ask what personal data is linked to your profile. Include your registered contact detail and the specific request, such as access, correction or deletion, so we can check it without asking for your password.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the date, amount reference and wallet name through support. Do not send a PIN, password or complete card detail; we only need enough context to trace the record.

Device access concern

Tell us when a sign-in alert or unfamiliar device appears on your account. We can guide the account-check step, ask for suitable verification and help separate a real login from a browser or phone session you no longer use.

HANDLING DETAILS

What We Do With Your Privacy Choices

Privacy work is part of the account path, not a separate promise hidden from the cashier.

Account data

We may hold your registration contact, phone verification result and account activity needed to provide access. These details help us identify your profile when you ask about a sign-in, a wallet status or a Privacy Policy request.

Payment references

A DANA, OVO, GoPay, QRIS, virtual account or bank transfer may produce a reference, status and time record. We use those details to match the transaction path, not to request your wallet PIN or banking password.

Cookies

Cookies can keep an account session working, remember selected settings and help us understand a failed page step. You can adjust cookie controls in your browser, though blocking some cookies may require another sign-in.

Account security

Phone verification, sign-in checks and device signals help us investigate access that does not match your normal account path. We may ask you to confirm account details before discussing private records or changing contact information.

Retention

We retain records only for the period needed for account operation, payment reconciliation, security checks and a lawful request. When a record is no longer needed, our handling process removes it or separates it from direct account identification.

Changes and contact

You can ask us to correct inaccurate details, explain a data use or remove eligible account information through support. We may need account verification first, and we will explain when a record must remain for security or transaction history.

Privacy Policy Answers For kode388

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet status. We describe the practical route for data access, correction, cookies, device security and payment references, while keeping eligibility wording tied to local requirements. If your situation is not covered, use the account support route and describe the exact record or action you want us to check.

The kode388 Privacy Policy covers registration details, phone verification, sign-in and device records, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, virtual account or bank transfer activity.

Phone verification helps us connect an account action to you and investigate an unfamiliar sign-in. It can also protect a request to change contact details or discuss private wallet records. We do not need your phone PIN or banking password.

Yes. Send an account data request through the support route linked to your profile. Include your registered email or phone detail and describe the records you want to access. We may verify ownership before releasing private account information.

Contact support with the wallet name, transaction date and reference shown on your account. For DANA, OVO, GoPay or QRIS, avoid sending a PIN or full credential. We use the supplied reference to check the displayed status.

On a mobile browser, cookies may keep your session active, remember settings and help identify a failed account step. You can change cookie controls in the browser path, but blocking necessary cookies may sign you out.

You can request a correction or removal of eligible information through account support. We first verify the request, then explain what can change. Some security, account or transaction records may need to remain for a stated operational or lawful reason.

Yes, access and eligibility depend on local law. Where local law permits, you can read this Privacy Policy before creating an account. If your location or account status raises a restriction, support can explain the available privacy contact path.

Related Pages

kode388 Indonesia kode388 Casino Liga 2 Over Under Access guide Account information