Reference

mujurtoto2 Privacy Policy for Your Account

mujurtoto2 Privacy Policy explains how we handle the account, device and wallet details connected with Sic Bo, Aviator, Bingo and other lobby areas.

Account clarityWallet data choicesDevice privacySupport access
mujurtoto2 mujurtoto2 Privacy Policy for Your Account
PRIVACY HELP ROUTES

Contact Us About Privacy Policy

A clear support path is available when you need to ask about personal data, an account record or a wallet reference. Start from the support route connected to your account and include the phone number used for verification, the relevant transaction reference and the specific change you want. We use those details to locate the right record without asking you to send a wallet passcode.

Team online

Account data request

Ask us to identify the account details connected with your phone verification. We may request a matching account step before discussing records, so private data is not disclosed to the wrong person.

Wallet status question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account queries, send the payment reference and status shown in your account. We use that reference to trace the relevant record.

Change or correction

Tell us which personal detail needs correction or removal and why. Our support route can explain whether the record may be changed while account security and legal retention duties remain active.

HOW WE HANDLE DATA

Explore Privacy Controls Across Your Account

Privacy work follows the same account path you use to reach the lobby: phone verification, sign-in, wallet status and support.

Account collection

We collect details you provide during account creation, phone verification and support contact. This can include your phone number, account identifiers and messages needed to resolve a privacy request.

Payment matching

DANA, OVO, GoPay and QRIS references help us match a payment event with your account. Bank transfer and virtual account records support reconciliation, while wallet passcodes stay outside our request.

Cookies and devices

Cookies and device signals can keep your session connected, remember a security setting and help identify unusual sign-in behaviour. Clearing browser data may require you to complete account verification again.

Session security

We compare account activity with phone verification and device signals when access looks unusual. If a session needs checking, support may ask for account details rather than a wallet passcode.

Retention practice

We retain account, payment and support records for as long as needed for the stated service purpose, security checks or legal duties. When a record is no longer needed, we remove or de-identify it.

Change requests

You can ask us to access, correct or clarify personal data through the account support route. Include the requested action and matching account step so we can protect your records during the response.

Browse Privacy Policy Questions Before Opening

These Privacy Policy answers cover the practical questions you may have before opening an account on mujurtoto2. We explain the data connected with sign-in, local payment references, device behaviour, correction requests and access conditions, so you can decide what to submit before starting the phone verification step.

The Privacy Policy covers account details, phone verification, device signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity.

Phone verification helps us connect an account request with the correct person and protect account records. It may be used again when an unusual device or access pattern needs checking.

No. Our Privacy Policy describes the payment reference and status details needed for matching, but we do not ask for your DANA or OVO wallet passcode to handle a support request.

Yes. Use the account support route, state whether you want access or correction, and include a matching account step. We check the request before discussing personal records.

Cookies can support sign-in continuity, security settings and session checks. If you clear them, you may need to verify your phone or sign in again before account access.

We keep records for the operational purpose, security need or legal duty that requires them. When those needs end, we remove or de-identify the relevant account, payment or support record.

Access and eligibility depends on local law. Where local law permits, you can follow the account path, complete phone verification and contact support about any privacy or access question.