Reference

mposurgaslot Privacy Policy for Wallet Data

mposurgaslot Privacy Policy explains what we collect when you open an account, sign in on a phone, or use DANA, OVO, GoPay and QRIS.

Account recordsWallet activityDevice accessPolicy requests
mposurgaslot mposurgaslot Privacy Policy for Wallet Data
POLICY SUPPORT

Get Privacy Help Beside Cashier

A clear contact path helps when you need an answer about personal data rather than a game or wallet result. From your account area, keep the relevant email, phone number, payment reference, or device detail ready so we can locate the correct record. We can explain a Privacy Policy request, clarify a status check, or route an access question for review by the appropriate support contact.

Team online

Account contact

Use the contact path connected to your account when asking what personal details we hold. Include your registered phone number and the subject of your Privacy Policy request so we can identify the correct account record.

Wallet reference

For a DANA, OVO, GoPay or QRIS question, provide the payment reference and approximate account step. This lets us separate wallet details from unrelated device records and explain what the Privacy Policy permits us to check.

Access concern

When a login or device session looks unfamiliar, contact us through the account support path and describe the phone or browser involved. We can direct the security request and explain the data action available under this Privacy Policy.

DATA PRACTICE

Security From Login To Starlight Spins

We apply this Privacy Policy to the practical moments you experience, from phone verification through a mobile session and an account request.

Account data

When you open an account, we use the details you submit and the phone verification step to create an access record. The Privacy Policy explains why those details are needed and how an account request can be sent to us.

Cookie controls

Cookies and similar session tools can keep a phone or desktop browser connected while you move between account pages. We use them for session continuity and site operation, and you can ask our support contact how a cookie-related request is handled.

Device signals

A mobile or desktop sign-in may create device and connection data linked to an access event. This helps us examine an unfamiliar session without treating your device signal as public profile data.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can be attached to a cashier event. We use that connection to trace a status question, while keeping payment data within the account handling process.

Retention requests

We retain records only for the operational, security, account and legal purposes described by this Privacy Policy. Ask us which category applies to a record, whether a correction is possible, and what request path applies where local law permits.

Privacy contact

Send a specific request through the account support route, naming the data category and the account step involved. We may need account details to verify the request before explaining access, correction, deletion or retention options.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the records you are most likely to ask about before opening or using an account. We focus on account access, wallet references, mobile sessions, cookies, retention and the contact route. Where a request depends on a legal condition, we will explain the applicable path rather than promise an action that cannot be provided.

It covers account details, phone verification, sign-in activity, device and connection signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account use. It also explains purposes, retention, request handling and access conditions.

We use your phone number as part of the account access and verification step. It helps connect your account request to the correct record and supports security checks when a sign-in or wallet status needs attention. The Privacy Policy describes its handling.

Yes. A DANA or QRIS reference can be connected to the relevant cashier event so we can check account status and answer a payment question. OVO, GoPay, bank transfer and virtual account references follow the same account-linked handling.

A phone or desktop browser may provide device and connection signals linked to a sign-in session. We use these details to maintain access and investigate unfamiliar activity. They are handled under this Privacy Policy and are not presented as public account details.

Use the account support contact and state whether you want access to a record or a correction. Include your registered phone number and the relevant category, such as account, device, cookie, wallet or support data, so we can verify and route the request.

Retention depends on the purpose of the record, including account operation, security, payment tracing and applicable legal needs. The Privacy Policy does not treat every record alike. Ask us about a specific category and we will explain the available retention request path.

Yes. Use the same account contact route and identify your location only when it is relevant to the request. Access or a particular data action depends on local law, so we will explain what can be handled where local law permits.