Reference

Open pikat4d Privacy Policy Before Account Access

pikat4d Privacy Policy explains what we collect when you create an account, verify your phone, browse on mobile, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice detailsCookie choices
pikat4d Open pikat4d Privacy Policy Before Account Access
CONTACT PATHS

Check Privacy Policy Help Through Support Chat

A direct support path helps you ask about the Privacy Policy without placing account details in a public message.

Policy questions Ask through support chat when you need to know which account, device or cookie details we hold. We will use the account path to locate your request and may ask for phone verification before discussing private records.
Wallet references For DANA, OVO, GoPay or QRIS questions, share the payment reference and approximate time, not your wallet PIN. This lets us trace a status without requesting credentials that should remain private to you.
Correction requests If your name, phone detail or account record needs correction, tell support chat what appears wrong and what should replace it. We may confirm account ownership before applying a change to protect your data.
HANDLING DETAILS

Explore How We Handle Account Data

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

Account creation

When you open an account, we collect the details needed to create your profile and send account-related messages. A clear phone verification step helps us connect the right person to the right account before private records are discussed.

Phone verification

The phone check is used to confirm account access and help prevent another person from changing private details. We do not ask you to place a wallet PIN or full payment password into support chat.

Device signals

Your browser, device type and login timing can be recorded when you move from sign-in to the lobby. These signals help us examine unusual access, including a new mobile device, without describing your private activity publicly.

Cookie choices

Cookies can keep a session working as you move between account pages and titles such as Fishing God or Bingo. You can manage cookie settings in your browser, although blocking some cookies may interrupt sign-in or saved preferences.

Retention period

We keep account, support and payment-reference records only for the operational or legal purpose connected to them. When a record is no longer needed for that purpose, our handling follows the applicable retention process.

Your requests

You can ask what personal data we hold, request a correction, or ask how a record is used through support chat. We may verify your account first, and the outcome can depend on local law and required records.

Browse pikat4d Privacy Policy Answers

These Privacy Policy answers focus on the account steps and local wallet records you are most likely to ask about before opening an account. We keep the wording tied to real actions, including phone verification, mobile browsing, QRIS receipts and support-chat requests. If your situation is not listed, contact us with the smallest amount of account detail needed to identify the issue.

It covers data linked to account creation, phone verification, sign-in, device activity, cookies, support requests and payment references. That includes records connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when those details are used to match your account.

Phone verification helps confirm that you control the account before private details are discussed or changed. It can also help us investigate an unfamiliar login. We use the verification step for account protection, not as a reason to request your wallet PIN in chat.

Yes. When you sign in from a phone or tablet, we may record device type, browser signals and login timing. These details help us understand access problems and unusual activity. They do not make your private account records visible to other people using the lobby.

We use payment references, status details and related timestamps to match a wallet action with your account. We do not need your wallet PIN for that check. If a receipt is missing, support chat can examine the reference you provide and explain the account record.

You can contact support chat to ask what personal data we hold or to request a correction. Describe the field that appears wrong, such as a phone detail, and complete account verification if requested. The result depends on local law and records we must retain.

Retention depends on why the record exists. Account, support and payment-reference details may remain while needed for account access, dispute handling, security checks or applicable legal requests. When that purpose ends, our process addresses the record according to the relevant retention requirement.

Use support chat and state that your question concerns the Privacy Policy. You can ask about cookies, device data, phone verification, wallet references or a correction request. Share only the details needed to locate your account, and never send a wallet PIN or full password.