Reference

Privacy Policy For Your pelangi toto Account

pelangi toto Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity in Indonesia.

Account dataCookie choicesWallet recordsLocal access
pelangi toto Privacy Policy For Your pelangi toto Account
ACCOUNT HELP PATH

Where To Ask About Privacy Policy

A clear contact route matters when you want to ask about the Privacy Policy or correct an account detail.

Privacy request Send a request through the account support path when you want to know which…
Wallet record If a payment reference appears incorrectly, mention the rail and date shown in your…
Access concern When a sign-in or phone verification issue affects your privacy request, tell us whether…
SIX DATA PRACTICES

How We Handle Your Account Data

We keep this policy tied to actions you can recognise: creating an account, confirming a phone, opening Auto Roulette Live or Omaha Poker Table, and checking a wallet status.

Account details

We use the name, contact detail and account credentials you submit to create and maintain your access. Phone verification helps us connect a sign-in attempt with the correct account. Keep your credentials private, and contact us if a detail is wrong or no longer belongs to you.

Device signals

A mobile browser or desktop browser may send basic device and session signals so we can keep pages connected during sign-in and detect unusual access. These signals help distinguish a normal return to the lobby from a request that needs extra account checks.

Cookie choices

Cookies can remember a session, preserve a selected page and support account security. You can control cookies through your browser settings, although blocking them may interrupt sign-in or remove saved preferences. We do not treat a cookie choice as permission to collect unrelated account details.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we keep the reference and status needed to match an account request. We do not ask for a wallet PIN or banking password through support, and payment records are handled for reconciliation and account security.

Retention period

We retain account, security and transaction records only for as long as needed for the purpose described in this policy, including dispute handling and required operational records. When a record is no longer needed, our process is to remove it or separate it from direct account identification.

Change requests

You may ask us to correct account details, explain a data use, or remove eligible information through the account support path. Include the account contact detail and a clear request. We may verify ownership first, and access remains subject to local law and necessary record duties.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account questions we expect before you open access from Indonesia. Each answer stays focused on data, cookies, verification, payment references and contact rights rather than describing unrelated lobby features. If your situation is not covered, use the account support path and identify the relevant account detail without sharing a password or one-time code.

It covers account details, phone verification, browser and device signals, cookies, support requests, payment references and retention. We use these details for account access, security, support and operational records. Access depends on local law, and we explain the available request path within the policy.

Yes. When your account uses DANA, QRIS, OVO, GoPay, bank transfer or a virtual account, we may keep the payment reference and status needed to match the account record. We do not need your wallet PIN or banking password for that matching process.

We use phone verification to connect an access attempt with the correct account and to help protect account changes. The verification detail is not a substitute for your password, and you should never send a one-time code in a support message or share it with another person.

You can request a correction through the account support path. State which account detail is incorrect and provide the contact detail attached to the account. We may ask for an ownership check before making a change, particularly when the request affects phone access or wallet records.

Cookies can keep a browser session active, remember a selected page and assist security checks. You can adjust them in your mobile or desktop browser settings. Blocking required cookies may interrupt sign-in or remove saved preferences, but it does not create permission for unrelated data collection.

We keep personal, security and transaction records for the period needed for their stated purpose, including account support, disputes and required operational duties. When a record no longer serves that purpose, our process is to remove it or separate it from direct account identification.

Use the account support path shown after sign-in and describe whether your request concerns access, correction, deletion, cookies or a payment reference. Include only the details needed to locate your account. We may confirm ownership, and any action remains subject to local law.