Reference

pas4d Privacy Policy for Your Account

pas4d Privacy Policy shows how we handle the details connected to your account, mobile browser, and wallet activity.

Clear data choicesWallet privacy contextPhone verification detailsPolicy contact path
pas4d pas4d Privacy Policy for Your Account
CONTACT YOUR WAY

Get Policy Help Near Account Support

A clear contact path matters when you want to ask about stored data or correct an account detail.

Account data request Ask us to confirm the account details connected to your phone verification and login record. We may request an account step to check that the request comes from you.
Wallet reference check Send the transaction reference, date, and rail name when a DANA, OVO, GoPay, or QRIS record needs correction. Do not include wallet passwords or private security codes.
Policy clarification Use the account support route for questions about cookies, device records, retention, or access requests. We will explain the relevant Privacy Policy section and the next step.
CONTROL YOUR RECORDS

See How pas4d Protects Account Records

We treat Privacy Policy work as an account process, not a hidden background setting. Our controls connect phone verification, sign-in activity, wallet references, and device behaviour so we can investigate a request…

Account details

We use the details you submit for account creation and phone verification to identify your account, respond to requests, and keep the correct person connected to account activity.

Device records

Mobile and desktop sign-ins may create separate device signals, such as browser or session details. These records help us detect unusual access and protect your account.

Cookie choices

Cookies can remember session settings and help the account area load correctly. You can manage browser cookie controls, although changing them may affect sign-in continuity.

Payment references

For DANA, QRIS, bank transfer, and virtual account activity, we retain reference details rather than wallet passwords. This supports matching, status checks, and account queries.

Retention period

We retain records for the time needed to provide account support, resolve payment questions, protect access, and meet applicable legal duties. Older records are removed or handled accordingly.

Change requests

To request access, correction, or clarification, contact us from the account support route with your account identifier. We may verify your phone before making a change.

Privacy Policy Answers Before Account Opening

These Privacy Policy answers cover the searches we hear most often before an account is opened. We keep the wording practical: what we collect, how wallet references are handled, how you request a change, and what happens when you use pas4d from a mobile browser or desktop device in Indonesia.

It covers account details, phone verification, cookies, device signals, login records, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

No. Our Privacy Policy describes the transaction references and status details needed for account matching and support. Your DANA or OVO password and private security code should never be sent to us.

Device and browser records help us recognise unusual sign-in behaviour and protect your account. A mobile browser and desktop browser can produce different signals and may lead to an extra verification step.

Use the account support route and state whether you want access, correction, or clarification. Include your account identifier, but not a wallet password. We may verify your phone before processing the request.

We keep records for the period needed for account support, payment reference checks, access protection, and applicable legal duties. After that need ends, records are removed or handled under the relevant requirement.

Our policy explains handling for Indonesian account access, including mobile use in Denpasar. Availability and eligibility depends on local law, and the service is provided where local law permits.

Contact us through the support route connected to your account. Describe the data question and include a relevant payment reference only when needed; we will direct the request to the appropriate policy process.