Reference

Open your legal starting point

Your n53 account terms, privacy choices, cookie settings and India payment records are gathered on this Legal page so you can understand the rules before you open your…

India legal termsPrivacy choicesCookie controlsUPI record contextEligibility by law
n53 Open your legal starting point
REQUEST ROUTES

Switch to the right legal contact

Legal questions need the right channel because account records, payment references and identity checks can contain private data.

Email legal desk Write to [email protected] with your account email, date of issue and any UPI, Paytm or PhonePe reference. We use that trail to route your request without exposing private details in chat.
Logged-in help panel Use the account help panel for term, access or privacy questions tied to your profile. The team can confirm identity first, then pass a legal request to the correct queue.
Record copy request If you need a copy of account records, send the request from your account email. We may ask for extra checks before releasing data linked to payments or device sessions.
DATA PRACTICE

Browse how we handle your records

Every rule on this page maps to a record we can locate: consent, cookie choice, login event, payment reference, account action or support message.

Data handling

We collect account, device, session and payment record data only for stated account, security, settlement and legal reasons. Internal access is role-based, with checks for staff actions that touch private records.

Cookie choices

Cookies help keep you signed in, remember consent choices and detect repeated failed access attempts. You can change browser settings, though some account and security functions may not work fully after blocking them.

Account security

Login checks, one-time codes and device signals help protect your account against unauthorised access. If an access pattern looks unusual, we may pause account changes until identity checks are complete.

Record retention

We keep records for legal, tax, fraud prevention, dispute and settlement needs, then delete or anonymise them when retention reasons expire. Some payment records must stay longer under applicable rules.

Contact ownership

Legal and privacy requests go through named queues so your message reaches people allowed to handle that data. Customer care can help you choose the route but cannot bypass verification.

Correction requests

You can ask us to correct outdated profile details or explain why a record cannot be changed. We answer from the same channel used for verification to reduce impersonation risk.

Browse legal questions before joining

These answers cover the Legal page only: account terms, privacy rights, cookies, record access and contact routes. They are written for India readers who want to know how the account relationship works before joining. If your question depends on location, payment trail or identity checks, we may need to see your account context before giving a final answer.

The account terms explain eligibility, wallet use, payment records, offer rules and dispute handling. Access depends on local law and is available where local law permits, so check your location before joining.

We use personal data to create and manage your account, verify access, process payment records, answer legal requests and meet applicable duties. We do not sell your account data to outside advertisers.

Yes, you can request a copy through the account help panel or [email protected]. We may verify your identity and remove data that belongs to another person before sending any record.

Send the correction request from your account email and describe the field that needs updating. Some records, such as payment references or past account actions, may be kept as created for audit reasons.

Payment references are kept to match wallet activity, resolve disputes and meet legal or tax duties. They are not treated as a separate account contract, and access is limited to approved internal roles.

Cookies remember consent choices, support login security and help us detect repeated failed access attempts. You can adjust browser settings, but blocking required cookies may affect account and security functions.

Start with [email protected] or the logged-in help panel, depending on whether you can access your account. We assess the account record, payment trail and relevant terms before replying.