Reference

Privacy Policy for i610 India accounts

The i610 Privacy Policy explains how we handle your account details, KYC checks, UPI, Paytm, PhonePe and Google Pay records, cookies and device signals before you open an…

India account privacyUPI record handlingCookie choicesData request support

Explore Lobby Read FAQ

How this policy applies in India

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

This policy covers personal data you share with us when you create an account, complete verification, use the wallet, contact support or adjust cookie settings on i610.org. We collect only what we need to run account access, protect the wallet, check identity, process local payment records

1
and answer privacy requests. UPI, Paytm, PhonePe and Google Pay references may appear in transaction logs, receipts and support tickets when you use those options. We do not sell your personal data. We may share limited data with payment partners, identity-check providers, fraud-prevention services, hosting partners
2
and law requests where applicable. Account access and eligibility depend on local law and are available where local law permits, so privacy handling may also reflect India-specific legal duties.

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

CONTACT ROUTES

Contact us about privacy choices

Privacy questions should reach the team that can verify your account and act on the request, not a general inbox that only handles lobby queries.

Privacy inbox Email us from the address linked to your account and describe the privacy request clearly. We check account ownership first, then route correction, export, deletion or cookie-related queries to the right internal queue.

Chat handoff If you start in live chat, ask for a privacy handoff and avoid sending sensitive documents in the chat window. The team will move you to a safer channel when identity proof is needed.

Payment data query For UPI, Paytm, PhonePe or Google Pay records, share the transaction time and account reference, not full bank details. We compare wallet logs with processor records before answering your request.

ACCOUNT SAFETY

How we handle your account data

Our privacy work sits inside the account, wallet and support flow rather than as a separate afterthought.

Account details

We collect details such as name, mobile number, email address, login records and verification status when you open or manage an account. These records help us protect access and answer account-specific privacy requests.

Payment records

Wallet entries may include UPI reference IDs, Paytm or PhonePe timestamps, processor responses and withdrawal checks. We use them to reconcile transfers, investigate mismatches and respond when you ask about payment data.

Cookie controls

Cookies and similar tools help us keep sessions active, remember language choices and detect unusual account behaviour. You can change browser settings, though some security and login functions may not work normally without them.

Security checks

We use device signals, IP records and login patterns to reduce account misuse and unauthorised wallet activity. Access to these records is limited, and any support action needs account ownership checks first.

Retention periods

We keep account, KYC, payment and support records only for business needs, dispute handling and legal duties. When data is no longer required, we delete it or reduce it so it no longer identifies you.

Change requests

You can ask us to correct inaccurate data, export account records or request deletion where allowed. Some records may need to remain for payment reconciliation, fraud checks, disputes or legal requirements.

Privacy Policy questions before you join

Before you open an account, you may want to know what data is collected, how local payment records are handled and how to contact us later. These answers explain the privacy steps we use across account creation, wallet activity, cookie settings and support. They are written for India and should be read with the full policy on this page.

It covers account details, login records, identity checks, wallet activity, payment references, support messages, cookie choices and device signals. We use this data to manage your account, protect access and respond to privacy requests.

We store transaction references, timestamps, processor responses and wallet entries linked to your account. These records help us reconcile payments, investigate errors, process withdrawals and answer your questions about payment data.

Yes. Contact us from your linked email or verified mobile number and explain what needs correction. We may ask for proof before changing KYC, payment or contact records to protect your account.

You can request deletion where the law allows it. Some records may need to remain for payment reconciliation, disputes, fraud checks or legal duties, but we will explain what can be removed.

Cookies help keep you signed in, remember basic choices, support security checks and understand whether pages load correctly. You can change browser settings, but some account and safety functions may be affected.

Only teams that need to handle the request, verify ownership, check payment records or apply a change should access it. We limit internal access and avoid sharing sensitive documents through open chat.

Yes. Access and eligibility depend on local law and are available where local law permits. Privacy handling may also reflect India-specific duties for payment records, identity checks, disputes and lawful requests.

Privacy Policy for i610 India accounts

Contact us about privacy choices

How we handle your account data

Account details

Payment records

Cookie controls

Security checks

Retention periods

Change requests

Privacy Policy questions before you join

01 What personal data does the Privacy Policy cover?

02 How are UPI, Paytm and PhonePe records handled?

03 Can I ask i610 to correct my account data?

04 Can I request deletion of my data?

05 Why does the site use cookies?

06 Who can see my privacy request?

07 Does local law affect account access and privacy handling?

Related Pages