Reference

kios62 Privacy Policy: Your Data Path

Our Privacy Policy explains how we handle the account details, device signals and wallet records used when you enter kios62.

Account detailsDevice signalsWallet recordsRequest support
kios62 kios62 Privacy Policy: Your Data Path
REQUEST ROUTES

Ask About Your kios62 Data

A clear support route matters when a privacy question appears beside a login or cashier issue.

Account data request Ask us which account details we hold and why they are used.
Wallet record question For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account query, share the…
Security concern If a login or phone verification event looks unfamiliar, use the account support route…
HANDLING DETAILS

Six Ways We Handle Privacy

We organise privacy around the moments you can recognise: opening an account, signing in from a phone, checking a wallet status, or asking for a record change.

Account creation

We collect the details needed to create and maintain your account.

Device and browser

Login time, browser type, device signals, and security events can help us identify unusual access.

Cookies

Cookies and similar storage can keep a session working, remember selected settings, and help us understand technical failures.

Payment matching

Payment references help connect a deposit or withdrawal enquiry to your account.

Security controls

We limit account data access to the people and systems that need it for support, security, or account operations.

Retention and changes

We retain records for the period needed for account service, security, dispute handling, and applicable obligations.

Privacy Policy Questions for Indonesia

These Privacy Policy answers address the searches we expect from someone preparing to open or manage a kios62 account. They cover phone verification, cookies, payment references, device records, deletion requests, and access conditions. If your situation is not listed, send the question through the support route beside the cashier path so we can assess the specific record.

It explains how we handle account details, phone verification records, device signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

Phone verification helps us confirm account ownership before access or sensitive changes. It can also help us investigate an unfamiliar login, wallet-status question, or request involving your account records.

Yes. Operational records may connect your account with lobby actions such as opening Baccarat, Super Bingo, or Fish Hunter. We use those records for account service, security checks, and applicable obligations.

We may record device and browser type, login timing, session signals, and security events. These details help us identify unusual access and diagnose sign-in problems without requesting unrelated files from your phone.

Use the support link beside the cashier path and state whether you want access, correction, deletion, or a use restriction. Include your account identifier; we may complete an identity check first.

We use transaction references to match account activity, check status, and answer payment questions. We do not need your wallet password for that process, and payment services may keep their own records.

Account access and eligibility depends on local law. If you are unsure whether access is available where you are, contact support before sharing additional details or starting an account request.