Reference

pariban4d Privacy Policy for Indonesia

Our Privacy Policy explains how pariban4d handles the account details connected with DANA, OVO, GoPay and QRIS, including what we collect when you open an account and sign…

Account recordsWallet referencesDevice sessionsContact requests
pariban4d pariban4d Privacy Policy for Indonesia
CONTACT ROUTES

Where to ask about account data

A direct support route helps when a Privacy Policy question is tied to a real account event.

Account data request Ask us to explain, correct or remove a personal detail held with your account.
Wallet record question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the cashier…
Login privacy concern If a mobile browser or desktop session appears unfamiliar, contact our account support path…
SIX CONTROL POINTS

Six data controls behind your account

We apply the Privacy Policy through ordinary account controls rather than vague promises.

Data we collect

We may receive your phone number, account details, login events, device signals and requested payment references.

Cookie choices

Cookies and similar browser storage can help remember a session, protect account access and keep a requested page working.

Account protection

We use phone verification before account access and examine sign-in signals when an event looks unusual.

Retention periods

We retain account, support and payment-reference records only for as long as needed for the purpose described in this Privacy…

Policy changes

If we change how personal data is handled, we update this Privacy Policy and identify the revised date on the…

Your correction path

You can contact us to ask what account data is held, request a correction or ask about deletion where the…

Privacy Policy questions for your account

These answers address the Privacy Policy searches we hear most often from Indonesian account holders. Each response points you toward a practical account step, device setting or support route, so you can understand how a request is handled before you share more details or continue from the lobby.

It covers account creation details, phone verification, login and device events, cookies, support messages and payment references. It also explains retention, correction requests and contact routes. The same Privacy Policy applies whether you access your account from a mobile browser or desktop where local law permits.

We do not need your DANA or QRIS password to match a cashier event. We may retain a transaction reference, amount status and date so a requested account record can be checked. Never send a wallet password through support when asking about a payment reference.

Phone verification helps connect a sign-in to the correct account and gives us a practical way to investigate an unfamiliar session. It also supports correction requests because we can compare the registered phone number with the account record before making a change.

Use the account support contact path and state whether you want access, correction or deletion of a specific record. Include your registered phone number, the relevant date and a short description. We may request additional matching details before responding to protect your account.

The Privacy Policy applies when you sign in through a mobile browser and move from the account page to the lobby. Cookies or session storage may remember access, while device signals can help identify unusual activity. Clearing browser storage can sign you out.

Retention depends on why a record exists, such as account administration, a DANA or bank transfer status check, a support request, dispute handling or legal duties. When the purpose ends, the record is deleted or placed under restricted handling according to our process.

Yes. Use the signed-in support route when possible and provide the device type, approximate time and registered phone number. Do not send a password. We can explain the related session record and help you review account access under the Privacy Policy.