Reference

567luk Privacy Policy for Indonesia Accounts

Our Privacy Policy explains how 567luk handles your account details, phone verification, device sessions and wallet records when you use the lobby in Indonesia.

Account dataWallet recordsDevice sessionsPolicy access
567luk 567luk Privacy Policy for Indonesia Accounts
CONTACT ROUTES

DANA Status Help Under Privacy Policy

A clear contact path matters when a Privacy Policy question is tied to a live account event.

Account access Ask us to explain account data connected with phone verification, sign-in events or a…
Wallet receipt For DANA, OVO, GoPay or QRIS records, provide the transaction reference rather than sharing…
Mobile session If your phone browser returns to the login screen or a device record looks…
DATA PRACTICE

How Dragon Tiger Data Stays Account Linked

We handle Privacy Policy requests through the same account controls that protect access to Dragon Tiger, Slots and other lobby areas.

Data handling

We collect account, verification, device and transaction references needed for access, security and support. We do not need the contents of your phone to connect a login with a recorded account event.

Cookies

Cookies and similar browser storage can keep a session working between account screens. You can clear them in your browser settings, though signing in again may be required afterward.

Account security

Phone verification, login records and device signals help us investigate an unusual sign-in. Never send us a password, wallet PIN or full security code when asking about Privacy Policy.

Retention

We retain account and transaction records for as long as needed for account operation, security checks, dispute handling and legal duties. The period can differ by record type and local requirements.

Who to contact

Send a data question through the support route connected with your account. Include your registered contact detail and request type so we can locate the correct record without unnecessary wallet information.

Request changes

You may ask us to correct an inaccurate account detail, explain a stored record or clarify a data use. We may verify account ownership before making a change.

Privacy Policy Answers for DANA Accounts

These Privacy Policy answers focus on the questions we expect when you connect an Indonesian wallet, use a mobile browser or request help with account data. They explain the practical next step without asking you to share more personal detail than necessary.

It covers account creation, phone verification, login and device records, wallet references, support messages, cookies and retention. It also explains how to ask about, correct or clarify data linked to your account.

Do not send a DANA password, wallet PIN or security code to us. Our records may include a transaction reference and status needed for account support, but your private wallet credentials should remain with you.

A mobile browser can create session, device and security records when you sign in. These details help us identify unusual access and keep the correct account connected without reading your phone contents.

Contact us through the account support route and state which record needs correction. We may ask for account ownership checks before changing a phone detail, contact detail or other stored account field.

Retention depends on the record and the reason it was created. Transaction references may remain for account operation, security, dispute handling and legal duties, with periods shaped by local requirements.

Yes, send a clear data request through support and identify your account contact detail. We will explain the available request path and may verify ownership before discussing private account records.

Yes. The policy applies when OVO or GoPay activity is connected with your account, including payment references and status checks. Access and eligibility depends on local law and where local law permits.