Reference

Open With pijar4d Privacy Policy

Our Privacy Policy shows how we handle your account details, wallet records and device activity when you use pijar4d.

Clear data purposesWallet record detailsRequest paths

Check DANA And QRIS Data Use

pijar4d Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We use account and transaction details to process the actions you request and to keep account access orderly. During registration, we may record your name, phone number, verification result, login activity and device details. When you select DANA, OVO, GoPay, QRIS, bank transfer or a virtual

1
account, we retain the payment reference, amount, status and receipt details needed to match the transaction to your account. We do not describe these records as permission to use your wallet outside the requested transaction. Access or eligibility depends on local law, and our Privacy Policy
2
may change when our data practices change. We will show the current wording on this page so you can check the applicable version before opening an account or sending a request.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT DATA HELP

Reach Us About Account Data

A clear contact path helps when a Privacy Policy question concerns login, phone verification or a wallet record. Contact us through the account support route shown near your account area and include the registered phone number, payment reference or device path involved. We use those details to locate the request without asking you to send a full password or wallet PIN.

Team online

Account access

If phone verification prevents account access, tell us the registered number and device type. We can direct your request to the account-data path without asking for your password.

Wallet status

For DANA, OVO, GoPay or QRIS records, include the transaction reference and status shown in your account. We use that receipt detail to identify the relevant Privacy Policy request.

Policy questions

When you need a copy, correction or explanation, send the request through our available support contact. We may ask for account verification before changing or disclosing personal data.

DATA CONTROL STEPS

Secure Your Account Data Path

Our handling process separates ordinary account activity from requests about personal data. We record the policy version connected to your account activity, protect login details during phone verification and use retention rules…

Data collection

We collect details you provide during registration, including your phone number, plus technical signals from the browser or device used to sign in and reach the lobby.

Cookie choices

Cookies and similar device storage can remember session preferences and help us understand an account visit. You can manage browser permissions, although some login functions may then need repeating.

Login security

Phone verification connects account access to the registered contact route. Never send us your password, wallet PIN or one-time code when asking about a Privacy Policy matter.

Payment matching

A DANA, OVO, GoPay or QRIS reference lets us match a receipt to the correct account. We use the reference for status checks rather than requesting unnecessary wallet credentials.

Record retention

We retain account, security and transaction records for the period needed for account administration, payment matching and dispute handling, then remove or restrict them under our internal process.

Change requests

You can ask for a copy, correction or clarification through account support. We verify the requestor first, then explain the available action and any reason a record must remain.

Find Privacy Policy Answers

These Privacy Policy answers address the account, device and payment questions we hear most often. If your situation involves a specific phone verification result, QRIS receipt or access request, use the support path so we can check the correct record.

It covers account registration, phone verification, login activity, device details, cookies, wallet and payment references, retention, data requests and the way we respond to questions about personal information.

We retain the reference, status, amount and receipt details needed to match a DANA or QRIS action to your account. We do not need your wallet PIN to investigate that record.

We may collect your name, registered phone number, verification result and account activity. We can also receive browser or device signals when you sign in, depending on your device settings.

Yes. Send a request through account support with your registered phone number and the change you need. We verify account control before providing a copy or correcting an eligible detail.

Cookies can maintain your session and remember selected settings while you move between login and account pages. Browser controls let you remove or restrict them, though access may require repeated sign-in.

We keep records for the period needed for account administration, payment matching, security checks and dispute handling. After that need ends, records are removed or restricted under our internal retention process.

Use the account support contact shown near your account area and describe whether you need access, correction or an explanation. Access or eligibility depends on local law and account verification.

Open With pijar4d Privacy Policy

Reach Us About Account Data

Account access

Wallet status

Policy questions

Secure Your Account Data Path

Data collection

Cookie choices

Login security

Payment matching

Record retention

Change requests

Find Privacy Policy Answers

01 What does the pijar4d Privacy Policy cover?

02 How does Privacy Policy treat DANA and QRIS records?

03 What account data do you collect at registration?

04 Can I request a copy or correction of my data?

05 How are cookies used on my device?

06 How long does pijar4d retain account data?

07 Where can I ask about Privacy Policy access?

Related Pages