Reference

Open the wdtotologinlink Privacy Policy

wdtotologinlink Privacy Policy sets out what we collect when you create an account, sign in from a phone, or use DANA and QRIS for a wallet transaction.

Account clarityWallet recordsCookie choicesContact route

Explore Our Lobby Read FAQ

Check how DANA data enters our Privacy Policy

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

Our Privacy Policy separates account details from transaction records so you can understand the reason for each use. During account creation, we may request your phone number and verification result to protect sign-in; when you use DANA, OVO, GoPay or QRIS, we retain the reference needed

1
to match the wallet event to your account. Bank transfer and virtual account references can be handled in the same way, while card or wallet credentials are not treated as general profile content. We use access and transaction details to investigate failed status updates, confirm account
2
ownership and maintain a clear activity record. Availability and eligibility depend on local law, and the policy applies only where local law permits. You can contact us through the support path connected to account help to ask about a specific record.

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

PRIVACY HELP DESK

Ask about privacy beside the cashier path

A clear contact route matters when a wallet record or sign-in detail looks unfamiliar.

DATA CONTROL ROOM

Browse account security and cookie controls

We keep the Privacy Policy practical by tying each data category to an account action you can recognise.

Account data

We use the phone number and verification outcome supplied during account creation to identify your account and reduce mistaken access. If a detail changes, contact us through account help so we can check ownership before updating the record.

Device signals

A sign-in from a mobile browser may create device and session signals used to protect the account. These signals help us notice unusual access patterns, but they do not replace the phone verification step required for account access.

Cookie choices

Cookies can remember a session and help the account page load the correct state after you move from login to the lobby. Your browser controls can limit cookies, although some account and Privacy Policy functions may then need another sign-in.

Wallet matching

When you use QRIS, DANA, OVO or GoPay, we use the payment reference, status and time to match the event with your account. The matching record supports investigation of a pending or failed wallet status without exposing your wallet PIN.

Retention checks

We retain account, support and transaction records only for the period connected to account protection, dispute handling or legal duties. A request can ask which category remains, why it remains and whether deletion or restriction can be assessed.

Correction route

If your phone verification detail, contact record or support note is inaccurate, tell us which field needs correction. We compare the request with the account record and may ask for an ownership check before making a change.

Find Privacy Policy answers before account access

These Privacy Policy answers address the questions we expect before you open an account from Indonesia. They cover account creation, mobile browsing, wallet references, cookies, retention and requests for access or correction. If your question concerns a particular record, use the support path connected to account help and include only the details needed to locate it.

It covers data connected with account creation, phone verification, sign-in sessions, cookies, support requests and wallet references. It also explains retention, security steps and request routes for records linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use phone verification to connect you with the correct account and reduce mistaken access. The verification result can support a sign-in check or a privacy request. We may ask for an ownership check before discussing personal data or changing an account field.

Yes. The policy covers a mobile browser path from login to the lobby, including session and device signals used for account protection. If cookies are limited in your browser, you may need to sign in again before reaching account or privacy controls.

We use a DANA or QRIS reference, status and time to match a wallet event with your account and investigate a pending record. The reference supports reconciliation, while your wallet PIN and other secret credentials should never be sent through support.

Yes. Contact us through the account-help route and identify the field or support record you believe is inaccurate. We may confirm ownership before making a correction, and we will explain if a transaction record must remain for dispute handling or legal duties.

Retention varies by category and purpose. Phone verification, session details, support messages and wallet references may remain while needed for account protection, status investigation, dispute handling or legal duties. You can ask which category applies and why it is still retained.

Yes. Privacy rights, account access and eligibility depend on local law, and our services are available where local law permits. If a request has a location-specific limit, we will explain the applicable route through the support contact linked to your account.

Open the wdtotologinlink Privacy Policy

Ask about privacy beside the cashier path

Browse account security and cookie controls

Account data

Device signals

Cookie choices

Wallet matching

Retention checks

Correction route

Find Privacy Policy answers before account access

01 What does the wdtotologinlink Privacy Policy cover?

02 Why does wdtotologinlink request phone verification?

03 Does the Privacy Policy cover mobile browsing?

04 How are DANA and QRIS records used under this policy?

05 Can I ask for my wdtotologinlink data to be corrected?

06 How long does the Privacy Policy keep account records?

07 Does access to my data depend on local law?

Related Pages