Reference

asdtoto Privacy Policy for Your Account

Your account details, wallet references and device choices are covered in the asdtoto Privacy Policy, so you can see what we collect before opening the lobby.

Account dataWallet referencesDevice choicesPhone verification
asdtoto asdtoto Privacy Policy for Your Account
CONTACT ROUTES

Get Privacy Answers Through Account Support

A clear support path helps when a privacy question concerns login, phone verification or wallet status. Open the account support route and include the email or phone linked to your account, without sending a wallet password. We can use the payment reference shown beside the cashier status to locate the relevant record and explain the next step where local law permits.

Team online

Account privacy request

Use the support path inside your account to ask what personal data is linked to your profile, including the account contact used for phone verification.

Wallet record question

Mention whether the record concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account so we can narrow the payment-status data involved.

Access concern

If a device sign-in or account step looks unfamiliar, tell us the device type and approximate time; never place your password or wallet PIN in the request.

ACCOUNT SAFETY

How Device and Account Data Stay Managed

We keep the Privacy Policy practical by connecting each data category with an account action you recognise.

Account details

We use contact and verification details to connect your sign-in with the right account. Phone verification is completed before account access, helping us separate one profile from another.

Cookie settings

Browser cookies and similar storage can remember session choices or help us understand a sign-in event. You can manage browser permissions, though some account steps may then need repeating.

Device signals

We may record device type, browser details and security events linked to access. If you move from mobile to desktop, these signals help us assess whether the sign-in fits your account pattern.

Wallet references

A payment reference can connect DANA, OVO, GoPay, QRIS, bank transfer or virtual account status with your account. We use that reference for matching, not for collecting your wallet password.

Retention period

We retain records only for the period needed for account operation, security checks, support questions and applicable legal duties. The Privacy Policy explains the purpose behind each retention category.

Change requests

You can contact support to request correction, access or another permitted change to your personal data. Include the account contact and the specific record, while keeping passwords and PINs out of the message.

Privacy Policy Questions Before Account Access

These Privacy Policy answers focus on the searches we expect from an Indonesian account holder. They cover account setup, mobile access, wallet references, cookies, retention and contact steps, so you can understand the data path before opening an account. If your situation is not listed, use the account support route and describe the specific record without sharing secret credentials.

It covers account details, phone verification, device signals, cookies, security events, payment references and retention. It also explains how to request access or correction where local law permits.

We may keep a DANA or QRIS reference and its status so a cashier request can be matched with your account. We do not need your wallet password or PIN for that match.

Yes. The Privacy Policy covers OVO and GoPay references in the same way as other supported wallet records: we use the status and reference needed to identify the related account activity.

We use the phone contact supplied during account setup and the verification result connected to it. This helps link sign-in activity to your profile without asking you to send a password through support.

You can contact the account support path with your linked email or phone and ask about device records. Include the approximate sign-in time, but leave out passwords, wallet PINs and verification codes.

Retention depends on the purpose, such as account operation, security checks, payment status or legal duties. The current Privacy Policy sets out the applicable categories and explains how to request clarification.

Use the support route inside your account and identify the record you want corrected or accessed. State whether it concerns login, cookies, DANA, OVO, GoPay, QRIS or another account detail.