Reference

Privacy choices for your India account

Speed Baccarat, Fortune Rabbit and Football Strike sit behind an account flow where we explain what data we collect, why we use it and how you can ask…

India account dataUPI privacy contextCookie controlsSupport requests

Browse games Read FAQ

How l9ve treats India data

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

This policy explains how we handle the data you share when you create an account, verify your wallet, use UPI, Paytm, PhonePe or Google Pay, contact support, set login security or ask us to correct a record. We collect only what is needed to run your

1
account, meet payment checks, keep the lobby session stable and respond to privacy requests. Access and eligibility depend on local law and are available where local law permits, so some account steps may differ by state or device. We may retain records needed for dispute handling,
2
safety checks, tax or payment obligations, then remove or anonymise data when it is no longer required. If a third party helps with payments, identity checks, hosting or analytics, we require that work to stay tied to the stated purpose.

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

CONTACT PATHS

Privacy contact routes for India

Privacy questions need a clear route, not a maze. Use the channel that matches your request, include the email or mobile number linked to your account, and avoid sending card images or…

Email privacy desk Write to the privacy desk when you want a copy of account data, a correction, or deletion where law allows. Include your account email and a short reason so we can route it properly.

Live chat handoff Start in chat if your privacy question is tied to a current login, device issue or wallet check. The agent can create a case and move sensitive follow-up to email when needed.

Wallet query route For UPI, Paytm, PhonePe or Google Pay records, share the transaction reference and date only. We use those details to match payment data without asking for screenshots unless required.

ACCOUNT CARE

How we manage account data

We treat privacy as part of routine account operations. Login events, payment checks, cookies and support cases each have a different purpose, so they are not all kept for the same period.

Data collection scope

We collect account details, device signals, payment references and support messages only for stated account purposes. Speed Baccarat or Crash Game sessions may create logs, but those logs are used for settlement, security and dispute checks.

Cookie choices

Cookies help keep you signed in, remember language choices and measure page errors. You can clear them in your browser; some account functions may ask you to log in again after removal.

Payment privacy

UPI, Paytm, PhonePe and Google Pay data is used to match deposits, withdrawals and failed payment cases. We do not ask you to post full bank details in chat for routine checks.

Account security

We use verification prompts, session checks and restricted staff access to reduce unauthorised account changes. If you suspect a login problem, contact support so we can lock sensitive edits while checking.

Retention schedule

Some records must remain for payment disputes, fraud checks, tax duties or legal requests. When those reasons end, we delete, anonymise or separate data from active account tools.

Request handling

To update or remove data, send a request from your account email or verified mobile number. We confirm identity first, then reply with the action taken or the reason for any limit.

Privacy Policy questions for your account

These answers cover the privacy questions we receive most often from you in India. They focus on what data is collected, how payment records are handled, how cookies work and how to reach us when you want a change. If your request depends on location, access remains subject to local law and available only where local law permits. Keep your account email updated so replies reach you.

We collect the details needed to run your account: name or contact fields you provide, login events, device signals, wallet references and support messages. Game-session logs may also be stored for settlement and dispute checks.

Payment references help us match deposits, withdrawals, failed transfers and refund checks. We use the reference, amount, time and provider name; avoid sending full bank screenshots unless support specifically asks.

Yes. Send the request from your account email or verified mobile number. We will confirm identity, compile the data we can share, and explain if any record must stay restricted for legal reasons.

Cookies keep your session active, remember basic preferences and help us spot broken pages or unusual login patterns. You can remove them in your browser, but account pages may ask for a fresh login.

Retention depends on the record type. Support chats may be shorter, while payment, tax, security or dispute records may need to remain longer before deletion, anonymisation or separation from live account tools.

Contact us from your verified email or mobile number and state the data you want changed. If deletion is allowed, we act on it; if not, we explain the legal or payment reason.

Yes. Account access and eligibility depend on local law and are available where local law permits. Privacy requests still receive a response, but some account actions or data uses may vary by location.

Privacy choices for your India account

Privacy contact routes for India

How we manage account data

Data collection scope

Cookie choices

Payment privacy

Account security

Retention schedule

Request handling

Privacy Policy questions for your account

01 What personal data does l9ve collect?

02 How are UPI, Paytm and PhonePe records used?

03 Can I ask for a copy of my data?

04 How do cookies affect my privacy?

05 How long do you keep account records?

06 How do I correct or delete details?

07 Does location affect privacy access?

Related Pages