Reference

2jz legal terms for India

This page explains how we handle legal access, data use, cookie handling and account changes when local law permits.

Local lawData useAccount recordsCookies
2jz 2jz legal terms for India
REQUEST PATHS

Where to send legal requests

If you need a copy, a correction or a formal query about this page, use the path that matches your account record. Sending the message from the email or phone number tied to the account helps us confirm who is asking, and it shortens the back-and-forth. When a request touches UPI, Paytm or PhonePe records, include the date and reference if you have it, so we can locate the right entry faster.

Team online

Email request

Write from the email linked to your account and say whether you want a copy, a correction or a formal legal reply. We use that address to verify the request before we act.

In-app form

Use the form in your account area when you can sign in. It keeps the request tied to the right profile, which helps us avoid mixing your record with another person's file.

Postal notice

If you need a signed notice, send it to the postal address listed on the page with your account email and a clear subject. We process it after matching the record.

DATA AND ACCESS

How we handle data and access

We handle data with a narrow purpose: account access, record keeping, legal requests and security checks.

Purpose limits

We use account data only for sign-in, record keeping, legal handling and security checks. If a new use is needed, we tell you what changes and ask for any step the law requires.

Cookie control

Session cookies help us keep you signed in, remember form steps and spot unusual access. They do not change the policy itself, and you can clear them through your browser settings.

Access logs

Login times, device type and request history help us check for misuse and fix account disputes. We keep these logs for a limited period, then remove or anonymise them under retention rules.

Identity checks

Before we release records or change account details, we may ask for proof that matches the file. That step protects your data and makes sure we update the correct profile.

Change requests

You can ask for correction, deletion where local law permits, or a copy of stored details. Send the request through the account channel so we can verify and track it properly.

Contact trail

If you raise a concern, we keep the message chain with the case record until the matter closes. That trail helps us explain what we changed, what we kept and why.

Questions about rights and records

These answers cover the rights and steps that matter most on this page: copies, corrections, access checks, record timing and the channel you should use. If your situation involves a local rule or a regional exception, we follow the law that applies to you and answer through the contact route linked to the account.

Yes. Send the request from the account email or phone number so we can match the record. If local law permits, we will share the copy after identity checks and remove data that cannot be released.

Tell us exactly which field needs a change and send any proof that supports it. We verify the request against the account file first, then update the record where the law allows.

We ask for proof so we do not release private records to the wrong person or change the wrong profile. It protects your account and lets us process the request with the right context.

We keep records only for the period needed for account operation, dispute handling and legal duties. When the retention window ends, we delete or anonymise what we no longer need.

Yes. If the query involves UPI, Paytm or PhonePe, send the date and reference, if you have it. That helps us trace the entry without exposing other account data.

We log the message, check the record and reply through the same channel unless you ask for another route and local law allows it. If more proof is needed, we tell you what is missing.