Reference

Open dausbet Privacy Policy Before Account Access

dausbet Privacy Policy explains what we collect when you create an account, verify your phone, use a mobile browser or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice choicesYour requests
dausbet Open dausbet Privacy Policy Before Account Access
REQUEST ROUTES

Ask About Privacy Through Support

A clear support route helps when you want to ask about personal data rather than a game or wallet result.

Access request Ask us what account details we hold by using the support route in your account area. We may request a phone verification step before releasing personal data to the correct account holder.
Correction request If your contact detail or verification record needs correction, describe the change through support and attach only the necessary proof. We will assess the request against account-safety and legal requirements.
Wallet privacy help For a DANA, OVO, GoPay or QRIS receipt connected with your account, share the transaction reference rather than wallet credentials. This lets us trace the record while limiting sensitive payment details.
DATA PRACTICES

Explore How We Handle Your Data

Privacy choices work best when the handling steps are visible. We separate account identification from payment references, limit access to records needed for support or service operation, and use account checks before…

Account collection

When you open an account, we collect the details needed for phone verification and account access. We do not ask you to place a wallet PIN or banking password into our account form.

Device signals

A mobile browser or desktop session may provide device, browser and session signals. We use them to recognise unusual login patterns, investigate access issues and keep privacy controls tied to the right session.

Cookie choices

Cookies can remember a session path and support basic account functions. You can manage cookie settings through your browser, though turning them off may affect sign-in continuity or request handling.

Account protection

Phone verification helps us check account ownership before access or a data response. Never send a password, wallet PIN or full banking credential through support when asking about Privacy Policy matters.

Record retention

We retain account, support and transaction references only for the period needed for service records, dispute handling, security checks or legal duties. Retention can differ by record type and applicable local requirements.

Change requests

You can ask us to access, correct or remove eligible personal data through the stated support route. We may verify your identity first and explain if a record must remain for a legal or security reason.

Find Privacy Policy Answers For dausbet

These Privacy Policy answers address the searches we hear most often before account creation. If your situation is not covered, contact us through the account support route with a clear description and the smallest amount of personal data needed to identify your request.

It covers account details, phone verification, device and browser signals, cookies, support records and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create and verify the account, help confirm account ownership and handle privacy requests. We may ask for another check before discussing records connected with that number.

Our account process does not require you to send a DANA, OVO or GoPay PIN to us. Payment records may contain a reference, amount or status needed to match a transaction, not your wallet password.

Use the support path shown after account access and state that you are making a personal data request. Include your linked phone number, then complete any ownership check we reasonably require.

Yes, you can ask for an eligible correction through support. Tell us which account detail is inaccurate and provide only the proof needed to assess the change without exposing unrelated financial credentials.

Send a removal request through the account support route. We will check ownership and explain which records can be removed, while some transaction, dispute or security records may need to remain.

Yes. Account access and data handling depend on local law. If you are in Indonesia, use the current Privacy Policy and contact support when you need clarification about an eligible request.