Reference

Open n32 legal terms for India

n32 keeps this page focused on the rules that shape your account, data, and access in India.

India accessLocal lawAccount recordsCookie terms

Explore jurisdiction rules and account use

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

We treat access to n32 as jurisdiction-based, so the terms that apply to your account depend on local law and are available where local law permits. If your region or details do not meet the checks we ask for, we may pause access until you fix

1
the record or send the document we request. That keeps the account trail clean and helps us answer legal queries with the right record in front of us. When you use UPI, Paytm, PhonePe, or Google Pay, the matching transaction path stays linked to your account
2
file so support can locate it later. The same rule applies to identity, device, and message logs: we hold only what we need for administration, dispute handling, and the notices you send through support.

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

CONTACT ROUTES

Open contact paths for policy requests

If you want a copy of the terms attached to your account, need a correction, or want us to check a notice tied to your records, send the request through the support…

Email request Use the registered email on your account and send the exact change you want. We use that address to match the request, confirm it is yours, and reply with the next step.

In-app chat Open chat when you need a quick check on access, consent, or a record correction. We keep the thread with your account so our support team can trace the request and follow up cleanly.

Postal notice For formal legal notices, share your full name, account email, and what you need changed. Written requests help us keep an audit trail and route the matter to the right policy contact.

DATA CARE

Switch on data handling controls

We collect only the records needed to run your account, confirm identity, and keep a trace of changes you ask for.

Data use

We use your signup details, session logs, and contact history to verify the account, answer requests, and keep a change trail. We do not use extra fields unless they are needed for a clear legal reason.

Cookies

Cookies help us remember your session, language, and security state. You can clear them in your browser, though some pages may ask you to confirm your details again when you return.

Account security

If we see an unusual login, a device change, or a mismatch in account data, we may ask for a fresh check before access continues. That protects your records and keeps the audit trail accurate.

Record retention

We keep legal and account records only as long as we need them for checks, dispute handling, or local obligations. Once that period ends, we remove them or strip the details that identify you.

Change requests

When you want to correct or update your details, send the exact field and the new value through support. We confirm the request against your account before making the change and note it in the log.

Contact route

If you want a copy of what we hold, ask support from the email tied to your account. We will point you to the correct process and tell you what extra detail, if any, we need.

Open questions on your legal rights

This section answers the common legal points tied to your account: who can access it, what we store, how cookies work, and where to send a correction request. If a local rule changes, the terms that apply to you change with it, and support handles the account record under the latest rule set. Use the support route if you want a copy of your current record.

Access depends on local law and is available where local law permits. You must use accurate personal details and complete any verification we ask for so the account record stays valid.

We keep the details you submit, the checks you complete, message history with support, and session logs that help us confirm changes. We only retain what we need for account administration and legal duties.

Yes. Send the exact field you want changed from the email tied to your account. We may ask for a fresh check before we update the record, especially if the request affects security or access.

Cookies help us remember login state, language choice, and security settings. If you clear them, some pages may ask you to confirm your details again, which is normal and helps keep access safe.

When you use UPI, Paytm, PhonePe, or Google Pay, we keep the matching transaction record with your account history so support can check it later. We do not publish that record, and we use it only for account checks and disputes.

Use the support route in your profile and include your registered name, email, and the exact request. That gives us enough detail to route the notice and reply through the same account trail.

If the law changes in your region, the terms that apply to your account change with it. We will adjust access and record handling to match the new rule set and tell support how to respond.

Open n32 legal terms for India

Open contact paths for policy requests

Switch on data handling controls

Data use

Cookies

Account security

Record retention

Change requests

Contact route

Open questions on your legal rights

01 Who can open an account?

02 What records do you keep?

03 Can I ask for changes to my details?

04 How do cookies affect my account?

05 How do you handle payment records?

06 How can I send a formal notice?

07 What if local rules change?

Related Pages