Reference

Privacy Policy For Your genting Account

genting Privacy Policy explains what account, device and wallet details we collect when you open an account, sign in, or use the lobby.

Account dataWallet recordsCookie choicesAccess requests
genting Privacy Policy For Your genting Account
HELP WITH DATA

Get A Clear Privacy Support Path

A privacy question should not leave you guessing, especially when a login, wallet reference or verification step is involved.

Account request Use the support area after signing in to ask what personal details we hold, why a field is needed, or how a correction request should be submitted. Include the account contact you used so we can avoid sending private details to the wrong person.
Wallet record If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, mention the payment rail and the relevant reference. We can then separate a wallet status question from a Privacy Policy request and check the correct record.
Access concern When a login or verification issue may involve account security, contact us through the signed-in support route where possible. We may ask for an account step or verification response before discussing data, while keeping your secret password out of the request.
DATA HANDLING

What Your Privacy Choices Cover

Privacy Policy choices work best when each request names a specific record or purpose. We handle account access, cookie settings, payment references and security events separately so a request about one area…

Account security

We use login records, verification responses and device signals to help identify unusual account access. A security check can require confirmation through your account contact. We do not need your password in a support request, and you should never place it in a message.

Cookie controls

Cookies and similar browser storage can remember a session, support account movement and help us understand technical errors. You can manage available cookie choices in your browser or through the settings presented by the service, although some account functions may need session storage.

Payment references

A wallet or bank record may show a rail such as QRIS, DANA, OVO, GoPay, BCA, BRI, Mandiri or BNI, together with a reference and status. We use those fields to reconcile activity and respond to a payment-related privacy question.

Retention purpose

We keep personal data for the period connected to account operation, security checks, dispute handling or a legal requirement. When a purpose ends, we remove, anonymise or restrict the record where practical, rather than keeping it without an operational reason.

Correction request

If your account contact or another personal field is wrong, ask for a correction through support and identify the affected field. We may verify that you control the account before changing it, which helps prevent an unknown person from redirecting account contact.

Policy contact

For a copy request, purpose question, correction, restriction or deletion query, use the account support path and write Privacy Policy in your message. Tell us the request type and account contact; we will explain the next step where local law permits.

Answers About genting Privacy Policy

These Privacy Policy answers focus on the questions you are most likely to ask before opening or using a genting account. They cover data collection, wallet references, cookies, account access, retention and requests. If your situation is not listed, send a specific question through support so we can connect it to the right account record and explain the available path where local law permits.

It covers personal details linked to your account, login and device records, verification responses, cookie activity, payment references and support messages. It also explains why we use those details, how retention works, how security checks operate and how you can ask about or change eligible data.

We use account details to create and maintain access, device and session signals to help detect unusual logins, and verification responses to confirm account control. These records also help us investigate a technical issue or answer a request about your account without mixing it with another person’s data.

Yes. Privacy Policy treatment includes references and status linked to DANA, OVO, GoPay and QRIS, as well as bank transfer or virtual account activity. We use those details to reconcile an account event and answer a specific request; a payment reference is not the same as your full identity.

Sign in where possible, open the account support route and write Privacy Policy in your message. Name the request, such as copy or correction, and identify the account contact or field involved. We may verify account control before responding, and the available action depends on local law.

Cookies or browser storage can keep a session active, support movement between account pages and help us diagnose technical errors. Your mobile browser provides its own controls, and the service may present additional choices. Disabling required session storage can prevent some account access steps from working.

Retention depends on the reason for holding a record. Account operation, security checks, payment reconciliation, dispute handling or a legal duty may require different periods. When the purpose ends, we aim to remove, anonymise or restrict eligible data, subject to a continuing legal or security need.

You can send a restriction or removal request through the account support route and explain which data or purpose concerns you. We will assess the request under the applicable rules. Some records may need to remain for security, dispute handling or legal reasons where local law permits.