Reference

ugbet88 Privacy Policy: Your Data Path

ugbet88 Privacy Policy explains what we collect when you open an account, sign in from a mobile browser, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet statusCookie choicesAccess requests

Browse Our Lobby Read FAQ

Your DANA And QRIS Data Explained

ugbet88 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy separates account details from payment references so you can understand why each item is needed. When you create an account, we may record your name, phone number, verification result, sign-in time, device details and security events. When you use DANA, OVO, GoPay, QRIS,

1
bank transfer or a virtual account, we receive transaction references and status updates rather than unrestricted wallet access. We use this data to match a payment with your account, investigate a stalled receipt and protect the account from unauthorised entry. We keep records only for the
2
period needed for account support, security checks, dispute handling and legal duties. Access to our services depends on local law, and our policy applies where local law permits. You can ask us what data is held, request a correction or ask about deletion through the account
3
help path.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP ROUTES

Get Privacy Help Beside Account Access

A clear support route matters when a privacy question appears during login or a wallet check.

Account data request Use the account help path to ask what personal account data we hold. Include your registered phone number so we can verify the request before disclosing any record.

Wallet reference query For DANA, OVO, GoPay, QRIS or bank transfer questions, provide the payment reference and date. We can check the status record without requesting your wallet password or PIN.

Login privacy concern If a new device shows an unexpected sign-in or verification prompt, report it through account help. We may ask for account details and device context to secure the correct profile.

HANDLING PRACTICE

How We Protect Your Login And Wallet Data

We handle Privacy Policy requests as account operations, not as a generic inbox. Phone verification comes before account access, device and sign-in events help us spot unusual activity, and payment references let…

Account security

Before we discuss account records, we check the phone verification connected to your profile. This step helps prevent another person from receiving sign-in details or changing your stored contact data.

Device records

A mobile browser may send device type, browser settings, sign-in time and security signals. We use these records to recognise account activity and investigate an unfamiliar login.

Cookie controls

Cookies can retain session choices and help the account page load correctly. You can manage browser cookie settings, though switching them off may require another login or remove saved preferences.

Retention period

We retain account, security and payment reference data only while it supports account service, dispute checks, fraud prevention or legal duties. Older records are removed or restricted when no longer needed.

Policy changes

If this Privacy Policy changes in a material way, we will place the updated wording on this page. Check the page before opening an account or submitting a new data request.

Correction requests

You can ask us to correct an inaccurate phone number or account detail through account help. We verify the request first, then update the record when the change is supported.

Privacy Policy Answers For Indonesia Accounts

These Privacy Policy answers cover the account steps, device signals and wallet references you are most likely to ask about before opening an account. They also explain how to reach us when you need a record checked, corrected or removed.

It covers account details, phone verification, device and sign-in records, cookies, payment references and support requests connected with your account, including activity involving DANA, OVO, GoPay and QRIS.

We use your phone number to create and verify the account, confirm that a privacy request comes from you and help protect access when a new device or unusual sign-in appears.

No. For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we handle payment references and status details. We do not ask for your wallet password or PIN.

Our records may include device type, browser settings, sign-in time and security signals. These details help us recognise your account session and investigate an access alert without reading unrelated device content.

Yes. Use the account help path, identify your registered phone number and state whether you want a copy or correction. We verify your identity before showing or changing account records.

We keep account, security and payment reference records while they support service, dispute handling, fraud prevention or legal duties. When that need ends, records are removed or restricted where local law permits.

You can submit a removal request through account help. We assess it against active account support, security, dispute and legal needs, then explain which records can be removed or must remain.

ugbet88 Privacy Policy: Your Data Path

Get Privacy Help Beside Account Access

How We Protect Your Login And Wallet Data

Account security

Device records

Cookie controls

Retention period

Policy changes

Correction requests

Privacy Policy Answers For Indonesia Accounts

01 What does the ugbet88 Privacy Policy cover?

02 Why does ugbet88 need my phone number?

03 Does the Privacy Policy give ugbet88 my wallet password?

04 What device data is collected during mobile access?

05 Can I request a copy or correction of my data?

06 How long does ugbet88 keep account data?

07 Can I ask for my data to be removed?

Related Pages