Reference

Privacy Policy for Your tuan123 Account

Our Privacy Policy explains what tuan123 collects when you open an account, sign in from a mobile device, browse Sic Bo or Royal Fishing, and use DANA, OVO…

Account clarityWallet recordsCookie choicesSecurity steps
tuan123 Privacy Policy for Your tuan123 Account
CONTACT ROUTES

Get Policy Help Through Account Support

Questions about the Privacy Policy should reach the support route linked to your account rather than a public comment thread.

Account request Open support from the account area and state whether you want a copy, correction or deletion request under the Privacy Policy. Include your registered contact detail, but never send your password, one-time code or complete wallet credentials in the message.
Wallet record For a DANA, OVO, GoPay or QRIS question, attach the payment reference or receipt with sensitive digits hidden. We compare that reference with the account ledger so we can discuss the relevant record without exposing unrelated wallet activity.
Security concern If a login from an unfamiliar phone appears beside your account, report the device and approximate time through support. We can review session details, restrict account access where needed and explain which personal data was involved in the security check.
OUR CONTROLS

What We Do With Your Account Data

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

Account details

We use your registration details to create the account, complete phone verification and respond to requests made through support. If a detail is wrong, tell us which field needs correction and provide enough account context for us to avoid changing another person’s record.

Device signals

When you sign in, we may record device and session signals such as browser context, approximate timing and security events. These records help us distinguish a normal mobile return from an unfamiliar login and help us investigate an account concern.

Cookies

Cookies can keep a signed-in session working as you move from account verification to the lobby. They may also remember policy preferences on your browser. You can manage browser cookie settings, although disabling necessary cookies may interrupt sign-in or account requests.

Wallet matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference lets us match a receipt to your account and check a status question. We ask for only the payment detail needed for that check and do not ask for your wallet password.

Security controls

We protect account records through sign-in controls, phone verification and checks for unusual sessions. You also protect your data by using a private device, keeping codes confidential and signing out when a shared browser has been used.

Retention requests

We keep records while they support account administration, security investigations, payment reconciliation or applicable legal duties. You can ask what we hold, request a correction or ask whether deletion is available; we explain any record that must remain and why.

Privacy Policy Questions Indonesian Customers Ask

These Privacy Policy answers cover the account and wallet questions we hear most often before registration. They explain how to make a request, what happens when you change devices, and why payment references or cookies may appear in our records. If your situation is unusual, contact support with the smallest useful amount of personal detail. Account access remains subject to local law.

The Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, game browsing records, support messages and payment references. It explains why we use each category, how we protect it, how long records may remain and how you can request access or correction.

Phone verification helps us confirm that the person opening or recovering an account controls the registered contact. It also supports security checks when a new device signs in. We use the verification record for account protection and do not treat it as permission to contact you for unrelated purposes.

We may keep a payment reference, amount status and timing needed to match a DANA or QRIS request with your account. Similar records can apply to OVO, GoPay, bank transfer and virtual account payments. We do not need your wallet password or one-time code for reconciliation.

Yes. Send an account support request asking for the personal data connected with your account. Include your registered contact detail and explain the request clearly. We may verify ownership before responding, and where local law permits, we will provide the available records or explain any restriction.

Contact support from the account area and identify the inaccurate field, such as a contact detail or payment reference. We may ask for an ownership check before making a change. Do not send your password or verification code; those credentials are never needed to correct an account record.

A new phone can create a fresh session and an additional device-security record. The Privacy Policy allows us to compare that sign-in with your phone verification and account history. If the device is yours, complete the requested check; if it is unfamiliar, report it to support promptly.

Ask support to assess deletion of the personal data connected with your account. We first verify the request and identify records that can be removed. Some account, security or payment records may need to remain for legal duties, dispute handling or protection against unauthorised activity.