Reference

Privacy Policy for Baccarat and Wallet Data

Baccarat, Fa Chai, Football Strike, Aviator, Bingo and Fishing War activity creates account data we use to run your wallet, verify access and answer privacy requests.

Account data handlingUPI and wallet recordsCookie controlPrivacy request path

Browse the lobby Read FAQ

How dl22 Handles India Privacy Duties

dl22 Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

Your account data can include your name, mobile number, email address, login history, device type, IP address, cookie IDs, gameplay records for Baccarat or Aviator, and payment confirmations from UPI, Paytm, PhonePe or Google Pay. We use this data to create your account, protect access, process

1
wallet activity, answer support requests, check unusual behaviour and meet legal duties that apply to our operations. We do not sell your personal data. We share limited data only with payment partners, hosting vendors, security tools, support systems or public authorities when a valid request applies.
2
If access or eligibility is discussed, it depends on local law and is available where local law permits. Retention periods vary by record type, legal need and account activity, and you can ask us to correct or update your data where the law allows.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

CONTACT PATHS

Privacy Help for UPI Records

Privacy requests work faster when you contact us from the email or mobile number linked to your account.

HANDLING CARE

Cookies, Security and Account Data

We keep privacy handling close to the way your account actually works. Login checks, wallet movement, live table activity and support chats create different records, so each record type has its own…

Data we collect

We collect account details you give us, device and login signals, wallet records, support chat history and game activity such as Baccarat rounds or Fishing War sessions when they relate to your account.

Why we use it

We use your data to open and maintain your account, verify payment activity, protect access, answer your questions, manage cookies and meet legal requests that apply to our service in permitted regions.

Cookie choices

Cookies remember session status, language preference, security flags and basic device signals. You can adjust browser settings, though some account functions may need cookies to keep your logged-in session working.

Security checks

We apply login alerts, device matching and payment-reference checks to reduce account misuse. If a privacy request involves sensitive data, we verify your identity before sharing or changing records.

Retention approach

We keep records only for the period needed for account service, dispute handling, legal duties, security checks or payment reconciliation. Some wallet records may remain after closure if law requires it.

Request handling

You can ask for access, correction, deletion or restriction where applicable. Send clear details through email or chat, and we will explain what can be changed after verification.

Privacy Questions Before You Join

These answers focus only on privacy handling for your account, wallet, device and support data. If your question involves eligibility, access, payment records or location, we will check the relevant account context before replying. For anything personal, contact us through the linked email or in-account chat so we can verify you safely.

We collect the details you provide, such as name, mobile number, email address and login credentials, plus device signals, IP address, wallet activity and game records linked to your account sessions.

We need payment references to match deposits and withdrawals with your wallet, resolve failed transfers, prevent account misuse and answer your privacy questions about stored payment records.

Cookies help keep you logged in, remember basic preferences and flag unusual access attempts. You can manage them in your browser, but some account actions may need session cookies to work.

Yes, you can request correction of data that is inaccurate or outdated. We may ask for identity checks and supporting details before changing profile, contact or payment-related records.

Retention depends on the record type. We keep data for account service, payment reconciliation, security checks, dispute handling and legal duties, then remove or reduce it when it is no longer needed.

Only teams and vendors that need the data for support, security, payments, hosting or legal handling can access it. Each access is limited to the task being handled.

Access and eligibility depend on local law and are available where local law permits. Privacy rights may also vary by region, so we check your request against the rules that apply.

Privacy Policy for Baccarat and Wallet Data

Privacy Help for UPI Records

Cookies, Security and Account Data

Data we collect

Why we use it

Cookie choices

Security checks

Retention approach

Request handling

Privacy Questions Before You Join

01 What account data do you collect when I join?

02 Why do you need UPI, Paytm or PhonePe data?

03 How do cookies affect my privacy on dl22?

04 Can I ask you to correct my account data?

05 How long do you keep my account records?

06 Who can see my data inside the service?

07 Does privacy access depend on my location in India?

Related Pages