Reference

Open kode syair sgp Privacy Policy

Our Privacy Policy explains what we collect when you open an account, sign in on mobile, browse Live Blackjack Grand or check DANA and QRIS status.

Account clarityWallet recordsCookie choicesSecurity checks
kode syair sgp Open kode syair sgp Privacy Policy
CONTACT THE RIGHT DESK

Switch from wallet questions to support

A clear contact route helps you ask about your Privacy Policy rights without describing the whole account again.

Account privacy chat Use the support chat shown after account access when you want to ask what personal details we hold or why a verification step appears. Include your account contact detail so we can separate your request from another account with a similar name.
Wallet record check If your question concerns DANA, OVO, GoPay or QRIS records, send the payment reference and approximate date through the account support path. We can then identify the relevant status entry without asking you to share a wallet password or private security code.
Policy change request Ask through support chat when you need a correction, access copy or deletion assessment. We may request an account verification step before changing personal details, because the Privacy Policy protects your profile from requests made by another person.
HOW WE HANDLE RECORDS

Explore account security beside cookies

We keep the Privacy Policy practical by connecting each data purpose to an account action you can recognise.

Account data

We may collect the contact and verification details you submit while opening or maintaining an account. We use them to provide account access, answer privacy requests and connect a support conversation with the correct profile, rather than treating an unverified message as a confirmed instruction.

Device signals

Your browser or phone can provide session, device and connection details when you sign in. These records help us spot unusual access and keep a session connected while you switch from Live Blackjack Grand to another lobby area.

Cookie controls

Cookies may remember a session, language setting or account-area preference. You can manage cookie behaviour in your browser settings, although restricting some cookies may require you to sign in again or repeat an account step before the lobby opens.

Payment references

A DANA, OVO, GoPay or QRIS transaction can leave a reference, status and time record in the account flow. Bank transfer and virtual account entries may be retained for matching and support, while we never ask for your wallet PIN in a policy request.

Retention rules

We keep personal records only for the period connected to the stated purpose, account protection, dispute handling or a legal requirement. When a record is no longer needed for those reasons, our handling process assesses it for removal or secure restriction.

Your requests

You can ask for access, correction or a deletion assessment through support chat. We may confirm your account identity first, explain any lawful reason for keeping a record, and tell you which part of the request can be completed.

Browse Privacy Policy questions

These Privacy Policy answers focus on the account and payment questions you are most likely to ask before opening access. We keep the wording tied to actual actions, such as signing in from a new phone, checking a QRIS reference or asking for a copy of your data. Where access or eligibility is relevant, it depends on local law.

The Privacy Policy covers account details, verification responses, device and session records, cookie settings, support messages and payment references. It explains why we use each category, how we protect account access, how retention works and how you can request access or correction.

We need the details you submit to create and protect your account, confirm a privacy request and connect support with the correct profile. A verification step may appear before account access or a data change, and service eligibility depends on local law.

Yes. The Privacy Policy includes references and status details connected with DANA, OVO, GoPay and QRIS, along with bank transfer and virtual account entries. We use these records to match account activity and answer payment-status questions without requesting your wallet PIN.

A new phone or browser can create device and session records linked to your sign-in. We use those signals to identify unusual access and may ask for account verification. Cookie restrictions can also end a session, requiring you to sign in again.

Open the support chat available in your account and state whether you want access to your data or correction of a particular detail. Include your account contact reference, but never send a password. We may verify your identity before completing the request.

We retain records for the period needed for their stated purpose, account security, payment matching, dispute handling or a valid legal requirement. The Privacy Policy does not promise one fixed period for every record; support can explain the reason a category remains stored.

You can request a deletion assessment through support chat. We first verify that the request comes from the account holder, then check whether a record must remain for security, payment matching, dispute handling or law. Where local law permits, eligible data can be removed or restricted.