Reference

lurus4d Privacy Policy for Your Account

lurus4d Privacy Policy explains what we collect when you open an account, verify your phone and move between Live Casino, The Dog House Megaways and Football Betting.

Account dataWallet statusMobile cookiesPolicy requests

Browse Our Lobby Read FAQ

Know What DANA And QRIS Data We Use

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

We apply this Privacy Policy to the account details you provide, the phone verification step before access, login activity, device signals, selected lobby pages and payment status. When you choose DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we use the transaction reference and

1
status needed to match your account and resolve a receipt question; we do not ask for your wallet password. Cookies can keep your session and language settings working on a mobile browser or desktop. We retain records for the period needed for account security, dispute handling
2
and legal duties. Access to lurus4d and any related processing depends on local law, and where local law permits, you may ask what we hold, request a correction or ask us to remove data that we no longer need. The current policy text applies when you
3
use the site, and changes will be shown through the policy page or account contact route.

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

REQUEST SUPPORT

Get A Clear Route For Privacy Requests

A privacy question should not be mixed with a stalled wallet receipt. We separate account access, payment-status and data requests so our team can locate the right record without asking you to repeat unnecessary details. From a signed-in mobile browser or desktop session, use the contact route shown in your account area; include your account phone number and request type, but never send a wallet password.

Team online

Account data path

Use the signed-in account contact route to ask about collected details, phone verification records or a correction. We may ask for account checks before discussing personal data.

Wallet status path

For DANA, OVO, GoPay or QRIS receipt questions, include the payment rail, transaction reference and date. We use those details to separate a status check from a wider data request.

Privacy change path

Ask us to amend, provide or remove eligible account data through the policy contact route. We assess the request under local requirements and explain any record we must retain.

DATA PRACTICE

Keep Account And Device Data In View

Our privacy work follows the same account steps you see on the site: phone verification, a signed-in session, wallet status matching and access from your chosen device.

Collected account details

We may hold your account name, phone number, verification result and login events.

Mobile and desktop signals

A mobile browser can create session, language and device records while you move from login to Live Casino or Fishing…

Cookie choices

Cookies can remember a signed-in session and basic display settings.

Account protection

Phone verification, login event checks and limited internal access help protect account records.

Retention approach

We keep account, security and payment references only as long as needed for the stated purpose, dispute handling or legal…

Changes and contact

You can ask for access, correction or eligible removal through the account contact route.

Privacy Policy Answers Before Account Access

These Privacy Policy answers cover the questions we expect before you open an account or connect a local wallet. They explain account records, cookies, payment references, mobile access and the route for asking us to change or provide your data. If your question involves eligibility, access depends on local law, and our account contact route can help clarify the next step.

It covers account details, phone verification, login events, device signals, cookies, lobby activity and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use your phone number for the account path and the verification step before access. It also helps us match a genuine account with a privacy, login or payment-status request.

No. We use payment references and status details to match a transaction, not your DANA, OVO or GoPay wallet password. Never place a wallet password in a support or privacy message.

Cookies can keep your signed-in session and basic display settings available while you use a mobile browser. Blocking them may interrupt continuity between login, the lobby and your account area.

Where local law permits, you can request access to eligible account data through the contact route shown after sign-in. We first check account ownership before preparing a response.

Yes, you can ask for a correction or eligible removal through the policy contact path. We assess the request against local requirements and explain any security or payment record that must remain.

The policy remains available for reading, while account access and related processing depends on local law. Where local law permits, contact us from your account area with a specific privacy question.

lurus4d Privacy Policy for Your Account

Get A Clear Route For Privacy Requests

Account data path

Wallet status path

Privacy change path

Keep Account And Device Data In View

Collected account details

Mobile and desktop signals

Cookie choices

Account protection

Retention approach

Changes and contact

Privacy Policy Answers Before Account Access

01 What does the lurus4d Privacy Policy cover?

02 Why does lurus4d need my phone number?

03 Does the Privacy Policy record my wallet password?

04 How do cookies affect lurus4d on mobile?

05 Can I ask lurus4d for a copy of my data?

06 Can I request a correction or removal under this Privacy Policy?

07 Does local law affect access to the Privacy Policy or account?

Related Pages