Reference

Privacy Policy for resort slot

resort slot Privacy Policy explains what we collect when you open an account, use DANA, OVO, GoPay or QRIS, and move between the lobby and cashier.

Account dataWallet recordsCookie choicesContact route
resort slot Privacy Policy for resort slot
CONTACT PATHS

Privacy help beside your account

A clear contact path matters when you want to ask about your Privacy Policy choices or correct an account record. Start from the support link in your account area and include the email or phone detail connected to your profile, without sending a password or wallet PIN. If your question concerns a DANA receipt, QRIS reference or access problem, the relevant transaction date helps us locate the record. We use the same route for policy questions and account-security concerns.

Team online

Policy questions

Use the support link inside your account to ask how the Privacy Policy applies to a record, cookie choice or account detail. Include the subject of your request and the contact detail linked to your profile so we can separate your case from another account.

Wallet records

For DANA, OVO, GoPay or QRIS questions, attach the payment reference or receipt date rather than a wallet password. We check the account-side status against the available transaction record and explain what data we hold for that payment.

Access concerns

If a sign-in or phone-verification issue may involve account misuse, contact us through the account help path and describe the device behaviour. Never send your password, PIN or one-time code; we use safer account checks before discussing protected records.

DATA PRACTICES

What we do with your records

We keep this policy practical by linking each data use to an account action you can recognise.

Account creation

When you open an account, we collect the details needed for the account path and phone verification. We use those details to identify your profile, send account-related responses and connect a cashier record to the correct account rather than relying on a display name alone.

Cookies and devices

Cookies and device signals can remember a session choice, recognise a returning browser and help us investigate unusual access. You can manage browser cookie settings, although switching them off may require another sign-in or prevent a saved lobby preference from working.

Payment matching

A DANA, OVO, GoPay or QRIS reference helps us match a wallet event with your account. Bank transfer and virtual account records may be retained for reconciliation. We do not need your wallet PIN to check whether a payment reference reached the cashier record.

Account security

Phone verification before account access gives us an account step to check when a sign-in looks unfamiliar. We may record device type, sign-in time and security events, then use that trail to investigate access concerns without asking you to reveal a password.

Retention periods

We retain account, support and transaction records only for the period needed for the stated purpose, account administration, dispute handling or applicable legal duties. When a record is no longer needed, we remove it, anonymise it or restrict access where appropriate.

Requests and changes

You can ask us to access, correct or clarify personal data connected to your account through the support link. Tell us which record you mean, such as a phone detail or QRIS reference. We verify the request before making a change and assess it where local law permits.

Privacy Policy answers for Indonesia

These Privacy Policy answers cover the searches we expect before you open an account or return to the lobby. We explain the practical records behind phone verification, cookies, wallet checks and support requests, including what to send when a receipt or device event needs attention. If a question depends on location or a legal request, we apply the rules relevant to you; access depends on local law. You can use the account support route when the answer does not resolve your specific record.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, and payment records linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security checks and how to request access or correction where local law permits.

Phone verification helps connect account access to the contact detail you supplied and gives us a check when sign-in behaviour looks unusual. We may record the verification event, device type and time, but you should never send a password, wallet PIN or one-time code through support.

Yes. The Privacy Policy covers the account-side reference, status and timing needed to match a QRIS, DANA, OVO or GoPay event. For bank transfer or virtual account activity, we may also keep reconciliation details. We do not need your wallet PIN to investigate a receipt.

Use the support link in your account and describe the record you want reviewed, such as a phone detail, sign-in event or QRIS reference. We verify that the request comes from the account holder, then assess access, correction or another request under applicable local rules.

We keep records for the period needed for account administration, payment reconciliation, support handling, dispute checks or legal duties that apply to us. After that purpose ends, we remove, anonymise or restrict the record where appropriate. The exact period can differ by record type and local law.

You can manage cookies through your mobile browser settings. Turning some cookies off may remove a saved preference or require another sign-in, while device and security records may still be needed to protect account access. Contact support if a cookie choice causes an account-path problem.

Use the support route inside your account and state whether your concern involves personal data, a device sign-in, a wallet receipt or a correction request. Include only safe identifying details, such as the linked contact and transaction date. Eligibility and access questions depend on local law.