Reference

n160 legal terms for India access

These legal terms explain how we handle your account data, cookies and request flow on n160, including what we keep, what we can change and where your request…

India accessData useCookie rulesAccount requests
n160 n160 legal terms for India access
REQUEST CHANNELS

Where to send legal requests

If you need a legal correction or data request, use the channel that fits the record you want to create.

Email Send your request from the email linked to your account, add the account ID and say whether you need a data copy, a correction or a closure request. We reply with the next step and any identity check needed.
Live chat Use chat when you want a quick status check on a legal request. Keep the question specific, and we will tell you if the file is waiting on identity confirmation, a record search or a policy decision.
Support form The form is useful when you want a dated request with attachments. Add screenshots, date ranges or the exact field you want changed, and we route it to the team that handles records and account changes.
DATA HANDLING

How we handle data and cookies

We handle legal data in small, readable steps. Access logs, device signals, cookie records and support messages are stored only for account control, security checks, issue handling and local legal duties.

Data handling

We keep only the data needed to run your account, confirm requests and match payment references. If you ask why a field is stored, we can explain the reason and tell you whether the law requires us to keep it longer.

Cookie use

Cookies help us keep you signed in, remember language choices and spot unusual access. They do not need to store your full payment details, and you can ask what cookie data sits against your account record.

Account security

We use account checks when a request changes sensitive details, withdrawal routing or login access. If the request looks unusual, we may ask you to confirm device or contact details before we proceed.

Record retention

Request logs, support transcripts and payment references stay only as long as needed for account handling, legal duties and issue resolution. After that, they are archived or removed according to the rule that applies.

Change requests

For corrections, deletion questions or copies of stored data, tell us exactly what you want changed and why. The clearer your request, the faster we can find the right record and answer you.

Contact path

Use the same contact route you used to open the request, so we can link replies to the right account. If you write from another address, we may ask for one more check.

Common legal questions on your account

This section answers the legal questions that usually come before account use. You can check how we store data, how cookies work, who can ask for corrections and what happens when local law changes the access rule in your region. If you need a record change, use the same contact path tied to your account so we can verify it quickly and keep the reply with the right file.

We keep the details needed to run the account, match payment references, answer support requests and meet legal duties. If a field is not needed for those tasks, we do not keep it longer than required.

Yes. Send a request through the support route with your account details and we will tell you what can be shared, what must stay private and whether any identity check is needed before release.

Tell us the exact field, the correct value and any proof that helps us locate it. We check the record, update what the rule allows and confirm the change in the same thread.

No. Cookies help with session state, language and access checks. Payment references sit in the ledger and support logs, not in the browser cookie itself, where they do not belong.

If your location is outside the allowed area, we restrict access there and keep the request path open for account records and legal questions. We follow the rule that applies in that location.

Use email, chat or the support form, whichever matches the record you want handled. Add your account ID and a short explanation, and we will route it to the right team.