Reference

ubo138 Privacy Policy And Your Account

The ubo138 Privacy Policy explains how we handle your account details, phone verification, device signals and wallet records before you open the lobby.

Account dataWallet recordsCookie choicesAccess requests
Browse Lobby Read FAQ
ubo138 ubo138 Privacy Policy And Your Account
CONTACT PATHS

Ask About Your Privacy Policy

A clear support route helps when your account record, phone verification or wallet reference needs explanation.

Account data request Ask us to identify the account details we hold, such as your contact record, phone verification status and recent login signals. We may ask you to confirm the account step or device used so we do not disclose private data to the wrong person.
Wallet record question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the transaction date and the visible reference through our cashier-side support path. Never include your wallet PIN. We can compare the account record with the payment reference and explain the next step.
Correction request Tell us which contact detail, device record or account entry needs correction and why. We review the request against the account step used for verification, then explain whether the change can be made, retained for a legal reason or requires more proof.
HANDLING DETAILS

How We Apply The Privacy Policy

We apply the Privacy Policy to practical account events rather than treating every record the same way.

Account records

We keep the contact and verification details needed to maintain your account path. The phone verification step can be matched with login activity when we check access. If your contact record changes, request a correction through support rather than opening a second account.

Device signals

Your browser and device may create security signals such as session details, login time and access pattern. These signals help us investigate an unfamiliar sign-in from a mobile browser or desktop without treating the device itself as your identity.

Cookie choices

Cookies can remember sign-in state, language selection and page settings so you do not repeat the same choice on each visit. You can adjust browser cookie controls, although removing necessary cookies may affect the account path or prevent a requested page from loading.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may hold a reference, amount status and time needed to match an account event. We do not ask for a wallet PIN, and the payment provider remains responsible for its own records.

Account security

We use phone verification, session checks and unusual-login signals to protect account access. Keep your password and wallet credentials private, and contact support if a login or Wallet Verification Steps record does not match your activity.

Retention requests

We retain records only for account operation, security, dispute handling or legal duties that apply to the request. Ask us which record you mean and why you want it changed or removed; we will explain the available result under local requirements.

Privacy Policy Questions For ubo138

These Privacy Policy answers focus on the account and payment situations you are most likely to ask about before opening an account. We keep the process specific: name the record, identify the account step, and use the support path beside the cashier area. Any access or eligibility decision depends on local law.

It covers account details, phone verification, login and device signals, cookies, support records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains why we use, retain, correct or restrict access to those records.

Yes. Send an account data request through the cashier-side support path and identify the contact detail or verification step used at registration. We may ask you to confirm account ownership before replying, so private records are not released to another person.

We may retain transaction references, status and timing to connect a wallet event with your account. We do not need your wallet PIN. DANA, OVO, GoPay and QRIS also have their own data rules, so their handling remains separate from our Privacy Policy.

Device type, browser session and login signals help us check unusual account access and investigate a support request. A mobile browser and a desktop may create different signals. These details are used for account operation and security checks, not as a replacement for phone verification.

Describe the incorrect account entry, provide the corrected detail and use the support path beside the cashier area. Include the account contact used for phone verification. We will assess the request, explain any proof needed and tell you if a legal retention duty affects the change.

You can request removal or restriction by naming the records involved and explaining the request. Some data may need to remain for account security, payment disputes or legal duties. We will explain the available action, and the result depends on local law.

Cookies may remember session status, language and page settings so your account path works across visits. You can change cookie controls in your browser. Blocking necessary cookies may stop phone verification, login or a policy page from working as intended.

Related Pages

ubo138 Indonesia Account information About Us Wallet Verification Steps FAQ