Reference

ucl300 Privacy Policy for Indonesia

ucl300 Privacy Policy explains how we collect, use and protect the details connected with your account, wallet status and device access.

Account clarityWallet recordsCookie choicesContact path
Explore Our Lobby Read FAQ
ucl300 ucl300 Privacy Policy for Indonesia
CONTACT OUR TEAM

Privacy Help Beside Account Support

A clear contact path helps you ask about Privacy Policy matters without repeating your account story. Use the support route shown after sign-in and include the email or phone detail linked to your account, plus the subject of your request. We can then identify the relevant account record, wallet status or device session before responding. If you cannot sign in, use the account-access contact path shown on the site and avoid sending a password, wallet PIN or one-time verification code.

Team online

Account privacy request

Ask us to explain the personal details connected with your account, including the phone verification step. We will use the account contact path shown on the site and may ask for identifying details before discussing records.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the payment reference and status shown in your account. Do not include wallet PINs or one-time codes in a support message.

Device access concern

If a mobile browser or desktop session looks unfamiliar, contact us through the account support route and describe the device path. We can review the access context and guide you through account security steps.

DATA HANDLING

What We Do With Account Details

We keep Privacy Policy practice close to the actions you take: account creation, phone verification, wallet status checks and support conversations.

Data collected

We may receive your account contact details, phone-verification result, sign-in context, support messages and payment references. These details help us connect a wallet status or account step to the correct record without asking for unrelated information.

Cookie use

Necessary cookies can keep your session and selected settings working on mobile and desktop. We may also use limited usage signals to understand page performance. Your browser controls can help you manage optional cookie behaviour.

Account security

Phone verification and sign-in checks help us distinguish your account access from an unfamiliar session. Keep your password and verification code private, and contact support if a device path or account action does not look familiar.

Payment records

A DANA, OVO, GoPay or QRIS reference helps us trace a wallet status. Bank transfer and virtual account records may contain a reference supplied by the payment route. We use these details for matching, support and required checks.

Retention period

We retain account, security and payment-related records for the period needed to operate the account, resolve disputes, prevent misuse or meet legal duties. When a record is no longer needed for those purposes, our handling follows the applicable retention process.

Changes and access

You can ask what personal details we hold, request a correction or raise a concern through our support path. Include your account contact detail and the change requested; we may verify your identity before providing or editing information.

Privacy Policy Answers for Your Account

These Privacy Policy answers address the searches we expect before an Indonesian customer opens an account or checks a wallet record. Each answer stays focused on personal data, cookies, access and contact steps rather than general lobby content. If your situation is not covered, use the support route shown on the site and describe the account action involved.

The ucl300 Privacy Policy covers information connected with account creation, phone verification, sign-in sessions, cookies, support messages and payment references. It also explains why we use those details, how we retain them and how you can request access or a correction.

Phone verification helps connect account access with the person completing the sign-in step and helps us investigate unfamiliar sessions. We may use the result when handling an account request, but you should never send your verification code or password to support.

Yes. The Privacy Policy covers payment references and status information linked with DANA, OVO, GoPay and QRIS. For bank transfer or virtual account activity, we may also handle the reference needed to match a transaction with your account.

You can contact us through the support path shown on the site and ask about the personal details connected with your account. Include your account contact detail and the request type. We may verify your identity before discussing or providing records.

Send a correction request through the account support route, stating which detail is wrong and what it should say. We may ask for account verification before changing it, especially when the detail affects phone access, wallet matching or security.

Cookies can keep a mobile browser session and necessary settings working as you move from sign-in toward the account area. Your browser settings can manage optional cookies. Clearing cookies may require you to sign in again and repeat a verification step.

Yes, access and eligibility depends on local law. We may use location or account context when applying access controls, but that does not change your ability to ask about personal data. Contact us through the site if you need a policy clarification.

Related Pages

ucl300 Indonesia Badminton BWF Tour Bet Access guide ucl300 Casino Account information