Reference

Open sgm win Privacy Policy Details

Our Privacy Policy explains how we collect, use and protect the account details behind your sgm win access, including phone verification, wallet status and device sessions.

Account dataWallet recordsDevice sessionsCookie choices
sgm win Open sgm win Privacy Policy Details
CONTACT ROUTES

Reach Us About Privacy Policy

A clear contact route helps you act on the Privacy Policy instead of searching through account screens. When you ask about personal data, include the phone number linked to your account and a short description of the request, but never send a password or full wallet credentials. We use the account help path for identity checks, payment receipt questions and requests to correct details. If you are checking access from Semarang or another Indonesian location, tell us the device path and the page where the issue appeared.

Team online

Account help

Use the account help path when you want to ask what personal details are linked to your sign-in. We may request a phone verification step before discussing account-specific data, so the request is connected to the right account rather than a random message.

Wallet records

For a DANA, OVO, GoPay or QRIS record, include the payment name, date and receipt reference. We can use those details to locate the relevant status without asking you to share a wallet PIN, password or complete payment credential.

Change request

Ask us to correct an account detail through the same support route used for login help. We review the request against your verified account data, explain any missing step, and confirm whether the requested change can be applied under local law.

DATA PRACTICES

Explore Our Privacy Handling Steps

We treat privacy as an operating process tied to sign-in, wallet reconciliation and account support.

Account details

We collect details needed to create and maintain your account, including contact data and the phone verification step before access. These details help us identify the account during support conversations and distinguish your request from another person using the same device.

Payment matching

A DANA, OVO, GoPay or QRIS reference can be used to match a cashier event with your account. Bank transfer and virtual account entries may also be retained for reconciliation, receipt checks and answering a status question you send to support.

Cookies

Cookies and similar device records can remember a session, support security checks and help the account path load correctly. You can manage cookie settings through your browser, although changing them may affect sign-in continuity or parts of the account page.

Device security

We may record device type, browser details, session time and technical signals connected with account access. These entries help us notice unusual sign-in activity, including a change from a phone to desktop, without treating the device itself as your identity.

Retention period

We retain personal and transaction records only for the period needed for the purpose described in the Privacy Policy, account support, security checks or applicable legal duties. When a record is no longer needed, our handling process calls for deletion or a suitable restriction.

Your request

You can contact us to ask what account data we hold, request a correction, or ask how a wallet or device entry was used. We may verify your identity first, then explain the available action and any limit required by local law.

Check Privacy Policy Answers Before Access

These Privacy Policy answers address the practical searches you may make before opening an account or asking about a wallet record. We focus on account access, Indonesian payment references, cookies, device sessions and contact requests so you can understand the next step without reading unrelated platform material. Where a question depends on eligibility or location, the answer remains subject to local law and applies where local law permits.

It covers account details, phone verification, payment references, device and browser records, cookies, support requests, retention and security handling. It also explains how you can ask about your data or request a correction through the account help path.

Phone verification helps connect an account request with the person seeking access and supports account recovery or data questions. We may use that step before discussing personal details, wallet records or a requested change with you.

Yes. A DANA or QRIS reference may be handled as a transaction record so we can match a cashier event, check a receipt or answer a status request. Never send us your wallet PIN or complete payment credential.

You can ask for a correction through account help. Include the phone number linked to your account and describe the detail that appears wrong. We may verify your identity, then confirm the correction or explain why an exception applies.

Cookies can preserve a sign-in session and support security checks when you move from your phone browser to the lobby. Browser settings let you manage them, but removing cookies may require you to complete account access steps again.

We keep personal, device and payment records for the period needed for their stated purpose, account support, security checks or applicable legal duties. The policy explains the retention approach, including deletion or restriction when a record is no longer needed.

The policy is available for you to read, while service access or eligibility depends on local law. We apply the described handling where local law permits, and you can contact account help if your location creates a specific question.