Reference

How Privacy Policy Applies To Your Account

opera toto Privacy Policy explains how we collect, use and protect the account details you provide before you enter the lobby.

Account dataWallet recordsCookie choicesAccess requests
opera toto How Privacy Policy Applies To Your Account
CONTACT ROUTES

Where To Ask About Your Data

A clear contact route helps when a Privacy Policy question is tied to a real account event. Start from the support link displayed beside your account access area and describe the issue without sending a password or wallet PIN. We can use the account email, phone verification step and payment reference you provide to locate the correct record. If a QRIS receipt, DANA status or bank transfer appears unfamiliar, keep the receipt ready while we check the account trail.

Team online

Account access

Use the support link beside account access when you need to ask which personal details are attached to your opera toto account. We may request a phone verification step before discussing records, helping us avoid sharing account data with the wrong person.

Wallet status

For a DANA, OVO, GoPay or QRIS record, include the payment reference and approximate time rather than your wallet password. We check the account trail and explain what status data is stored, while keeping the payment credential outside the support exchange.

Change request

If a contact detail is outdated or you want to ask about deletion, send the request through the account support route. We first confirm account ownership, then explain which records can be changed and which must remain for policy or legal reasons.

DATA CONTROLS

Six Controls Behind Our Privacy Policy

Privacy Policy choices matter most when they match the way an account actually works. We separate login details from wallet credentials, review device activity when access looks unusual and keep cookie settings…

Data collection

We collect details you enter during account creation, such as contact data and verification results, plus technical signals from the device and browser used to sign in. Those records help us connect your request to the right account without asking for unnecessary wallet credentials.

Cookie settings

Cookies help keep your session connected while you move from account access to a mobile lobby. Your browser controls whether optional cookies remain active. Changing that setting can affect remembered preferences, but it does not erase account records or payment references.

Account security

We use phone verification before sensitive account access and compare sign-in activity with the device path previously used. If a pattern looks unusual, we may pause a request and ask you to confirm ownership before discussing personal or wallet-linked data.

Payment separation

DANA, OVO, GoPay and QRIS provide payment status details, not permission for us to read your wallet password or PIN. We retain the reference needed to match a transaction to your account and keep the credential itself outside our support process.

Retention period

We retain account, verification and payment-reference records only for the period needed to provide account support, resolve disputes, protect access and meet applicable legal duties. When a record no longer serves one of those purposes, our process can remove or anonymise it.

Your request

You can ask for access, correction, deletion or an explanation through the support route shown in your account. We may ask for a phone verification step, and where local law permits we explain any reason a particular record cannot yet be removed.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and payment questions we hear most often from people in Indonesia. They explain what to prepare, where to send a request and why verification can be needed. If your situation involves a specific DANA, QRIS, phone or device record, use the support path connected to your account.

It covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account use. It also explains your choices for access, correction, deletion and policy questions.

Phone verification helps us confirm that the person asking about an account record is the account holder. We may use it before changing contact details, discussing wallet-linked activity or handling a deletion request, particularly when the request comes from a new device.

No. The policy distinguishes a payment reference or status from your private wallet credential. When you use DANA, OVO, GoPay or QRIS, we need enough transaction detail to match the account record, but you should never send a PIN or password to support.

Open the support route displayed beside account access and ask for a copy or explanation of your stored data. Include the account contact detail you can verify and the relevant payment reference if needed. We confirm ownership before releasing personal records.

Yes, you can request a correction through the account support route. Tell us which detail is wrong and what the accurate value should be. We may repeat the phone verification step, and some changes may require a matching account or payment record.

We keep payment references for the period needed to match account activity, answer support questions, resolve disputes, protect access and meet applicable legal duties. The exact period can depend on the record and local requirements, so you can ask support for a clear explanation.

You can submit a deletion request through the support route shown in your account. We confirm ownership and assess each record separately. Where local law permits, we remove or anonymise data that no longer has a valid support, security or legal purpose.