Reference

How pronet33 Handles Your Privacy Policy

Your pronet33 Privacy Policy gives you a clear route for understanding account details, wallet records and access choices before you open the lobby.

Account data explainedWallet records identifiedMobile access coveredContact route included

Explore Our Lobby Read FAQ

Privacy Policy For DANA And QRIS

pronet33 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy describes the account details we receive when you create an account, complete phone verification and enter the lobby. It covers payment references from DANA, OVO, GoPay and QRIS, including status details needed to match a wallet action with your account. Bank transfer and

1
virtual account references may also appear when you choose BCA, BRI, Mandiri or BNI routes. We use these records to confirm account activity, investigate a status mismatch and protect access. We do not describe access as available everywhere; eligibility depends on local law. If you are
2
in Denpasar or elsewhere in Indonesia, read the current policy before proceeding and use our contact path for a specific question.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Get Privacy Policy Help From Account Support

A clear support route helps you ask about Privacy Policy details without posting account data in a public message.

Policy questions Send a Privacy Policy question through the account contact path and mention the section or data type involved. We can explain how account, cookie or wallet records are handled without asking you to reveal a password.

Wallet record check If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, include the date, amount reference and visible status only. We use those details to locate the relevant account event while keeping your wallet credentials private.

Access request For a copy, correction or removal request, contact us from the email or account route connected with your profile. We may ask for an account step to confirm that the request comes from you.

DATA HANDLING

Your Data Path From Login To Lobby

We keep the Privacy Policy practical by connecting each data point to an account action you can recognise.

Account details

We handle the details you provide for account creation and phone verification so we can connect the correct profile to its access request. Check your account details before asking us to change a name, phone number or contact route.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference records. We use those references to match status and investigate an account question, not to request your wallet password or security code.

Cookies and sessions

Cookies can support sign-in continuity, language settings and session controls on your browser. You can review browser cookie controls on Android or desktop, though disabling them may affect the account path described in the Privacy Policy.

Account security

Phone verification is part of the access path before account details are shown. Keep your password and verification code private, and contact us through the account route if you see a login or wallet status you do not recognise.

Retention timing

We retain account and payment references only for the period needed for the stated account, security and legal purposes. A retention question should include your account contact route so we can explain what record is involved and its current status.

Change requests

You can ask us to correct account details, explain a data category or address a permitted removal request. We first check the request against your profile, then reply through the contact route connected with that account.

Privacy Policy Questions About Your Account Data

These Privacy Policy answers focus on the account steps and local wallet records you are most likely to ask about before opening or accessing pronet33. If your situation is not covered, use the account contact route and share only the minimum details needed to identify the request.

The Privacy Policy covers account details, phone verification, browser cookies, session activity, payment references and requests concerning access or correction. It also explains how DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may relate to your account activity.

Phone verification helps connect an account access request with the correct profile and reduces the chance of another person viewing account details. Keep the code private. If verification fails, use the account support route rather than sending the code in a public message.

Yes. The Privacy Policy covers payment references and status details created when you use DANA or QRIS, as well as OVO and GoPay. These records help us match an account event or investigate a mismatch without requesting your wallet password.

Contact us through the email or account route connected with your profile and state whether you want a copy, correction or explanation. Include only the relevant account detail. We may verify your identity before handling the request, and access depends on local law.

The same Privacy Policy applies when you sign in through an Android browser, although cookie controls and session prompts may look different from desktop. Browser settings can affect continuity, so check them before asking support about repeated sign-in or access prompts.

We keep account, security and payment references for the period needed for the purpose described in the Privacy Policy and any applicable legal requirement. For a record-specific question, contact us from the connected account route so we can explain the relevant retention status.

Yes. Use the account contact path and provide the visible date, reference and status for the DANA, OVO, GoPay or QRIS event. Do not send a password, verification code or full wallet credentials. We will use the limited details to locate the account record.

How pronet33 Handles Your Privacy Policy

Get Privacy Policy Help From Account Support

Your Data Path From Login To Lobby

Account details

Payment references

Cookies and sessions

Account security

Retention timing

Change requests

Privacy Policy Questions About Your Account Data

01 What does the pronet33 Privacy Policy cover?

02 Why does pronet33 need phone verification?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How can I request a copy or correction of my data?

05 How does the policy apply on an Android browser?

06 How long does pronet33 keep account information?

07 Can I ask about a wallet record I do not recognise?

Related Pages