Reference

37win Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open a 37win account, use the mobile lobby, or connect DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice sessionsCookie choices
37win 37win Privacy Policy for Your Account
CONTACT PATHS

Get Privacy Policy Help From Your Account

A clear contact path helps when you want to ask about the Privacy Policy, correct account details or understand a wallet record. Start from the support route connected to your account so we can match your request with the correct phone verification and payment reference. If access is unavailable, include the email or phone detail linked to the account without sending a password. We use the information needed to identify the request, then explain the next step in plain English. Requests remain subject to local law and account-security checks.

Team online

Account request

Use the account support path to ask what personal details we hold or to request a correction. We may ask for the phone verification detail linked to your account before discussing records connected with DANA, OVO or another wallet.

Payment record

For a QRIS, bank transfer or virtual account question, provide the transaction reference and approximate date rather than a password or full security code. This lets us locate the relevant payment record while limiting unrelated account details.

Access concern

If your device shows an unfamiliar session or your login stalls, contact us through the account help route and describe the device path used. We can check security events and guide the next verification step without asking you to disclose secret credentials.

HANDLING DETAILS

Six Practical Privacy Controls at 37win

We keep the Privacy Policy practical by linking each data use to an account action you recognise.

Account creation

When you open an account, we collect the details required for the account path and phone verification. We use those details to connect your sign-in with the correct wallet status and to respond to a Privacy Policy request about your account.

Session protection

A phone, browser or device signal may be recorded when you sign in from mobile or desktop. We compare these signals with account activity to identify an unusual session, while keeping your password and private security codes out of support messages.

Cookie controls

Cookies can keep the login path working and remember necessary page settings. Your browser can restrict or remove them, although changing those settings may affect account access. The Privacy Policy explains which cookie use supports a requested function.

Wallet matching

Payment references from DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity help us match a status to your account. We do not need your wallet password for this check, and support should receive only the reference needed.

Retention periods

We retain account, device and transaction records for the period needed to operate the account, investigate security events, handle disputes or meet legal duties. When a record no longer serves one of those purposes, our handling follows the applicable local requirement.

Change requests

You can ask us to correct inaccurate details, explain how a record is used or request removal where local law permits. Include your account contact detail and the precise request; we may verify identity before making any change.

Privacy Policy Questions About 37win

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. We describe the practical route for data requests, device concerns and wallet records without asking you to expose private credentials. If your situation depends on a local requirement, contact us with the minimum account detail needed to identify your request.

The 37win Privacy Policy covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references. It applies when you access the lobby, use mobile or desktop, connect DANA, OVO, GoPay or QRIS, and request help with your personal data.

We use phone verification to connect you with the correct account and reduce mistaken or unauthorised access. It also helps us locate a data request or wallet status without asking for your password. Any handling remains subject to local law and the Privacy Policy.

Yes. The Privacy Policy includes transaction references and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These records help us match a payment event to your account; do not send wallet passwords or private security codes.

You can contact us through the account support path and identify the detail you believe is inaccurate. Include the phone or email connected with your account, explain the correction clearly and complete any identity check we request before the record is changed.

Cookies may support sign-in, necessary page functions and selected settings when you use the mobile lobby. Your browser can restrict or clear cookies, but that may interrupt account access. The Privacy Policy explains the purpose of cookie use and the available browser control.

We keep records for the period needed to operate your account, protect sessions, resolve payment questions, handle disputes or meet legal duties. The exact period can depend on the record and local requirement. You can ask support to explain retention for a specific request.

Send a clear removal request through the account support path and include the account contact detail needed to locate it. We verify the request before acting, and removal may be limited where a record is needed for security, dispute handling or legal duties.