Reference

netwin22 Privacy Policy For Your Account

netwin22 Privacy Policy explains how we collect, use and protect details linked to your account, wallet checks and mobile access.

Account dataCookie choicesLocal access
netwin22 netwin22 Privacy Policy For Your Account
CONTACT ROUTES

Wallet Status Help And Privacy Requests

A clear contact route matters when you want to understand a record rather than guess what happened. We connect privacy questions with the same account help path used for login or wallet status issues, so you can identify your account once and avoid sending sensitive details across unrelated channels. Use the help link beside the cashier path and include only the details needed to locate your request.

Team online

Account data request

Ask for the account details we hold by using the linked help path. Include your registered phone number and request type, but never send your password, wallet PIN or full payment credentials.

Payment reference check

If a DANA, OVO, GoPay or QRIS reference appears in your account history, we can use that reference to investigate a status question without asking for your wallet login details.

Login and device concern

Tell us when an unfamiliar device, browser session or account change appears. We can use the security event and your account step to direct the privacy request to the right support queue.

DATA HANDLING

Mobile Login And Account Security

We handle privacy through practical account controls rather than vague promises. Your account is the reference point for data requests, while device signals help us spot unusual access on mobile or desktop.

What we collect

We collect details needed for an account, such as your phone number, login activity, verification state, payment references and support messages. Device and browser signals help connect a request to the correct account.

Why we use data

We use account data to provide access, confirm payment status, answer support requests, detect suspicious sessions and meet applicable legal duties. We do not use wallet credentials to operate your DANA or QRIS account.

Cookies on mobile

Cookies can keep your session active, remember selected settings and measure basic page performance. You can manage cookie controls in your browser, although changing them may require another login on your device.

Account protection

Phone verification and session checks help protect the account before access is granted. If you change device or browser, we may ask for an account step again instead of relying on an old session.

How long we retain

We retain records for as long as needed for account operation, payment matching, security checks, support history and legal duties. When a record is no longer needed, our process removes or anonymises it.

Requesting a change

You can ask us to access, correct, restrict or delete eligible account data through support. We may verify ownership using your registered phone number before changing records or disclosing account details.

Privacy Policy Questions For netwin22

These Privacy Policy answers address the searches we hear most often before an account is opened. They explain what sits behind wallet references, cookies, device checks and account requests, while keeping the steps practical for Indonesian access. If your case is specific, use the privacy contact route and tell us which record or account step you want us to check.

The netwin22 Privacy Policy covers account details, phone verification, device signals, cookies, payment references, support messages, security events and the retention of those records for stated operational or legal purposes.

No. We may retain a transaction reference, amount or status needed to match an account event, but the Privacy Policy does not require your DANA, OVO, GoPay or QRIS wallet password.

Phone verification helps connect the request to the account owner and reduces mistaken access. The Privacy Policy treats verification records as account security data and explains their use for access and support.

Yes, where local law permits. Send a request through the linked support path with your registered phone number and the records you want. We may verify ownership before sending account data.

Cookies can retain a session, save selected settings and measure basic page performance. You can adjust browser controls, but disabling some cookies may end a session or require another login.

Use the privacy contact route and name the detail that needs correction. We may ask for a phone verification step, then update eligible account records after checking the request.

Yes. Account access and data rights depend on local law. Where local law permits, we process details for account operation, payment matching, security, support and applicable legal duties.