Reference

ukppg Privacy Policy For Your Account

ukppg Privacy Policy explains what we collect when you open an account, enter the lobby, or use DANA, OVO, GoPay and QRIS.

Account dataCookie choicesData requestsLocal-law access
ukppg ukppg Privacy Policy For Your Account
HELP WITH REQUESTS

Contact Us About Privacy Policy

A clear contact path helps you ask about the Privacy Policy without mixing a data request with a game or wallet question. Start from your signed-in account help route when you can, because the account step lets us match your request to the correct phone verification record. If you cannot access the account, use the available support contact and include only the details needed to locate the issue. We can help with privacy questions linked to DANA, QRIS, device access or payment receipt status.

Team online

Account help route

Use the account help path for a Privacy Policy question after login. Include your account identifier and the topic, such as cookie settings, phone verification, stored payment references or a request to correct account data.

Wallet status query

If your privacy question follows a DANA, OVO, GoPay or QRIS status check, mention the transaction reference rather than sending a full wallet password. We use the reference to separate payment support from broader data requests.

Access issue contact

When login stalls, contact support through the channel shown on our account help path and explain whether the issue affects a phone check, cookie choice or device session. We will ask for only the details needed to respond.

DATA HANDLING DETAILS

What ukppg Keeps And Why

The Privacy Policy is designed around practical account events rather than vague categories. We use information to keep your session connected to the right account, identify unusual access, answer support requests and…

Account creation

When you open an account, we use the details you submit and the phone verification step to create a distinct account record. This helps us avoid confusion between your login identity, device session and payment reference.

Cookie controls

Cookies and similar browser signals can keep your session active and remember choices made on the site. You can review browser settings on your mobile or desktop device, while some changes may affect account access or saved preferences.

Session security

We use account, phone and device signals to identify a session that needs an additional access check. If a session appears unusual, support may ask you to confirm account details without requesting a wallet password.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity may create references needed for status checks. We use those references to connect a receipt or pending record to your account without treating them as your login secret.

Retention choices

We retain records only for the operational, security or legal reason described in the Privacy Policy. When you ask about removal or retention, we assess the request against account security and local requirements before replying.

Change requests

To request correction, access or clarification, contact us through the account help route and state the exact data topic. We may verify account ownership through the phone step before making a change or releasing account details.

Privacy Policy Questions About ukppg

These Privacy Policy answers cover the searches we hear most often before an account is opened. They explain the practical difference between account data, device signals, wallet references and a formal request to access or correct information. If your situation is not covered, use the support route while signed in, or contact us through the available account help channel when login is unavailable.

The ukppg Privacy Policy covers data connected with account creation, phone verification, login sessions, device and browser signals, cookies, support messages and payment references. It also explains how to ask about access, correction, retention or deletion, subject to local law.

Yes. The Privacy Policy explains that DANA and QRIS activity can produce transaction references used for receipt and status checks. Similar records may come from OVO, GoPay, bank transfer or a virtual account, while wallet passwords should never be sent to support.

Phone verification helps connect account access to the person who opened the account and helps us handle unusual sessions. Under the Privacy Policy, this record may support login checks, account recovery and a request to access or correct account data.

You can contact us through the account help route and identify the data you want, such as account details, cookie choices, support messages or payment references. We may verify ownership first, then assess the request where local law permits.

Cookies can support session continuity and remember selected preferences on a mobile browser or desktop device. You can adjust browser controls, but disabling some cookies may interrupt login or remove saved choices. The Privacy Policy explains these effects before you request help.

Send a correction request through the signed-in account help path and describe the exact field that is wrong. If you cannot log in, use the available support contact. We may use phone verification or another account check before changing the record.

The page is written for Indonesian account access, but eligibility and some data rights depend on local law. We apply the relevant process where local law permits and can explain which request path fits your account and location.