Reference

Open the pg1x2 Privacy Policy

pg1x2 Privacy Policy shows how we handle the account details, device signals and wallet references connected with Dragon Tiger, Royal Fishing and your account activity.

Account dataWallet referencesDevice choicesCookie controls
pg1x2 Open the pg1x2 Privacy Policy
PRIVACY SUPPORT

Find Privacy Help Beside Your Account

A clear contact route matters when your account record or wallet reference needs attention. From the account area, use the privacy contact path and include the email or phone detail connected to your account, plus the request you want us to check. We may ask for account verification before discussing personal data, so another person cannot obtain your records through a simple message. If you are in Surabaya or elsewhere in Indonesia, the same request path applies where local law permits.

Team online

Data request

Ask us what personal data is connected to your pg1x2 account, why it is used and which account activity created the record. Include your verified contact detail so we can match the request to the correct account before replying.

Correction path

If your phone number, email address or account detail is inaccurate, send the requested change through the privacy contact route. We check the account step first, then update the record when the request is confirmed and allowed under local law.

Wallet question

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference, tell us the transaction date and status shown in your account. We use those details to locate the record without asking you to share a wallet password.

DATA PRACTICES

Check How We Handle Account Data

We keep this policy practical by linking each data use to a real account step. Phone verification helps us connect access to the right account; device and session signals help us detect…

Phone verification

When you verify a phone before account access, we use the submitted number and verification result to confirm the sign-in path. Keep that number current, because it helps us distinguish your request from an unauthorised attempt.

Device signals

A mobile browser or desktop session may provide device type, browser details, language and security signals. We use these records to maintain a session and investigate unusual access, not to ask for the password of DANA or another wallet.

Cookie choices

Cookies can remember sign-in state, language settings and pages you have opened. You can adjust cookie controls in your browser; switching them off may require another sign-in or prevent a privacy preference from being remembered.

Payment references

DANA, OVO, GoPay and QRIS may return a reference, amount status or confirmation code for an account transaction. We use that payment data to reconcile the account record, while wallet credentials remain with the relevant payment service.

Retention timing

We keep account, security and transaction records for the period needed to provide the requested service, resolve disputes and meet applicable obligations. When a record no longer has a stated purpose, our process removes or de-identifies it.

Your request

You can contact us about a copy, correction, deletion request or question about processing. We may verify your identity using the account email or phone detail, and we apply the result according to local law and the nature of the record.

Browse Privacy Policy Answers for pg1x2

These Privacy Policy answers focus on the account, device and payment questions you may have before opening access. We keep the wording tied to actual steps such as phone verification, wallet reconciliation and mobile sign-in, so you can decide what to send us and how to request a change. If your question is not listed, use the privacy contact route beside your account.

The pg1x2 Privacy Policy covers account details, phone verification, device and browser signals, security logs, cookie choices, payment references and messages sent to support. It explains why we use each category, how long records may remain and how you can request access or correction.

We may receive the contact details and account identifiers you submit, along with the phone verification result needed for account access. A mobile or desktop session can also create security and browser records. We request data connected to the account process rather than unrelated personal details.

Yes. The Privacy Policy explains how we use DANA and QRIS references, along with OVO, GoPay, bank transfer and virtual account status, to match an account transaction and answer a payment question. We do not need your wallet password to check a reference.

You can send a correction request through the privacy contact route beside your account. Tell us which email, phone detail or account field is wrong and provide the verified contact detail linked to it. We confirm the request before changing the record where local law permits.

Use the same privacy contact path and state whether you want a copy, deletion or another access request. We may verify your identity first. Some security, transaction or legal records may need to remain for a defined purpose, depending on local law.

Cookies can preserve your sign-in state, language preference and privacy choice when you move through the lobby on a mobile browser. You can manage them in browser settings. If you disable required cookies, you may need to sign in again or repeat a preference.

Open the privacy contact route in your account area and describe the concern with the email or phone detail connected to your account. For a payment record, add the DANA, OVO, GoPay or QRIS reference and status, but never send a wallet password.