Reference

Privacy Policy for Your pg5000 Account

pg5000 keeps your account, device and wallet details connected to a clear Privacy Policy, so you can understand what is collected before opening the lobby.

Account dataWallet recordsCookie choicesPhone verification
pg5000 Privacy Policy for Your pg5000 Account
PRIVACY HELP ROUTE

Get Privacy Answers Before You Open

A direct support path makes the Privacy Policy easier to use when a wallet record, sign-in event or account detail looks unfamiliar. Contact us through the account help route and include the phone number linked to your account, the relevant date and the request you want handled. We use those details to locate the correct record without asking you to send a password or wallet PIN.

Team online

Account privacy request

Ask us to explain, correct or remove eligible account data through the account help route. Include your registered phone number and the subject of your request so we can verify ownership before discussing personal records.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference appears unfamiliar, send the transaction date and visible reference only. We can compare the payment status with your account without requesting your wallet password or full banking credentials.

Sign-in concern

Tell us when a device sign-in or phone verification event does not match your activity. We can review the account record, explain the security step and direct you through the next access check where local law permits.

DATA HANDLING DETAIL

What We Keep Clear Inside pg5000

Privacy decisions are tied to ordinary account actions rather than hidden categories. We separate contact details from payment references where practical, limit staff access by task and retain records only for operational…

Account data use

We use your phone number and account identifiers to confirm ownership, keep sign-in activity associated with the right account and answer requests. Phone verification is an account step, not permission for us to read unrelated contacts or files on your device.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records help us match wallet status and resolve disputes. We handle the reference needed for that task rather than asking for your wallet PIN or complete banking login.

Cookies and sessions

A mobile browser can retain session markers and preference cookies linked to your visit. You can clear them from browser settings or block selected cookies; clearing them may sign you out and require phone verification again.

Account protection

We use sign-in checks, phone confirmation and access records to identify activity that does not match your account pattern. Never send us a password, wallet PIN or one-time code when asking for privacy assistance.

Retention approach

We keep personal records for the period needed to operate the account, settle a payment question, handle a complaint or meet a legal duty. When a record is no longer needed for those purposes, we remove or separate it where practical.

Changes and requests

You may ask whether we hold account data, request a correction or ask about deletion through support. We may request phone verification before making a change, and some records may need to remain where local law permits.

Privacy Policy Questions About pg5000

These Privacy Policy answers address the account and device questions you are most likely to have before opening pg5000 from Indonesia. They explain the practical steps for data requests, wallet references, cookies, phone checks and account access, while recognising that some handling depends on local law.

The pg5000 Privacy Policy covers account details, phone verification, device and session signals, support messages, cookie data and payment references. It explains why we use each category to operate access, check wallet status, protect an account and respond to requests where local law permits.

Yes. Privacy Policy handling includes the payment reference and status connected with DANA, OVO, GoPay and QRIS. We use those details to match a transaction to your account and investigate a question, but we do not ask for your wallet PIN or full banking login.

Use the account help route and ask for a personal data request. Include your registered phone number, the email or account identifier available to you and the data category you want checked. We may confirm ownership by phone before discussing or sending account records.

You can request a correction when your account name, phone detail or another record is inaccurate. Send the requested change through support and explain which field is wrong. We may complete phone verification first, then confirm whether the correction has been applied.

The Privacy Policy allows session and preference cookies that help keep your mobile browser connected during sign-in and account navigation. You can clear or block cookies in browser settings. After doing so, you may need to sign in and complete phone verification again.

We retain personal data while it is needed for account operation, wallet questions, dispute handling, security checks or a legal duty. Retention can differ by record type. When the reason ends, we remove, anonymise or restrict the record where local law permits.

You may ask us to delete eligible personal data through the account help route. We first verify ownership and assess the request against operational and legal needs. Some transaction, security or dispute records may need to remain where local law permits.