Reference

Privacy Policy for Your Account Data

mahjong33 Privacy Policy tells you what we collect when you create an account, open Live Blackjack Royal, or choose DANA, OVO, GoPay and QRIS, and why each data…

Account clarityWallet dataCookie choicesAccess requests
mahjong33 Privacy Policy for Your Account Data
CONTACT ROUTE

Get Privacy Help Beside Account Support

A privacy question should not be mixed with a stalled wallet status, so we keep a clear contact path for both matters.

Privacy request Choose the privacy contact path shown in your account and state whether you want to access, correct or delete personal data. We may ask for an account step that confirms you are making the request for your own record.
Wallet reference If your question relates to DANA, OVO, GoPay or QRIS, share the transaction reference rather than a password or wallet PIN. This lets our support team check the matching record while keeping sensitive wallet credentials out of the conversation.
Login concern For an unfamiliar login or device event, contact account support through the route displayed on the site and describe the date, device and action you noticed. We can review the account record and explain the security step available under our Privacy Policy.
SECURITY PRACTICE

What We Do With Your Privacy Choices

Privacy controls work best when each data use has a visible reason. We connect account records to access, payment matching and security checks, while cookies help remember selected settings on your device.

Account data

We collect details needed to create and maintain your account, including contact data and verification results. These records help connect your login to the correct account without requiring you to repeat the same account step each time.

Device signals

Your browser and device can produce login time, operating system and security signals. We use these records to identify unusual access, not to read private files on your phone or computer while you browse the lobby.

Cookie choices

Cookies can remember a session setting or help us understand whether a page loads correctly. You can adjust cookie controls in your browser; changing them may affect saved preferences or require another login step.

Account security

Phone verification and login events help us protect the account connected to Live Blackjack Royal or Surabaya Live Table. Never send a password, wallet PIN or one-time code through support, even when asking about privacy.

Record retention

We keep account, payment-reference and security records only for the account, security or legal purpose described in the Privacy Policy. When a retention period ends, the record is removed or separated from direct account details where practical.

Change requests

You can ask us to access or correct your personal data through the privacy contact route. Include the account identifier and requested change; we verify ownership first, then explain the result or any local-law reason a record must stay.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account and wallet questions you are most likely to have before creating an account. We focus on the records created by login, phone verification, device use and local payment references, including DANA, OVO, GoPay and QRIS. If your situation is different, contact us through the privacy route shown on the site and include only the account details needed to locate your request.

The mahjong33 Privacy Policy covers account creation, phone verification, device signals, cookies, security events and payment references. It explains why we use each category, how long records may remain, and how you can request access or correction where local law permits.

For DANA or QRIS, we may record the selected rail, transaction reference, amount status and time so the account record can be matched. We do not need your wallet password or PIN. OVO and GoPay references are handled for the same matching purpose.

Yes. Our Privacy Policy explains how OVO and GoPay references can be linked to an account transaction record. We use the reference and status needed for reconciliation, while wallet credentials remain outside our support request. A privacy contact can explain a specific record.

Yes, you can request a correction through the privacy contact route shown after account access. State which account detail is wrong and provide the account identifier. We verify ownership before changing the record, and the result depends on local law.

Send an access request through the privacy support path and identify the account you control. We may ask for phone verification or another account step before releasing data. We then explain which records can be supplied and any lawful reason for withholding a part.

Retention depends on the purpose of each record. Account, payment-reference and security data may remain while needed for account operation, fraud checks or legal duties. The Privacy Policy describes the approach, and support can explain a retention question for your account.

Yes. You can adjust cookie settings in the browser controls on your phone or computer. The mobile path from login to the lobby may then ask you to sign in again or may not remember selected settings, while essential account security steps continue.