Reference

pasir4d Privacy Policy For Your Account

Our Privacy Policy explains how pasir4d handles the details you provide before you enter the lobby, including your phone verification, login activity and wallet status.

Clear data purposesWallet details explainedContact path includedMobile access covered
pasir4d pasir4d Privacy Policy For Your Account
CONTACT ROUTES

Get Privacy Policy Help Before Access

A direct contact route helps when you want to understand a data entry before opening your account.

Account data request Ask us to identify the account details connected with your phone verification or login…
Wallet data question If DANA, OVO, GoPay or QRIS appears in a transaction record, tell us the…
Correction request When a profile detail is inaccurate, contact us with the field that needs attention…
DATA PRACTICES

Six Privacy Checks Behind Your Login

We apply the Privacy Policy to the records that help you reach the lobby and to the signals that help us protect that access.

Account details

We use the details entered during account creation to provide login access, connect your phone verification and keep your account record distinct from another person’s. Please keep submitted details accurate, because a mismatch can delay a privacy request or account check.

Wallet references

A DANA, OVO, GoPay or QRIS reference may be stored with a transaction record so we can trace the status shown in your account. Bank transfer and virtual account references serve the same matching purpose without revealing your wallet PIN.

Cookie controls

Cookies can keep a selected page state, remember a session setting and help us understand whether a page loads correctly on your mobile browser. You can manage browser cookie controls, although switching them off may affect parts of the account path.

Device signals

We may use device type, browser details and session timing to check unusual login behaviour. These signals help us protect your account without treating a device label as your identity by itself, and they support checks when access behaves differently.

Retention period

We retain account, transaction and contact records for the period needed for the purpose explained in this policy, account security and applicable legal duties. When a record no longer needs retention, our handling follows the deletion or anonymisation process available for that record.

Your requests

You can ask what personal data we hold, request a correction, ask about use or retention, or raise a deletion question. Send the request through our contact route and include enough account context for us to verify ownership without receiving your password.

Privacy Policy Answers For pasir4d

These Privacy Policy answers address the searches we hear most often before an account is opened. We keep each answer tied to a real account action, from phone verification to a DANA or QRIS reference, so you know what to expect when you contact us. If your question concerns eligibility or access, it depends on local law.

It covers details you submit for an account, phone verification, login and device signals, cookie use, payment references and contact requests. It also explains why we use those records, how retention works, and how you can ask for access, correction or deletion where local law permits.

Phone verification helps connect your account to the contact detail you submitted and helps us distinguish an authorised login from an unusual attempt. We use that step for account protection and request handling, not as permission to ask for your password or wallet PIN.

Yes. The policy explains that a DANA, OVO, GoPay or QRIS reference can be used to match a transaction with your account and check its status. It does not require you to send a wallet PIN, and bank transfer references follow the same matching principle.

Use our account contact route and identify the profile field that is wrong, such as a phone detail or account name. We may request an ownership check before making the change. Do not include your password, wallet PIN or unnecessary payment credentials in the request.

Cookies can retain a session setting, selected page state or basic page function when you use a mobile browser. Your browser controls can limit them, but some account steps may behave differently afterward. The policy explains why those cookie functions are used.

We keep account, transaction and contact records for the period required by their stated purpose, account protection and applicable legal duties. The exact period can differ by record type. You can contact us to ask how retention applies to a particular account record.

You can send a deletion question through our contact route, and we will assess it against the record purpose and applicable legal duties. Where local law permits, we explain what can be removed, what must remain, and whether anonymisation is available instead.