Reference

Open toto 1818 Privacy Policy Clearly

toto 1818 Privacy Policy sets out what we collect when you create an account, verify your phone and use DANA, OVO, GoPay or QRIS for wallet activity.

Account dataWallet recordsCookie choicesSecurity requests
toto 1818 Open toto 1818 Privacy Policy Clearly
PRIVACY HELP

Find Privacy Help Beside Cashier Status

A privacy request should not get lost beside a wallet query, so we keep the account-help route close to the cashier status path. Tell us which account detail, cookie choice or payment reference you are asking about, and include the phone or account identifier needed to locate the record. We may ask you to complete a security check before discussing account data. Our support route can also explain how a DANA, QRIS, bank transfer or virtual account reference appears in our records.

Team online

Account help

Use the account-help route when you want to ask what contact details, phone verification records or login events we hold. We match the request to your account before discussing any personal record, so a clear account identifier helps us avoid sending details to the wrong person.

Wallet privacy

Choose the cashier-status path for a privacy question about DANA, OVO, GoPay or QRIS activity. We can explain the payment reference and status stored for reconciliation, while wallet PINs and secret credentials are not requested through ordinary support messages.

Security request

If a login event or device record looks unfamiliar, contact account help and describe the time, device path and affected wallet reference. We may pause the conversation for identity checks, then record the request so our team can protect the account and respond consistently.

DATA PRACTICE

Switch Devices With Privacy In Mind

Privacy is handled at the points where account activity creates a record: registration, phone verification, wallet matching, cookie use and support contact.

Data collected

We may hold your account contact details, phone verification result, login timestamps, device and browser signals, support messages and wallet references. When you open a title such as Live Blackjack Royal, the related account event may be recorded for session security and operational checks.

Cookie controls

Cookies can keep a mobile session connected to the account you verified and help us remember necessary security settings. If you block or clear them, some account steps may repeat, including login or phone verification; changing browser settings changes cookie behaviour on that device.

Account security

Phone verification gives us an account step to compare when access looks unusual. We do not ask you to place a wallet PIN in a support message. If a device path changes before you open Football Goal Rush or another title, a security check may be required.

Retention period

We keep account, payment-reference and support records for the period needed to operate the account, resolve disputes, maintain security and meet applicable legal duties. When a record is no longer needed for those purposes, we follow our deletion or de-identification process.

Policy changes

When we change this Privacy Policy, we place the revised date and wording on this page. A new version may explain a different cookie setting, retention period or request route. Reading this page before using DANA, QRIS or bank transfer keeps your account choices current.

Request changes

You can ask us to access, correct or delete eligible account details, or object to a particular use where local law permits. Send the request through account help with enough detail to identify the record; we may verify your identity before making a change.

Check Privacy Policy Answers Before Access

These Privacy Policy answers focus on the account steps Indonesian customers usually ask about: phone verification, mobile cookies, wallet references, device changes and requests for access or correction. We keep each answer tied to the records we handle rather than describing unrelated lobby functions. If your question concerns a specific account event, include its date, device path or payment reference when you contact us through account help.

It covers records created when you open an account, complete phone verification, log in, use cookies, contact support or connect wallet activity. That includes device signals and DANA, OVO, GoPay, QRIS, bank transfer or virtual account references used to match account events.

Phone verification gives us a practical way to confirm that an account request is connected to the right person. We may store the verification result and related event time, then use them during account access or a security request; access depends on local law.

Our Privacy Policy distinguishes payment references from secret wallet credentials. We may retain a DANA or QRIS transaction reference and status for reconciliation, but you should not send a wallet PIN, password or secret code through account help or any support message.

Necessary cookies can connect your mobile browser session with the account settings and security steps you have already completed. Clearing cookies may sign you out or ask for phone verification again. You can change cookie settings in your browser, subject to necessary functions.

Yes. Send an account-help request stating the detail you believe is wrong and the correction you want. We may request identity checks before changing contact, phone or wallet-reference records, and we handle the request according to applicable law and the Privacy Policy.

We retain records while they are needed for account operation, security checks, dispute handling or legal duties. The period can differ by record type, such as a login event, support message or bank transfer reference. We remove or de-identify records when those needs end.

Contact account help promptly and provide the approximate time, device path and any related wallet status. Do not include a password or wallet PIN. We may verify your identity, record the security request and take account-protection steps where local law permits.