Reference

Open ug008 Privacy Policy Before Account Access

Your account data, wallet records and device choices are explained in the ug008 Privacy Policy before you open an account.

Clear data purposesWallet record contextPhone-first policy accessLocal law wording
ug008 Open ug008 Privacy Policy Before Account Access
PRIVACY HELP

Contact Us About Your Privacy Policy

A clear contact path helps you raise a privacy request without mixing it with a game or wallet question.

Account privacy request Send your question through the account support path and identify the phone number connected…
Wallet record query If your request concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account…
Access concern When a phone check or device sign-in blocks your privacy request, tell us which…
DATA CONTROL

Explore ug008 Data Choices And Security

Privacy is easier to manage when each control has a clear purpose. We connect account creation, phone verification, device activity and wallet records only to the tasks described in our Privacy Policy.

Account data

We may hold your account contact details and phone verification result so we can provide access to the correct account. We use those details for account administration and security checks, not as a reason to request your private wallet credentials.

Cookies and sessions

Cookies can keep a login session working and help us recognise an unusual device path. You can manage cookies in your browser settings, although switching them off may require another phone check before account access continues.

Account security

Phone verification and device signals help us investigate sign-in activity that does not match your usual path. If something looks wrong, contact support with the time and device type; do not include your password, PIN or one-time code.

Retention timing

We keep account, support and payment records only for the period needed for account operation, security checks, dispute handling or legal duties. A request to remove data may not erase records that must remain connected with a transaction.

Request a correction

You can ask us to correct an account detail that is outdated or inaccurate. Tell us the field that needs attention and the phone number linked to your account, so we can verify the request before making a change.

Local access

Our handling of account data does not change the access rule for a location. Before you open an account or use the lobby, check that access is available where local law permits and contact us if the policy wording is unclear.

Browse Privacy Policy Answers For ug008

These Privacy Policy answers focus on the questions you may have before opening an ug008 account from Indonesia. We cover account data, wallet records, cookies, device checks, correction requests and local access wording. If your situation is not listed, use the privacy contact path and include only the account details needed to identify your request.

The ug008 Privacy Policy covers account details, phone verification, device signals, cookies, support messages and payment references connected with your account. It explains why we use each category, when records may be retained, and how you can ask about access, correction or removal.

We use phone verification to connect account access with the correct person and reduce sign-in confusion. The result can also help us investigate an unusual device path. You do not need to send us your password, PIN or one-time code for a Privacy Policy request.

Yes. The Privacy Policy explains that DANA, OVO, GoPay and QRIS references may appear in payment records used to match account activity. Bank transfer and virtual account details can serve the same purpose, while secret wallet credentials should never be shared.

Use our account support path and state the phone number linked with your ug008 account, the data field you want corrected, and the reason for the request. We may verify ownership before changing it, and we will explain if a record must remain for security or legal duties.

You can ask us which account data may be removed and which records must be retained. Payment references, support history or security records may need to stay available for a defined purpose. We will assess your request and explain the result through the privacy contact path.

Cookies can keep your session active and support device-security checks. Browser settings let you remove or block them, but this may interrupt the path from login to your account and trigger another phone verification step. The Privacy Policy explains the purposes connected with these cookies.

The Privacy Policy explains data handling, but it does not override local access rules. Availability depends on local law. Check the position for your location before opening an account, and contact us if you need the policy wording applied to a specific account request.