Reference

Privacy Policy For Your win39 Account

Our Privacy Policy explains how we handle the details you provide when you open a win39 account, sign in from a phone or desktop, and use DANA, OVO…

Account dataWallet checksCookie choicesContact requests
win39 Privacy Policy For Your win39 Account
CONTACT YOUR WAY

Privacy Questions Reach Our Support

A clear contact path matters when a login record, wallet reference or account detail looks unfamiliar. We ask you to contact our support team from the email or contact route connected with your account whenever possible, so we can check ownership before discussing personal data. You can also include the date, device path and payment reference that caused the question. We use those details to locate the right record without asking you to send a password or wallet PIN.

Team online

Account contact

Send a Privacy Policy request through the contact route linked to your account. Include your account identifier and the change you want us to check; we may ask for phone verification before discussing personal records.

Wallet status

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, share the transaction date and reference rather than your wallet PIN. We compare the event with our account records and explain what can be corrected.

Access support

When sign-in or phone verification stalls, tell us whether you used a mobile browser or desktop browser and which step failed. We use that device context to separate an access issue from a data request.

YOUR RECORDS CONTROL

What We Do With Account Data

We keep this policy practical by connecting each data use to an account action you can recognise.

Account details

When you open an account, we record the details needed to create access and support phone verification. We use those details to identify your account during contact, not to expose them in public areas of the lobby.

Device signals

A sign-in from a mobile browser can create device and session records used to protect account access. If you change to desktop, these records may help us investigate why a verification prompt or login check appeared.

Cookies

We use necessary cookies and similar session tools so the account page can keep you signed in during a visit. Your browser settings can remove or restrict them, although some account steps may then need to be repeated.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can produce references connected with your account. We use these references to check status, resolve mismatches and respond to payment questions.

Account security

We may compare login, phone verification and device events when access looks unusual. We do not ask you to provide a password or wallet PIN in a support message, and you should keep both private.

Retention requests

We keep records for account operation, security checks, disputes and duties that apply where you access the service. You can ask how long a record is kept or request a change; access depends on local law and the record involved.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and wallet questions you may have before opening access or contacting us. We explain what happens during phone verification, why device details can appear in a support check, how payment references are used and how to request a change. If your situation is not covered, contact us with the account detail you can safely share, and we will direct the request through the appropriate path where local law permits.

It covers data connected with opening and using your account, including contact details, phone verification records, login events, device signals, cookies and payment references. It also explains how we use, retain and discuss those records when you contact support about access or wallet status.

Phone verification helps us connect account access with the correct person and reduce mistaken or unusual sign-ins. We may use the verification result when you ask about personal data or a DANA, OVO, GoPay or QRIS reference. Access depends on local law.

Yes. The policy includes transaction references associated with DANA and QRIS, along with OVO, GoPay, bank transfer and virtual account references. We use those records to check status or resolve an account mismatch; we do not ask for your wallet PIN.

You can contact us from the route linked to your account and describe the correction you need. Include an account identifier and the relevant date or verification step. We may confirm ownership before changing records, and the request is handled where local law permits.

Necessary cookies can keep a browser session working while you move through sign-in and account steps. Your browser can restrict or remove cookies, but that may clear session settings and require another login. We use cookie-related records for the stated account and security purposes.

You may ask us which personal records are connected with your account and request a copy where local law permits. Send the request through your account contact route, identify the records you mean, and be ready for an ownership check before we disclose anything.

We retain records for as long as needed to operate account access, investigate security events, resolve payment disputes or meet applicable duties. The period depends on the record and local requirements. Contact us if you want a retention explanation for a specific account detail.