Reference

panen 138 Privacy Policy, plainly stated

panen 138 Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and move through the lobby from a mobile…

Clear collection reasonsCookie choicesAccount data requestsIndonesia access wording
panen 138 panen 138 Privacy Policy, plainly stated
PRIVACY CONTACT

Where to ask about your account data

A direct support route helps when your question concerns personal data rather than a lobby screen. Sign in first when you can, then use the account support path shown near the cashier area so we can connect your request with the correct record. If login is unavailable, include the phone number linked to the account and a short description without sending a password or wallet PIN. We use the same privacy process for questions from users in Makassar, Denpasar and elsewhere in Indonesia.

Team online

Account data request

Ask us to confirm which account details we hold, including phone verification status, login events and payment references. We may ask for an account step that confirms your identity before releasing or changing personal data, so another person cannot request your records.

Payment record question

For a DANA, OVO, GoPay or QRIS receipt, share the transaction reference and approximate date through the account support path. We use those details to locate the record without asking for your wallet password, PIN or full banking credentials.

Correction request

If your phone number or another account detail is incorrect, tell us what needs changing and why. We check the request against the signed-in account or a verification step, then explain whether the record can be corrected, retained or restricted.

HANDLING DETAILS

What we retain after account checks

Privacy depends on consistent handling after the first account check, not only on the wording of a page.

Account details

We may hold the phone number, login identifier and verification result attached to your account. These details help us confirm that a request comes from you and help us separate one account record from another when you ask for a correction.

Device signals

A mobile browser or desktop session can produce device and security signals such as sign-in time, browser type and unusual access patterns. We use these signals to protect account entry and investigate suspected misuse, not to request your device password.

Wallet references

DANA, OVO, GoPay and QRIS records may show a reference, amount status and matching result. Bank transfer and virtual account records serve the same accounting purpose. We do not need your wallet PIN to connect a receipt with your account.

Cookie controls

Cookies can keep a session active, remember a security choice and help us understand whether a page loads correctly. You can manage cookie settings in your browser; blocking some cookies may require another login or limit a security function.

Retention checks

We retain records for the period needed for account security, payment matching, dispute handling and legal duties. When a purpose ends, deletion or anonymisation is considered, subject to records that must remain available under applicable requirements.

Request handling

For access, correction or deletion questions, we first confirm the account holder and clarify the requested record. We then explain the action taken or the reason a record must remain, using the support path connected to your account.

Privacy Policy questions about panen 138

These answers address the privacy searches we hear most often before an account is opened. They cover the account path, wallet references, mobile cookies, data requests and access wording for Indonesia. If your situation involves a specific receipt, phone verification result or sign-in event, use the account support path so we can check the relevant record rather than relying on a general answer.

It covers account details, phone verification, device signals, cookies, payment references, security events, retention and requests about your personal data. It applies when you browse areas such as Dragon Tiger or Basketball Betting and when you use DANA, OVO, GoPay, QRIS or bank transfer.

We use your phone number to create and identify the account, complete the phone verification step and connect support requests with the correct record. If you ask for access or a correction, we may use that verified detail to reduce the chance of disclosure to another person.

No wallet PIN is needed for us to match a DANA or QRIS payment reference with an account. We may retain the reference, status and related receipt details required for payment checks, but you should never send a wallet PIN, password or full banking credential to support.

Cookies can keep your session, remember a security setting and help us detect unusual sign-in behaviour while you move from login to the lobby. You can adjust them in your mobile browser settings. Restricting some cookies may sign you out or affect account security functions.

Yes. Use the account support path and state whether you want access to a record, a correction or another privacy action. We may confirm your identity through the signed-in account or phone verification, then explain what can be changed and what must be retained.

Retention varies by purpose. Account security events, payment references and support records may need to remain available for matching, disputes, misuse checks or legal duties. When the reason ends, we consider deletion or anonymisation, subject to requirements that apply where local law permits.

The policy explains data handling for Indonesian account activity, including local wallet references and phone verification. Account eligibility and access depend on local law. If you are unsure whether access is available from your location, contact support through the account path before submitting personal details.