Reference

pg raja Privacy Policy Explained

The pg raja Privacy Policy explains how we handle your account details, phone verification, cookies and wallet records when you use our Indonesia-facing service.

Account dataPhone verificationWallet recordsCookie choices
pg raja pg raja Privacy Policy Explained
CONTACT ROUTES

Get Help With Policy Requests

A clear contact path helps when your Privacy Policy question concerns a phone check, cookie setting or wallet record. We ask you to use the support contact displayed inside your account and include the email or phone detail linked to the request. That lets us locate the right record without asking you to send a full payment credential. If you are in Medan, the same account support route applies as it does elsewhere in Indonesia, where access depends on local law.

Team online

Account contact

Use the support contact shown after sign-in when you want to ask about your Privacy Policy rights, stored account details or a correction. Include the account identifier requested on that page, but never send your password or a complete DANA, OVO, GoPay or bank credential.

Wallet status

For a data question linked to QRIS, virtual account or bank transfer activity, provide the visible payment reference and approximate date. We can then check the related status record while keeping the request focused on the specific transaction rather than collecting unrelated account material.

Access concern

If phone verification prevents account access, contact us through the account support route and describe the device path you used, such as a mobile browser or desktop browser. We may request a limited identity check before discussing personal records or changing account-linked details.

DATA PRACTICE

How We Handle Your Records

We keep the Privacy Policy practical by linking each data use to an account action you can recognise.

Account details

We handle details such as your account identifier, contact field and phone verification state to create, protect and maintain access. Keeping these fields accurate helps us separate your account from another person’s request, especially when you ask for a correction or a copy of your records.

Payment references

DANA, OVO, GoPay and QRIS can generate a reference or status record connected with your account activity. We use the reference to match a payment event and investigate a displayed status. We do not ask you to place a wallet PIN or full banking password in a support message.

Cookies

Cookies and similar browser storage can remember a sign-in state, a security preference or a page choice. When you move from a mobile browser to desktop, the available cookie state may change. You can adjust browser controls, although some account steps may then need to run again.

Security checks

Phone verification and device signals help us spot an unusual account access pattern before personal records are discussed. We may ask you to repeat an account step when a browser changes or a request involves sensitive details. These checks are designed to limit access to the correct account holder.

Retention timing

We retain a record only while its account, security, support or payment-status purpose requires it, subject to applicable legal duties. A payment reference may need a different retention period from a temporary cookie. You can ask which category applies to a record through the account support contact.

Change requests

You can ask us to correct eligible account details, explain a data use or address a record linked to your Privacy Policy request. Tell us what should change and why. We may verify your phone or account connection first, then respond through the contact route attached to your request.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account actions you are most likely to check before opening an account or contacting us. They cover phone verification, cookies, payment references, record changes and access requests for Indonesian accounts. If your situation is not covered, use the support contact shown in your account and describe the exact policy question.

The pg raja Privacy Policy covers account details, phone verification, cookies, device-related security signals and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, account requests and how to contact us about your records.

Phone verification helps connect an account request to the correct person and reduces the chance of another person discussing or changing private records. We may repeat the step when you sign in from a new browser or ask us to change sensitive account details.

Yes. The Privacy Policy covers payment references and status records connected with QRIS, DANA, OVO and GoPay, along with bank transfer and virtual account activity. These records help us investigate a displayed status, but you should not send a wallet PIN or full banking password.

Use the support contact shown inside your account and state which account detail is wrong, what the corrected detail should be and why. We may ask for phone or account verification before making a change, so the request is handled for the correct account.

Cookies or browser storage may preserve a sign-in state, security choice or page preference. If you switch from a mobile browser to a desktop browser, the stored state may not follow you. Browser controls can remove cookies, but some account steps may need repeating.

You can ask through the account support contact for an explanation of the records connected with your account, including verification details or a payment reference. We may verify your account connection before discussing them, and retention can differ between cookies, security records and payment status.

Yes. Account access and eligibility depend on local law. Our Privacy Policy describes how we handle records when the service is available to you, while local rules may affect whether you can open or use an account. Contact us if your location creates a policy question.