Reference

Open Your Privacy Policy Path

welcome to hk Privacy Policy explains what we collect when you create an account, use DANA or QRIS, and move between the lobby and cashier.

Account dataWallet recordsCookie choicesPrivacy requests
welcome to hk Open Your Privacy Policy Path
HELP WITH PRIVACY

Contact Us About Your Policy

A clear request path matters when a phone number, wallet record, or login device needs attention. We keep privacy help close to the account and cashier areas so you can describe the issue without sending payment details through an unrelated route. Include the email or phone connected to your account, the request you want handled, and any receipt reference that helps us locate the record. We may ask for account checks before changing personal data.

Team online

Account request

Use the privacy contact route shown inside your account when you want a copy of your stored details, a correction to your phone record, or an explanation of how an account field is used.

Wallet query

For a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference, send the receipt number and date through the support path beside the cashier so we can separate payment status from personal data.

Security concern

If a login device looks unfamiliar, contact us through the account support route and pause further account changes. We may confirm ownership before discussing activity connected with Two Factor Setup or another security step.

ACCOUNT SAFEGUARDS

Explore How We Handle Your Data

Privacy controls work best when they match the way you actually use the account. We record only the details needed for access, wallet status, security checks, and support handling, then apply retention…

Account details

We may hold your name, phone number, login credentials, verification results, and account preferences. These details let us connect one account with casino access and local wallet status without asking you to repeat the same account step.

Device signals

Your browser type, device identifier, IP-related signals, and login time may be recorded for access checks. On mobile, this helps us notice a new device before account changes or wallet actions continue.

Cookies

Cookies can keep your session active, remember selected settings, and help us understand whether a page request came from the same browser. You can manage cookie controls through your browser, though some account functions may then need another login.

Security steps

We use account verification and security events to protect access. Two Factor Setup can add a separate check after your password, and an unfamiliar login may prompt us to confirm ownership before discussing account or wallet records.

Storage periods

We keep account, support, and payment references only for the period needed for account operation, dispute handling, security checks, or legal duties. When a record is no longer needed, our handling follows the deletion or anonymisation process set in policy.

Your requests

You can ask for access, correction, deletion where available, or an explanation of use through the privacy contact route. We may request a matching phone or account detail first so another person cannot obtain your records.

Browse Privacy Policy Questions

These answers focus on the questions we expect you to ask before opening an account or connecting a local wallet. They explain the Privacy Policy in practical terms, including device access, payment references, cookies, retention, and requests for a copy or correction. If your situation is not covered, use the privacy contact path connected with your account.

It covers account details, verification, login and device events, cookies, support messages, and wallet references. It also explains why we use those records, how long they may remain, when a provider handles its own data, and how you can request access or correction.

We use your phone number to create and protect account access, connect you with verification steps, and investigate account requests. It can also help us distinguish your account from another record when you ask about a DANA, OVO, GoPay, or QRIS transaction.

It covers the payment references we receive, such as a receipt number, amount status, date, and linked account details. DANA and QRIS may process additional data under their own terms, so you should also check the relevant provider wording for its handling.

Yes, send a request through the privacy contact route shown in your account. Tell us which records you want, such as account details, device events, support messages, or wallet references. We may verify the matching phone or account detail before releasing a copy.

Use the privacy request path and identify the field that needs correction, such as a phone number or account name. Include the accurate replacement and a matching account detail. We may pause the change until ownership checks are complete.

Yes, cookies may keep a mobile session active, preserve selected settings, and support account navigation from login to the lobby. Your browser controls can limit them, but turning some off may require another login or affect account page functions.

The period depends on the type of record and the reason it is needed. We may retain account, security, support, and payment references for operation, dispute handling, or legal duties, then delete or anonymise them under the Privacy Policy process.