Reference

Privacy Policy For Your sorongtoto Account

Our Privacy Policy explains how we handle the details connected with your sorongtoto account, from phone verification to wallet activity through DANA and QRIS.

Clear data purposesWallet activity recordsMobile account accessRequest-based changes
sorongtoto Privacy Policy For Your sorongtoto Account
CONTACT ROUTES

Ask About Privacy Through Support

A direct support request gives you a practical route for questions about the Privacy Policy, account records, or a wallet reference. Please contact us from the account help path so we can connect the request with the correct profile. Include the email or phone number attached to your account, but never send a password, wallet PIN, or full payment credential. Our team can explain the request process and identify the next step.

Team online

Account help path

Open the help area after signing in and select the privacy question route. We use the account session and your attached phone number to reduce mistaken identity before discussing stored account data.

Payment record query

If your question concerns DANA, OVO, GoPay, QRIS, or a bank transfer reference, send the date and partial reference only. We can trace the record without asking you to disclose a wallet password.

Access concern

For an unfamiliar login or device session, tell us through the same support route and change your account password first. We can help connect the security event with the relevant Privacy Policy request.

DATA PRACTICE

How sorongtoto Handles Policy Requests

We handle privacy requests against the account record rather than treating a general message as proof of identity.

Account data

We may hold your account name, contact detail, phone verification result, login history, and request history. These fields help us provide account access and respond to a Privacy Policy request tied to the correct person.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account record can include a route, amount reference, and status. We do not need your wallet PIN or full banking password to match that activity.

Cookies and sessions

Cookies and session tokens help keep your signed-in path connected while you move from a mobile browser to the lobby. You can clear browser data, although this may sign you out and remove saved session settings.

Device protection

We may record device type, browser version, approximate network details, and sign-in events. These signals help us identify an unusual login before discussing account data or changing a contact detail.

Retention period

We retain account, support, and transaction references only for the period needed for account operation, security checks, dispute handling, and legal duties. When a record is no longer needed, our process removes or separates it.

Change requests

You can ask us to correct inaccurate profile data, explain a stored field, or assess a removal request through support. We may ask for phone verification before making a change that affects account access.

Privacy Policy Answers For Indonesia

The questions below focus on the Privacy Policy choices you are most likely to consider before opening an account from Indonesia. We explain what happens to account, device, cookie, and payment references in plain terms. If your situation is unusual, use the account help path and include only the minimum detail needed to locate your request.

You can read the current Privacy Policy on this page before opening an account. The page explains account data, cookies, device signals, payment references, retention, and request routes. We may update the wording when our data practice changes, so check this page again after a policy notice.

It covers details connected with your account, including contact data, phone verification, login events, support messages, device signals, cookies, and payment references. A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference can be used to trace status without storing your wallet password.

Phone verification helps connect a request to the correct account before we discuss stored details or change access data. It also supports account protection when a new device or unusual login appears. We will not ask you to send a password or wallet PIN through support.

Yes. Send a correction request through the signed-in account help path and identify the field that needs changing. We may ask for phone verification before editing contact or access data. We assess removal requests against account operation, security needs, and duties that apply where local law permits.

Yes. The Privacy Policy covers cookies and session tokens used when you sign in from a mobile browser. They help keep your account path connected while you open the lobby. Clearing browser data can end the session, so you may need to verify your account again.

Use the account help path and provide the transaction date, payment route, and partial reference. For DANA or QRIS, we can match the status without a wallet password. Do not send full card, bank, wallet, or login credentials in a privacy request.

Yes. Access and eligibility depend on local law. Our Privacy Policy explains how we handle data for an account request, but it does not change the legal rules that apply to your location. If access is not permitted, do not attempt to bypass a local restriction.