Reference

duniaselot777 Privacy Policy

Our Privacy Policy explains how duniaselot777 collects, uses and protects your account, device and payment details when you access Blackjack, Mines or other lobby areas.

Clear data purposesWallet detail handlingYour request optionsLocal access wording
duniaselot777 duniaselot777 Privacy Policy
REQUEST HELP DIRECTLY

Contact Us About Your Privacy Policy

A clear contact route matters when you need to ask about the Privacy Policy, correct account data or question a wallet record. Use the support path attached to your account and include the phone number or account identifier already linked to your access. That lets us locate the relevant record without asking you to send a full payment credential.

Team online

Account privacy request

Ask us to explain a data use, correct a phone detail or clarify why verification is connected to access. We use the account path so your request stays linked to the right record.

Wallet data question

For DANA, OVO, GoPay or QRIS references, send the receipt reference and date rather than your PIN or one-time code. We can check the status without requesting secret wallet credentials.

Access concern

If a sign-in or phone-verification step appears unfamiliar, contact us through the account help route before continuing. We may ask for account details needed to confirm that the request is yours.

DATA HANDLING DETAILS

Browse How We Handle Your Privacy

Our Privacy Policy is supported by practical controls rather than broad promises. We separate account credentials from payment references, use session and device details to identify unusual sign-in activity, and keep access…

Account data

We collect details needed to create and maintain your account, including contact data and phone-verification status. These records help us connect your sign-in to the correct account without exposing another person’s details.

Device signals

When you sign in from a mobile browser or desktop, we may record session, browser and device signals for access security. These signals help us spot unusual activity around your account.

Cookies

Cookies and similar browser storage can keep a session active, remember basic preferences and support security checks. You can adjust browser controls, though some account steps may then need to be repeated.

Payment references

We use transaction references, timestamps and status details to match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We do not ask for your wallet PIN or one-time code.

Retention

We retain account, security and transaction records for as long as needed to provide access, resolve disputes, protect the service and meet applicable legal duties. Removal timing can differ by record type.

Your requests

You may request access, correction, clarification or deletion of eligible data through our support route. Include your account identifier, and we may verify ownership before changing or releasing account details.

Find Privacy Policy Answers Quickly

These Privacy Policy answers address the account steps you are most likely to meet from Indonesia, from phone verification to wallet status checks. We keep each answer practical so you know what data may be used, which request route to take and when local rules affect access.

It covers data collected when you create an account, verify your phone, sign in, use the lobby or contact support. It also explains cookies, device signals, payment references, retention and your request choices.

Phone verification helps connect access to the correct account and supports account security. We record its status and related account details, but you should never send us a one-time code through support.

Yes. We may use transaction references, timestamps and status records for DANA, OVO, GoPay and QRIS. We use these details to match activity, not to request your wallet PIN.

You can request a correction through the account support route. Include your account identifier and describe the incorrect field. We may verify ownership before changing the record connected to your access.

Cookies may keep your session active, remember basic settings and support security checks. Browser controls can restrict them, but sign-in or phone verification may need to be repeated afterward.

Retention depends on the record and its purpose. We keep account, security and transaction details for service, dispute handling, protection and legal duties, then remove or restrict them when no longer needed.

You may ask for deletion of eligible data through our support path. Some account, security or transaction records may need to remain for legal duties or dispute handling, and we will explain the reason.