Reference

wdtot Privacy Policy For Your Account

Clear account and wallet data choices sit at the centre of our Privacy Policy, so you can understand what happens when you open the lobby, verify your phone…

Account data explainedWallet records clarifiedDevice access coveredPrivacy requests welcomed

Explore Our Lobby Read FAQ

How Wallet Data Enters Our Privacy Policy

wdtot Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy describes the account details we collect when you create access, confirm your phone and move through the lobby. A DANA, OVO, GoPay or QRIS transaction can create a payment reference, status record and receipt trail; bank transfer or virtual account activity can add

1
the bank route used, such as BCA, BRI, Mandiri or BNI. We use these records to match your account, check a pending cashier status and investigate a payment question. Device type, browser signals and login time help us protect access and understand failed sessions. We retain
2
records only for operational, security or legal needs, then remove or anonymise them through our data process. Services and eligibility depend on local law, and our Privacy Policy applies where local law permits.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY SUPPORT

Get Privacy Help Before Account Access

A clear contact path helps when you want to ask about your Privacy Policy rights, correct an account detail or understand a wallet record.

DATA CONTROL POINTS

Six Privacy Controls Behind Your Login

We handle privacy through practical account steps rather than vague promises. Phone confirmation helps us distinguish your access from an unfamiliar sign-in, while device and session records help us investigate unusual activity.

Account creation

When you open an account, we collect the fields needed to create access and connect your account with wallet activity. Phone verification may be required before account access, especially when a session needs extra confirmation.

Login protection

We record sign-in time, device type and session signals to help identify an unusual login. If a session fails on mobile, these records help support trace the access event without exposing your password.

Cookie choices

Cookies can keep a session open, remember selected settings and help pages load correctly. You can clear or restrict them in your browser settings, although some account functions may then need another sign-in.

Wallet matching

A payment reference connects a DANA, OVO, GoPay or QRIS status with the correct account. For bank transfer and virtual account activity, we use the available reference and route data to resolve receipt questions.

Retention checks

We keep account, security and payment records for as long as an operational, dispute or legal need remains. When that need ends, we remove, aggregate or anonymise the record through our retention process.

Change requests

You can ask us to correct account data, explain a collection purpose or address a deletion request. We first confirm that the request belongs to you, then assess security, payment and legal effects before responding.

Privacy Policy Answers For wdtot Accounts

These Privacy Policy answers focus on the questions you may have before opening an account or linking an Indonesian wallet. We keep the wording practical: what we collect, why a record exists, how you can ask for a change and what happens when access depends on local law.

The wdtot Privacy Policy covers account details, phone confirmation, login and device signals, cookies, payment references, support messages and retention. It explains how we use those records to provide account access, check wallet status, protect sessions and respond to requests.

Yes. When you use DANA or QRIS, we may receive a payment reference, amount status and receipt-related record needed to match the transaction with your account. We do not need your wallet password to check that a payment status belongs to you.

Phone verification helps confirm that the person requesting account access controls the registered contact detail. It also supports account recovery and reduces the risk of an unfamiliar device entering the account. We use the confirmation event for these security purposes.

You can request a correction if your registered name, phone detail or account record is inaccurate. Send the affected field and enough account context for us to locate it. We may confirm your identity first, especially where the change could affect wallet access.

We retain payment references and related account records while they support transaction matching, disputes, security checks or a legal requirement. After the relevant need ends, we remove, aggregate or anonymise them according to our retention process.

Use our support contact path and state that your request concerns the Privacy Policy. Include your registered phone or email, the subject of the request and a payment reference only when relevant. Never send your password, wallet PIN or complete payment credential.

Our Privacy Policy is written for account and wallet access in Indonesia, but availability and eligibility depend on local law. Where local law permits, we process the records needed for account security, payment matching, support and your privacy requests.

wdtot Privacy Policy For Your Account

Get Privacy Help Before Account Access

Six Privacy Controls Behind Your Login

Account creation

Login protection

Cookie choices

Wallet matching

Retention checks

Change requests

Privacy Policy Answers For wdtot Accounts

01 What does the wdtot Privacy Policy cover?

02 Does the Privacy Policy include DANA and QRIS data?

03 Why does wdtot ask for phone verification?

04 Can I ask wdtot to correct my personal data?

05 How long does wdtot keep payment records?

06 How can I contact wdtot about the Privacy Policy?

07 Does the Privacy Policy apply to access in Indonesia?

Related Pages