Reference

mob77 Privacy Policy For Your Account

mob77 Privacy Policy explains how we handle your account details, wallet records and activity connected with rooms such as VIP Baccarat and Royal Fishing.

Account dataWallet recordsCookie choicesAccess requests
mob77 mob77 Privacy Policy For Your Account
POLICY CONTACT PATH

Privacy Questions Through Your Account

A clear contact route helps you deal with a Privacy Policy question without sending sensitive details to an unknown address. Start from the support link inside your account and describe whether your request concerns login data, a wallet record or a correction to your profile. If a DANA, OVO, GoPay or QRIS entry needs checking, include the transaction reference rather than your wallet password. We may ask for account verification before discussing private records.

Team online

Account support link

Use the support link shown inside your account for a Privacy Policy question. Include your account ID and the specific record involved, but never send a wallet password or login code.

Cashier record check

For a payment-data request, tell us whether the record concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use the reference to locate the correct entry.

Access request path

Ask for a copy, correction or removal through the account support route. We first confirm account ownership, then explain what can be changed under the applicable local rules.

SIX DATA CONTROLS

Six Controls Behind Your Account Data

We handle Privacy Policy duties through practical account controls rather than vague promises. Login events, device details and verification steps help us detect unusual access, while cookie settings support the mobile browser…

Data we receive

We may receive your contact details, account credentials, verification material, device signals and activity records. Payment references from DANA, OVO, GoPay and QRIS help us match wallet events to your account.

Cookie handling

Cookies can keep your session and selected settings available on a mobile browser. They may also help us understand page errors, and you can manage browser cookie choices through your device settings.

Account security

We use login checks, account verification and device signals to reduce unauthorised access. We will not ask for your wallet password through support, and you should keep login codes private.

Record retention

We retain account, payment and activity records for the period needed to provide access, resolve disputes, detect misuse or meet legal duties. When the need ends, records are removed or restricted.

Policy changes

If a material Privacy Policy change affects your account data, we will place the updated wording where you can read it before continuing. The page date and current terms remain visible for checking.

Your requests

You can ask us to access, correct or remove eligible personal data through the account support route. We may request identity details first, so private records are not disclosed to another person.

Privacy Policy Answers For mob77 Accounts

These Privacy Policy answers cover the searches we hear most often before account access. They explain wallet records, cookies, correction requests and account verification in plain terms, while keeping the same local context used across our Indonesia account flow. If your question is not listed, use the support path inside your account and identify the exact record or policy point you need us to check.

It covers account details, verification records, device signals, cookies, login events, activity records and payment references. It also explains why we use them, how long we retain them and how you can request changes.

DANA and QRIS references help us match a payment status to the correct account, investigate a missing record and respond to a receipt question. We do not need your wallet password for that check.

Yes. Use the support route inside your account and ask for a data copy under the Privacy Policy. We verify account ownership first, then explain which records can be provided and in what format.

Send a correction request through account support and name the field that is wrong, such as contact details or a verification record. We may ask for matching account details before applying the change.

Yes. The Privacy Policy explains that cookies can maintain your session and settings on a mobile browser. You can also manage cookie choices through your browser settings, although some account functions may be affected.

We use account verification, login checks and device signals to identify unusual access. Support will not request your wallet password or login code, and payment checks use transaction references instead.

You can request removal through the account support path. We assess the request against account operation, dispute handling and legal duties, so some payment or verification records may need to remain restricted.