Reference

Privacy Policy For Your kode555 Account

kode555 Privacy Policy explains what we collect when you create an account, sign in from a mobile device, browse Live Blackjack Table, or use DANA and QRIS.

Account clarityWallet recordsCookie choicesLocal access
kode555 Privacy Policy For Your kode555 Account
HELP WITH PRIVACY

Get Clear Answers About Your Records

A privacy question should not slow down your account decisions. We keep the contact route close to the sign-in and cashier areas, so you can ask about a phone record, wallet reference…

Account path Open the support route from your signed-in account when you need a Privacy Policy explanation. We can use the account identifier and phone verification status to locate the relevant record without asking you to resend unrelated wallet details.
Wallet status For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share the payment reference and status shown in your account. We use that context to separate a transaction query from a request to change personal data.
Correction request If your name, phone detail or contact record needs attention, state the exact change through the account support route. We may ask for an account step or phone check before changing information linked to access or wallet records.
DATA HANDLING

What Our Privacy Process Covers

We treat this Privacy Policy as an operating process, not a page kept apart from your account.

Collected details

We may handle the account details you submit, your phone verification result, sign-in events, device signals and payment references. We use these details to provide account access, match wallet activity and investigate a request tied to your own account.

Cookie controls

Cookies can remember sign-in context and selected settings on the device you use. If you clear cookies or change browser permissions, you may need to repeat an account step before the lobby or wallet status appears.

Account security

Phone verification helps connect account access with the contact detail you provided. We may check sign-in or device signals when a request concerns access, a wallet reference or a change to information held on your account.

Retention timing

We keep records only for the period needed to support account questions, check payment status, protect access or meet applicable legal duties. A retention question can name the record involved, such as a QRIS reference or sign-in event.

Who to contact

Use the support route attached to your account for Privacy Policy questions. Tell us whether your concern involves a device, cookie, phone detail, DANA status or another record so the request reaches the right handling path.

Change requests

You can ask us to correct personal details, explain how a record is used or clarify whether a record remains necessary. We may confirm account ownership before acting, especially when the request could affect sign-in or payment history.

Privacy Policy Answers Before Account Access

Before opening an account, you can use these Privacy Policy answers to understand the practical steps behind data access, wallet records and device use. We keep the wording tied to kode555 account activity, including phone verification, QRIS references and mobile sign-in. Where access or eligibility matters, it depends on local law.

The kode555 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support requests and payment references. It explains why we use each category, how retention works and how you can ask for correction or clarification through your account support route.

Yes. The Privacy Policy explains that DANA and QRIS activity can create payment references and status records linked to your account. We use those details to match a transaction question, check its state and respond to support requests without treating wallet data as public profile content.

Phone verification connects the contact detail you provide with account access and helps us assess requests involving sign-in or personal data. If you ask to change a phone record, we may repeat an account check before updating information that could affect access.

You can request a correction through the support path connected to your account. Identify the detail that is wrong, such as a phone or contact record, and explain the requested change. We may confirm account ownership before making an update to protected account data.

Cookies can retain sign-in context and selected settings on your phone or browser. Clearing them may remove that context, so you might repeat phone verification or another account step before returning to the lobby. Our Privacy Policy explains this device behaviour and related choices.

Retention depends on the type of record and the reason it remains necessary. A DANA, GoPay, bank transfer or virtual account reference may be kept for account support, status checks, security review or legal duties where local law permits.

Use the support route shown after account access or near the cashier path. Include your account identifier and the subject of your question, such as cookies, QRIS status or data correction. We will use those details to identify the relevant Privacy Policy request.