Reference

Legal access for your pg138 account

pg138 Legal sets out how your account, wallet records and access requests are handled before you open the lobby.

Account termsData requestsLocal access rulesSecurity contacts
pg138 Legal access for your pg138 account
POLICY SUPPORT

Three ways to raise a Legal request

A clear contact trail helps us handle Legal questions without mixing them with a game or cashier request.

Account policy path Open support from the account area and state whether your request concerns access, account…
Wallet record check For a DANA, OVO, GoPay or QRIS question, include the payment rail, date and…
Security contact If you believe account access or a phone detail has been used incorrectly, contact…
DATA PRACTICE

How our Legal process handles records

We keep the Legal process practical: identify the account, locate the relevant record, check the requester's ownership and then respond through the account contact path.

Account data

We associate account details with the phone verification step used for access. When you ask for a correction, tell us which detail is wrong and provide the account contact route so we can compare the request with the record we hold.

Cookie choices

Cookies can help retain a session and remember basic access settings on your device. If you clear them, you may need to verify your phone again. Our Legal process treats a cookie change separately from a request to close your account.

Wallet references

Cashier records may show DANA, OVO, GoPay, QRIS, bank transfer or virtual account references. We retain enough transaction context to investigate status and ownership, while a Legal request can ask us to explain the record connected to your account.

Account security

We do not ask you to disclose a password, wallet PIN or one-time code through support. A security request starts with the account contact path, followed by an ownership check before protected access details or account changes are discussed.

Record retention

Retention depends on the type of record and the reason it was collected. Transaction references may need to remain available for account and payment checks. You can ask which category applies to a record and why it is still held.

Requesting changes

To request a correction, access copy or eligible removal, describe the record, use the phone-linked support route and explain your preferred outcome. We assess the request under the applicable Legal terms and where local law permits, tell you what can be changed.

Questions about pg138 Legal terms

These answers focus on the Legal issues you may search for before opening an account or sending a policy request. They cover access, account records, cookies, wallet references and contact steps, with local eligibility stated plainly. If your question concerns a specific record, use the account support path so we can check it safely.

pg138 Legal explains that access starts with the account path and phone verification, while eligibility depends on local law. We may ask you to confirm account ownership before discussing protected details. Read the policy prompt shown during access and contact support if the wording is unclear.

Yes, you can send a data request through the account support route. Describe the records you want, such as phone details, cookie settings or wallet references. We first confirm ownership, then assess the request under the applicable Legal terms and where local law permits.

Legal treats DANA and QRIS references as transaction-linked account records. Include the rail, date and reference shown in your cashier history when asking a question. We use those details to locate the correct entry, check its status and explain what can be changed.

No. Clearing cookies removes local session or preference data from your device; it does not close an account or erase every account record. You may need to complete phone verification again. For closure or data removal, submit a separate request through the Legal contact path.

You can request a correction by identifying the inaccurate phone or wallet detail and contacting support from the linked account route. We compare the request with account records and may perform an ownership check. The permitted outcome depends on the applicable Legal terms and local law.

Use the account policy support path and clearly request account closure. Do not send a password, wallet PIN or one-time code. We confirm ownership, explain any remaining account or transaction record requirements, and process the request where local law permits.

Contact support from your account area and provide the payment rail, date and reference, without sharing your wallet PIN. For DANA, OVO, GoPay, QRIS or bank transfer records, we can check the account match and route a security concern for further review.