Reference

udangbet77 Privacy Policy for Indonesia

Our Privacy Policy at udangbet77 explains what we collect when you open an account, sign in from a mobile browser, or check wallet status through DANA and QRIS.

Account recordsCookie choicesWallet checksPrivacy requests
udangbet77 udangbet77 Privacy Policy for Indonesia
PRIVACY HELP PATH

Privacy Help Along Your Account Path

A clear contact path helps when your account record or wallet receipt needs attention. From the support route displayed on our site, tell us the account phone or email connected to the request, the date of the relevant action, and whether it concerns DANA, OVO, GoPay, QRIS, or a bank transfer. We use those details to locate the right record without asking you to send a password.

Team online

Account data request

Ask which personal details are linked to your account and state the phone or email used at opening. We may verify ownership before discussing any record.

Wallet record query

For a DANA, OVO, GoPay, QRIS, or bank transfer query, include the receipt reference and date. We use that context to separate payment evidence from unrelated account data.

Policy change request

Use the displayed support contact path to request correction, clarification, or a copy of available data. Please describe the exact field or policy passage you want us to check.

HANDLING YOUR RECORDS

Data Handling Behind Your Lobby Access

We keep this policy practical by connecting each data action to an account step you can recognise.

What we collect

We may hold account contact details, phone verification status, login timestamps, device signals, cookie choices, support messages, and payment references supplied through DANA, OVO, GoPay, QRIS, or bank transfer.

Cookie controls

Cookies can preserve your selected settings, help maintain a signed-in session, and show which policy page was opened. Your browser controls can clear them, although some account steps may then need repeating.

Account protection

Phone verification before account access helps connect a sign-in with the correct account. We do not ask for your password in a support message, and device signals can flag an unfamiliar session for checking.

Payment separation

A DANA or QRIS receipt is used to match a transaction reference, while OVO and GoPay status details help resolve the relevant wallet event. These records are not treated as permission to read your wallet.

Retention approach

We retain account, support, technical, and transaction records only for the period needed for the stated purpose, account reconciliation, dispute handling, security checks, or legal duties that apply.

Changes and requests

If a detail is inaccurate or you want clarification about this Privacy Policy, contact us through the displayed support path. Include the affected account step so we can route the request correctly.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. We explain the practical path for access, correction, cookies, device details, and contact requests, while eligibility remains subject to where local law permits. If your situation is not listed, use the support route shown on the site.

It covers account details, phone verification, device and browser signals, cookie choices, support messages, and transaction references connected with DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account.

Phone verification helps connect account access with the correct record and assists with unusual sign-in checks. We use the status for account administration and do not request your password through support.

Yes. The Privacy Policy covers payment references and receipt details supplied during reconciliation. We use a DANA or QRIS reference to locate the related account event, not to access your wallet contents.

You can send a request through the support contact path displayed on our site. Identify the account phone or email and the record you want checked; we may verify ownership first.

Describe the incorrect field, such as a contact detail or account status, and send it through the displayed support route. Include the relevant account step so we can review the correct record.

It does. Cookies can keep a mobile browser session and remember your policy choice, while technical logs may record browser type and access time. Clearing cookies can require another sign-in.

We keep records for the time needed for the stated account, reconciliation, security, dispute, support, or legal purpose. The applicable period can differ by record type and local legal requirement.