Reference

Open with pikat4d Privacy Policy

pikat4d Privacy Policy shows how we handle your account details, phone verification, device signals and wallet records when you access our pages.

Account dataWallet recordsCookie choicesRequest changes
pikat4d Open with pikat4d Privacy Policy
REQUEST HELP

Contact us about policy requests

A clear request helps us locate the right account record without asking you to resend unrelated details. Use the support contact shown in your account area, state the policy question, and include the relevant account step or payment reference. We can then check access, wallet status or a correction request without exposing another person’s data.

Team online

Account access request

Tell us which phone-verification step is blocked and use the support contact displayed after login. We will use the account details needed to identify your request and avoid unnecessary data collection.

Wallet record query

For a DANA, OVO, GoPay or QRIS record, include the date and reference shown in your account. We use those details to locate the relevant entry without requesting your wallet password.

Correction request

Ask us to correct account details through the policy contact route inside your account area. Describe the field that needs changing, and we may ask for a matching account check first.

DATA CONTROL

See how account data is protected

We manage this policy around the account actions you can actually recognise: phone verification, login sessions, wallet status and requests made from a mobile browser or desktop.

Data handling

We collect details needed for account creation, phone verification, support replies and payment references. We separate those records by purpose so a QRIS reference is not treated as a general permission for unrelated use.

Cookies and devices

Cookies and device signals help keep a mobile-browser session connected from login to the account area. You can manage browser cookie settings, although changing them may affect access checks or saved session preferences.

Account security

Phone verification supports the account access check, while session controls help reduce unauthorised entry. Never send a password or wallet PIN through a support request, even when asking about Privacy Policy.

Retention timing

We keep account, support and payment-reference records while they serve account operations, dispute handling or legal needs. When a record no longer serves those needs, we remove it or make it non-identifying.

Who to contact

Use the support contact visible in your signed-in account area for questions about collection, use, access or deletion. Include only the details needed to locate your own account and explain the request clearly.

Change requests

You can ask us to correct inaccurate account details or explain how a record is used. We may verify your phone-linked account before making a change, so another person cannot alter your data.

Find answers about Privacy Policy

These Privacy Policy answers focus on the searches we hear before an account is opened or a wallet record is queried. Each response points to a practical account step, device setting or support route, so you know what to prepare before contacting us. Access and eligibility remain where local law permits.

It covers account details, phone verification, device and cookie signals, support requests, and records connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We may collect details you enter for an account, phone-verification records, session signals, cookie preferences and payment references needed to check wallet status or answer a support request.

Phone verification helps connect an access request to the correct account. We may use that check when you ask for a correction or account-data request, without asking for your wallet PIN.

Yes. The policy covers references connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity when those records support account or payment-status handling.

Use the support contact shown inside your account area, identify the field that is inaccurate, and explain the requested change. We may complete a phone-linked account check before editing it.

We retain account, support and payment-reference records while needed for operations, disputes or legal needs. After that purpose ends, we remove the record or make it non-identifying.

Yes. The policy applies when you move from mobile login to the account area or lobby. Cookies and device signals may support the session, and your browser settings can affect that process.