Reference

slotdadu Privacy Policy for Your Account

The slotdadu Privacy Policy explains what we collect when you open an account, verify your phone, browse Blackjack or Hi Lo, and use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet record contextYour request path

Explore Our Lobby Read FAQ

What We Record During Wallet Access

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

Our Privacy Policy covers account details, phone verification results, sign-in events, device and browser signals, pages opened, support messages, and payment references connected with your account. A DANA, OVO, GoPay or QRIS reference helps us match a wallet action without treating your wallet PIN as account

1
content. Bank transfer and virtual account references may also appear when you choose those routes. We use these records to provide account access, detect unusual activity, answer privacy requests, and meet applicable legal duties. Access or eligibility depends on local law. The policy applies when you
2
use a mobile browser or desktop browser, including sessions where you move from the account page to the lobby.

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

CONTACT ROUTES

Where Privacy Questions Reach Us

A privacy request should include the account email or phone detail you used, the subject of your request, and enough context for us to locate the record.

Account privacy request Ask us to access, correct, or explain personal data linked to your account. Include your verified phone detail so we can check identity before sharing account-specific material.

Wallet record question If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the date and reference shown in your account. We use those details to trace the relevant record.

Device access concern Tell us when a mobile or desktop sign-in looks unusual. We can review the access context, guide an account check, and explain which security records the Privacy Policy covers.

DATA PRACTICES

Six Practical Data Safeguards

We handle privacy through specific account steps rather than broad promises. Phone verification helps us distinguish an account holder from an unknown request, while device and sign-in records help us investigate access…

Account details

We use the name, contact detail, phone verification result, and account activity you provide to maintain your profile and respond to requests about your personal data.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references may connect an account action with a transaction record. We do not ask for your wallet PIN.

Cookie choices

Cookies and browser storage can keep a session available between the login page and lobby. You can manage browser permissions, though changing them may affect account access.

Security checks

We compare phone verification, sign-in timing, and device signals when an account request needs checking. This helps us avoid disclosing personal data to the wrong person.

Retention periods

We keep records for the purpose described in the Privacy Policy and for applicable legal or dispute needs. When a record is no longer required, our process removes or separates it.

Change requests

You can ask us to correct inaccurate account data, explain a processing purpose, or address an eligible deletion request. We may verify your identity before making a change.

Privacy Policy Questions Before You Join

These Privacy Policy answers focus on the account decisions you make before opening access, including phone verification, browser use, wallet references, and requests about stored data. If your question is not covered, use the privacy contact route and include the account detail we can verify.

It covers account details, phone verification, device and browser signals, lobby activity, cookies, support messages, payment references, retention, security checks, and requests to access or change personal data.

No. The Privacy Policy addresses payment references and account-linked status, not your wallet PIN. We may retain a DANA or QRIS reference needed to identify an account action.

Phone verification helps connect an account request to the correct account holder. We may use that result before discussing personal data, changing account details, or responding to an access request.

Yes. It covers browser type, device signals, session details, and cookies used when you move from login to the lobby on mobile or desktop. Browser settings can limit cookie storage.

Contact us through the privacy route with your account email or verified phone detail and describe the records you want. We may complete an identity check before sending account-specific data.

Yes. Send the inaccurate detail and the correction you want. We review the request against account records and may ask for phone verification before updating information linked to your profile.

Records remain for the stated collection purpose and any applicable legal, security, or dispute need. After that period, we remove, anonymise, or separate them through our retention process.

slotdadu Privacy Policy for Your Account

Where Privacy Questions Reach Us

Six Practical Data Safeguards

Account details

Payment references

Cookie choices

Security checks

Retention periods

Change requests

Privacy Policy Questions Before You Join

01 What does the slotdadu Privacy Policy cover?

02 Does slotdadu store my DANA or QRIS PIN?

03 Why does slotdadu ask for phone verification?

04 Does the Privacy Policy cover mobile browser data?

05 How can I request a copy of my slotdadu data?

06 Can I ask slotdadu to correct my account data?

07 How long does the Privacy Policy allow records to stay?

Related Pages