Reference

9rt Privacy Policy for India accounts

This Privacy Policy explains how we handle your account details, device data, cookies, and UPI, Paytm, PhonePe references when you use 9rt in India.

India data scopeUPI reference handlingCookie choicesAccount update requests
9rt 9rt Privacy Policy for India accounts
HELP PATHS

Contact paths for privacy requests

Privacy requests need enough detail for us to identify your account without exposing extra data. Use the same phone number or email linked to your account when you write to us, and include the request type in the subject line. We may ask for a short verification step before making changes, sharing a copy, or deleting records that no longer need to be kept.

Team online

Privacy email

Send privacy questions, correction requests, or deletion requests from the email linked to your account. Include your username and the data category involved so we can route the case without asking for unrelated details.

Live chat handoff

Start with chat if you need help finding the right privacy path. Our team can confirm the request type, then move sensitive account matters to email where identity checks are safer.

Account verification

Before we act on a privacy request, we may match your email, phone number, recent login pattern, or payment reference. This helps prevent another person from changing or viewing your account data.

ACCOUNT CONTROLS

UPI and account privacy controls

This section explains how we apply the Privacy Policy inside normal account activity. We keep privacy controls close to the places where data is created: login, wallet, device checks, cookies, and support…

Account details

We collect details you provide during account opening, profile updates, and support contact. This may include your name, phone number, email, login credentials, language preference, and records of privacy requests.

Payment records

UPI, Paytm, PhonePe, and Google Pay references help us match wallet activity with your account. We keep transaction IDs, timestamps, and verification status, not unnecessary payment app passwords or private banking credentials.

Cookies and device data

Cookies and similar files help us remember your session, detect unusual access, and understand device compatibility. You can manage browser cookies, though some account security functions may not work correctly without them.

Security checks

We log sign-in attempts, IP signals, device type, and failed verification events to protect your account. When activity looks unusual, we may pause sensitive changes until you confirm the request.

Retention windows

We keep personal data only for account operation, legal duties, dispute handling, fraud checks, and audit needs. When those reasons no longer apply, records are deleted or separated from direct identifiers.

Change requests

You can ask us to correct account details, receive a copy of data categories, or delete eligible records. We will explain any legal reason if a record must be kept longer.

Privacy answers before you join

These answers focus only on how the Privacy Policy works for your account and data. They cover what we collect, why we keep certain records, how payment references are treated, and how you can contact us. If your request depends on local law, we will explain the outcome in plain language after checking your account details.

We collect account details you provide, login and device data, cookie records, support messages, and payment references linked to UPI, Paytm, PhonePe, or Google Pay. We collect only what is needed for account operation and legal duties.

Payment references help us match wallet activity, confirm transaction status, handle disputes, and detect misuse. We record items such as transaction IDs and timestamps, but we do not ask for private banking passwords.

Yes. Send the correction request from the email or phone number linked to your account. We may verify your identity first, then update details that are wrong or explain why a record cannot be changed.

You can request deletion of eligible personal data. Some records may need to remain for legal, audit, dispute, or security reasons. If we must keep anything, we will explain the category and reason.

Cookies help keep your session active, remember device settings, and detect unusual account access. You can manage cookies in your browser, but blocking all cookies may affect login checks and account security features.

Only team members who need access for privacy handling, verification, legal duties, or technical support can view your request. We limit internal access and keep request records separate from unrelated account activity.

Yes. Some account access, eligibility, correction, deletion, and record-retention outcomes depend on local law and are available where local law permits. We will check your request against those rules before responding.