Reference

sohoslot Privacy Policy for Your Indonesia Account

Our sohoslot Privacy Policy shows what account, device and wallet details we handle when you access the lobby, including payment references from DANA, OVO, GoPay and QRIS.

Account dataWallet referencesDevice choicesYour privacy rights
sohoslot sohoslot Privacy Policy for Your Indonesia Account
PRIVACY HELP PATH

Get Privacy Help Beside Account Access

A privacy request should be easy to send, even when your question starts with a wallet receipt or a sign-in concern.

Account support path Open the support path from your account when you need a copy, correction or…
Payment receipt check For DANA, OVO, GoPay or QRIS questions, share the receipt reference and status only.
Access concern If a phone, browser or login session looks unfamiliar, contact us through account support…
RECORDS AND CONTROL

What sohoslot Records and Protects

Privacy handling follows the account actions you take, rather than a broad collection of unrelated details.

Account details

We may hold your phone number, verification result and account identifiers so we can sign you in, connect a support request and distinguish your records from another account.

Device signals

Browser type, device details, approximate network location and login time can support access checks. These signals help us investigate an unfamiliar mobile session without reading private device content.

Cookie choices

Cookies can keep a session active and remember selected settings. You can adjust browser cookie controls, although refusing necessary cookies may affect account access and privacy request routing.

Payment separation

For DANA, OVO, GoPay, QRIS and bank transfer records, we use transaction references and status details. We do not ask you to provide a wallet password through support.

Retention handling

We retain account and request records only for operational, dispute and legal needs that apply to the service. When a record is no longer needed, our handling process removes it or separates it.

Change requests

You can ask us to correct inaccurate account data or explain its use through account support. Include enough account detail to verify your request, but never include your password.

Privacy Policy Answers for Your Account

These Privacy Policy answers cover the questions we expect you to ask before opening an account or connecting a local wallet. We keep the process tied to identifiable account steps, from phone verification to a payment receipt check. If your situation is not covered, send the request through account support and describe the record you want us to locate.

It covers account details, phone verification, device signals, cookies, payment references, support requests, retention and the steps available to ask for access or correction of your personal data.

We use your phone number for account identification and clear phone verification before account access. It also helps us connect a privacy request to the correct record when you contact support.

No. We handle transaction references and status details for DANA, OVO, GoPay, QRIS, bank transfer or virtual account processing. Do not send wallet passwords or full private credentials to support.

Yes. Send a correction request through account support with your registered phone number, the inaccurate field and a short explanation. We may verify account ownership before changing the record.

Use the account support path and ask for a personal data copy under the Privacy Policy. Provide your registered phone number and request details; we will assess the request under applicable law.

Yes. Cookies may maintain your mobile session and remember settings. Your browser controls can limit them, but necessary cookie restrictions may prevent sign-in or the support path from working correctly.

Yes. Account access and eligibility depend on local law. We apply the policy to website handling where local law permits, including access from Indonesian locations such as Surabaya and Bandung.