Reference

Privacy Policy for Your Account

DANA, OVO, GoPay, QRIS, account login, cookies, and device checks all create data points, and this Privacy Policy explains how we handle them before you open your account.

Account data explainedDANA and QRIS contextCookie choicesSupport contact paths

Browse lobby Read FAQ

What We Collect and Why

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

Your account needs enough data to keep login, wallet, and help requests accurate. We collect details you give us during account setup, such as your phone number, username, and contact channel, plus payment references linked to DANA, OVO, GoPay, QRIS, or bank transfer activity. We also

1
record device signals like browser type, IP range, session time, and security events when you move between mobile and desktop. We use this data to run account access, check wallet records, respond to your requests, prevent duplicate account activity, and keep our policy records aligned with
2
local law. Access and eligibility depend on local law and apply only where local law permits.

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

CONTACT ROUTES

3 Ways to Ask About Privacy

A privacy question should not feel buried under general help topics. We separate account access, wallet record checks, and cookie questions so you can reach the…

ACCOUNT CARE

6 Privacy Controls We Use

Privacy work happens behind the screen, but you should still know the steps. We limit access to account and wallet data by role, keep session records for security checks, and use cookie…

Account setup data

When you join, we record the details needed to create and protect your account: username, phone, password status, and contact channel. We use them for login checks, support replies, and account recovery steps.

Payment record handling

DANA, OVO, GoPay, QRIS, and bank transfer references stay connected to wallet history so deposits and withdrawals can be matched. We do not ask support agents to collect your wallet password.

Device and session signals

Mobile browser, desktop browser, IP range, login time, and failed password attempts help us spot unusual account access. You can reduce shared-device risk by logging out from Profile after each session.

Cookie use

Cookies remember language, session status, and basic preference choices. They also help us understand whether the lobby loads properly on Android Chrome, iPhone Safari, and desktop browsers without naming your private activity publicly.

Retention checks

We keep account, payment, and support records only for business, security, and legal reasons. When data is no longer required for those purposes, we remove it or separate it from your active account.

Change requests

You can ask us to correct contact details, check stored account data, or close certain records where allowed. We verify ownership first, then explain what can be changed and what must remain.

Questions About Your Data

These answers focus only on privacy handling at wdselot77: what we collect, how we use it, and how you can reach us. Keep your registered phone and username ready when asking about account records. For your safety, we will not discuss private wallet or login details through a channel that is not linked to your account.

We collect the details needed to create and protect your account, such as username, registered phone, login status, and support contact choices. Payment references from DANA, OVO, GoPay, QRIS, or bank transfer may attach to wallet records.

Device type, browser, IP range, session time, and failed login attempts help us detect unusual access. These records also help support check whether an account issue came from mobile, desktop, or a shared connection.

Yes. Contact us by live chat, email, or account message and tell us what needs correction. We verify your account first, then update the data where our records and local law allow the change.

Cookies keep you signed in during a session, remember basic display choices, and help pages load correctly on Android Chrome and iPhone Safari. You can clear cookies in your browser settings, but login may reset.

Support can view account-linked transaction references needed to answer wallet questions, but we do not ask for your DANA, OVO, GoPay, or bank password. Never send a private PIN in chat or email.

We keep records for security, account operation, dispute checks, and legal reasons. When a record is no longer needed for those purposes, we remove it, anonymise it, or separate it from active account use.

Use live chat from 09:00 to 23:00 WIB for quick questions, or email support for written requests. If logged in, open Profile, choose Help, and send an account message for faster ownership checking.

Privacy Policy for Your Account

3 Ways to Ask About Privacy

6 Privacy Controls We Use

Account setup data

Payment record handling

Device and session signals

Cookie use

Retention checks

Change requests

Questions About Your Data

01 What personal data do you collect when I open an account?

02 Why do you record my device and login activity?

03 Can I ask to update my phone number or account data?

04 How do cookies affect my privacy on mobile?

05 Do you share my wallet details with support agents?

06 How long do you keep my account and payment records?

07 Who should I contact for a privacy request?

Related Pages