Reference

Open a Clear Privacy Policy Path

coba777 Privacy Policy explains what we collect when you open an account, use the mobile lobby, or check wallet status through DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
coba777 Open a Clear Privacy Policy Path
CONTACT ROUTES

Switch To Support For Privacy Requests

A clear contact route helps you ask about your data without guessing which account team to reach.

Account access If you cannot enter your account after phone verification, contact us through the support…
Wallet records For a DANA, OVO, GoPay or QRIS record, send the transaction reference shown on…
Data questions For a copy, correction or deletion request, use the contact path presented with this…
HANDLING DETAILS

Browse The Controls Behind Your Data

Privacy depends on practical controls, not broad promises. We separate account details from the activity needed to operate access, apply checks when wallet records are reconciled and limit internal handling to the…

Collection

We collect details you enter during account creation, including contact details needed for phone verification. We also receive operational records from actions such as opening Super Sic Bo, checking Fish Hunter or moving from login to the mobile lobby.

Cookies

Cookies can remember a selected session, support security checks and retain your policy choice. On a phone or desktop browser, you can adjust available cookie controls through the page settings; changing them may require another login before account access continues.

Account security

We use sign-in activity, device signals and phone verification to identify unusual access. These checks may appear when you switch from a mobile device to desktop or when account activity does not match your recent session. Never send us your password or one-time code.

Payment records

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount, status and time record. Bank transfer and virtual account records may include matching details needed to reconcile the payment, while wallet data remains connected to the account action that created it.

Retention

We keep records only for the period needed for account operation, security checks, dispute handling and legal duties that apply where local law permits. When a retention need ends, eligible data is removed, anonymised or separated from active account access.

Your requests

You can ask what account data we hold, request a correction, ask about processing or seek deletion where the law permits. We may verify ownership through the account contact before acting, then explain any record we must retain and the reason it remains.

Check Answers About Privacy Policy

These Privacy Policy answers address the searches we hear most often before an account is opened or a wallet is connected. They cover account records, device behaviour, payment references and requests made through the support path. If your question concerns a specific record, include its date and reference rather than sending unnecessary personal details.

It covers account details, phone verification, login activity, cookies, device signals and payment records created through DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains your access, correction and deletion requests where local law permits.

We use your phone number for account contact and the verification step before access. It helps connect the right person to the account when a login stalls or a privacy request is made. We do not need your password or one-time code for support.

Yes. The policy covers references, status details and timing created when you use QRIS, DANA, OVO or GoPay. These records help us match a wallet action to your account and investigate an unclear receipt without treating the wallet selection as permission for unrelated collection.

Cookies may remember a session, policy choice or security state on your mobile browser. If you change cookie controls, the lobby may ask you to sign in again. Desktop and phone browsers can show different settings, so check each device where you access your account.

You can request details held for your account through the support contact shown in the policy area. We may confirm ownership using your account contact before responding. The response can cover account, access and payment records, subject to duties that require certain records to remain.

You may ask us to correct inaccurate details or remove eligible information where local law permits. Send the request through the account support route and identify the record clearly. We will explain if a security, payment reconciliation or legal reason means part of it must remain.

The policy page is intended to explain our handling of account and payment data, while access or eligibility depends on local law. Where local law permits, you can use the stated contact path for data questions, including requests connected with a mobile login or wallet receipt.