Reference

sopislot Privacy Policy for Your Account

Your DANA, OVO, GoPay and QRIS details stay tied to the account steps that need them, while our Privacy Policy explains what we collect, why we use it…

Account dataWallet recordsDevice choicesYour privacy requests
sopislot sopislot Privacy Policy for Your Account
PRIVACY HELP PATH

Where To Ask About Your sopislot Data

A direct support path helps you ask about Privacy Policy matters without placing personal details in a public chat. Start from your signed-in account and describe whether your request concerns access, correction, wallet records, device activity or deletion. We may ask for an account step to confirm identity before discussing private data. This keeps a question from being answered against the wrong profile, whether you are checking a QRIS reference or a login record.

Team online

Account support

Use the support route inside your account when you want to ask what personal data we hold or why a verification step appears. Include the account contact detail connected to your request, but do not send a password, one-time code or full wallet credential.

Wallet privacy

For DANA, OVO, GoPay or QRIS questions, tell us the transaction reference and date rather than sharing a screen containing your full balance or secret code. We can use that limited reference to locate the relevant record and explain its privacy handling.

Access request

If you want to correct, receive or remove eligible account data, state the request clearly through the account support path. We check account ownership first, then explain any records that must remain for security, transaction history or a legal duty.

ACCOUNT DATA CARE

Inside Our Privacy Handling Process

Privacy Policy choices affect what happens around login, wallet checks and mobile access, so we describe the working steps rather than using broad promises.

Data we receive

When you open an account, we may receive contact details, verification results, sign-in time, browser or device signals and records linked to your selected wallet route. A QRIS, bank transfer or virtual account reference helps us connect a payment question to the correct account without requesting your secret credential.

Cookie choices

Cookies and similar browser storage can remember a session, preserve a language or device setting and help us identify an interrupted account step. You can manage browser storage through your device settings, although removing it may require you to sign in again before reaching the lobby.

Mobile sessions

Our mobile path does not require a separate application download. Your phone browser may retain a session identifier, screen preference and security signal so the route from login to the lobby remains connected. Clearing browser data removes local storage, not necessarily records already held for the account.

Account protection

We use account checks before exposing private records and may look at sign-in patterns, device changes or repeated verification attempts to spot unusual access. Keep your password and one-time code private; support will not need either one to discuss a Privacy Policy request.

Retention periods

We keep personal and transaction records only for as long as they serve the stated account, security, dispute or legal purpose. A DANA, OVO, GoPay, QRIS or bank transfer reference may remain after a profile request because removing it immediately could prevent a status check.

Changes and contact

If your contact detail changes or you believe a record is inaccurate, contact us through the signed-in support route and name the field that needs attention. We may request an account confirmation before changing it, then explain the outcome and any limit that applies.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the account and wallet questions you are most likely to ask before opening access. We explain the practical route for data requests, browser settings, transaction references and account checks, so you know what to prepare before contacting support. Where a request depends on a legal or security requirement, we will explain that limit rather than asking you to guess.

The sopislot Privacy Policy covers account contact details, verification records, sign-in activity, device signals, cookies and wallet-related references. It also explains how we use those records for account access, transaction checks, security questions, retention and requests to correct, receive or remove eligible data.

A DANA or QRIS reference lets us match a payment-status question with the correct account and date. We use the reference for that operational purpose, not as a request for your password, one-time code or full wallet secret. Send only the details support asks for.

Yes, you can ask for an eligible copy through the signed-in account support route. State that your request concerns the Privacy Policy and identify the account contact detail used at registration. We confirm ownership first and may withhold security secrets or records restricted by law.

Contact support from your account and identify the exact field that appears wrong, such as a contact detail or verification status. We may ask you to complete an account confirmation before making a change, then explain whether the correction is accepted or requires another step.

Yes. The Privacy Policy covers session identifiers, browser storage, device signals and settings that may appear when you use a phone browser. Clearing cookies can sign you out or remove local preferences, but it does not automatically erase account or transaction records held for another purpose.

Retention depends on the purpose and applicable requirement. A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference may remain for security, dispute handling, account history or a legal duty after a profile change. Ask support to explain the category relevant to your request.

Yes. Account access and eligibility depends on local law, and our Privacy Policy is applied where local law permits. If a regional rule changes what we can provide, retain or remove, we will explain the relevant limit through the account support path rather than asking for unnecessary personal data.