Reference

ukmppg Privacy Policy For Indonesia Accounts

Our Privacy Policy explains how we collect, use and protect the account details you provide when you open ukmppg access.

Account dataWallet recordsDevice securityPrivacy requests

Explore Our Lobby Read FAQ

How Our Privacy Policy Applies To You

ukmppg Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy applies when you create or use an account, contact support, verify a phone number, open a game page or use a payment route connected with our service. We may handle your name, phone number, login details, device identifiers, approximate location signals, payment references

1
and messages sent to support. We use these details to provide account access, detect unusual login activity, reconcile wallet status and answer requests. DANA, OVO, GoPay and QRIS references help us match a payment attempt to the correct account; we do not treat a wallet name
2
alone as proof of identity. Access and eligibility depends on local law, and we may limit processing where local rules require it. The policy also applies to account activity from mobile browsers and desktop browsers, including sessions opened from Bandung or other Indonesian locations.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY HELP

Where To Send A Privacy Request

A clear contact path helps when you want to ask about account data rather than a wallet status. Use our support route from the account area and include the phone number linked to your profile, the subject of your request and any relevant reference shown beside a DANA, OVO, GoPay or QRIS transaction. We may ask for an account check before discussing personal data. That step protects your profile when a request comes from a new device or an unverified address.

Team online

Account data request

Ask us which personal details are connected with your account and why we use them. Include your verified phone number and the device path you normally use, such as an Android browser or desktop session. We will use those details to locate the correct record before replying.

Correction request

If your phone number, display details or payment reference appears incorrect, send the relevant account step and a clear description of the change needed. We may compare the request with the account record and wallet status before applying an update, especially when QRIS or bank transfer data is involved.

Privacy contact

For questions about cookies, retention, device signals or a previous support message, use the same support path and mark the request as privacy-related. Do not send a password or full wallet credentials. We will ask only for details needed to identify your account and handle the request.

DATA HANDLING

What We Do With Account And Device Data

Privacy choices are easier to understand when each data use has a practical reason. We connect account details to login, phone verification, wallet reconciliation and security checks rather than collecting data without…

Account creation

When you open an account, we collect the details needed to create your login and complete phone verification before account access. We use those records to keep your profile separate from another account and to send account-related replies. You should provide current details so requests reach you.

Payment matching

A DANA, OVO, GoPay, QRIS, virtual account or bank transfer reference may be stored with transaction status and time. We use this record to match a cashier event with your account and investigate a stalled wallet status. We do not need your wallet password to perform that check.

Device signals

Browser type, session identifiers and selected device signals can help us recognise an unusual login or repeated failed access attempts. These signals support account security on mobile and desktop paths. They are not a substitute for your password, and you should close shared-device sessions after leaving the account.

Cookies

We may use cookies or similar storage to keep a session active, remember selected settings and measure whether a page loads correctly. You can clear browser storage through your device settings, although doing so may sign you out or require phone verification again when you return.

Retention

We keep account, payment and support records only for the period needed for account operation, security checks, dispute handling and legal duties. Retention can differ by record type. When a record is no longer needed, we remove it, anonymise it or restrict access according to our internal process.

Your request

You can ask for a copy of personal data, a correction, a restriction or deletion where applicable under local rules. Send the request through support with your verified phone number and the reason. Access depends on local law, and we may retain limited records when a legal or security duty applies.

Privacy Policy Questions About ukmppg

Search questions often focus on a particular account step, wallet reference or device change. These answers keep the Privacy Policy practical for an Indonesian account holder, whether you are checking a phone verification record, opening the lobby from mobile or asking why a payment status is linked to your profile. If your situation is not covered, send a privacy request through support.

The Privacy Policy covers personal details, phone verification, login activity, device signals, cookies, payment references and support messages connected with your account. It also explains why we use those records for account access, security checks, wallet matching and legal duties. Access depends on local law.

We may store a wallet or QRIS reference, transaction time and status so we can match a payment event with your account. We do not need your wallet password for that purpose. Bank transfer and virtual account references may be handled in the same account-matching process.

Device and browser signals help us recognise an unusual login, repeated failed access or a session that changes suddenly. A mobile browser and desktop browser may create different session records. These signals support security, but they do not replace your password or phone verification.

Use the support route from your account area and state that the request concerns the Privacy Policy. Include your verified phone number, the data period you mean and whether you want a copy or correction. We may perform an account check before sharing personal details.

You can request a correction or deletion where applicable by sending a privacy request through support. We check the account before changing records. Some payment, security or support details may need to remain for legal duties or dispute handling, where local law permits.

Retention depends on the type of record and its purpose. Account, wallet and support data may be kept for account operation, security checks, dispute handling and legal duties. When a record is no longer needed, we remove it, anonymise it or restrict access.

The Privacy Policy remains the same, but a new mobile or desktop device may create fresh session and security records. You may need to complete phone verification again. If the change was not yours, contact support promptly and include the affected account step without sending your password.

ukmppg Privacy Policy For Indonesia Accounts

Where To Send A Privacy Request

Account data request

Correction request

Privacy contact

What We Do With Account And Device Data

Account creation

Payment matching

Device signals

Cookies

Retention

Your request

Privacy Policy Questions About ukmppg

01 What does the ukmppg Privacy Policy cover?

02 Does ukmppg store DANA, OVO, GoPay or QRIS details?

03 Why does ukmppg use device data on mobile?

04 How can I request my data from ukmppg?

05 Can I ask ukmppg to correct or delete my data?

06 How long does ukmppg keep account and payment data?

07 Does the Privacy Policy change when I use a new device?

Related Pages