Reference

Privacy Policy For Your Account

mposurga login Privacy Policy explains how we use the details you provide for account creation, phone verification, wallet status and access to our lobby.

Account detailsWallet recordsDevice accessPolicy requests
Browse Our Lobby Read FAQ
mposurga login Privacy Policy For Your Account
HELP WITH REQUESTS

Contact Paths For Privacy Questions

A clear support route matters when your Privacy Policy question concerns a real account event. We ask you to send enough detail for us to locate the record without sharing a wallet password or full payment credential. If your question follows a phone verification step, sign-in attempt or receipt status, mention that event and the date shown in your account. We then use the account help path to identify the request, protect the account and provide a relevant response.

Team online

Account help path

Use the support route connected to your account when you need a copy of your stored details, a correction or an explanation of a Privacy Policy decision. We may ask you to confirm the account phone number before discussing private records.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account references, include the payment rail and the receipt status shown to you. We use those details to locate the right event without requesting your wallet PIN or password.

Access concern

If a phone verification or mobile sign-in issue affects your policy request, tell us which device path you used and what appeared on screen. Account access depends on local law, and we handle eligibility questions through the same protected route.

DATA HANDLING

How We Apply Privacy Controls

We apply this Privacy Policy to the account actions you can identify: registration details, phone confirmation, sign-in sessions and payment references.

Account details

We use the details supplied during account creation and the phone verification result to identify your account and respond to account requests. Keep your sign-in details private; our support route will not ask you to disclose a wallet PIN or password.

Payment references

A DANA, OVO, GoPay or QRIS record can show a rail, reference and status connected with your account. Bank transfer and virtual account records follow the same purpose. These references help us reconcile an event without storing your wallet secret.

Device sessions

When you sign in through a phone or desktop browser, session and device signals can help us identify unusual access. We use them for account protection and request handling, not to ask for unrelated content from your device.

Cookies

Cookies and similar session tools can keep the account path working, remember a sign-in state and help us understand whether a request belongs to the active session. You can manage browser cookie settings, although some account steps may then need to be repeated.

Retention period

We keep account, security and payment-reference records for as long as needed to provide the requested service, handle disputes or meet applicable duties. When a record is no longer needed, we remove it or separate it from direct account use.

Change request

Ask us to correct eligible details, explain a data use or remove a record through the protected account support path. Include your account phone number and request type; we may verify ownership before making a change.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the searches we expect before an account is opened or when a wallet event needs clarification. We keep each answer tied to an identifiable mposurga login step, such as phone verification, mobile sign-in or a DANA and QRIS reference. If your situation is not covered, use the account support path with the smallest useful set of details. Do not send passwords, wallet PINs or full payment credentials in a request.

It covers account details, phone verification, sign-in sessions, cookies, device signals and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, request handling and how to contact us about eligible corrections or removal.

We use the verification result to connect the account to the phone number supplied during registration, protect sign-in access and identify the correct account when you request help. We do not need your wallet PIN or password to handle a Privacy Policy request.

No. A DANA or QRIS record may contain a payment rail, reference and status needed to match an account event, but your wallet password and PIN should remain private with the wallet provider. Do not include those secrets in support messages.

Use the protected account support path and state whether the request concerns your account details, phone verification result, device session or payment reference. Include the account phone number and relevant event date. We may confirm account ownership before changing the record.

We retain account, security and payment-reference records only while they support account service, dispute handling or applicable duties. The period can differ by record type. When continued retention is not needed, we remove the record or separate it from direct account use.

You can request removal of eligible details through the account support path. We first identify the account and assess whether a record is still needed for security, dispute handling or legal duties. If removal is allowed, we apply it to the relevant stored details.

The policy is written for supported Indonesia regions, but access and eligibility depends on local law or where local law permits. If your account request concerns a location, device session or wallet event, contact support with that specific context rather than sending private credentials.

Related Pages

mposurga login Indonesia skybola Account information Sic Bo mposurga login Casino