Reference

Open pg1x2 Legal access with clarity

pg1x2 Legal sets out how you open an account, use DANA or QRIS, and access Dragon Tiger and the wider lobby where local law permits.

Account checksWallet recordsLocal access
pg1x2 Open pg1x2 Legal access with clarity
CONTACT ROUTES

Switch to the right Legal contact path

A clear contact path helps you resolve policy questions before they affect account access. Tell us whether your question concerns a phone check, a wallet record, a data request, or a withdrawal verification step. Include the account detail and payment reference you can safely share, but never send your password or one-time code. Our support team can explain the applicable Legal process and identify the next step for your case.

Team online

Account access

If phone verification does not match your account details, contact support with the account email or phone number used during registration. We can explain the Legal check, confirm which detail needs attention, and direct you through the next access step without asking for your password.

Wallet status

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account questions, share the payment reference and visible status only. We use those details to locate the relevant record, explain whether a Legal review is required, and clarify what you should do next.

Data requests

Questions about stored account details, cookies, or a requested correction belong with our policy contact route. State the change you want and the account identifier you can verify. We will explain the Legal handling path and any identity check needed before making an update.

DATA PRACTICES

Browse how pg1x2 handles Legal data

Legal handling is visible in the way we manage account records, wallet references, and access controls.

Account details

We use the details you enter during account opening to identify your account, complete phone verification, and connect later policy requests to the correct record. Keeping your name, phone number, and contact details accurate helps us avoid delays when access or withdrawal checks arise.

Cookies

Cookies can support session continuity, saved page settings, and the handoff from sign-in to the lobby on your device. You can manage browser cookie settings, but disabling them may interrupt account access or require you to repeat a sign-in step.

Account security

Your password and one-time verification code should remain private. We use account checks when a sensitive change, unfamiliar access pattern, or withdrawal request needs confirmation. If you suspect that someone else accessed your account, contact support before changing wallet details.

Record retention

We retain account, payment reference, and support records for the period needed to operate the service, resolve disputes, protect accounts, and meet applicable Legal duties. Retention can differ by record type, so a request may receive a specific explanation rather than one general timeframe.

Correction requests

If your account detail is wrong, tell us which field needs correction and provide the account identifier used for verification. We compare the request with the existing record before changing it, helping keep phone checks, wallet references, and future contact aligned.

Policy contact

For a copy request, deletion question, cookie concern, or other Legal matter, use our support contact path and describe the exact request. We may ask you to confirm ownership first, then explain what can be changed, retained, or restricted under local law.

Check Legal answers before opening

These Legal answers cover the questions we expect you to ask before creating an account or using a wallet. They explain access, account ownership, stored data, cookies, and contact steps in plain terms. If your situation is not covered, send our support team the relevant account or payment reference without sharing private sign-in credentials.

Legal describes the policy terms governing account opening, access, wallet records, data handling, cookies, security checks, and contact requests. We apply those terms where local law permits. Read the notice before registering, and ask support to clarify any condition that could affect your account.

Access depends on local law. Where local law permits, you can open the account path, complete phone verification, and reach the lobby from a mobile browser or desktop browser. If access is restricted for your location or case, the applicable policy condition takes priority.

Phone verification helps us connect the account to the contact detail you entered and reduce mistaken or unauthorised access. Complete the check before using account functions that require identity confirmation. Never send your password or one-time code to another person, including support.

We associate DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references with the relevant account record so status questions can be checked accurately. We may request a payment reference or ownership confirmation, but you should remove private credentials before sharing any receipt detail.

Yes, you can contact support to request a correction or ask how a record is handled. Describe the field or record concerned and provide an account identifier for verification. We check ownership first, then explain whether the change can be made under the applicable Legal terms.

Retention depends on the type of record and the operational, security, dispute, or legal reason for keeping it. Account details, wallet references, and support messages may follow different periods. Contact us with the record type you mean, and we will explain the relevant handling path.

Use the support contact route for questions about access, phone verification, wallet status, cookies, stored data, or a withdrawal check. Include the account email or phone detail and a safe payment reference when relevant. We will identify the policy path without requesting your password or code.