Reference

pandagendut Privacy Policy for Your Account

Our Privacy Policy explains what pandagendut collects when you create an account, verify your phone and access the lobby from a mobile browser or desktop.

Account dataWallet referencesDevice choicesPolicy access
pandagendut pandagendut Privacy Policy for Your Account
CONTACT PATHS

Browse Privacy Help Through Your Account

A clear support route helps you ask what data we hold, why a record appears or how to correct an account detail.

Account support path Open the account support area to ask about stored profile data, phone verification or a login record. We use the account details you provide to locate your request and avoid discussing private account matters through an unrelated conversation.
Wallet status check If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the transaction reference through the cashier support path. We compare the reference with the account record and explain what can be corrected without asking for your wallet password.
Policy request Ask us to explain a Privacy Policy point, request a copy of relevant account data or seek a correction through support. Include your account phone number and the specific record involved so we can verify the request before replying.
HANDLING DETAILS

Explore How We Handle Your Data

The practical details matter when your account connects login activity, device use and wallet records.

Account records

We use details you submit during account creation and phone verification to establish access, match support requests and maintain an account history. If a detail changes, ask us to correct it through the account support path after we confirm your identity.

Device signals

When you move from login to the lobby on a mobile browser, we may receive device and session signals that help maintain access and identify unusual activity. These signals support security checks; they are not treated as a substitute for your account details.

Cookies and storage

Cookies or browser storage may remember a session choice, keep a page working or help us understand a return visit. You can manage browser storage through your device settings, although removing it may require another login or affect saved session preferences.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may retain reference numbers, status results and account links rather than your wallet password. These records help us check a receipt, resolve a mismatch and answer a payment question.

Security controls

Phone verification, login records and account review steps help us protect access to your profile. Do not share your password or verification code with support. If you notice an unfamiliar session, contact us through the account path and state when you noticed it.

Retention requests

We keep records for as long as needed for account operation, security, disputes and legal duties, then assess whether they are still required. You can ask what remains, request correction or ask about deletion, subject to local law and necessary record-keeping.

Browse Privacy Policy Answers Before Joining

These Privacy Policy answers address the account and wallet questions you are most likely to ask before opening access. We keep the examples tied to actual steps, such as phone verification, mobile login, QRIS status and support requests. If your situation is not covered, use the account support path with the specific record or payment reference involved.

It covers data connected with your account, phone verification, login sessions, device signals, support requests and payment references. It also explains cookies, retention, security handling, correction requests and account access conditions where local law permits.

We use phone verification to confirm the account access step, connect support requests to the right account and help detect unusual login activity. We do not ask you to send a verification code or password through a support message.

Yes. The policy treats DANA, OVO, GoPay and QRIS references as transaction data used for status checks, receipt matching and account support. We may also handle bank transfer or virtual account references, but we do not need your wallet password.

When you move from mobile login to the lobby, we may receive session and device signals needed for access, security checks and browser continuity. Cookie settings are controlled through your device or browser, and removing storage may require another login.

Use the account support path and state whether you want a copy, correction or clarification. Include the phone number linked to your account and identify the record, such as a QRIS receipt reference. We verify the request before discussing account data.

We retain records while they are needed for account operation, security, disputes and legal duties. Payment references may remain after a status check for reconciliation. You can ask what is retained and request deletion, subject to local law and necessary records.

Start with the support path inside your account and describe the Privacy Policy concern clearly. For a wallet mismatch, include the DANA, OVO, GoPay or QRIS reference. For access questions, mention your phone verification step and device path.