Reference

buaya77 Privacy Policy for Your Account

buaya77 Privacy Policy explains how we handle the account, wallet and device details connected with Super Sic Bo, Wild Wild Riches and other lobby areas.

Account clarityWallet recordsCookie choicesPrivacy requests
buaya77 buaya77 Privacy Policy for Your Account
HELP WITH REQUESTS

Privacy Help for Wallet and Login Records

A clear support path helps when you need to ask what we hold, correct an account detail or question a wallet record.

Account data Ask us to locate the personal details connected with your account. Include your registered contact route so we can compare the request with the account record before discussing it.
Wallet record For DANA, OVO, GoPay or QRIS questions, share the transaction reference and date rather than wallet credentials. We can then check the payment record while keeping sensitive wallet access details private.
Access concern If a phone verification step or unfamiliar device blocks your request, tell us the device type and sign-in time. We use those details to review the session without asking for your password.
OUR DATA PRACTICE

How buaya77 Handles Your Data

Our privacy process follows the path your information takes: account entry, lobby access, wallet reference, security check and support request.

Account creation

When you open an account, we use the submitted contact details and phone verification result to create the profile and protect the sign-in path. We do not need your DANA, OVO or GoPay password for this step.

Cookie controls

Cookies and similar session tools help keep your login, language choice and page security connected. Your browser can restrict or clear them, although doing so may require another sign-in before you reach the lobby.

Device signals

We may record browser family, operating system, approximate session time and security events. These signals help us compare a familiar mobile path with an unusual desktop login without reading unrelated files on your device.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference lets us match a deposit or withdrawal request to your account. We use the reference for checking status and do not request a wallet PIN.

Retention choices

We retain account, security and transaction records only as long as needed for the stated purpose, dispute handling or applicable obligations. When a record no longer serves that need, our process is to remove or de-identify it.

Privacy requests

You can ask for access, correction, deletion or a restriction where local law permits. Send the request through account support with enough detail to identify the record; we may verify your account before making a change.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers address the questions we expect before an account is opened or a wallet record is checked. We keep the wording tied to actual account steps, device sessions and payment references, so you can decide what to share and how to contact us. If your request involves eligibility or access, it depends on local law.

The buaya77 Privacy Policy covers account details, phone verification, sign-in events, cookies, device signals, support messages and payment references. It explains why we use each category, how long records may remain and how you can request access or correction where local law permits.

We may collect the contact details you submit, your phone verification result and account activity needed for sign-in protection. We do not need a DANA, OVO or GoPay password. Providing accurate details helps us match a privacy request with the correct account.

No. We use transaction references and status details for DANA, OVO, GoPay, QRIS, bank transfer and virtual account checks. Your wallet password or QRIS PIN should not be sent to support. If a message requests either credential, do not share it.

Device and browser signals help us recognise a normal mobile login, connect a session to the account and flag unusual access. We may record the browser family, operating system and session time, but these signals do not give us access to unrelated files.

Open the account support area and select the privacy request path. State whether you want access, correction, deletion or a usage explanation, then include your registered contact route. We may verify the account before responding, and some requests depend on local law.

Retention depends on the purpose of each record. We may keep account, security and payment references while needed for account protection, dispute handling or applicable obligations. After that need ends, our process is to remove or de-identify the record.

You can submit a deletion request through account support where local law permits. We first confirm the request belongs to you, then assess records that must remain for security, unresolved disputes or applicable obligations before removing or de-identifying eligible data.