Reference

ug344 Privacy Policy And Your Account

Our Privacy Policy explains what ug344 collects, why we use it and how you can request changes before opening an account.

Clear data purposesWallet record contextAccount access stepsCookie choices
Explore Our Lobby Read FAQ
ug344 ug344 Privacy Policy And Your Account
HELP WITH DATA

Where To Ask About Privacy Policy

A direct support request gives you a practical route for questions about this Privacy Policy, rather than leaving you to guess which account detail matters. Open the account help path while signed in and mention the email or phone detail connected to your account, without sending a password or full wallet credential. We can then identify the relevant record, explain its use and route a correction or access request for checking.

Team online

Account privacy request

Use the account help path to ask what personal details are held for your ug344 account. Include your registered phone detail and the request type, such as access, correction or deletion, but never include your password or full wallet PIN.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, send the transaction date and visible reference through account support. We use that information to locate the record without asking you to disclose a wallet password or security code.

Login privacy concern

When a sign-in alert or phone verification prompt looks incorrect, contact us through the account help route before changing repeated details. We can check the access record, explain the security step and help you keep the account information accurate.

DATA IN PRACTICE

How ug344 Handles Personal Data

Privacy choices matter most at the points where your account, device and wallet meet. Our handling approach separates account identity details from the operational records needed to check a payment or protect…

Account details

We use the phone or contact detail supplied during account creation to identify your account and complete the required verification step. Keeping that detail current helps us distinguish your request from another account when you ask for access or correction.

Device and browser

A mobile browser or desktop browser may create technical records such as sign-in time, browser type and security signals. These records help us investigate unusual access and keep a session connected to the correct account without reading unrelated device content.

Cookies and settings

Cookies can remember session settings and support privacy choices during a return to the lobby. You can manage cookies through your browser controls, although removing them may require another sign-in or reset preferences used for account access.

Wallet matching

A DANA, OVO, GoPay or QRIS reference may be retained with transaction status so we can match the correct account and investigate a pending record. Bank transfer and virtual account details are handled for the same account-check purpose.

Security records

Phone verification, sign-in history and security signals help us protect your account from incorrect or suspicious access. We may ask you to confirm an account detail before discussing private records, and we will not ask for your password.

Retention and changes

We retain personal data only for the account, security, transaction or legal purpose that requires it, then assess whether it is still needed. To request a copy, correction or removal, contact account support with the detail connected to your account.

Privacy Policy Answers For ug344

These Privacy Policy answers address the searches we expect before you create or use an account. They cover the data connected to sign-in, wallet references, cookies, device records and requests for access or correction. If your situation is not listed, account support can review the specific record after confirming the account detail.

The ug344 Privacy Policy explains how we use account details, phone verification records, device signals, cookies and payment references. It also describes how to request access, correction or removal of personal data, subject to account checks and where local law permits.

We use the phone detail supplied during account creation to identify your account and complete phone verification before access. It also helps account support locate the correct record when you ask about a sign-in, wallet status or Privacy Policy request.

Yes. The Privacy Policy covers DANA, OVO, GoPay and QRIS references connected with account activity, along with bank transfer and virtual account details used for transaction matching. We use visible references and status records, not your wallet password or PIN.

When you sign in from a mobile or desktop browser, we may record technical details such as browser type, access time and security signals. These records help protect the account and investigate unusual access; they do not give us access to unrelated files on your device.

Open the account help path and state whether you want access, correction or removal. Include the registered phone or contact detail and a clear description of the record. We may confirm ownership first, then explain the available response under this Privacy Policy.

We keep personal data while it serves an account, security, transaction or legal purpose, then assess whether retention is still required. The period can differ by record type. Account support can explain the reason for a particular record when you submit a verified request.

Access and eligibility depend on local law. If you access the service from Indonesia, the Privacy Policy applies to the account, device and wallet records created during that use. Check the account path and contact support if a local access question remains.

Related Pages

ug344 Indonesia FAQ Access guide LinkAja Fast Transfer Live Roulette Diamond