Reference

2ess3 Legal Terms for India Access

This page explains how your account, data, payments and access are handled on 2ess3 in India.

IndiaLocal lawUPIData records
2ess3 2ess3 Legal Terms for India Access
CONTACT ROUTES

How to reach the legal team

For legal requests, corrections or access questions, start from the contact tools in your account.

Email request Send the request from the email linked to your account and add the subject you want handled. We use that trail to verify identity, log the request and reply in writing with the next step.
In-account message Open the help form after you sign in if you need a correction, access check or account status update. That route keeps the request tied to your profile and cuts delays from mismatched details.
Postal request If local law or your own record-keeping needs a signed letter, use the postal address shown inside your account footer. We keep the letter with the same file as your payment and access records.
DATA CARE

How we handle your records

We keep only the records needed to run an account, settle payments, answer disputes and meet legal duties.

Data handling

We store profile details, payment trails, support messages and device logs only for account operation, dispute handling and legal duties. Each record stays tied to the same profile so we can trace changes without mixing accounts.

Cookies

Cookies keep you signed in, remember language choice and support fraud checks. They do not replace your account record; they sit beside it so the site can load faster and keep sessions stable.

Account security

We expect you to protect your password and device access. If a login looks unusual, we may pause sensitive changes until you confirm the action through the contact route linked to your profile.

Retention

We hold records only as long as needed for settlement, dispute work, security checks and legal duties. After that, we delete or de-identify the parts that no longer need to stay linked to you.

Change requests

If you want a correction, send the exact field, the right value and proof that matches the profile. We update what the law allows and keep the earlier record only where retention rules require it.

Contact owner

For any legal request, use the same email or phone number tied to the account so we can verify you quickly. If a request needs extra review, we reply with the next step in writing.

Questions on access and records

These answers cover the main legal requests around your account, your data and who can contact us. If a request touches payments, dispute files or a location-based restriction, we may need extra identity checks before we act. Local law can also change what we can share or delete, so we handle each request against the current rule set.

Yes. Send a request from the email or phone number tied to your account and ask for the record you want to see. We will confirm identity first, then share what local law allows us to release.

Yes. If a profile field is wrong, tell us the exact change and include matching proof. We update the live record where the law allows and keep older copies only when retention duties require them.

Yes, you can ask for closure. We will close the account once we finish any pending checks, settlements or disputes, then keep only the records that local law says must stay on file.

Payment records stay on file for settlement, security and dispute handling. That includes entries linked to UPI, Paytm, PhonePe or Google Pay, plus the timestamps and status markers needed to match each transaction.

The account holder should send the request through the contact route linked to the profile. If someone else writes to us, we may refuse or ask for proof before we share anything.

Access depends on local law, and the same rule applies to state-level restrictions or any order that affects your location. If access is paused, we will show the reason we can share and the next permitted step.

Only when needed to run the account, process a payment, meet a legal duty or answer a dispute. We do not hand out records casually; each disclosure follows the purpose tied to the request.