Reference

pan4d Privacy Policy for Your Account

pan4d Privacy Policy shows how we handle the details connected to your account, device, wallet status and access to games such as Speed Blackjack and Fish Hunter.

Clear data purposesWallet details explainedAccount access controlsCookie choicesSupport request path
pan4d pan4d Privacy Policy for Your Account
CONTACT WHEN NEEDED

Where To Ask About Privacy Policy

A clear contact route helps you ask about your personal data without explaining your request twice.

Account privacy request Use the account support route to ask what personal details are linked with your pan4d profile. We may request an account step or identity detail before discussing records, so another person cannot obtain your login, wallet or transaction data.
Wallet record question If a DANA, OVO, GoPay or QRIS receipt appears beside the wrong account status, send the transaction reference through support. We use that reference to locate the relevant record and explain what data was checked during the status review.
Change or removal request Ask us to correct a detail, close an account or explain a retention period through the same support path. We will confirm which request you made, check whether a legal or security record must remain, and tell you the next step.
HANDLING DETAILS

What Our Privacy Process Covers

We treat the Privacy Policy as an operating process rather than a footer link. Each request is matched to the account record, device event or wallet reference involved, then handled according to…

Account opening data

When you open an account, we collect the details needed to create access and send account messages. Phone verification can be part of that step. We do not treat a completed form as permission to use every detail for an unrelated purpose.

Device and session signals

A phone moving from login to the lobby may create session, browser and device records. We use these signals to keep the account path working and flag unusual access. The same approach can apply when you return on a desktop browser.

Cookies and preferences

Cookies can retain a sign-in session, language choice and basic page preference so you do not repeat the same step on every visit. You can manage cookie settings in your browser, although disabling necessary cookies may interrupt account access.

Wallet and transaction records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create references used to match a deposit or withdrawal request. We use those references for account records, receipt checks and dispute handling, including when a wallet status stalls.

Retention and closure

Closing an account does not always remove every record immediately. We may retain transaction, security or support records for the period needed for legal duties, dispute handling and account protection, then remove or restrict them when that purpose ends.

Requests and corrections

You can ask us to access, correct or clarify personal data connected with your account. Include the relevant account detail and request type. We verify the requester first, then explain any limits where a record must remain for security or legal reasons.

Privacy Policy Answers For pan4d

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet record. We keep the wording practical: what data is involved, why a check happens, what your device may send and which account step helps us locate a request. If your situation is different, use the support path above and describe the specific record.

It covers account details, phone verification, device and session data, cookies, wallet references, support requests and retention. It also explains why we use each category, how access is protected and how you can ask for a copy, correction or clarification where local law permits.

We use account and phone details to create access, complete verification, send necessary account messages and identify the correct record when you contact support. The same details can help match a DANA, OVO, GoPay or QRIS receipt to your account.

Yes. When you sign in from a phone or desktop, we may record browser, session and device signals for access continuity and security checks. These records help us investigate unusual login behaviour without treating your device as a separate account.

A DANA or QRIS request can create a transaction reference, amount status and time record. We use those details to match the cashier event, check a receipt and answer a support request. The record is retained only for the relevant operational, security or legal purpose.

Yes. Send a correction request through the account support route and identify the detail that appears wrong. We may verify your account before making a change, then confirm whether the correction is possible or whether a transaction or security record must remain unchanged.

The period depends on the type of record and its purpose. Account, transaction, security and support records can have different retention periods. When a purpose ends, we remove, restrict or anonymise the relevant detail unless a legal or dispute-handling need requires continued storage.