Reference

pix4d Privacy Policy For Your Account

Your pix4d Privacy Policy explains how we handle account details, device signals and wallet records when you use our Indonesia service.

Account clarityWallet recordsDevice choices
pix4d pix4d Privacy Policy For Your Account
PRIVACY HELP PATH

Privacy Help Along Your Cashier Path

A clear support route matters when your privacy question connects with an account or wallet record.

Account request Ask us to locate, correct or explain account data through a signed-in support request.
Cashier record For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, share the transaction…
Access concern If phone verification or a device session blocks your account, tell us which step…
SIX PRIVACY CONTROLS

Six Controls Behind Our Privacy Policy

We apply the Privacy Policy at each practical point in your account journey, from phone verification to a wallet status check.

Data handling

We use account details to create access, phone verification data to protect sign-in, and cashier references to trace DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We avoid asking for wallet passwords or PINs in support messages.

Cookie choices

Cookies and similar session tools help keep your login and Privacy Policy preferences connected across pages. You can adjust browser settings, but blocking required cookies may interrupt account access or send you back to phone verification.

Account security

We treat a phone verification step, device session and unusual sign-in signal as security details. If access changes after a new phone or browser is used, we may pause the request until account ownership is checked.

Retention periods

We keep records only for the account, security, payment or support purpose that requires them, subject to legal and operational needs. A cashier reference can remain after a session ends so a status question can be resolved later.

Contact route

You can ask about your personal data through the account support path, with a transaction reference when the request concerns a wallet record. We may need to confirm ownership before sharing, changing or removing protected account data.

Policy changes

If this Privacy Policy changes, we will present the revised wording on the policy page and identify the effective context where needed. Check this page before opening an account or changing a DANA, QRIS or bank transfer preference.

Privacy Policy Answers For pix4d Accounts

These Privacy Policy answers address the questions we expect before you open or use a pix4d account in Indonesia. They cover account creation, phone verification, wallet records, device access, cookies and requests to change personal data. We keep the answers tied to real steps: sign in, open the cashier path, provide a transaction reference where relevant, and avoid sending passwords or wallet PINs. If a question involves eligibility, access depends on local law.

The pix4d Privacy Policy covers account details, phone verification, device and session signals, cookies, support requests, and payment references. It explains why we use each data type, how we protect account access, how long records may remain, and how you can ask about eligible changes.

When you use DANA, OVO, GoPay or QRIS, we may receive a transaction reference, status, amount context and timing from the payment flow. We do not need your wallet password or PIN for a support check. Bank transfer and virtual account records follow the same account process.

Send a privacy request through your signed-in account support path and describe the data you want located or explained. Add your registered phone details only in that protected route. We may verify account ownership before responding, and access depends on local law.

The Privacy Policy allows us to use limited device, browser and session signals for sign-in security, page operation and unusual-access checks. These signals are not a request for your private device content. Changing browsers can trigger phone verification or another ownership check.

Cookies connect your login session with page settings and help keep the Privacy Policy preference you selected. Browser controls can block them, but required cookies may be needed for account access, cashier status checks or a return to the correct verification step.

Yes, you can request a correction or deletion of eligible account data through support. Tell us what appears wrong and include a relevant record reference when needed. Some payment, security or legal records may need to remain for the period required by local rules.

We limit access to people and service processes that need the data for account security, payment tracing or support. We do not ask you to publish private details. If a request involves another person or protected wallet record, ownership checks apply before disclosure.