Reference

Privacy Policy for Your uge138 Account

Our uge138 Privacy Policy shows what we collect when you open an account, sign in from mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsDevice controlsRequest access
uge138 Privacy Policy for Your uge138 Account
PRIVACY HELP

Get Privacy Policy Help Near Account Access

A clear support route helps you act on this Privacy Policy without guessing where to start.

Account data request Use the account help path to ask what personal details are connected with your…
Wallet record question For a DANA, OVO, GoPay or QRIS reference, include the wallet name, date and…
Sign-in privacy issue If a mobile or desktop sign-in looks unfamiliar, contact us through the account support…
DATA CONTROLS

What uge138 Records And Protects

Privacy depends on practical controls, not a vague promise. We limit account access to the details needed for verification, wallet matching, support and security checks, while your browser…

Account handling

We use your account details to create access, confirm ownership and respond to requests about this Privacy Policy.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment status to the correct account.

Cookies and sessions

Essential cookies can keep your sign-in session and selected settings working across the lobby.

Device security

We may record browser, device and sign-in signals to identify an unfamiliar access attempt.

Retention period

We keep personal and payment records only for as long as their operational, security or legal purpose requires.

Your requested changes

You can ask us to access, correct or delete eligible personal data through the support route linked in your account.

Answers About Account And Wallet Privacy

These Privacy Policy answers focus on the questions we expect you to ask before opening an uge138 account. They cover phone verification, wallet references, cookies, device access, retention and requests for changes. If your situation is not covered, use the account help route and include only the details needed to locate your account. Where access or eligibility is discussed, it depends on local law.

It covers personal details, phone verification, sign-in activity, device signals, cookies, support records and payment references connected with your account. It also explains why we use those records, how retention works and how you can request access, correction or deletion where local law permits.

Phone verification helps us confirm that the person asking about an account is authorised to receive account details or request a change. We may use the verification step before discussing DANA, OVO, GoPay, QRIS or other payment references linked to your account.

Yes. We explain how DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are used to match payment status with your account. These records can include a reference, date and status, but you should never send us a wallet password or security code.

Sign in and use the account help route linked near account access and cashier areas. State whether you want access, correction or deletion, and identify the relevant account detail. We may verify ownership first and will explain any records that must remain stored.

Yes. Essential cookies may keep a session active and remember necessary settings on your phone or desktop browser. You can manage or clear site data through your browser controls, but removing essential cookies may end the session or affect account access.

Retention varies according to the purpose of each record, such as account security, payment matching, support or a legal requirement. We remove, anonymise or isolate data when that purpose ends, unless another lawful reason requires us to keep it longer.

Use the support link shown beside account access and describe the unfamiliar sign-in without sharing a password. We may ask for phone verification, review access signals and secure the account before discussing any private details or wallet status.