Reference

km266 Privacy Policy For Your Account

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

Account dataWallet recordsCookie choicesAccess requests
km266 km266 Privacy Policy For Your Account
CONTACT PATHS

Where To Ask About Your Data

A clear contact path helps when you want to understand a Privacy Policy entry or check a record connected with your account. Start from the account support route and include the phone number or email linked to your profile, along with the relevant payment reference if your question concerns DANA, OVO, GoPay or QRIS. We use those details to locate the correct record without asking you to send a wallet password. Requests about account access remain subject to local law and the verification step required to protect your profile.

Team online

Account data request

Ask us to identify the personal details linked to your km266 account. Include your registered contact detail so we can verify that the request comes from you before discussing sign-in records or phone verification.

Wallet record check

For a DANA, OVO, GoPay or QRIS question, send the payment reference and approximate transaction date through account support. We can compare the reference with the account ledger without requesting your wallet PIN or password.

Policy change request

If a stored contact detail is inaccurate, tell us what needs changing and why. We may ask for a verification step before editing the account, particularly when the request affects access from a phone or a new device.

HANDLING DETAILS

Six Ways We Handle Privacy

We apply the Privacy Policy to the practical parts of your account journey: opening an account, confirming a phone, moving between a mobile device and desktop, and matching a wallet receipt.

Account collection

We collect the details needed to create and maintain your account, including contact data and phone verification status. We do not ask for unrelated personal details simply because you browse Live Baccarat Diamond or Fan Tan Live Arena.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets us match a cashier event with the correct account. Bank transfer and virtual account records may also be retained for reconciliation, dispute checks and required financial records.

Cookie controls

Cookies can keep a session active and remember selected settings on your browser. You can manage browser cookie controls, but removing required cookies may sign you out or prevent the account page from recognising your device.

Device security

We may record device, browser and sign-in time details to identify unusual account access. If you move from a phone to desktop, these records help us separate a normal device change from a request that needs verification.

Retention period

We keep personal and payment records only as long as needed for account operation, security checks, dispute handling or legal duties. When a record no longer has a valid purpose, we remove it or reduce it to a form that no longer identifies you.

Your request

You can ask what data we hold, request a correction, or ask whether deletion is available. Send the request through account support with your registered contact detail; we verify identity first and explain where local law requires continued retention.

Privacy Policy Answers For km266

These Privacy Policy answers address the questions we expect before account creation, especially around phone verification, wallet references, cookies and device access. If your circumstances are different, use the account support path with the contact detail attached to your profile. We will explain the applicable process without asking for your DANA, OVO, GoPay or QRIS password.

The km266 Privacy Policy covers contact details, phone verification status, device records and account activity needed to provide access and security checks. We use the data for account support, payment matching and required records, while access and eligibility depends on local law.

No. We use payment references, receipt details and status data to match a DANA, OVO, GoPay or QRIS event with your account. We do not need your wallet PIN or password for this process, and you should never send those credentials to support.

Phone verification confirms that the contact detail used for account access belongs to you. We retain its status and related security records so we can protect the profile, investigate unusual sign-ins and process a later data request after identity checks.

Yes. Send an account support request using your registered contact detail and state whether you want a data copy or correction. We verify your identity before replying, then explain the records available and any retention rule that limits an immediate change.

Cookies can remember your session and selected browser preferences so the account page works consistently. You can adjust cookie settings in your browser. Removing required cookies may sign you out, reset preferences or stop the site from recognising an active session.

We retain payment and device records for the period needed for account operation, security checks, dispute handling or legal duties. After that purpose ends, we remove the record or reduce it so it no longer identifies you where that process is available.

We apply this Privacy Policy to account data handled through our service, but access and eligibility depends on local law. If you are in Indonesia, including Makassar, use the account support path to ask how a local requirement affects your specific data request.