Reference

How your privacy works on 2o26

Our Privacy Policy explains what account data we collect, why we need it, and how you can ask us to correct, access, or remove it where the law…

Account data explainedKYC records handled carefullyUPI, Paytm, PhonePe contextCookie choices included

Explore the lobby Read FAQ

Data rules for India account activity

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

This Privacy Policy applies when you use 2o26.co, create an account, verify your identity, contact our team, use cookies, or make wallet movements through India payment options. We collect data that lets us run your account, process KYC checks, detect unusual access, handle disputes, meet legal

1
duties, and keep records linked to UPI, Paytm, or PhonePe transactions. We do not ask for more than we need for those purposes. Some data may be handled by payment partners, identity-check vendors, hosting providers, fraud-prevention tools, and customer care systems under contract. Your access may
2
depend on where you are located, and availability is subject to local law where it permits account access.

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

CONTACT PATHS

Three ways to reach our privacy team

Privacy questions should reach the right inbox without making you repeat your account story.

Privacy email Email our privacy desk when you want a copy of stored account data, a correction request, or an update on deletion where the law allows it. We may ask brief verification questions before acting.

Live chat handoff Start with chat if your privacy concern is linked to a current login, cookie setting, or wallet record. The agent can move the case to our privacy desk and share a case number.

Document request channel If KYC data needs checking, our team will tell you which document is needed and where to upload it. Do not send identity files through social messages or open comment threads.

ACCOUNT CARE

Six controls around your account data

We handle privacy as part of the account flow, not as a separate afterthought. The checks below explain how data moves from account creation to wallet use, play records, cookies, security alerts…

Data minimisation

We ask for details tied to account creation, KYC, wallet use, fraud checks, and customer care. If a field is not needed for those purposes, we aim to avoid collecting it.

Cookie control

Cookies help keep you logged in, remember basic choices, and read device signals for security. You can clear cookies in your browser, though some account functions may ask you to log in again.

Payment record handling

UPI, Paytm, and PhonePe references are stored with account activity so deposits, withdrawals, refunds, and disputes can be traced. We do not display full sensitive payment credentials in your account area.

Session and device checks

We may record IP address, device type, browser, location signals, and login time to detect unusual access. These records help us secure your account and support privacy requests linked to access history.

Retention rules

Some records must be kept for legal, tax, fraud-prevention, dispute, or payment reasons. When retention is no longer needed, we delete, anonymise, or restrict data according to our internal schedules.

Correction requests

If your name, email, mobile number, or KYC detail is wrong, contact us with the correct detail. We will verify the request before changing account records or asking for fresh proof.

Privacy Policy questions before you join

These answers explain how our Privacy Policy works in practical account situations. They cover data access, corrections, cookies, payment records, identity checks, and privacy contact steps for India. If your request involves local eligibility or account access, we apply the rules that match your location and the law that applies.

We may collect your name, email, mobile number, date of birth if required, KYC details, login records, device signals, payment references, play activity, cookie choices, and messages you send to support.

KYC details help us verify account ownership, prevent misuse, process withdrawals, answer disputes, and follow legal duties. We ask only through secure account channels and may reject unclear or mismatched files.

Yes. Contact our privacy desk from your account email or mobile number. We may verify your identity first, then share available data in a practical format where the law allows release.

Cookies remember login state, language choices, device checks, and fraud-prevention signals. You can clear or block cookies through your browser, but some account pages may ask for fresh login or verification.

Payment references help us match deposits, withdrawals, refunds, and disputes to your account. We store transaction context, status, timestamps, and partner references, but we avoid showing sensitive credential details in account screens.

Yes. Send the corrected detail through the privacy contact path or support handoff. For sensitive fields, we may ask for proof before updating records so your account history stays accurate.

Deletion depends on legal, payment, tax, security, and dispute needs. If we must keep certain records, we can restrict use where possible and delete or anonymise data when retention is no longer required.

How your privacy works on 2o26

Three ways to reach our privacy team

Six controls around your account data

Data minimisation

Cookie control

Payment record handling

Session and device checks

Retention rules

Correction requests

Privacy Policy questions before you join

01 What personal data does 2o26 collect?

02 Why do you need KYC details?

03 Can I ask for a copy of my data?

04 How do cookies affect my privacy?

05 How are UPI, Paytm, and PhonePe records used?

06 Can I correct wrong account details?

07 When is my data deleted?

Related Pages