Reference

ug388 Privacy Policy, Made Clear

The ug388 Privacy Policy shows what we collect, why we use it and how you can ask us to change or remove eligible details.

Account clarityWallet recordsDevice controlsContact path
Explore Our Lobby Read FAQ
ug388 ug388 Privacy Policy, Made Clear
CONTACT THE TEAM

Privacy Help Beside Your Account

A direct support path helps when your Privacy Policy question concerns a login, phone check or wallet record. Start from the account support route and include the email or phone detail connected to your account, plus the type of request you are making. Do not send a full wallet password or one-time security code. We use the details you provide to locate the relevant account record and respond about access, correction, deletion or a payment status question.

Team online

Account privacy request

Ask us to confirm which account details we hold, correct a spelling or update a contact detail through the signed-in support path. We may ask you to complete an account check before changing personal data, especially where the request affects phone verification.

Wallet record question

For DANA, OVO, GoPay or QRIS records, send the transaction reference and date shown in your account. We use that narrow detail to trace a status without asking you to disclose your wallet password, PIN or one-time security code.

Access and deletion help

If you cannot sign in or want to ask about deletion, contact support from the available account route and explain the issue. We first protect the account from an unverified request, then tell you what can be changed under local law.

DATA HANDLING

Inside ug388 Privacy Controls

We keep the Privacy Policy practical by linking each data use to an account action: access, security, wallet matching, support or service operation.

Account details

We use your registration and phone verification details to create the account path, confirm that a request comes from you and send account-related replies. Keeping these details current helps us handle a sign-in problem without confusing your record with another account.

Device and session data

A mobile or desktop session may provide device type, browser details, language setting, approximate network signals and sign-in times. We use these signals to maintain access and flag unusual activity, not to read unrelated files, contacts or messages on your device.

Cookies and preferences

Cookies can keep a session open, remember a selected setting and help us understand whether a page request worked. You can adjust cookie controls in your browser. Clearing them may sign you out or require the account path to load again.

Payment matching

When you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we record the reference, amount status and timing needed to match the account action. We do not ask for your wallet PIN, password or one-time code.

Retention and removal

We keep personal records only as long as needed for the stated account, security, support or legal purpose. A removal request may not erase records that must remain for a dispute, fraud check or legal duty; we explain the reason when that applies.

Your request route

To request access, correction or an eligible removal, use the support path connected to your account and describe the exact record involved. We may verify ownership before acting, and we respond with the next step rather than exposing another person’s account details.

Answers About Your Privacy Policy

These Privacy Policy answers cover the account and payment questions you are most likely to have before opening an account. We keep the same practical approach across mobile and desktop: explain the record, identify the reason for using it and show you the support route when a change is possible. For access or eligibility questions, the answer depends on local law.

The ug388 Privacy Policy covers registration details, phone verification, sign-in and device signals, cookies, support messages and payment references. It explains why we use each category, how long records may remain and how you can request access, correction or an eligible removal.

Phone verification helps us connect account access with the person making the request and reduce mistaken or unauthorised changes. We use the verified contact for account security and related replies. Keep one-time codes private; support will not need your code to discuss the policy.

Yes. The Privacy Policy covers transaction references and status details created when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. We use those records to match a wallet action with your account and investigate a receipt or status question.

A session can provide device type, browser details, language setting, approximate network signals and login time. We use this data to keep the account path working and identify unusual access. We do not need access to unrelated files, contacts or messages on your device.

You can ask for the personal account details we hold by using the signed-in support route and describing your request as a Privacy Policy access request. We may verify account ownership first. We then explain the available record, any limits and the next action.

Send a correction request through account support and identify the detail that needs changing, such as a contact record or spelling. We may complete an ownership check before editing it. Payment references and security records may need a separate explanation because they support account protection.

We retain personal data for the time needed to provide account access, protect sign-in, answer support requests, resolve disputes or meet a legal duty. If you ask for removal, we assess the record and tell you when security or legal reasons require continued retention.

Related Pages

ug388 Indonesia Access guide Live Roulette Wheel About Us Account information