Reference

Privacy Policy for Your ukppg Account

ukppg Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesRequest support
Explore Our Lobby Read FAQ
ukppg Privacy Policy for Your ukppg Account
HELP WITH YOUR RECORDS

Get Privacy Policy Help Before Changing Data

A clear support route helps when a Privacy Policy question concerns your account rather than a general lobby matter. Tell us which account step caused the concern, such as phone verification, a QRIS receipt or a wallet status that does not match your record. We may ask for limited account details so we can locate the request without asking you to send a password or wallet PIN. Requests from Yogyakarta and other Indonesian locations follow the same policy path, subject to local access rules.

Team online

Account request

Use the account support path for questions about the data attached to your phone verification, sign-in record or profile. Include the email or phone detail linked to your account, but never send your password, wallet PIN or one-time security code.

Wallet record

For a DANA, OVO, GoPay or QRIS data question, share the transaction reference and approximate time rather than a full wallet credential. We can use that reference to check the status shown in your account and explain what the Privacy Policy covers.

Correction request

If a profile detail is outdated or appears incorrect, ask us to review the specific field and explain the change you need. We may verify account ownership before making an update, so the correction is applied to the right ukppg account.

WHAT WE HANDLE

Privacy Policy Controls Across Your Account

We handle account data in context: login events support security, wallet references support payment reconciliation, and support messages help us answer a Privacy Policy request.

Account security

Phone verification is part of the account access step, and device or login signals may be used to identify unusual activity. If a sign-in looks different from your usual path, we may request an account check before discussing personal records.

Cookie controls

Cookies can keep your session available while you move between account pages and the lobby. Your browser supplies controls for clearing or limiting them. Turning them off may affect sign-in continuity, but it does not erase records already retained for another purpose.

Payment matching

A payment reference can connect a DANA, OVO, GoPay or QRIS request with the account step that created it. We use that link to check status and investigate mismatches, without requesting the private password or PIN for your wallet.

Retention timing

We keep records only for as long as their account, security, support or legal purpose requires. The period can differ between a login event, a payment reference and a support request, so ask us for the reason a specific record remains.

Your requests

You can ask what personal data we hold, request a correction, and ask whether deletion or restriction is available for a particular record. We may first confirm that you control the account, especially when the request concerns phone verification or wallet history.

Contact route

Send a focused Privacy Policy request through the account support path and describe the record involved. We will use the details you provide to locate the matter, explain any limits under local law, and tell you what further step is needed.

Privacy Policy Answers For ukppg Accounts

These Privacy Policy answers address the account and wallet questions we hear most often from people in Indonesia. They explain what may be collected, how to ask for a change and why a verification step can be necessary. If your situation involves a particular DANA, OVO, GoPay or QRIS reference, include that reference when contacting support so we can check the correct record.

The ukppg Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, support messages and payment references. It explains why we use each type of data, how retention is considered and how you can ask for access or correction where local law permits.

Yes. Privacy Policy treatment includes references showing whether a DANA or QRIS request was created, matched or checked. We use those references to reconcile an account request, not to request your wallet PIN. Ask support about a specific reference if its status looks incorrect.

Phone verification helps connect account access with the person completing the account step and can help us investigate an unusual login. It also gives support a safer way to identify the relevant account. We will not ask you to disclose a one-time security code in a support message.

You can request correction when a profile detail is wrong or out of date. Describe the exact field and the change needed through the account support path. We may confirm account ownership before editing it, and the available action depends on local law and the record's purpose.

Send a Privacy Policy request that identifies your account and the data category you want to understand, such as login records, cookies, support messages or payment references. We may ask for verification before responding, then explain what can be provided and any applicable legal limit.

Retention varies by record. A support request, login event and DANA, OVO, GoPay or QRIS reference can have different account, security or legal purposes. We keep each category for the period needed for that purpose, and you can ask why a particular record remains.

Yes. Your browser settings let you clear or limit cookies and similar storage. Those controls may interrupt a saved sign-in path or require you to verify again, but they do not automatically remove account or payment records retained for security, support or legal needs.

Related Pages

ukppg Indonesia ukppg Casino Account information Access guide About Us