Reference

pg raja Privacy Policy For Your Account

The pg raja Privacy Policy explains what we collect when you open an account, enter the lobby, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
pg raja pg raja Privacy Policy For Your Account
HELP WITH DATA

Get A Clear Privacy Support Path

A direct support path helps when your login record, wallet reference or privacy request needs checking.

Account access Tell us when a verification step blocks access, and we will ask for the minimum account detail needed to identify your record before discussing a Privacy Policy request.
Wallet records For DANA, OVO, GoPay or QRIS questions, share the payment reference and date shown on your receipt so we can check the stored status without requesting your wallet PIN.
Privacy requests Ask through the account support route to correct, access or question personal data. We may verify your account first so another person cannot request changes on your behalf.
HANDLING DETAILS

What We Do With Your Personal Data

We keep the Privacy Policy practical by linking each data use to an account action: login verification, wallet matching, session protection or support.

Account security

We use your login and verification details to recognise the account during access checks. Keep your password private, and contact support if a device or session appears unfamiliar.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount and status record. We use that trail to match receipts without storing your wallet PIN.

Cookie controls

Cookies can remember a session or selected setting on your browser. You can restrict them in device settings, though a later login check may be required.

Data retention

We retain records for the period needed for account security, payment reconciliation and applicable legal duties. A request can ask what remains and why it is held.

Correction requests

If your phone, email or account detail is wrong, contact us through the displayed support route. We verify ownership before changing a record connected to access.

Policy contact

Questions about this Privacy Policy should include your account identifier and a plain description of the issue. We use those details to route the request accurately.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account steps you are most likely to ask about before opening access. We explain how payment references, cookies, device checks and correction requests fit together, while eligibility remains dependent on local law. If your question involves a specific receipt or login event, keep that reference ready when using the support route shown in your account area.

It covers account details, verification records, login activity, device signals, cookies and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

We use account details to create access, complete verification, protect sessions and respond to data requests. Your eligibility to access the service depends on local law.

Yes. It covers the reference and status created when you use QRIS, DANA, OVO or GoPay. We use those records to match receipts and do not request your wallet PIN.

Use the support contact displayed in your account area, describe the incorrect field and provide the account identifier linked to it. We verify ownership before making a change.

Cookies can keep a session or selected setting on your device. If you restrict them, we may ask you to complete another login or verification step before access.

We keep records for account security, payment reconciliation and applicable legal duties. You can ask support which records remain, the reason for retention and whether a change is available.

Yes. Send that question through the account support route with your account identifier. We will explain the relevant handling purpose and verify the request before discussing account-linked data.