Reference

sorong toto Privacy Policy for Your Account

Our Privacy Policy explains how sorong toto handles the account details you submit, device signals used during login, and wallet records linked to DANA, OVO, GoPay or QRIS.

Account clarityWallet record controlDevice-aware accessClear contact path
sorong toto sorong toto Privacy Policy for Your Account
CONTACT ROUTES

Contact Us About Stored Account Details

A direct support request gives you a practical route for questions about this Privacy Policy.

Policy request Ask us to explain a data category, processing purpose, or retention point. Include your account phone number only through the account support route, not in an open message.
Correction request If your phone, name, or wallet reference is inaccurate, identify the affected account step. We may ask for account verification before changing a stored record.
Access concern If login or phone verification appears unusual, contact support with the time and device path. We use those details to check security events without exposing another account.
DATA HANDLING

Explore How We Handle Your Privacy

Our Privacy Policy separates account operation from data control. We limit internal access to records needed for account service, wallet status checks, security review, or legal duties.

Collected details

We handle details you provide during account opening, including your phone number and credentials, plus payment references from DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account.

Cookie controls

Cookies and similar device signals can keep a session working, remember selected settings, and help identify suspicious access. Your browser settings can restrict cookies, though some account steps may change.

Account security

Phone verification and sign-in event records help us check whether an account request matches its normal device path. Never send a password or wallet PIN in a support message.

Retention practice

We retain account, support, and payment-reference records only for the period needed for the stated service, security checks, dispute handling, or legal duties, then remove or restrict them when appropriate.

Request a change

You can ask us to correct account details, explain a processing purpose, or provide the available access response. We may verify ownership before disclosing or changing personal records.

Policy contact

For a Privacy Policy question, include the account phone number, relevant date, and affected step through our support route. This helps us distinguish a login matter from a wallet record.

Browse Answers About Privacy Policy

These Privacy Policy answers cover the questions you may have before opening an account or sending a support request. We focus on account records, device behaviour, wallet references, correction requests, and the access wording that applies in Indonesia. If your case is unusual, contact us with the smallest useful set of details.

It covers account details, phone verification, device and sign-in records, support messages, cookies, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account.

We use your phone number for account identification, phone verification, login support, and security checks. It also helps us match a wallet or payment reference with the correct account request.

Yes. The Privacy Policy covers DANA, OVO, GoPay, and QRIS references submitted during account or wallet steps, along with bank transfer and virtual account records used to identify a request.

Send a support request naming the account step and the record you want checked. We may confirm account ownership before explaining stored details, supplying an available access response, or making a correction.

We retain records for the period needed for account service, security checks, dispute handling, or legal duties. When a record is no longer needed, we remove or restrict it where appropriate.

The policy can cover browser type, device identifiers, approximate access time, cookie signals, and sign-in events. These details help keep sessions working and identify unusual access without revealing your password.

Yes. Use the support route and state that your request concerns the Privacy Policy. We will explain the relevant process, any ownership check, and the response available where local law permits.