Reference

w4dsukses Privacy Policy for Your Account Data

w4dsukses Privacy Policy explains what we collect when you create an account, verify your phone, browse Auto Roulette or Book of Dead, and use DANA or QRIS.

Account recordsWallet activityDevice sessionsCookie choices
w4dsukses w4dsukses Privacy Policy for Your Account Data
CONTACT YOUR WAY

Get Policy Help Near Account Access

A clear contact path matters when you want to understand a Privacy Policy entry or question a record. Start from the support route shown after account access and include the phone number linked to your account, the relevant date, and any payment reference. We use those details to locate the right record without asking you to send a password or full wallet credentials.

Team online

Account help route

Open the support form from your signed-in account and choose the Privacy Policy or data request topic. We can match your phone verification and account record without receiving your password.

Wallet status query

For a DANA, OVO, GoPay or QRIS question, share the transaction date and masked reference shown in your account. We use the payment status record to investigate without requesting a wallet PIN.

Access concern

If a mobile browser session, login record or phone verification looks unfamiliar, contact us through account support and include the device path. We can review session details and explain the next step.

DATA CONTROL ROOM

What We Do With Your Personal Records

We handle personal records according to the purpose stated in this Privacy Policy, not as an open-ended profile.

Account details

We use your phone number and verification result to identify the account during sign-in, support requests and security checks.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us reconcile status with your account.

Cookies and sessions

Our mobile and desktop paths may use session cookies for login continuity, fraud checks and selected settings.

Security signals

We can record device type, browser details, login time and approximate network signals when you access the account.

Retention approach

We keep account, payment and support records only for the operational, dispute and legal periods that apply to the service.

Changes and requests

You can ask us to correct an inaccurate phone, profile or contact record through account support.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers cover the questions we expect before you open an account or connect a local wallet. They explain the account step, mobile access, payment references and request path in plain English. If your question concerns eligibility, access depends on local law; our support route can clarify which policy process applies to your account.

It covers account details, phone verification, device sessions, cookies, lobby activity, payment references and support records created when you use w4dsukses through supported Indonesian access routes.

Phone verification helps us connect a sign-in and support request to the correct account. We use the result for access and security checks, and you should not send your password to support.

Yes. We may store a masked DANA or QRIS reference, amount status and transaction time so we can match a payment event to your account without asking for your wallet PIN.

When you sign in from a mobile browser, we may record device type, browser details, session time and network signals. This helps identify unusual access and keep the account path secure.

Use the support form inside your account, select the data request route, and identify the record you want corrected. We may verify ownership before confirming a change or explaining its status.

We retain payment and account records for the operational, dispute and legal periods that apply to the service. After that period, we delete or anonymise records when no longer needed.

Yes. Contact account support with your browser and device path, and we can explain the session cookies used for login continuity. Browser settings can restrict cookies, but access may then require another sign-in.