Reference

ugbet Privacy Policy for Your Account Data

ugbet Privacy Policy puts your account, wallet and device records in plain view, including activity linked to VIP Baccarat and QRIS.

Account dataWallet recordsDevice detailsPolicy requests

Explore Our Lobby Read FAQ

Privacy Policy for DANA and QRIS

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

Our Privacy Policy describes the records created when you open an account, complete phone verification, sign in, contact support, or select a wallet route. That can include contact details, sign-in events, device and browser signals, payment references, account activity, and messages needed to resolve a status

1
question. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a deposit or withdrawal request to your account; they do not change the policy purpose. We use these records to provide account access, check requests, respond to questions, protect account integrity, and
2
meet applicable obligations. We do not use this page to promise access in every location: eligibility depends on local law, and the service is available only where local law permits. The current policy explains applicable handling, retention and request routes.

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

HELP WHEN NEEDED

Get Policy Help Beside Account Support

A clear support route helps when a Privacy Policy question concerns a login event, wallet reference or account record. From the account help path, tell us which detail you want checked and include the phone number linked to your account. Our support chat can clarify a DANA receipt, QRIS status or data request without asking you to post private details publicly.

Team online

Policy questions

Use the support chat for a Privacy Policy question, naming the account step or record involved. We can explain the relevant handling route and tell you what details are needed for a precise response.

Wallet records

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the receipt reference through account support. Keep wallet passwords and one-time codes out of your message while we check the account match.

Change requests

Ask support to correct an account detail or explain a stored record. We may ask for phone verification before changing information, so the request remains connected to the right account.

ACCOUNT DATA PRACTICE

How We Handle Your Policy Requests

Privacy Policy work is tied to practical account events rather than vague profile labels. We separate contact details, wallet references, device signals and support messages so a request can be checked against…

Data handling

We use account details, sign-in records and payment references for access, status checks, support and account protection. A QRIS or bank transfer reference is handled as an account transaction record, not as a public profile detail.

Cookies and browser signals

Cookies and similar browser signals can help remember a session, recognise device activity and keep account steps connected. You can manage browser permissions, although changing them may affect sign-in or policy-request handling.

Account security

Phone verification comes before account access and may be requested again when a sensitive account change needs checking. Never share a one-time code in support chat, even when asking about wallet records.

Retention approach

We retain records only for the period needed for the purpose described in the Privacy Policy, account servicing, dispute handling or applicable duties. When a record is no longer needed, our handling follows the policy route.

Requesting a correction

To request a correction, contact support chat from your account and identify the detail, such as a phone number or payment reference. We may verify account ownership before changing or disclosing that record.

Device access choices

You can reach account settings and policy requests through a mobile browser or computer browser. Device details may be used to connect a sign-in event with your account and investigate an access concern.

Privacy Policy Answers for Your Account

These Privacy Policy answers cover the searches we hear before an account is opened or a wallet record is questioned. They focus on what is collected, how access works, how to ask for a change, and what local eligibility means for your account.

It covers account details, phone verification, sign-in and device signals, wallet and bank references, support messages, cookies, retention and requests to access or correct your records.

Yes. The Privacy Policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity so we can match status questions to your account.

Phone verification helps connect an account request to the right person before access or a data change. It can also help us investigate an unfamiliar sign-in or wallet reference.

Contact support chat through your account help path, identify the detail that needs correction and provide the related account context. We may verify ownership before making a change.

You can ask support to explain device and browser records connected with your sign-in activity. Use the account help path, and avoid sending passwords or one-time codes with the request.

We keep records for the period needed for account service, payment status checks, dispute handling or applicable duties. The Privacy Policy explains the retention approach for each relevant purpose.

Yes. Account eligibility and access depend on local law. We provide access where local law permits, and the Privacy Policy describes how requests are handled within that boundary.

ugbet Privacy Policy for Your Account Data

Get Policy Help Beside Account Support

Policy questions

Wallet records

Change requests

How We Handle Your Policy Requests

Data handling

Cookies and browser signals

Account security

Retention approach

Requesting a correction

Device access choices

Privacy Policy Answers for Your Account

01 What does the ugbet Privacy Policy cover?

02 Does the Privacy Policy cover DANA and QRIS data?

03 Why does ugbet ask for phone verification?

04 How can I request a correction to my data?

05 Can I ask what device data is stored?

06 How long does ugbet keep account records?

07 Does access depend on local law in Indonesia?

Related Pages