Reference

udangbet Privacy Policy For Your Account

Our udangbet Privacy Policy explains how we handle the details connected with your account, device and wallet activity.

Clear data purposesWallet record contextCookie choicesAccount request path
udangbet udangbet Privacy Policy For Your Account
PRIVACY CONTACT

Reach Us About Your Privacy Policy

A direct contact route helps when you want to ask about a record, cookie or account detail. Sign in first when possible, then use the support contact shown in your account area and include the email or phone linked to your udangbet account. For a wallet question, add the DANA, OVO, GoPay or QRIS reference without sharing a PIN or password.

Team online

Account privacy request

Use the support contact inside your account to ask what personal details are linked to your phone verification or login record. We may request account details before discussing the request.

Wallet record question

When a DANA, OVO, GoPay or QRIS reference needs checking, send the transaction reference and date only. Keep your wallet PIN, one-time code and password private while we trace the record.

Cookie assistance

If a cookie choice affects your sign-in path on mobile or desktop, contact us from the account support route. Tell us your device type and browser so we can examine the session issue.

DATA PRACTICES

How Your udangbet Data Is Handled

We keep this policy practical by linking each data use to an account action, payment check or security need.

Account data

We may use your phone number, login details and account identifiers to create access, verify an account request and respond to questions about your udangbet records.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match deposits or withdrawal checks with the correct account without requesting your wallet password.

Cookies and sessions

Cookies can remember a sign-in session, language setting or security preference. You can remove or restrict them in your browser, although some account steps may then need repeating.

Device security

We may record device type, browser details, approximate session timing and security events to investigate unusual access. On mobile, clearing site data can end your current login.

Retention periods

We retain records for as long as needed for account support, payment reconciliation, security checks or legal duties. When a record is no longer needed, our process removes or anonymises it.

Changes and requests

To request correction, access or deletion, contact us through the account support path with your linked phone or email. We verify ownership before changing or releasing personal details.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or asking us to change a record. We keep the request path tied to your account details, device session and payment reference so the right record is discussed. Where access is discussed, it depends on local law.

The udangbet Privacy Policy covers account details, phone verification, device and session records, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

We use your phone number to create and secure the account, complete the required phone verification step and confirm that a privacy or account-change request comes from the account holder.

Yes. The Privacy Policy covers payment references from DANA, OVO, GoPay and QRIS, plus bank transfer and virtual account records, when those details are needed for matching, support or security checks.

Contact us through the support path inside your account and identify the linked phone or email. We verify ownership, then assess your access or correction request against security and retention requirements.

Cookies can keep your login session and security preference connected between account pages. You can manage them in your mobile or desktop browser, though restricting cookies may require another sign-in.

We keep records for account support, payment reconciliation, security checks or legal duties for the period needed for those purposes. Afterward, records are removed or anonymised through our retention process.

You can submit a deletion request through account support. We first confirm ownership and then check whether payment, security or legal duties require certain records to remain for a defined period.