Reference

pandahoky Privacy Policy for Your Account

Our Privacy Policy explains how pandahoky handles the data connected with your account, device access and wallet choices.

Account dataCookie choicesWallet recordsPolicy requests

Explore Our Lobby Read FAQ

See How Wallet And Account Data Works

pandahoky Service availability depends on jurisdiction. Users are responsible for checking local law before access.

This Privacy Policy covers data you provide when opening an account, completing phone verification and contacting us about account access. It also covers technical data created when your phone or computer reaches the lobby, including device details, browser signals, login times and security events. Payment records

1
may show a DANA, OVO, GoPay or QRIS reference, while bank transfer and virtual account records help us match a deposit request to your account. We use these records to process account activity, investigate unusual access and answer support requests. We do not treat a wallet
2
name as permission to use unrelated data. You can ask what we hold, request a correction or ask about deletion through our support route. Where access or eligibility is discussed, it depends on local law and any applicable retention duty.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP WITH REQUESTS

Get A Clear Route For Privacy Questions

A privacy question should not leave you guessing which account step to take. Use the support route shown beside your account and cashier area, describe the data request in plain English, and…

Account data request Ask us to locate, correct or explain data linked with your account. Include your registered contact detail so we can confirm ownership before discussing records.

Cookie question Tell us which device path you used, such as mobile browser or desktop browser, when a cookie choice or stored preference needs clarification.

Wallet record check For a DANA, OVO, GoPay or QRIS reference, send the account identifier and transaction date through support. We use that detail to find the correct record.

DATA CONTROL

What Our Privacy Process Covers

We handle privacy as an account process rather than a vague promise. Phone verification helps us confirm that a request comes from the account owner, while device and login signals help us…

Account data

We may hold your contact details, verification status and account activity so we can provide account access and answer requests. We use only the data needed for the stated account purpose.

Device signals

When you move from login to a lobby such as VIP Baccarat or Fishing God, technical signals can record browser type, session timing and security events for account protection.

Cookie choices

Cookies can remember a session or preference on your mobile browser. You can clear stored cookies in browser settings, though doing so may require another account login.

Account security

Phone verification is part of account access and privacy checks. Never share a verification code with another person, and contact support if a login event does not look like yours.

Retention timing

We retain account, security and wallet records only for the period needed for account operations, dispute handling, security checks or a duty that depends on local law.

Change requests

To request a correction or ask what data is held, contact support from the registered account path. We may verify your phone or email before making a change.

Privacy Policy Answers Before Account Access

These answers address the Privacy Policy questions we expect you to ask before opening an account or using the mobile path. If your situation is not covered, send the details through support and we will direct the request to the right account process.

The Privacy Policy covers account details, phone verification, device signals, cookies, login events, support messages and wallet records connected with DANA, OVO, GoPay, QRIS or bank transfers.

Phone verification helps us confirm account ownership before access or a data request is handled. It also gives support a safer way to investigate a login that does not match your usual device path.

Yes. When you use a mobile browser, we may process browser type, session details, cookie settings and security signals needed for the account path. Clearing cookies can require you to log in again.

We may retain the wallet reference, account identifier, amount and timing needed to match a DANA or QRIS request. These records support account checks and payment questions without treating wallet data as broad permission.

Yes. Contact support from the registered account route, state which detail is incorrect and provide the relevant phone or email. We may verify ownership before changing the account record.

Retention depends on the purpose of the record, such as account security, dispute handling or a legal duty. The applicable period depends on local law and the specific account request.

Use the support contact displayed beside your account and cashier path. Include your registered contact detail, request type and any relevant date, while avoiding passwords or verification codes.

pandahoky Privacy Policy for Your Account

Get A Clear Route For Privacy Questions

What Our Privacy Process Covers

Account data

Device signals

Cookie choices

Account security

Retention timing

Change requests

Privacy Policy Answers Before Account Access

01 What does the pandahoky Privacy Policy cover?

02 Why does pandahoky need phone verification?

03 Does the Privacy Policy cover mobile browser data?

04 How are DANA and QRIS records handled?

05 Can I ask pandahoky to correct my account data?

06 How long does pandahoky keep privacy-related data?

07 Where do I send a Privacy Policy request?

Related Pages