Reference

0qqa Privacy Policy for Indian Accounts

This page explains how 0qqa collects, uses and stores the personal data linked to your account, payments and support requests.

Account DataCookiesUPILocal Law
0qqa 0qqa Privacy Policy for Indian Accounts
CONTACT PATHS

Ways To Reach Our Privacy Team

When you want to change a record, ask for a copy or raise a concern about data handling, use the routes below. We may ask for account details or a one-time code so the request stays tied to the right record. If a payment trace or legal retention rule blocks a change, we will say which part can move now and which part must stay on file.

Team online

Email Support

Use the email tied to your account and say what you want changed, copied or removed. We use that thread for privacy requests, and we may ask for extra proof before we touch the record.

In-Account Form

Send a message from inside your account when you want a faster link to your session record. It helps us match the request to the right device, payment trail or support history.

Written Notice

For written notices, use the address or legal mailbox shown in your account page. We keep that route for cases that need a signed record or a formal follow-up.

HOW WE WORK

Data, Cookies And Account Safety

We keep personal data on a need-to-know basis and limit internal access to staff who handle support, verification and legal requests.

Collection Scope

We collect only the data needed to open, secure and service your account: name, contact details, device signals, payment references and support messages. We avoid asking for extra fields unless a legal or security check needs them.

Cookie Use

Cookies help keep your session active, remember choices and reduce repeat checks when you move between pages. We use similar tools to spot errors and measure whether a page loads the way it should.

Account Security

Access to account records is restricted, and sensitive changes may need a one-time code or another check before they go through. That step helps us stop unauthorised changes if a device or login looks unusual.

Retention Periods

We keep records only as long as we need them for support, settlement, dispute handling or legal retention. After that window ends, we delete or anonymise the record instead of leaving it on file.

Access Requests

You can ask what we hold, ask for a correction or request deletion where local law allows it. We will verify the account first, then tell you what can change and what must remain.

Change Requests

Send the exact details you want updated so we can move quickly and avoid mistakes. If a payment trace, fraud check or legal duty stops the change, we will explain the reason in plain language.

Your Privacy Questions and Answers

These answers cover the parts of the policy you are most likely to check before opening an account. They explain what we collect, how cookies work, when records can be shared, and what happens if you ask for access or correction. If local law allows a request, we follow the same process across devices and support channels.

We collect the details needed to open, verify and service your account, such as name, contact points, device signals, payment references and support messages. We do not ask for extra fields unless a legal or security check needs them.

Cookies help keep your session active, save choices such as language and reduce repeat checks while you move through the site. We also use similar tools to spot errors and improve page stability.

Yes, but only when a payment route, hosting service or legal duty requires it. We share the minimum data needed for that task and expect partners to handle it under the same local-law limits.

Yes. Send the request through the contact route tied to your account and we will verify it before we respond. Where local law permits, we can share, correct or delete the record you asked about.

We keep records only for as long as they are needed for support, settlement, dispute handling or legal retention. Once that purpose ends, we remove or anonymise the record instead of keeping it indefinitely.

Send the updated details through support so we can match the change to the right record. If a legal duty or security check blocks part of it, we will tell you which fields must stay.

Our support routes handle them, and we may route a complex request to the team that manages account records or legal retention. We keep the thread in one place so you can follow what is pending.