Reference

peci toto Privacy Policy for Indonesia Accounts

Our Privacy Policy explains how peci toto handles the details connected with your account, device, cookies and wallet activity when you open the lobby from Indonesia.

Account dataCookie choicesWallet recordsAccess depends on local law
peci toto peci toto Privacy Policy for Indonesia Accounts
HELP WITH PRIVACY

Get Clear Answers Through Your Account Path

A direct support route helps when your privacy question is tied to a real account step, such as phone verification, a wallet receipt or a browser…

Account help Use the account help route for a Privacy Policy question about phone verification, login…
Wallet receipt path When a DANA, OVO, GoPay or QRIS reference appears in a privacy request, share…
Device access help If a cookie choice or phone-browser session affects your account request, tell us whether…
DATA HANDLING

What We Do With Your Privacy Choices

We keep this Privacy Policy practical by connecting each data category with a clear account purpose.

Account details

We use the details linked to your account to create access, complete phone verification and respond to account-specific requests. If you ask about a record, we may need to confirm that you control the account before discussing or changing personal details.

Cookies and device signals

Cookies can remember a session choice, while device and browser signals help us recognise unusual access patterns. You can manage browser cookie settings on your phone or desktop, although changing them may require you to repeat login or verification steps.

Wallet and cashier records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps connect a payment status with the correct account. We use the reference for matching, support and security checks, not as a reason to request your wallet PIN.

Account security

Phone verification and login records help us examine access that does not match your usual account path. Keep your password and wallet credentials private; our support route does not need those secrets to process a Privacy Policy request.

Retention approach

We retain account, security and cashier records only for the operational, dispute and legal purposes that apply to them. Retention can differ by record type, so a request should name the account detail or payment reference you want us to check.

Requests and corrections

You can ask us to explain, correct or remove eligible personal data through the account help route. State the request clearly, identify the account contact detail and expect an account-control check before we disclose, amend or act on the record.

Privacy Policy Answers Before Account Access

These Privacy Policy answers address the searches we hear most often from Indonesian customers before they open an account. They explain why a payment reference, device path or phone verification record may appear in our systems, and how to ask for help without exposing sensitive credentials. For a request tied to a particular account, use the account help route so we can check the correct record while access depends on local law.

It covers account details, phone verification, device and browser signals, cookies, cashier references and support requests connected with your account. It also explains why DANA, OVO, GoPay, QRIS, bank transfer or virtual account records may be used to match a payment status.

Phone verification helps connect an access request with the correct account and supports checks when login activity looks unusual. We may use that record when you ask about account access, but you should not send a password, wallet PIN or complete payment credential.

Yes. The policy covers payment references created when you use DANA, QRIS, OVO, GoPay, bank transfer or a virtual account. We use a receipt number or status reference to match the cashier event and investigate a support request without requesting your wallet PIN.

Open the account help route and state which detail needs correction, such as a contact record or device-related account note. Include the registered account detail so we can verify control of the account before changing the record or explaining why a correction cannot be made.

You may ask for removal of eligible personal data through account help. We first confirm account control, identify the records covered by your request and check whether a security, dispute or legal reason requires retention. Where local law permits, we then explain the available action.

Browser cookies can remember a session or preference, while device signals can help identify unusual access. You can adjust cookie settings in your Android, iPhone or desktop browser. After a change, the account path may ask you to log in or verify your phone again.

Give us your registered account contact, the category of data involved and the action you want, such as access, correction or removal. For a wallet matter, add only the receipt number and approximate date. Do not include your password, PIN or full wallet credentials.