Reference

Privacy choices for your l2r account

Our Privacy Policy explains how account details, cookie data, device signals and payment records linked to UPI, Paytm, PhonePe or Google Pay are handled when you open your…

Account dataCookie choicesUPI contextPaytm recordsContact paths

Explore the lobby Read FAQ

How this policy applies in India

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

This Privacy Policy covers the personal data we collect when you create an account, enter the lobby, contact support, set security controls, or use payment methods such as UPI, Paytm, PhonePe and Google Pay. We use those details to run your account, protect access, process wallet

1
activity, respond to your requests, and meet legal or risk checks that apply to our service. Access and eligibility depend on local law and are available where local law permits. We do not ask for more data than we need for these purposes, and we keep
2
retention periods tied to account, payment, security and legal needs. If a law, bank rule or payment partner asks us to keep a record for longer, we apply that requirement only to the relevant record.

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

CONTACT ROUTES

Three ways to ask about privacy

Privacy questions should reach the team that can see your account trail without exposing extra details.

Account privacy request Send a privacy request from the email or mobile number linked to your account. We use that match to confirm it is you before we share copies, change details, or explain retained records.

Payment record query For UPI, Paytm, PhonePe or Google Pay data questions, include the transaction time and reference if you have it. We check wallet records without asking for card data or app passwords.

Cookie and device help If you want to change cookie choices or ask about device signals, contact support with your browser or app version. We explain which settings can be changed and what may affect account access.

HANDLING STANDARDS

Six privacy controls we use

We handle privacy work as part of account operations, not as an afterthought. That means data requests, wallet checks, cookies, security alerts and retention decisions follow set internal steps.

Account data use

We use your name, contact details and login records to run the account, confirm changes and protect access. These records help us respond to you without exposing data to teams that do not need it.

Cookie handling

Cookies help keep sessions active, remember choices and spot unusual access patterns. You can manage many cookie settings in your browser, though some account security cookies are needed for safe sign-in.

Payment privacy

UPI, Paytm, PhonePe and Google Pay records are used to match deposits, withdrawals and refund queries to your account. We keep references, times and status data, not your app password.

Security checks

Login alerts, device data and verification results help us detect account takeovers and unusual wallet movement. Access to these logs is limited, and support may verify you before discussing them.

Retention periods

We keep account, payment and security records only for operational, legal, tax, dispute and risk needs. When a record is no longer needed, we delete it or remove direct identifiers where suitable.

Correction requests

If your mobile number, email or profile details are wrong, ask us to correct them. We may need proof of control over the account before updating records that affect access or payment checks.

Privacy questions before you open account

These answers explain how the policy works in common account situations. They focus on your rights, the data we collect, how payment records are handled, and how you can contact us. For anything account-specific, we will verify you before sharing private records.

We collect account details such as name, mobile number, email, login activity, device signals, wallet records and support messages. Payment references from UPI, Paytm, PhonePe or Google Pay may also be linked to your account.

Payment data helps match deposits, withdrawals, refunds and failed transactions to the correct account. We use references, time stamps and status records to resolve wallet queries and meet legal or payment partner duties.

Yes, you can request a copy of account-linked data through the privacy contact path. We will verify your identity first, then share data that can be disclosed under applicable law and account security rules.

You can ask us to correct profile details such as email, mobile number or spelling errors. For changes that affect login or wallet access, we may ask for extra verification before making the update.

Cookies help keep you signed in, remember settings, measure page performance and protect account access. Some cookies can be changed through your browser, while security cookies may be needed for safe account use.

Access is limited to team members and service partners who need records for support, payment processing, security checks, legal duties or account operations. We do not open private records for unrelated internal use.

Use the privacy request channel from your registered email or mobile number. Add the account detail involved, such as login, cookie, payment or correction request, so we can route it without asking for unnecessary data.

Privacy choices for your l2r account

Three ways to ask about privacy

Six privacy controls we use

Account data use

Cookie handling

Payment privacy

Security checks

Retention periods

Correction requests

Privacy questions before you open account

01 What personal data does l2r collect?

02 Why do you collect payment-related data?

03 Can I ask for a copy of my data?

04 Can I correct wrong account details?

05 How are cookies used on l2r.asia?

06 Who can see my account records?

07 How do I contact l2r about privacy?

Related Pages