Reference

udang bet Privacy Policy For Indonesia

The udang bet Privacy Policy explains what we collect when you open an account, access the lobby from a phone, or connect DANA, OVO, GoPay and QRIS.

Account clarityWallet data careCookie choicesDirect support
udang bet udang bet Privacy Policy For Indonesia
PRIVACY HELP DESK

Privacy Help For Wallet Receipts

A clear contact path helps when a wallet receipt contains the wrong account detail or your device keeps an old session.

Account access Tell us if phone verification, a saved session or a new-device check blocks your…
Payment receipt For DANA, OVO, GoPay or QRIS queries, share the transaction reference and approximate time.
Data request Ask through support chat or the listed email route to access, correct or remove…
CONTROL AND RETENTION

Cookies, Devices And Account Access

Our privacy process follows the account journey rather than treating every visit alike. A login from a phone can create device and session records, while a QRIS receipt creates a payment reference…

Account details

We use the contact and verification details you provide to identify your account, send access replies and confirm that a privacy request comes from the account holder.

Device signals

Browser type, device markers and session timing help us recognise unusual access. They also explain why a phone may request verification before the lobby opens.

Cookie controls

Cookies can keep a session active and remember selected settings. You can adjust cookie permissions in your browser, although switching them off may require another account check.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us trace a receipt without storing your wallet PIN. We use only the fields needed for that check.

Retention steps

We keep account and transaction records for the operational or legal period that applies, then delete or anonymise them when continued storage is not required.

Your requests

Contact us to ask what data we hold, request a correction, seek eligible deletion or ask about a cookie choice. We may verify identity before responding.

Privacy Policy Questions For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or connecting an Indonesian wallet. We keep each route practical: what we collect, why a device check appears, how payment references are handled and where to send a request. If your situation is not covered, use the support path above and quote only the account details needed to locate your record.

It covers account details, verification, device signals, cookies, payment references and retention. It also explains how to request access, correction or eligible deletion through our support route.

We use device and session signals to recognise account access, detect unusual activity and decide when phone verification is needed. They also help us investigate a repeated login problem.

No. We use transaction references and status details to match DANA, OVO, GoPay or QRIS activity. Do not send a wallet PIN, password or full secret credential to support.

Use the support chat after login or the contact email shown on our brand home. State that your request concerns the Privacy Policy and include your registered contact for ownership checking.

Yes. Send the incorrect field and the replacement detail through support. We may ask for phone verification or another account check before changing identity, contact or wallet-linked records.

Retention depends on the operational purpose and legal requirement connected with the record. When continued storage is not needed, we remove or anonymise the relevant account or transaction data.

The same privacy request route is available across Indonesia, including Semarang and Makassar. Account access and eligibility depend on local law, so local rules may affect what is available.