Reference

l9l Privacy Policy for Indian Accounts

Our privacy policy explains how we collect account details, wallet references, device signals, and support chats when you open and use l9l.

India account dataCookiesWallet recordsSupport chats
l9l l9l Privacy Policy for Indian Accounts
REACH US HERE

Talk to Us About Data

When you need privacy help, we keep the contact paths simple. Use the same account session for chat, or write from the email tied to your profile so we can confirm it…

In-app chat Open chat from your logged-in account and send the exact privacy request, such as a copy request, a correction, or a question about retention. We use the live session to confirm it is you before we reply.
Email request Write to [email protected] from the email linked to your account, add the date range or payment reference if needed, and say which record you want checked. That helps us locate it without extra back-and-forth.
Account form If you cannot use chat or email, submit the privacy form from your account area. Keep the request short and specific, and we will send the next step after we verify the details.
DATA CARE PATH

How We Keep Records Clear

We keep privacy handling practical: collect the account fields you enter, the device and cookie signals needed to run the session, and the wallet trail needed for audits or disputes.

Collection

We store the details you enter when you create the account, verify a payment, or ask for help. That usually means contact fields, login history, and transaction references, not extra personal data we do not need.

Cookies

Cookies and similar signals help us keep you signed in, remember session state, and spot unusual access. You can clear them in your browser, but some parts of the account flow may ask you to sign in again.

Security

We use password checks, device signals, and session timing to reduce unauthorised access. If you contact us about privacy, we may ask for matching account details before we share anything or apply a change.

Retention

We keep records only for the time needed to run the account, settle disputes, meet legal duties, or complete financial checks. After that period, we delete or archive them according to the case and the law.

Requests

You can ask for a copy, correction, or deletion of eligible data by contacting support from the email tied to your account. If a request conflicts with a legal hold, we will explain the limit.

Contact

For privacy matters, send the request through chat, email, or the account form, and include the date range if you want a narrower search. That helps us answer with the right record set.

Privacy Questions You May Ask

These answers cover the main privacy points: what we collect, why we keep it, how cookies and device signals work, and how you can ask for a copy or correction. If your request depends on local law, we check the rules that apply to your account and reply within those limits. Use the same support path for account changes, payment references, or any question about retention.

We collect the details you type into the account form, the login and device signals that help us secure the session, and any wallet reference tied to a deposit, withdrawal, or support query. We keep only what the process needs.

Cookies help us remember your session, keep the page state steady, and understand whether a login looks unusual. You can clear them in your browser, but you may need to sign in again after that.

Payment records let us match UPI, Paytm, PhonePe, or Google Pay entries to your account, check status, and answer later if there is a mismatch. We do not use those references for anything outside account handling.

Yes. Send the request through chat, email, or the account form, and tell us what you want copied or changed. We may ask for matching account details before we act on the request.

We keep records for the period needed to run the account, settle disputes, meet legal duties, and complete financial checks. When that period ends, we remove or archive the record set as required.

Use [email protected], in-app chat, or the account form and include the subject, date range, and any payment reference. That gives us enough context to route your privacy request to the right team.