Reference

Privacy Policy for Your Indonesia Account

Our pronet77 Privacy Policy shows what we collect when you open an account, sign in from a phone, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesPrivacy requests
pronet77 Privacy Policy for Your Indonesia Account
CONTACT ROUTES

Ask About Data Through Account Support

A clear support route helps when your Privacy Policy question concerns a phone number, wallet reference or sign-in record. Start from the account help path and include the email or phone attached to your account, plus the subject of your request. For your safety, do not send a password, one-time code or full wallet credential. We use the details you provide only to locate the relevant record and respond to the request.

Team online

Account data

Ask us to confirm the account details connected with your phone or email. We may request an account step or verification response before discussing personal records.

Wallet status

If a DANA, OVO, GoPay or QRIS reference looks wrong, share the transaction date and visible status. We can check the account record without asking for your wallet password.

Privacy request

Use the support contact shown in your account help path for access, correction or deletion requests. We will explain any identity check and any record that must remain stored.

DATA PRACTICE

Data Handling Behind Your Account Path

We keep our Privacy Policy practical by linking each data use to an account action: opening access, checking a login, recording a wallet event or answering your request.

Account creation

When you open an account, we use your submitted contact details and clear phone verification step to create access. We do not need your wallet password to connect a payment reference.

Cookies and sessions

Cookies can remember a sign-in session, language setting and security preference. Your browser controls cookie removal, although clearing required cookies may interrupt the account path.

Device signals

A phone or desktop may send browser type, session time and security signals. We use these details to identify unusual access, not to read private files stored on your device.

Wallet evidence

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can appear in account records. These entries help match a payment status without storing the wallet credential itself.

Retention period

We retain account, payment and security records only as long as needed for the stated purpose or an applicable legal requirement. A deletion request may not remove required transaction evidence.

Change requests

You can ask us to access or correct eligible data through the account support route. Include the relevant account contact and request type so we can complete the identity check.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the data connected with your account, local wallet records, phone access, cookies, retention and the steps for contacting us. If your situation is different, use the account support path and describe the record you want us to check.

It covers account details, phone verification, device and session signals, cookies, support messages and payment references. The Privacy Policy also explains why we use those records, how long they may remain, and how you can request access or correction.

Yes. The Privacy Policy covers DANA and QRIS references shown in your account, as well as OVO, GoPay, bank transfer and virtual account status. We use those references to match a payment event, while wallet credentials stay with the payment service.

Use the support contact in your account help path and state that you want an account data request. Include the phone or email attached to the account. We may confirm your identity before sharing records connected with your account.

You can request a correction when an eligible account detail is inaccurate, and you can ask about deletion. We first confirm the account holder and then explain whether a transaction, security or legal record must remain stored.

Device type, browser signals and session timing help us spot unusual sign-in activity and keep your account path consistent between phone and desktop. We do not use these signals to access private files or your device content.

Cookies can retain a session, language setting or security preference. Your browser can remove or restrict them. Required cookies may be needed for account access, while clearing them can sign you out or make a security check appear again.

Yes. Data access, correction and deletion depend on local law and the record involved. Where local law permits, we will explain the available request path, any identity check and the reason a required record cannot be removed.