Reference

Legal terms for India access

This page explains how n02 handles legal access, account records, and request paths for India.

India accessLocal lawAccount recordsRequest trail

Jurisdiction, records, and change rules

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

Our legal terms apply to the account you open on n02.club, the messages you send, and the records we keep for administration and checks. Access depends on local law and is available where local law permits, so the page you see is the one that controls

1
the current process for your region. If the law or our internal process changes, we update this text and use the new version from that point onward. We may ask for a name check, contact check, or document check before we accept edits to profile data,
2
withdrawal routing, or request history. When a UPI, Paytm, PhonePe, or Google Pay entry appears in your account, we keep the related record for reconciliation, dispute handling, fraud checks, and audit duties where they apply. After the retention period ends, we remove or anonymise the record.

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

REQUEST ROUTES

How to send a legal request

If you need help with access, a correction, or a written record of a legal question, use the routes below.

In-account form Send access, correction, or closure requests from the account area so we can tie the message to your profile, keep an audit trail, and reply with the exact change we can make after checking the details.

Written thread If you need a paper record, continue the conversation in the support inbox we show inside the account. That keeps the same reference number attached to the request from start to finish and avoids duplicate replies.

Region check When a legal question depends on where you are, we may ask which Indian region is linked to the account and what date the issue started. That helps us answer with the right policy text and process.

RECORD SAFETY

How we handle records and access

We treat legal handling as part of account care, not a separate formality. Cookies help us remember session state and security checks; device and login records help us spot unusual access; and…

Data map

We link account details, login events, and relevant request history so we can prove who asked for what and when. That record helps us handle disputes, correct errors, and keep the policy trail consistent for your account.

Cookie use

Cookies store session and language state, keep you signed in, and help us know when a check is needed again. Clearing them may end the session and ask for a fresh verification step on the next visit.

Account security

If access looks unusual, we may pause the request until the password, device, or contact detail is confirmed. That protects your account before we accept changes to personal or payment records and keeps the audit trail clean.

Record retention

We keep records only as long as needed for account administration, dispute handling, fraud checks, and duties that apply under local law. After that, we remove or anonymise them in line with our retention process.

Change requests

To correct, export, or close an account record, send a clear request from the account area and include the field you want changed. We may ask for proof before processing it, then confirm the result in writing.

Contact path

For legal questions, write through the in-account message path so the request stays linked to your profile and the region on file. We then answer against the current policy text and keep the thread together.

Questions about access and account rights

These questions cover access, data use, requests, and the way we confirm identity before any change. If you want a copy of a record, a correction, or a policy clarification, start from the account area so we can match the request to the right profile. Access and any service we offer depend on local law and are available only where local law permits.

Access depends on local law and is available where local law permits. If your region is eligible, we show the current policy text and any extra checks before you move ahead with the account steps.

We keep account details, login events, request history, and relevant payment records so we can run the service, settle disputes, and meet legal duties where they apply. We do not hold data without a stated purpose.

Yes. Send the change request from the account area, name the field that is wrong, and add any proof we ask for. We confirm the request before we update the record, so the trail stays clear.

We retain records only for the time needed for account administration, error handling, dispute resolution, fraud checks, and any legal duty that applies. After that, we remove or anonymise them in line with our process.

Cookies help keep the session active, store language choice, and support security checks. If you clear them, some pages may ask you to verify again before the account opens or a request is accepted.

Use the in-account message path and say which record you want copied. We may ask for identity confirmation first, then share the data that the policy allows us to provide in response to your request.

When we update the text, the latest version on the site controls the process from that point onward. We keep the page current so you can check what applies now and send questions against it.

Legal terms for India access

How to send a legal request

How we handle records and access

Data map

Cookie use

Account security

Record retention

Change requests

Contact path

Questions about access and account rights

01 Who can access n02 from India?

02 What records do you keep?

03 Can I correct my account details?

04 How long do you retain data?

05 Do cookies affect my access?

06 How do I ask for a copy of my data?

07 What if the policy changes?

Related Pages