Reference

dblototo Privacy Policy for Your Account

dblototo Privacy Policy shows what we collect when you open an account, verify your phone, use DANA or QRIS, and move between the lobby and your wallet.

Account dataWallet recordsCookie choicesDevice access
dblototo dblototo Privacy Policy for Your Account
CONTACT ROUTE

Reach us about your privacy record

A clear contact route helps you ask about the Privacy Policy without explaining your concern twice.

Data request Use the account support path to ask what personal data we hold, why it is used and which account step created the record. Include your verified phone number for matching.
Wallet reference For DANA, OVO, GoPay or QRIS questions, send the payment reference and status shown in your account. We use those details to locate the correct record without requesting your wallet password.
Access concern If a privacy setting or account check blocks access, contact us through the same support route. We can explain the request, device or verification detail connected with the restriction.
DATA PRACTICE

How we protect your account data

Privacy work is tied to practical account events rather than vague labels. We separate identity details from wallet references where our systems allow, restrict account access by staff role and use device…

Account security

Phone verification happens before account access, and sign-in activity can be checked against device and browser signals. These records help us investigate an unusual login without exposing your wallet credentials.

Payment records

We keep DANA, OVO, GoPay, QRIS, bank transfer and virtual account references so deposits or withdrawals can be matched to the right account. The record is not your wallet password.

Cookie control

Cookies can retain session choices and help us understand whether a page opened correctly on your phone or desktop. You can adjust browser cookie settings, though some account steps may then need repeating.

Device signals

We may store device type, browser version, IP address and sign-in time for account protection. When you move from login to the lobby, these signals help connect the session to your account.

Retention periods

We retain account, payment and support records only for the operational, security or legal period that applies to each record. When a period ends, deletion or anonymisation is considered.

Change requests

Ask us to correct inaccurate account details or explain a data use through the support route. We verify ownership first, then record the request and respond using the contact details on file.

Privacy Policy answers before account access

These Privacy Policy questions cover the account actions Indonesian customers ask about most. If your situation is not listed, use the account contact path and include the specific record, wallet reference or device issue you want us to check.

It covers personal data linked to your account, phone verification, device access, cookies, payment references, support messages and retention. It also explains your request options and when access depends on local law.

We use your phone number for account verification, sign-in matching and account contact. Verification takes place before access, helping us connect a Privacy Policy request with the correct account.

No. We record the payment rail, reference, amount status and account match needed for processing, but your DANA, OVO, GoPay or QRIS wallet password remains with that payment service.

We may collect device type, browser version, IP address, session time and sign-in signals. This supports account security and page operation when you move from phone login to the lobby.

Use the support path inside your account and identify the record you want checked. We verify account ownership before discussing personal data, then handle a copy, correction or explanation request.

Retention depends on the purpose and the record type. Account, payment and support entries remain for operational, security or legal needs, after which we assess deletion or anonymisation.

Yes, ask through the account contact route and specify cookies or account deletion. We explain any records that must remain for security or legal reasons, with access handled where local law permits.