Reference

0l0 Privacy Policy For India Accounts

0l0 keeps your account details, wallet records and device signals tied to the purpose they serve, so you can see how we handle them before you open an…

Account DataWallet TrailsCookie SettingsLocal Law

Browse lobby Read FAQ

How We Handle Your Data

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

For India accounts, we collect what you submit, what your browser sends, and what the wallet rail needs to complete a UPI, Paytm or PhonePe transfer. We use that data to run your account, confirm transactions, answer support requests, and meet record-keeping duties where law or

1
tax rules require it. Access is limited to staff who need the record for that task, and we avoid using the same data for unrelated purposes. If we need to share a request with a payment partner or a service provider, we share only the fields
2
needed to finish the job. When access or eligibility is discussed, it depends on local law and is available where local law permits. You can also ask for a copy, correction or deletion through the same path you used to contact us.

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

WRITE TO US

Where To Send Privacy Requests

If you want a copy, correction or deletion request, send it through the same channel you use for account support so we can match it to the right profile. We answer in plain English, keep the discussion limited to your record, and ask only for the details needed to verify the request. Where local law permits access, we process the change after we confirm the account holder.

Team online

Site form

Use the form in your account area when you want us to update a field, explain a record, or check a consent choice. We read every request against the account so the reply goes to the right place.

Registered email

Send a message from the email linked to your account if you need a copy of stored data or want us to correct a detail. That link helps us verify you before we touch the record.

Help inbox

If your request is about retention or deletion, write the date, the item you want changed, and any payment trail that helps us find it. We keep the thread focused on your own file.

RECORD CARE

How We Handle Records

This page explains how we handle personal data across account use, wallet activity and device access.

Data use

We keep profile details, login events, device signals and payment records only for account operation, transaction checks and support. We do not merge that record with unrelated contact lists or use it for a separate purpose.

Cookies

Cookies remember session state and language choice, so you do not need to reset them on every return. If you clear them, some settings reset, but the account and policy remain the same.

Account checks

When you ask for a copy, correction or deletion, we match the request against your registered contact path and may ask for a small check such as a recent transfer trail. That keeps the response tied to the right account.

Retention

We keep records only for as long as needed for account handling, dispute handling, audit trails and legal duties. After that, we remove or reduce them according to the retention step for that record type.

Change requests

You can ask us to correct a field, send a copy, or review deletion where the law allows it. If a record must stay for legal reasons, we explain which part remains and why.

Local law

Access or eligibility always depends on local law and is available where local law permits. If a region blocks a request, we keep the reply clear and route you through the same contact path.

Questions About Your Data

These are the questions we answer when you want to know what we collect, why we keep it, and how you can ask for a change. Each answer stays tied to your account, your wallet trail and the local law that applies to you. If a request needs manual checking, we ask for the minimum detail needed and reply through your registered contact path.

We keep the details you enter, login records, device signals and payment trails that help the account work. We do not use that data for unrelated purposes, and we limit access to staff who handle the task.

Payment trails help us match a deposit or withdrawal to the right account, fix mistakes and answer a support request. If a bank or wallet partner needs a field to finish the transfer, we send only that field.

Yes. Send the request from your registered contact path, and we will check that it matches your account before we reply. If local law allows access, we send the copy in a clear format.

Yes. Tell us which field is wrong, what it should show, and how we can confirm the change. We update records when the request matches the account and when no law requires the old record to stay.

We keep records only for as long as needed for account handling, support, dispute handling and legal duties. After that period, we delete or reduce them in line with our retention process.

Cookies help remember your session and language choice. If you clear them, some settings may reset, but the policy stays the same and the account can still be used where local law permits.

We still route the request through the policy path, but access or eligibility always depends on local law. If a region blocks a request, we explain the reason and point you to the same contact path.

0l0 Privacy Policy For India Accounts

Where To Send Privacy Requests

Site form

Registered email

Help inbox

How We Handle Records

Data use

Cookies

Account checks

Retention

Change requests

Local law

Questions About Your Data

01 What data do you keep?

02 Why do you store payment trails?

03 Can I ask for a copy?

04 Can I correct wrong details?

05 How long do you keep records?

06 Do cookies change my access?

07 What if I contact you from another place?

Related Pages