Reference

kerbau 28 Privacy Policy For Your Account

Our Privacy Policy shows how kerbau 28 handles your account, device and wallet data when you use Sic Bo, Bingo or the wider lobby.

Account dataWallet choicesDevice accessPolicy requests

Browse Our Lobby Read FAQ

How DANA And QRIS Data Is Used

kerbau 28 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy describes the data we collect when you open an account, verify your phone, sign in, contact support or request a cashier action. We may receive payment status details linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account steps, while the payment

1
provider handles its own records under its terms. Device type, browser signals, login time and security events help us identify unusual access and keep your account protected. We use this data to provide access, resolve wallet status questions, maintain records required by applicable rules and respond
2
to requests. Any access or eligibility decision depends on local law, and our handling applies where local law permits. You can ask us to explain, correct or remove eligible data through the contact path below.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH PRIVACY

Where To Ask About Your Privacy Policy

A clear contact route helps when you want to ask about the Privacy Policy or a wallet record. Sign in first when possible so we can match your request to the correct account, then use the account help form or the cashier-linked support path. You can also describe a device-access concern without sharing your password.

Team online

Account help form

Use the signed-in account help form for access, correction or deletion requests. Include your registered phone number and the subject of your Privacy Policy question, but never send your password.

Cashier-linked help

If a DANA, OVO, GoPay or QRIS record looks unfamiliar, open the cashier-linked help path and include the date, rail name and status shown on your account.

Access concern

For an unexpected sign-in or device alert, tell us the device type, approximate time and account phone number. We use those details to locate the relevant security event.

ACCOUNT DATA PRACTICE

How We Handle Records And Cookies

Collection

We collect details you provide during account opening, phone verification, support contact and cashier requests. Sign-in events, device type and browser data may also be recorded for account access controls.

Wallet records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment status to your account. We do not need your wallet password to investigate a status.

Cookies

Cookies and similar device signals can keep a session active, remember basic choices and flag unusual access. You can manage browser cookie settings, although some account functions may then need another sign-in.

Account security

Phone verification, sign-in records and device checks help us respond to account security events. If a device is not yours, contact us through the account help path and avoid sending secret credentials.

Retention

We keep account, payment-status and support records only for the operational, dispute, security or legal purpose that requires them. When a record is no longer needed, our process addresses its removal or restriction.

Your request

You can ask what data we hold, request a correction, raise an objection or ask about deletion where applicable. Send the request through signed-in account help so we can confirm ownership before responding.

Privacy Policy Answers For Your Account

These Privacy Policy answers cover the questions we expect before account access: what we collect, how wallet records are matched, how device signals work and how you can contact us. The same request path applies whether you connect from a phone in Yogyakarta or another supported Indonesian location where local law permits.

The Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment-status references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use your phone number for account identification and the verification step before access. It also helps us locate the correct account when you ask about a Privacy Policy request or a wallet status.

No. We use payment rail names and status details to match an account action, but you should never send a DANA, OVO, GoPay or banking password through support.

Cookies can maintain a sign-in session, remember basic access choices and help identify unusual device activity. You can change browser settings, but restricted cookies may require another account sign-in.

Yes. Use the signed-in account help form, state whether you want access or correction, and provide the registered phone number. We may confirm ownership before handling the Privacy Policy request.

We retain payment-status, account and support records for the operational, security, dispute or legal purpose that requires them. Retention can vary by record type and applicable local requirements.

Our data handling and account access depend on local law. We apply this Privacy Policy where local law permits, and you can contact us when a regional requirement affects your request.

kerbau 28 Privacy Policy For Your Account

Where To Ask About Your Privacy Policy

Account help form

Cashier-linked help

Access concern

How We Handle Records And Cookies

Collection

Wallet records

Cookies

Account security

Retention

Your request

Privacy Policy Answers For Your Account

01 What does the kerbau 28 Privacy Policy cover?

02 Why does kerbau 28 need my phone number?

03 Does the Privacy Policy store my wallet password?

04 How are cookies used under this Privacy Policy?

05 Can I request a copy or correction of my account data?

06 How long does kerbau 28 keep payment records?

07 Does access to this Privacy Policy depend on local law?

Related Pages