Reference

Privacy Policy for Your Account Data

pangkalan toto Privacy Policy shows what we collect when you create an account, verify your phone, use DANA or QRIS, and move through the lobby from a mobile…

Clear data purposesWallet record detailCookie choicesAccount request path
pangkalan toto Privacy Policy for Your Account Data
HELP PATHS

Get Clear Answers About Your Records

A direct account help path lets you ask how we use a phone number, device signal, cookie, or wallet reference. Open the support link shown in your account area and include the account step or payment receipt involved; this helps us locate the right record without asking you to post sensitive details in a public channel. Where local law permits, we can also explain an access question before you continue.

Team online

Account request

Use the support link inside your account area to ask what personal details are connected with your account and which policy purpose applies to that record.

Wallet status

For a DANA, OVO, GoPay, or QRIS reference, share the receipt code through the account help path so we can check the stored status without exposing wallet credentials.

Access concern

If a login or phone verification step stalls, tell us the device path and time of the attempt. We use those details to address access while limiting unnecessary collection.

DATA PRACTICE

Protect Your Login And Wallet Trail

We handle Privacy Policy requests through the account context that produced the record, rather than treating every browser visit as a complete identity.

Account details

We use the name, contact details, and phone verification you provide to create and protect your account. We do not need you to place private account details in a public support message.

Device signals

Browser type, device path, login time, and security events can help us identify unusual access. These signals support account protection and are considered alongside your verification step.

Cookie control

Cookies can remember the browser path and support security checks. Your browser settings let you remove or restrict them, although some account access steps may then need to run again.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity may create a reference or status record. We use it to match a receipt and resolve the related account question.

Retention purpose

We keep records only while their account, security, support, or legal purpose requires them. Ask through the account help path if you want the reason for a particular retention period.

Change request

You can ask us to correct an inaccurate contact detail or clarify how a record is used. Include the relevant account step, and we will use that context to assess the request.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we expect before you open an account, especially questions about phone verification, wallet records, cookies, access, and retention. Each answer points you back to a practical account step, so you can decide what to provide and how to contact us without guessing which record is involved.

It covers account details, phone verification, device and browser signals, cookies, lobby activity, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or a virtual account. We use those records for account access, security, support, and policy-related requests.

Phone verification helps connect an account request with the person trying to access it and helps us investigate an unusual login. We use the verification result for account security and do not ask you to send a phone code through a public support message.

Yes. The policy covers payment references and wallet status connected with DANA, OVO, GoPay, QRIS, bank transfer, and virtual account steps. A receipt code may help us trace a status question, while wallet passwords, PINs, and private access codes should remain with you.

Cookies can support the mobile browser path, remember a session choice, and help with security checks. You can remove or restrict them in your browser settings. After that change, some login or phone verification steps may need to run again.

Yes, you can use the support link in your account area to request a correction or ask how a detail is used. Mention the affected account step, such as phone verification or a wallet receipt, so we can locate the correct record.

Retention depends on the purpose of each record, such as account security, receipt matching, support, or a local legal need. The period may differ between a wallet reference and a login event. Ask through the account help path for a record-specific explanation.

Access depends on local law. Our Privacy Policy does not change that condition, and we apply account and verification steps according to the location and circumstances relevant to your request. Where local law permits, support can explain the data step involved.