Reference

pragmatic4d Privacy Policy Explained

Your account details and payment records deserve a clear explanation, so our Privacy Policy shows how pragmatic4d handles data linked to DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesRequest paths
pragmatic4d pragmatic4d Privacy Policy Explained
REACH OUR TEAM

Get Privacy Help Near Your Account

A privacy question should not require you to search through unrelated pages.

Account access requests Ask us to confirm the personal data connected with your account.
Payment record questions For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the transaction…
Cookie and contact choices Tell our support team if you want help with cookie settings, contact preferences or…
YOUR DATA PATH

What We Do With Your Privacy Choices

Our handling process follows the same account path you use to reach the lobby: identify the record, confirm the request, make the permitted change and keep a trace…

Data collection

We may receive your name, contact detail, verification material, login history, device information and transaction references when you open or…

Cookie controls

Cookies can keep a session active, remember selected settings and help us understand basic page errors.

Account security

We use login events, device signals and verification steps to identify unusual access.

Retention timing

We keep account, payment and support records only for the period needed for service, security, dispute handling or legal duties.

Correction requests

If your contact detail or account record is inaccurate, contact us through the account support path.

Deletion requests

You can ask whether your personal data may be removed, subject to records we must retain for security, payment reconciliation…

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the account questions we expect before registration: what we collect, why payment references appear, how cookies work, how to request a copy or correction, and where access applies. If your situation is different, use our support path with the smallest amount of detail needed to locate your account.

It covers personal data collected through our website and account paths, including contact details, verification records, login events, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay or QRIS.

We use account details to create access, confirm ownership, protect login sessions, answer support requests and connect payment status with the correct account. Access or eligibility depends on local law and applicable requirements.

Yes. The policy covers payment references and status information received for DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We do not ask for your wallet password or PIN.

Use the support path beside your account or cashier area and request an account data copy. Include your registered contact detail, then complete ownership checks before we provide records linked to you.

You can request a correction through support when your contact detail or another account record is inaccurate. We confirm ownership first, apply the permitted change and explain if a record must remain unchanged.

Cookies can maintain your session, remember settings and help identify page errors. Browser controls let you remove or restrict them, but some account functions may not work correctly when required session cookies are blocked.

Retention depends on the record and its purpose. We keep data for account operation, security, payment reconciliation, dispute handling or legal duties, then delete, anonymise or restrict routine access when it is no longer needed.