Reference

Legal Terms for 6c2 Access

This page sets out the legal terms that shape your use of 6c2 in India.

India accessRecord requestsAccount checksLocal law

Where Local Law Permits Access

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

Access depends on local law and is available where local law permits in your region. We may store account details, device signals, login history, and transaction records to run the account, check security, and answer requests. Payment records linked to UPI, Paytm and PhonePe can be

1
used to match deposits or withdrawals with the correct account and to resolve errors. We keep only the records we need for operations, dispute handling, tax or accounting duties, or any retention period required by law. If a rule changes, we may update access or record
2
handling without changing the rest of the page. When a restriction or correction applies, we act on it after the relevant checks are complete.

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

CONTACT ROUTES

How to Reach Our Legal Team

If you need a correction, a copy of your records, or a question about access, use the contact paths below.

Legal email Send access, correction, deletion or record questions here. Include your registered name, phone number, and the exact change you want. We compare the message with the account record before we move the request forward.

Form submission Use this when you need a written trail. Add the request date, the account email or phone, and any payment reference if the issue involves UPI, Paytm or PhonePe records.

Support chat Open this path for urgent account locking or a fast check on a legal request already sent. Keep your message short, factual, and tied to the account so we can match it quickly.

DATA HANDLING

Data, Cookies and Account Controls

We handle legal requests with a narrow set of records: account identity, device logs, transaction matching, and the message trail that shows what you asked us to change.

Account data

We keep the details you give when you create your account, plus the changes you make later, so we can run the account and answer legal requests. If a field changes, we keep the earlier record where the law or our audit trail requires it.

Cookies

Cookies and similar tools remember your session, language choice, and security state. They also help us spot repeated logins from the same device, which makes it easier to confirm that a change request is really yours.

Device logs

We may store device time, browser type, and access events to trace unauthorised use or a failed sign-in. These logs are kept only as long as needed for security checks, dispute handling, or any retention rule that applies.

Payment matching

If a legal request touches a transfer, we use the UPI, Paytm or PhonePe reference to match the entry with the account. That helps us resolve duplicate entries, missing credits, or withdrawal checks without guessing.

Change requests

To ask for a correction, deletion, or a copy, contact us from the registered account path and state the exact change you want. If the request affects identity or a stored payment record, we may ask for extra proof first.

Record retention

Some records cannot be removed on demand because local law, tax handling, or account dispute timing may require us to keep them. When the retention window ends, we remove or anonymise the item where the law allows.

Common Questions on Legal Access

These answers cover the legal points people ask about most: what data we keep, how access depends on local law, how to ask for a change, and what happens if a record needs verification. If your request touches identity, payment matching, or a retained record, we may ask for extra proof before we update anything. That keeps the response tied to the account and the correct record trail.

Yes. You can ask for the data tied to your account, such as the details you gave us, device logs, and request history. We send what local law allows and may redact items that belong to another person.

Send the registered name, phone number, and the exact field you want changed. If the change affects a payment record, include the UPI, Paytm or PhonePe reference so we can match it correctly.

Access depends on local law because some regions allow the service and others do not. If the rules change, we may restrict or restore access after checking the current legal position for your location.

Cookies do not decide the request, but they help us recognise your session and keep the account secure while we handle it. That makes it easier to verify that the person asking is the account holder.

We keep records only as long as we need them for account work, dispute handling, audit trails, or any retention period required by law. After that, we delete or anonymise them when the rule set allows.

Use the registered contact route, say which data you want removed, and include any related receipt or message if the item involves a transfer. We may keep a narrow record where the law requires it.

Start with the registered account route, then add the exact change, the date, and any transfer reference if one exists. That helps us route the request to the team that can act on the right record.

Legal Terms for 6c2 Access

How to Reach Our Legal Team

Data, Cookies and Account Controls

Account data

Cookies

Device logs

Payment matching

Change requests

Record retention

Common Questions on Legal Access

01 Can I ask what data you keep?

02 How do I request a correction?

03 Why might access depend on my region?

04 Do cookies affect legal requests?

05 How long do you keep records?

06 What should I send for a deletion request?

07 Who should I contact about a record change?

Related Pages