Reference

Privacy Policy for India Accounts

This Privacy Policy explains how 9qa handles your account details, device data, cookies, and payment records when you use the site from India.

Account dataCookiesRetentionRequests

explore lobby Read FAQ

How Local Law Shapes Data Use

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

Our privacy rules follow the law that applies where you are using the site. Some data handling steps may change if local law asks for a different notice, consent, retention, or request process. We collect only what is needed to open and secure an account, keep

1
transaction records, answer support messages, and stop misuse. That can include contact details, device signals, session logs, and records tied to UPI, Paytm, or PhonePe activity if you choose those rails. We do not treat every record the same way: some are kept for account access,
2
some for security checks, and some only for audit or legal duties. When access or eligibility is discussed, it depends on local law and is available where local law permits.

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

REQUEST CHANNELS

Where to Send Privacy Requests

If you want to ask about this policy, use the contact paths below and send the details linked to your account. We use those details to find the right record, confirm the request, and avoid changes to the wrong profile. For correction, deletion, export, or a copy of stored data, keep your message clear and include the email or mobile number on file.

Team online

Privacy email

Use the privacy inbox when you need a copy of stored details, a correction, or a deletion request. Include the email or mobile number on the account so we can match the right record.

Account message

If you are already signed in, send the request from your account area. That path helps us confirm identity faster and keep the request attached to the same profile and device history.

Postal request

For written requests, send a signed note with your account details and contact field. We may ask for extra proof before changing anything, because privacy changes must go to the right record.

DATA HANDLING

How We Keep Your Details Private

We keep privacy handling tight across collection, storage, sharing, and deletion. Cookies help us remember session state and security checks; they are not used to change your account…

Data collected

We keep contact details, login history, device signals, and request records only where they are needed to run the account…

Cookie use

Cookies and similar tools help us remember session state, spot repeated sign-in attempts, and keep your preferences tied to the…

Account security

When you ask for a privacy change, we check the account name, email, or mobile number already stored before acting.

Retention

Some records stay for a short time, while others remain longer because the law, payment checks, or dispute handling require…

Change requests

You can ask to correct, export, or delete data tied to your account, subject to the law that applies to…

Contact route

The request should go through the channel listed on this page so it reaches the right team.

Questions About Your Privacy Rights

These answers explain what the policy covers, how we check requests, and what happens when local law changes the process. We keep the record set focused on account access, security, payment handling, and support. If you want a correction, copy, or deletion step, use the contact path that matches your account and send enough detail for us to verify it.

It explains what account, device, cookie, and transaction records we collect, why we use them, how long we keep them, and how you can ask for a change when local law allows it.

We may store the contact data you give us, sign-in records, browser signals, and request history. If you use payment rails tied to your account, we keep the matching transaction record needed for audit and support.

Cookies help us keep you signed in, remember session state, and detect unusual access patterns. They also let us keep simple settings tied to the same browser without asking for the same choice again.

Yes. Send the correction request through the contact path on this page, include the account details we can match, and tell us exactly what should change. We may ask for proof before updating the record.

You can ask, but the result depends on local law and any record we must keep for security, dispute handling, or legal duty. If deletion is possible, we remove or anonymise the eligible part.

We check the email, mobile number, or other matching record before handling a sensitive request. That check helps us protect the account from unauthorised changes and keeps private details in the right hands.

Use the email, account message, or postal route listed here. Include the same contact details you used on the account, and our team will route the privacy request to the right record holder.

Privacy Policy for India Accounts

Where to Send Privacy Requests

Privacy email

Account message

Postal request

How We Keep Your Details Private

Data collected

Cookie use

Account security

Retention

Change requests

Contact route

Questions About Your Privacy Rights

01 What does this policy cover?

02 Which details do you store?

03 Why do you use cookies?

04 Can I ask for corrections?

05 Can I ask for deletion?

06 How do you keep access secure?

07 How do I contact you?

Related Pages