Reference

Privacy controls for your account

Your account details, DANA or QRIS status, and device access deserve a clear Privacy Policy.

Account dataWallet recordsCookie choicesContact requests
slotmenang123th Privacy controls for your account
CONTACT ROUTES

Ask about privacy through Support Chat Center

A direct contact path helps you resolve a privacy question without posting account details in public. Use Support Chat Center from the account area when you need to ask what data is linked to your profile, why a verification step appeared, or how to request a correction. We may ask for account identifiers so we can locate the right record, but you should keep passwords, wallet PINs, and one-time codes private. Your request remains about Privacy Policy handling, not a request to disclose another person’s data.

Team online

Data access request

Use Support Chat Center to ask which account details we hold and why they are connected to your sign-in, wallet reference, or account verification record. We will use the account path to check your identity before discussing private details.

Correction request

If your phone number or account detail is outdated, tell us through the support path linked to your account. Include the affected field, but never send a password, wallet PIN, or one-time code in your message.

Privacy concern

For a concern about cookies, device activity, or a payment reference, contact Support Chat Center with the relevant date and account detail. We can route the question to the team handling privacy requests and security checks.

DATA PRACTICES

How slotmenang123th handles your data

We keep this Privacy Policy practical by tying each data use to an account action you recognise.

Account details

When you open an account, we use the details you submit to create your profile, support sign-in, and connect your requests to the correct record. Before discussing private data, we may ask you to complete an account verification step.

Wallet references

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference can be stored beside a transaction request. We use that reference to match status questions, not to ask for your wallet PIN or one-time code.

Device signals

When you sign in from a mobile browser, we may record device and session signals that help identify unusual access. These signals support account protection and are separate from the game choices you make in Live Blackjack Gold or Crash Fast Lift.

Cookies

Cookies can remember a session, support account navigation, and help us understand whether a privacy notice has been shown. You can raise a cookie question through Support Chat Center, especially if your browser settings affect sign-in or policy access.

Retention

We keep account, support, security, and transaction records for the period needed to operate the account, examine disputes, and meet applicable duties. A retention question can be sent through Support Chat Center with your account reference.

Security requests

If you suspect another device reached your account, change your password through the account path and contact Support Chat Center. Tell us the sign-in date or device detail you recognise; do not include private wallet credentials in the message.

Privacy Policy answers for Indonesian accounts

These Privacy Policy answers focus on the account and wallet questions you are most likely to ask before opening access. We explain how to request data, how mobile sessions are handled, and what to do when a DANA, OVO, GoPay, or QRIS reference appears in a support case. If your question is not covered, use Support Chat Center and keep passwords, wallet PINs, and one-time codes out of the message.

It covers account details, sign-in and device signals, cookie use, support messages, wallet references, security records, retention, and requests to access or correct data. It also explains how we handle records connected with DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity.

Open Support Chat Center from your account path and ask for a data access request. We may first check account ownership before discussing private records. Give the relevant account detail, but do not send your password, wallet PIN, or one-time code.

Yes. The Privacy Policy covers device and session signals created when you sign in from a mobile browser or another device. These signals help us identify unusual account access. They are handled separately from your selections in titles such as Dragon Tower Fast Round.

A payment reference helps us match a status question with the correct account record. This can include DANA, OVO, GoPay, QRIS, bank transfer, or virtual account details. We do not need your wallet PIN or one-time code to investigate that reference.

Yes. Send a correction request through Support Chat Center and identify the field that needs changing, such as a phone number. We may verify the account first, then update the record where appropriate and explain any restriction that depends on local law.

We retain account, support, security, and transaction records for the period needed for account operations, dispute checks, security work, and applicable legal duties. To ask about a particular record, contact Support Chat Center with your account reference and the relevant date.

Change your password through the account path, then contact Support Chat Center with the sign-in date, device detail, or other signal you noticed. Do not place wallet credentials or one-time codes in the message. We will use the request to check the account record.