Reference

Open ukpppg Privacy Policy With Clarity

ukpppg Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity in Indonesia.

Account dataCookie choicesWallet recordsContact requests
ukpppg Open ukpppg Privacy Policy With Clarity
POLICY HELP DESK

Switch To The Right Privacy Contact

A clear contact path helps when a policy question does not fit the account screen. Tell us whether your request concerns a phone number, a wallet reference, a cookie choice or a record linked with a particular device. We use the details in your message to locate the relevant account safely, and we may ask for an account step before discussing private records. Support can also explain where to find the current Privacy Policy while you are checking access from Jakarta, Surabaya or another Indonesian location.

Team online

Account request

Use the support route shown beside your account area when you need to ask about personal data. Include your account identifier and the subject of the request, but do not send a wallet password, card secret or phone verification code.

Wallet record

If your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, provide the transaction reference and date. We use that narrow detail to trace payment status without asking you to disclose your wallet login.

Policy change

For a correction, deletion request or cookie question, describe the change you want and the email or phone route attached to your account. We check ownership before making an adjustment, then explain any record we must retain.

DATA CONTROL ROOM

Browse The Records We Handle

We separate the information needed to operate an account from the signals used to keep a session working.

Account details

We handle the account information you submit, such as contact details and phone verification status, so we can identify the account holder and respond to account requests. Keeping these details current helps us send a correction request to the right record.

Device signals

When you move from mobile login to the lobby or return on desktop, we may process browser, device and connection signals. These details help maintain a session and investigate unusual access; they are not a request for your device passcode.

Cookie choices

Cookies can remember a session and selected settings, while required cookies support account access. Your browser controls optional cookie storage. If you clear cookies, you may need to complete the login and phone verification path again.

Payment references

A DANA, OVO, GoPay or QRIS reference can show whether a cashier action is pending, cleared or needs checking. We use that reference for reconciliation and support, while wallet credentials remain with the relevant payment service.

Account security

Phone verification and session checks help us protect account access. Never share a verification code with another person. If a login stalls or looks unfamiliar, pause the account action and contact us through the support path attached to your profile.

Retention requests

We keep records only for the period needed for the stated account, security, payment or legal purpose, subject to applicable requirements. You can ask what we hold, request a correction or ask about deletion, and we explain any necessary retention.

Ask About ukpppg Privacy Policy

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. They also point you to the practical steps for checking, correcting or limiting how your information is handled.

The ukpppg Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It explains why we use each category, how we protect account access, how long records may remain and how you can ask about your personal data.

Yes. The Privacy Policy explains how we handle transaction references and payment status when you use DANA, OVO, GoPay or QRIS. We use those details to reconcile an account action and answer a support request; we do not ask for your wallet password or verification code.

We collect the details you enter for an account, the phone verification result and technical signals from the device or browser used for access. If you start a bank transfer or virtual account action, we may also receive the related reference needed to check its status.

You can contact us through the account support route and ask what personal data we hold or request a correction. Include your account identifier and explain the requested change. We verify account ownership first, then respond about the record and any step still required.

On mobile, required cookies can keep your login path and selected settings working as you move toward the lobby. Optional cookies may support preferences. Your browser lets you clear or restrict them, although clearing required cookies can send you back through account access.

The Privacy Policy does not treat every record the same. We retain account, security and payment references for the period needed for their stated purpose and applicable requirements. You can ask us to explain a retention period or whether a specific record can be removed.

Yes. Where local law permits, you can ask how we use your account, device, cookie or payment-reference data and request an available change. Send the request through your account support path; we may need phone or account verification before discussing private records.