Reference

ddbola Privacy Policy for Your Account

Our Privacy Policy explains how ddbola handles the account data connected with DANA, OVO, GoPay and QRIS activity, from phone verification through payment status checks.

Clear data purposesWallet activity contextRequest paths
Browse Our Lobby Read FAQ
ddbola ddbola Privacy Policy for Your Account
CONTACT ROUTES

Open A Privacy Request Through Support

A clear contact route helps you ask what data is held, why it is needed or how a correction should be made. Start from the support path attached to your account and describe the request without placing sensitive wallet credentials in an open message. We may ask for an account detail or phone verification step so we do not disclose data to the wrong person.

Team online

Account support

Use the signed-in support path for a data access, correction or deletion request. Include your account identifier and the email or phone detail already attached to the account.

Payment status

If a DANA, QRIS, OVO or GoPay record needs checking, send the transaction reference through account support. We use the reference to locate the relevant payment event.

Access concern

When a mobile browser session or phone verification stalls, tell us the device path and account step involved. Do not send a password, wallet PIN or one-time code.

DATA PRACTICES

Explore How We Handle Account Data

We keep the policy practical by connecting each data category with an account action you can recognise.

Account creation

We collect the details needed to open and maintain your account, including contact data and phone verification status. Keeping these fields accurate helps us match requests to the right account.

Mobile sessions

A mobile browser can provide device, browser and session signals when you sign in or move between account pages. These signals help detect unusual access without reading unrelated content on your device.

Cookies

Cookies can remember a session, language choice and selected site settings. You can manage cookies through your browser controls, although some account functions may not work as expected afterward.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may be retained for reconciliation, account support, fraud checks and required financial records.

Security checks

Phone verification and account checks help protect access. For a withdrawal or payment query, we may compare account details with the relevant transaction reference before responding.

Retention requests

We keep data only as long as needed for the stated purpose, account safety or a legal duty. Ask through support if you want the retention basis for a specific data category.

Browse Answers About Privacy Policy

These answers address the account and payment questions we expect you to ask before registration. They cover access, cookies, wallet references, correction requests and deletion limits, while the full Privacy Policy remains the controlling text for your account.

It covers account details, phone verification, sign-in and device signals, cookies, payment references, support messages, retention and requests to access or change your data.

We use phone verification to confirm account ownership, protect sign-in and connect a privacy request with the correct account. We do not ask you to send a one-time code through support.

Yes. The policy covers DANA and QRIS references, along with OVO, GoPay, bank transfer and virtual account records used for payment matching, support and required checks.

Cookies can keep a mobile session active and remember language or site settings. You can adjust them in your browser, but account pages may require a fresh sign-in afterward.

Open the signed-in account support path and state whether you want access or correction. Include your account identifier, then complete any ownership check we request before release.

You can submit a deletion request through account support. We assess it against account safety, payment reconciliation and legal retention duties, then explain which data can be removed.

The policy is written for our Indonesian account flow, but access and eligibility depends on local law. If you connect from Bandung, the same request path remains available where local law permits.

Related Pages

ddbola Indonesia Access guide VIP Baccarat FAQ ddbola Casino