Reference

dubibet Privacy Policy: Your Data Path

At dubibet, our Privacy Policy explains how we handle the details linked to your account, phone verification, device access and wallet activity.

Account dataDevice detailsWallet recordsYour privacy choices
dubibet dubibet Privacy Policy: Your Data Path
CONTACT ROUTES

Privacy Help Beside Account Support

A clear contact path matters when you want to ask about your Privacy Policy rights or a record linked to your account.

Privacy request Send a request through the account support route when you want to know what personal data we hold, why it is used or which service purpose is connected with it. Include enough account detail for us to verify ownership before discussing records.
Account access If phone verification or a device change blocks your request, explain the access issue through the same support path. We may ask for account details already on file rather than requesting sensitive information in an open message.
Wallet record For a DANA, OVO, GoPay or QRIS reference, include the date, amount reference and wallet name shown in your account. We use those details to locate the relevant record while keeping unrelated account activity outside the request.
DATA PRACTICE

Six Ways We Handle Your Data

The practical details below show how our Privacy Policy works during ordinary account use. We separate identity checks from device signals, keep wallet references tied to the correct account and limit internal…

Account details

When you open an account, we handle the contact details and phone verification data needed to establish access. We use those details for sign-in checks, account messages and security checks, not as a reason to collect unrelated personal details.

Device path

Your browser, operating system and connection details can be recorded when you move from mobile login to the lobby. These signals help us identify failed sessions, unusual access and technical faults without requiring a separate app.

Wallet records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may appear in account records. We use them to match a payment status or investigate a receipt, while the wallet provider remains responsible for its own data handling.

Cookies

Cookies and related tools may keep your session active, remember selected settings or help diagnose a page problem. You can manage cookie behaviour through your browser, although changing settings may affect login continuity or saved preferences.

Retention

We retain account, support and transaction records only for as long as the relevant service, security, dispute or legal purpose requires. When a record no longer serves a valid purpose, our handling process moves it toward deletion or anonymisation.

Changes and access

You can ask us to access, correct or clarify eligible personal data through the account support route. We verify your identity first, then explain the result, any correction made and any reason a particular record cannot be removed yet.

Privacy Policy Questions Answered

These answers focus on the searches we hear around the dubibet Privacy Policy, from account creation and phone verification to cookies, wallet references and data requests. Read them before opening an account, then use the account support route if your situation needs a record-specific response. Any access or eligibility question depends on local law.

The dubibet Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It explains why we use each category, when a service partner may process it and how you can ask to access or correct eligible data.

We use phone verification to establish that the account access request relates to you and to reduce unauthorised sign-ins. The verification record can also help us investigate an account recovery request, but we do not treat it as permission to collect unrelated contact details.

Yes. The Privacy Policy includes references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references to match payment status, resolve a receipt question or investigate an account discrepancy; the wallet provider handles its own separate privacy practices.

Use the support route inside your account and state whether you want access, correction or clarification. We verify account ownership before sharing records or changing details. Include the phone or email connected with your account so we can locate the correct data.

We may use cookies to keep a login session active, remember settings and diagnose technical problems between the mobile login page and the lobby. Your browser usually provides cookie controls. If you block some cookies, account continuity or selected preferences may not work as expected.

We may provide necessary data to a service partner handling hosting, security, identity checks or payment processing for a stated purpose. We do not share more than that task requires. We may also respond where a valid legal or security obligation applies.

You can request deletion of eligible personal data through the account support route. We first verify your identity and check whether a record still supports account security, a payment query, a dispute or a legal requirement. We will explain the result and any remaining retention reason.