Reference

Privacy Policy for Your panji388 Account

panji388 Privacy Policy shows how we handle the details connected with your account, including phone verification, device access and wallet status for DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice choicesPolicy requests
panji388 Privacy Policy for Your panji388 Account
ACCOUNT HELP ROUTE

Where to Ask About Privacy Policy

A clear support route matters when a privacy question appears beside a login or wallet check.

Account access If your phone verification does not match the account path, contact us through the…
Wallet record For a DANA, OVO, GoPay or QRIS privacy question, include the payment reference and…
Policy request To ask for a copy, correction or removal of personal data, state the request…
DATA HANDLING DETAILS

Six Practical Privacy Policy Commitments

We keep the working parts of our Privacy Policy specific to the way your account is used.

Account details

We may handle your phone number, account identifier and verification result to create access and protect the account. These details are connected to the account step rather than displayed as public profile content. We use them when a login or account request needs ownership checking.

Wallet activity

A DANA, OVO, GoPay or QRIS reference can be stored with an account request so we can match status and receipt questions. Bank transfer and virtual account records may also identify the transaction path. We do not need your wallet PIN for this matching process.

Cookies and devices

Cookies and device signals can help remember a session, maintain language settings and flag an unfamiliar sign-in. On mobile, the path may connect your login with the lobby; on desktop, the same account record helps us compare access events without treating each device as a new identity.

Account security

We use phone verification and sign-in checks to reduce access by someone who does not control your account. Never share your password, verification code or wallet PIN. If a device looks unfamiliar, our support route may ask questions that confirm ownership before discussing account data.

Retention choices

We keep personal records only for the period needed for account operation, security, dispute handling or a lawful payment record. When a retention period ends, records may be removed or separated from direct account details. A deletion request can be limited by a record we must retain.

Change requests

You can ask us to correct inaccurate account details, explain a stored record or review a deletion request through support. Include the account identifier and the specific item, such as a device event or QRIS reference. We verify ownership before making a change to private data.

Privacy Policy Answers for Indonesia Accounts

These Privacy Policy answers address the questions we expect when you are deciding whether to open an account or check an existing record. They focus on personal data, payment references, device access and contact steps rather than general lobby features. If your question involves eligibility or access in Indonesia, that position depends on local law, and our support route can explain which account detail we can discuss after ownership checks.

It covers account details, phone verification, device and browser signals, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains why we use those records, how long they may remain and how you can ask about them.

We use the phone verification result to connect an account request with the person seeking access and to identify unusual sign-ins. It is part of the account security process, not a public profile field. We may repeat ownership checks before discussing private records through support.

Yes. The policy covers references and status details connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account requests. These records help us locate a receipt or status question, while wallet PINs should never be sent to us.

Use the account support route and identify the record you want copied or corrected, such as your phone detail, device event or wallet reference. We confirm that you control the account before responding. A request may be limited when a record must remain for security or lawful payment handling.

Cookies can keep a session active, remember language settings and help connect a recognised mobile device with your account. Device signals may also help identify an unfamiliar login. You can ask support about a cookie-related record, although changing browser settings may affect account access.

We retain records for the period needed for account operation, security checks, dispute handling or a valid payment record. After that need ends, data may be removed or separated from direct account details. If you request deletion, we explain any record that still needs to remain.

Yes. Contact us with your account location and the exact Privacy Policy question. Access and eligibility depends on local law, so the response may differ by jurisdiction. We can explain the data request path available to you after confirming account ownership and the relevant account record.