Reference

Open the panda10001 Privacy Policy

panda10001 Privacy Policy explains how we handle your account details, wallet records, device signals and cookie choices while you access our lobby in Indonesia.

Account dataWallet recordsCookie choicesPhone verification
panda10001 Open the panda10001 Privacy Policy
CONTACT YOUR WAY

Browse Privacy Support Through Your Account

A clear contact route helps you ask about personal data without searching through unrelated pages. We keep privacy questions connected to the account and cashier paths, so a request about a wallet reference, login record or phone verification can reach the right context. Include the email or phone detail linked to your account and a short description of the request. We may ask for account checks before discussing private records, and we will use the details you provide only to handle the support request.

Team online

Account support

Use the signed-in account support path when your question concerns profile details, phone verification or a record connected to your account. We can then identify the relevant account context before explaining what data we hold or how a requested change can be handled.

Cashier context

For a DANA, OVO, GoPay or QRIS reference, include the payment rail and the visible status from your cashier path. This helps us locate the matching transaction record without asking you to send unrelated account details or private wallet credentials.

Receipt questions

If a payment receipt or status check raises a privacy concern, send the reference shown in your account rather than a wallet password or full banking secret. We use the reference to investigate the record and explain the data action connected to it.

DATA HANDLING

Switch Through Your Privacy Choices

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

Account details

We may handle the details you enter for an account, including contact information and phone verification status. These details help us provide access to your account and respond to account-specific requests. Check your profile first, then contact support if a correction is needed.

Payment records

A DANA, OVO, GoPay or QRIS action can create a reference, amount, status and time record. Bank transfer and virtual account checks can create similar matching details. We use these records to reconcile requests and answer receipt questions without storing your wallet password.

Device signals

When you move from a mobile login into the lobby, we may process browser, device and session signals needed for page delivery, fraud checks and account continuity. These signals are not a request for access to your contacts, photos or unrelated files.

Cookies

Cookies can remember session choices and help us understand whether a page loads correctly. Your browser controls optional cookie settings, while disabling required cookies may interrupt login or account functions. Contact us if you want help understanding a cookie connected to your session.

Account protection

Phone verification and sign-in checks help us distinguish an account holder from an unauthorised request. Never send a password, one-time code or full wallet credential through support. We may request limited account identifiers before discussing private account or payment records.

Retention requests

We keep records only for the operational, security, dispute and legal purposes that apply to the account activity. Where local law permits, ask support about access, correction, deletion or retention concerns. Include your account contact detail so we can assess the request accurately.

Ask About panda10001 Privacy Policy

These Privacy Policy answers cover the account steps Indonesian customers ask about most often, from phone verification and mobile cookies to DANA or QRIS records. We keep the answers tied to how our account path works rather than describing unrelated platform features. If your situation is not listed, use the account support path and include the smallest useful detail.

The panda10001 Privacy Policy covers account details, phone verification, login sessions, device signals, cookies, support messages and payment-status records. It explains why we use each category, how it supports account operation, and how you can ask about access, correction, deletion or retention where local law permits.

Privacy Policy applies to references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those records to match a request, check a receipt and answer support questions. Do not send us your wallet password or full banking secret.

Phone verification confirms an account access step and can create a status record linked to your profile. It does not give us access to your contacts or personal files. If the phone detail is incorrect, contact support from the account path and ask for a profile correction.

When you use a mobile browser, we may process device type, browser details and session signals needed to deliver the login-to-lobby path and protect the account. We do not request access to unrelated phone content. Browser controls can manage optional cookies used during that session.

You can contact support through your account path and ask which personal records we hold about you. Include the account email or phone detail used for access. We may verify ownership before responding, and the available request process depends on local law.

Start with the profile details shown in your account, then contact support if something remains wrong. For a DANA, OVO, GoPay or QRIS record, include the visible reference and status rather than private wallet credentials. We assess correction requests against the applicable account and legal records.

Send a retention question through the account support path and identify the record category, such as phone verification, login activity or a QRIS receipt. We will explain the applicable purpose and request route. Where local law permits, you may also ask about deletion or restricted handling.