Reference

wd168 Privacy Policy For Your Account

wd168 Privacy Policy explains what we collect when you open an account, sign in on mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet record contextMobile access controlsAccount contact route
wd168 wd168 Privacy Policy For Your Account
CONTACT YOUR WAY

Get Privacy Help Beside Account Support

A clear contact path helps when you want to ask about the Privacy Policy, correct an account detail or understand a wallet record. We ask you to contact us from the account area where possible, because that lets us connect the request to the right profile without asking you to send a password. If you are in Surabaya or elsewhere in Indonesia, use the same route for access questions, data requests and account-security concerns.

Team online

Account contact form

Use the account support contact form for Privacy Policy questions, correction requests or access concerns. Include the phone number linked to your profile and a short description, but never include your password, wallet PIN or one-time verification code.

Wallet status trail

When your question concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, mention the transaction reference and date. We use those details to locate the relevant record while keeping the request focused on your account data.

Security escalation

If a sign-in event or phone-verification step looks unfamiliar, contact account support promptly through the signed-in route or the contact option shown on the access page. We may ask for account details to confirm identity before discussing private records.

DATA CONTROL

What We Keep And How You Act

Privacy depends on clear handling at each point of the account journey, from the first phone check to a later visit from your mobile browser.

Account details

We may collect your phone number, account profile details, login events and verification status. These records help us connect you to the right account when you move from sign-in to the lobby, including access to Account Security Tips.

Cookies and sessions

Cookies or similar storage can keep a session active, remember selected settings and support safer sign-in. On mobile, clearing browser storage may sign you out or remove preferences; you can then complete the phone-verification step again.

Account security

We use sign-in events, device signals and phone verification to help identify unusual access. Do not send us your password or one-time code. If you change phones, use the account contact route so we can address access questions safely.

Retention approach

We keep records for as long as they are needed for account operation, security checks, dispute handling or legal duties. Payment references from DANA, QRIS, bank transfer or a virtual account may remain after a session ends when a record must be reconciled.

Your access request

You can ask what personal data is connected to your account, request a correction or ask about deletion where applicable. Send the request through account support and identify the profile with its linked phone number, without attaching secret credentials.

Policy changes

If we change this Privacy Policy, we will place the updated wording on this page and show the applicable date. Check this page before opening a new account or using a different device, especially when access depends on local law.

Privacy Policy Answers For wd168

These Privacy Policy answers address the account questions we expect you to ask before sharing details or connecting a local wallet. They cover collection, payment records, cookies, access requests, security and policy updates. If your situation is not covered, contact us through the account support route with only the details needed to locate your profile.

It covers data used during account creation, phone verification, sign-in, mobile or desktop access, wallet activity and support requests. It also explains cookies, device signals, retention, security handling and your options to request access or corrections.

We use the linked phone number to create and identify your account, complete the phone-verification step and help protect sign-in access. It also lets support connect a privacy request to the correct profile without asking for your password.

Yes. The Privacy Policy covers references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. These records help match a wallet or bank request with the correct account and resolve status questions.

You can contact us through the account support contact form to ask what data is linked to your profile or request a correction. Include your linked phone number and the specific record involved, but do not send passwords or one-time codes.

Cookies and similar storage can maintain your session, remember settings and support safer access. Clearing them may sign you out or remove preferences on your mobile browser. You can still contact us about the data connected to your account.

We may use device signals, sign-in events and phone verification to identify unusual access. If a sign-in does not look like yours, contact account support through the available access route and avoid sharing your password or verification code.

This policy applies to the account journey and related data handling where local law permits. Eligibility and access depends on local law. The current wording appears on this page, so check it again when we publish an update.