Reference

Privacy Policy for tunai777login Accounts

tunai777login Privacy Policy shows how we handle your account details, mobile-browser activity and wallet records from DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesPhone verification
tunai777login Privacy Policy for tunai777login Accounts
CONTACT DATA HELP

Get Policy Help Before Account Access

A clear contact path helps you ask about Privacy Policy details before opening an account or while checking a wallet record. Use the support link shown in our account area and include the email or phone detail connected to your profile. We may request a matching account step so we do not disclose private data to the wrong person.

Team online

Policy questions

Send your question through the support route displayed on the site. Tell us whether it concerns account creation, phone verification, cookies or a DANA, OVO, GoPay or QRIS record so we can direct it correctly.

Access checks

If you cannot reach your account, explain the device path you used, such as a mobile browser, and the last successful sign-in step. We use those details to separate an access issue from a data request.

Receipt queries

For a payment record, share the transaction reference and rail name rather than your wallet password or full security code. Our support route can compare a QRIS, bank transfer or virtual account status with your account record.

ACCOUNT DATA PRACTICE

How We Protect Your Account Trail

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

Data collection

We collect account details you provide, phone verification results, sign-in events and payment references needed for account administration. When you open Live Roulette, Aviator or Bingo pages, related browser activity may be recorded for security and service continuity.

Cookie handling

Cookies and similar browser storage can remember a session, preserve a language or region setting, and help us identify suspicious sign-in patterns. You can review cookie controls in your browser, although restricting them may interrupt account access.

Account security

We use phone verification, sign-in event checks and limited device signals to protect your account. Never send a wallet password or security code through support; DANA, OVO, GoPay and QRIS credentials remain with their respective services.

Payment matching

A QRIS receipt, bank transfer reference or virtual account status can help us match a transaction to your account. We use the minimum payment detail needed to investigate status and do not treat a receipt as permission to access your wallet.

Data retention

We retain account, security and transaction records only for as long as needed for the stated service purpose, dispute handling or legal obligations. When a record is no longer needed, our handling follows the retention process described in this policy.

Change requests

You can ask support to correct inaccurate account details, explain a data use or clarify whether deletion or access action is available. Include the relevant account step and contact detail so we can verify the request before responding.

Privacy Policy Questions for Indonesia

These Privacy Policy answers cover the account and payment questions we expect you to ask before access. They explain the practical records connected with a mobile session, phone verification and local wallet activity, while keeping the answer tied to where local law permits and to the contact path available through your account.

It covers data collected during account creation, phone verification, sign-in, mobile-browser sessions, support contact and payment matching. It also explains cookies, security checks, retention and how to ask about your personal data.

Yes. We may retain a DANA or QRIS reference, status and related account details needed to reconcile a transaction. The wallet provider handles its own customer data under its separate terms.

Phone verification helps us confirm that the account belongs to you and supports safer access checks. We may retain the verification result and related event details, but you should never send a security code to support.

The policy can cover browser type, device signals, session events and pages opened during a mobile or desktop visit. These details help maintain a session and identify unusual access around casino or Sportsbook pages.

Use the support link shown in your account area and state whether you want access, correction or an explanation of a record. Include your connected phone or email detail so we can verify the request.

We keep payment references and account records for the period needed for reconciliation, disputes, security and legal duties. The exact period can depend on the record type and applicable local requirements.

Yes. You can contact support through the displayed account help route or review cookie controls in your browser. Restricting session cookies may prevent phone verification or sign-in from completing correctly.