Reference

Privacy Policy For Your tuanmuda88 Account

Our Privacy Policy explains how tuanmuda88 handles the account details connected with DANA, OVO, GoPay and QRIS, from phone verification through wallet status checks.

Account dataWallet recordsCookie choicesContact requests
tuanmuda88 Privacy Policy For Your tuanmuda88 Account
CONTACT ROUTES

Policy Help For Wallet Status

A direct contact request helps us separate a Privacy Policy question from a delayed wallet status. When you write to our support route, include your account identifier and the subject of your request, but do not send a full password or one-time verification code. This lets us check the right record without asking you to expose secret login details. If you are in Medan or elsewhere in Indonesia, the same account privacy path applies where local law permits.

Team online

Data access request

Ask which account fields and transaction references we hold by sending a support request from the contact path connected with your account. We may ask for an account step to confirm that the request comes from you.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, tell us the date, rail and visible status. We use those details to locate the relevant record without requesting your wallet password.

Correction request

Send the field you want changed and the reason for the correction. We compare your request with the account record, then explain any identity check needed before updating personal data.

DATA CONTROLS

Six Data Safeguards For Your Account

We handle Privacy Policy duties through practical controls rather than broad promises. Account access starts with phone verification, while sign-in events and device signals help us investigate an unfamiliar session.

Account details

We use the details needed to create and maintain your account, including contact data and phone verification status. Keeping your phone number current helps us connect a privacy request with the correct account record.

Device signals

A mobile browser may send device and sign-in signals that help identify an unfamiliar session. These signals support account protection and are not treated as a separate profile for unrelated purposes.

Cookie settings

Cookies can keep the account path working between sign-in and the lobby. You can review cookie controls in your browser settings, although removing some cookies may affect session continuity.

Wallet records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be stored to match a transaction status with your account. We do not need your wallet password to check that reference.

Retention approach

We keep personal data and transaction records for the period needed to provide account service, resolve disputes, reconcile payments and meet legal duties. When no valid need remains, handling follows our deletion process.

Change requests

To request access, correction or deletion where available, contact us with your account identifier and the requested action. We may verify account control before changing or disclosing personal data.

Privacy Policy Questions About Your Data

These Privacy Policy answers cover the account steps most likely to matter before you continue: phone verification, wallet references, browser cookies, device signals and requests for access or correction. If your question is not listed, contact us through the support route with only the details needed to identify your account.

It covers account details, phone verification, sign-in and device signals, cookies, wallet references and support requests. It also explains why we use those records, how retention works and how you can request access or correction where applicable.

Phone verification helps connect account access with the person creating the account and supports checks when you request a data change. We use the verification status for account protection, not as permission to collect unrelated personal details.

Yes. The Privacy Policy covers transaction references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. These references help us match a visible payment status with the correct account.

You can send a data access request through our support route and identify the account concerned. We may ask for an account-control check before responding, so personal data is not disclosed to someone who cannot verify the account.

State the account field that appears wrong, provide the corrected detail and explain the request through support. We compare the request with the account record and may complete a phone or account check before making the change.

We retain records for the time needed to provide account service, reconcile DANA, OVO, GoPay, QRIS or bank activity, resolve disputes and meet legal duties. The exact period depends on the record type and applicable requirements.

Cookies can support the mobile sign-in path and keep a session connected while you move between account and wallet pages. You can manage them in browser settings, but removing required cookies may interrupt that session path.