Reference

Open dolanantogel Privacy Policy

dolanantogel Privacy Policy explains what we collect when you open an account, use the lobby, or connect DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record handlingCookie choicesAccount contact path
dolanantogel Open dolanantogel Privacy Policy
CONTACT ROUTES

Check your privacy request path

A clear contact route helps you ask about a stored detail, a cookie choice or an account correction without sending sensitive wallet credentials. Start from the support contact path linked near account access and include the phone number or account identifier attached to your profile. We may ask you to complete phone verification before discussing private records. This protects you when a login or payment status stalls, whether you are checking a DANA Fast Transfer reference or a QRIS receipt from a mobile device.

Team online

Account access

Use our account support path when you need to ask which profile details we hold or why phone verification is required. Send your account identifier, but never include a wallet PIN, full password or one-time security code in the message.

Payment records

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, share the transaction reference and approximate time. We use that limited detail to locate the status record while keeping your wallet credentials outside our support request.

Privacy changes

Ask us to correct an account detail, explain a cookie setting or discuss retention through the same contact route. We may verify ownership by phone before changing records, so another person cannot redirect your profile information.

DATA PRACTICES

Explore the controls behind your policy

Privacy choices work alongside the account steps you already use: phone verification before access, a login session on your chosen device and a payment reference when a wallet action is checked.

Account details

We collect details needed to create and maintain your account, such as your phone contact and verification result. We use them for access checks and support identification, not to request your DANA, OVO or GoPay password.

Device sessions

A phone or desktop session can create technical records such as browser type, approximate connection data and login time. These signals help us recognise an unusual access pattern and ask for verification before private account details are discussed.

Cookie settings

Cookies can remember a practical choice, such as a language or lobby preference, and may help keep a session working. You can clear or restrict them in your browser, although some account pages may then require another login.

Payment references

We retain the reference, amount status and time needed to match a wallet or bank action. For QRIS and virtual account checks, our records are used to reconcile status; your wallet PIN and banking password stay with the payment provider.

Security records

Login attempts, phone verification events and account changes may be logged to protect your profile. If you move from Live Roulette Gold to Aviator Quick Arena on mobile, the session record helps us investigate access that does not match your normal pattern.

Retention requests

You can ask what personal details are held, request a correction or ask about removal through our support contact path. We may keep limited security or transaction records where needed for a lawful request, dispute handling or account protection.

Find answers about Privacy Policy

These Privacy Policy answers focus on the account questions you may search before opening access. They explain the records connected with phone verification, device sessions, local payment references and cookie choices. If your situation needs an account-specific answer, use our support contact path and provide only the identifier needed to locate your profile. Access depends on local law, and we may confirm ownership before discussing private data.

The Privacy Policy covers account details, phone verification, device and login records, cookie settings, support messages and payment references. It explains why we use each category, how we protect access and how you can ask for a correction or clarification through our support contact path.

Yes. The Privacy Policy includes the reference, status and timing needed to match DANA or QRIS activity with your account. It also covers OVO, GoPay, bank transfer and virtual account references. We do not need your wallet PIN or banking password to check a payment status.

Phone verification helps us confirm that the person requesting account access or a data change controls the profile contact. It can also help us investigate an unusual login. We may ask for this step before sharing private records or changing details attached to your account.

You can request a correction through our account support path. Include your account identifier and describe the detail that needs changing, without sending a password or wallet code. We may verify ownership by phone, then assess the request against security needs and local law.

The Privacy Policy allows cookies to support session functions and remember practical choices on your phone. You can clear or restrict them in browser settings. After that change, the lobby or account page may ask you to log in again, and some preferences may not remain.

We keep account and transaction details for the period needed to operate access, answer disputes, protect against suspicious activity or meet a lawful request. When a record is no longer needed, we remove or anonymise it through our retention process where local law permits.

Use the support contact path linked near account access and state that your message concerns the Privacy Policy. Add the relevant account identifier or payment reference only. For a DANA, QRIS or login question, this helps us find the correct record without receiving private wallet credentials.