Reference

Legal terms for India and account use

We keep this page focused on what matters before you open an account: who may access the service, how we use records, and how you can ask for…

India law firstUPIPaytmPhonePe
7sensi Legal terms for India and account use
CONTACT PATHS

Where to send legal queries

If you need a legal response, use the channel that matches your request. Simple corrections can go to email, time-sensitive access issues can go through the in-app form, and record-related requests should…

Policy email Use this for access, correction or deletion requests. Add your account email, the change you want and the dates that matter. We reply after we verify you own the account and can act on it.
In-app form Send a quicker request from inside your account when you need a status update or need us to note a legal concern. It keeps the conversation tied to your profile and helps us trace the request history.
Written request Use a written request when you need a formal record for dispute handling or statutory retention questions. We will ask for proof of identity, then confirm what we can share, correct or keep.
RECORD CARE

How we handle your records

We keep legal handling narrow: only the data needed for account operation, payment verification, dispute review and statutory retention stays in active use.

Data handling

We collect account details, login logs and transaction trails only when they are needed to run the account, confirm a payment or answer a legal request. We avoid extra fields unless a law or verification step asks for them.

Cookie choices

Cookies remember your session, language and device state. They do not replace account checks, and you can clear them in your browser. If you do, some pages may ask you to log in again before they load private details.

Account security

Your password, one-time codes and recovery details stay linked to your profile. We use them to block unauthorised access, and we may pause a request if the login pattern looks unusual until ownership is confirmed.

Retention

We keep records for as long as the law, a dispute or an audit trail requires. After that period, we delete, mask or archive them so only the minimum data remains available for the next lawful step.

Change requests

If you want a correction, write the exact field, the correct value and any supporting proof. We check the record against your account and reply with the outcome, or explain why a change cannot be made yet.

Contact trail

Every legal request gets a reference so you can follow the thread later. Keep that number with your email copy, because it helps us reopen the same case without asking you to repeat the full history.

Questions on access and data

These questions cover access, data use, retention and the way we handle correction requests. We keep the answers short so you can check what applies before you open an account or send a legal query. If a rule depends on your state, your device or a local law, we say so plainly. When a step needs ownership proof, we explain what we need and why.

Access depends on local law and any location-specific restriction in force at the time. If a state or territory is not permitted, we keep the service closed there and show the same rule on the account screen.

We keep the details needed for login, verification, payment traceability and dispute handling. That can include device logs, ticket history and transaction entries, but only for the period required by law or an active case.

Yes. Send the exact field, the correct value and proof where needed. We check the record against the account, then confirm the change, explain the hold or tell you if another legal step is required.

Cookies remember session state, language and a few device preferences. They help the page load the right account view, but they do not replace login checks. If you clear them, you may need to log in again.

Use the contact path on this page and say which record you want to access. We may ask for identity proof before we send anything sensitive, then we reply within the time allowed by law.

Our policy team handles it after the request is logged. We keep the reference number, note the channel you used and reply through that same route unless the law asks for a different method.