Reference

Open with pikat4d Legal terms

pikat4d Legal sets out how account access, wallet records, data requests and policy changes work before you enter the lobby.

Account conditionsData handlingLocal-law accessPayment records
pikat4d Open with pikat4d Legal terms
POLICY HELP DESK

Contact us about Legal questions

A clear contact path matters when a Legal condition affects your account or wallet status. We keep policy questions close to the account support panel, so you can refer to the exact step rather than describe the whole matter from memory. Include your account identifier and a short description of the issue.

Team online

Account access

Use the support panel when a verification step pauses access. We can point you to the relevant Legal condition and identify which account detail needs attention.

Wallet records

For DANA, OVO, GoPay or QRIS questions, send the payment receipt and account reference through support. We use those details to match the transaction record.

Policy changes

Ask us about a changed clause or account condition through the same support route. We will direct your request to the policy contact handling Legal matters.

DATA CARE PRACTICE

Protect your account under Legal terms

We handle policy duties through practical account controls rather than broad promises. The steps below explain what happens to your data, how account security is checked, and how to request a change.

Data handling

We use account details to create access, verify the account holder, record wallet activity and respond to Legal requests. We do not ask for unrelated details during a routine support case.

Cookies

Cookies can keep your session and policy choices connected to the same device. You can adjust browser cookie controls, although some account and security functions may then require another check.

Account security

Phone verification is completed before account access, and unusual login or wallet activity may trigger an additional check. Keep your sign-in details private and contact support if access changes unexpectedly.

Record retention

We retain account, payment and support records for the period needed for security, dispute handling and Legal obligations. A retention request can be sent through the account support path.

Who to contact

Our account support team is the first contact for policy, data, verification and wallet-record questions. Include the relevant account step so the request reaches the correct policy handler.

Request changes

You may ask us to correct account details, clarify stored records or explain a policy clause. Send the request from your account support route so we can confirm ownership first.

Find answers about pikat4d Legal

These Legal answers cover the practical questions that arise before account access, during verification and when you need a record changed. If your situation is not listed, use the support path with your account reference and the relevant payment or login step.

pikat4d Legal covers account access, phone verification, personal-data handling, cookies, payment records, security checks, retention and requests to correct or clarify stored details.

Access or eligibility depends on local law. You are responsible for confirming that the relevant services are permitted where you are located before opening or using an account.

Phone verification helps connect an account to the person requesting access and supports security checks. We complete it before account access and may ask for another check when details conflict.

DANA and QRIS references are linked to the account activity needed to identify a payment, investigate a status question and meet applicable Legal record duties. Send receipts through support.

Yes. Send a correction or clarification request through the account support path. We first confirm account ownership, then assess the requested change against security and Legal record requirements.

Cookies can retain session and policy choices on your device. If you disable them, you may need to confirm settings again, and some access or security functions may not work as expected.

Include your account identifier, the clause or screen involved, and any relevant DANA, OVO, GoPay, QRIS or bank-transfer receipt. Never send your password or private sign-in code.