Reference

Read the pantai66 Privacy Policy Clearly

The pantai66 Privacy Policy explains what we collect when you open an account, verify your phone, use DANA or QRIS, and contact our help team.

Account dataWallet recordsCookie choicesAccess requests
pantai66 Read the pantai66 Privacy Policy Clearly
PRIVACY HELP DESK

Contact Us About Your Privacy Choices

A direct support route helps you resolve a privacy question without repeating your account story across unrelated channels.

Account help Use the account help path when you need to ask what data we hold, why a phone verification record appears, or how to request a correction. We first match the request to your account details so private information is not disclosed to another person.
Wallet receipts If a DANA, OVO, GoPay, or QRIS receipt is connected to the wrong account, send the reference through account help. We use the reference to locate the status and explain which payment details are stored for reconciliation.
Access questions For a copy, removal request, or concern about a cookie, write through the same support route and state the action you want. We may verify your phone before processing it, and access remains subject to local law.
DATA HANDLING

See How Account Data Stays Protected

Privacy is handled through practical account controls rather than a broad promise. We separate identity checks, payment references, device signals, and support conversations by their operational purpose, then limit account details to…

Phone verification

Before account access is completed, phone verification helps us connect the person making a request with the correct profile. We store the result and related time record for account protection, while avoiding any request for your DANA, OVO, or bank password.

Device records

A mobile browser and a desktop browser can produce different device or session signals when you sign in. We use those signals to spot unusual access around titles such as Live Roulette Prestige, not to create a separate identity without your account step.

Cookie control

Cookies can keep a session active, remember a selected language, or help us understand whether a page loads correctly. Your browser controls allow you to remove or block them; some account pages may then ask you to sign in again.

Payment matching

For QRIS, DANA, OVO, GoPay, bank transfer, and virtual account payments, we keep the reference, amount status, and account match needed to trace a receipt. We do not use that record as permission to access your external wallet.

Retention timing

We keep personal data while it supports account access, payment reconciliation, security checks, disputes, or a legal requirement. When the reason ends, we remove or anonymise the record according to our internal retention process rather than keeping it without purpose.

Change requests

You can ask us to correct inaccurate contact details, explain a stored device signal, provide available account data, or remove data where permitted. Send the request through account help; we may confirm your phone and explain any limit required by local law.

Find Privacy Policy Answers Before Opening

These Privacy Policy answers address the account and payment questions we expect from Indonesian customers. They explain the practical steps behind data access, wallet references, cookies, device records, and contact requests, so you can decide what to share before opening an account. If your situation is different, use the support path with the relevant phone or payment reference.

It covers account details, phone verification, login and device records, cookies, support messages, and payment references. It also explains why we use each category, how long we retain it, and how you can request access, correction, or removal where local law permits.

No. For DANA and QRIS, we use the transaction status and reference needed to match a payment with your account. We do not need your external wallet password. The same principle applies to OVO, GoPay, bank transfer, and virtual account records.

Phone verification helps us confirm that a privacy request comes from the person connected with the account. We keep the verification result and related account record for access protection, then use it when checking a correction, data copy, or removal request.

You can send a removal request through account help and explain which account data you want addressed. We may retain records needed for payment reconciliation, security, disputes, or legal duties. Any removal decision depends on local law, and we will explain the reason.

Cookies may preserve your login session, remember a language setting, or show whether a page loaded correctly. You can block or clear them through your browser. If you do, the account area may require another sign-in and some saved preferences may disappear.

Yes, where local law permits. Contact us through the account help path and identify the profile using its registered phone or another requested account step. We can then explain the available records, including verification, device, support, and payment-reference data.

Yes. The same Privacy Policy applies when you sign in from a mobile browser or desktop browser. A new device can create a session or security record, but your data rights remain the same. Account access and eligibility depend on local law.