Reference

How 0ron Handles Your Privacy

This Privacy Policy explains what we collect when you open an account, how we use it for verification, login security, and payment records, and how we protect it…

Account dataDevice signalsPayment recordsCookie settings
0ron How 0ron Handles Your Privacy
REQUEST PATHS READY

Where To Send Privacy Requests

Privacy requests can reach us through the channels listed here. Use the path that suits your case: a message from your account area for correction or deletion requests, email for documents, or…

Email Privacy Team Use this email route for correction, access, or deletion requests. Include your account email and any payment reference if the issue touches UPI, Paytm, or PhonePe records, so we can find the right file without delays.
Account Form The form in your account area is the cleanest way to ask for a data copy or a change to stored details. It creates a timestamped trail, which helps us verify the request and reply in order.
Chat Support Chat works well for quick status checks. We will still move anything sensitive to a verified channel before we change data, since privacy requests need a clear identity check and a written record.
DATA HANDLING FLOW

How We Treat Your Data

Our privacy handling is built around the account you create, the devices you use, and the checks we need to keep the service stable.

Data We Store

We keep contact details, login signals, device type, and transaction references that help us verify your account and answer your request. We do not collect extra fields just because they are available.

Cookies And Session

Cookies help us remember your session, keep pages stable, and reduce repeat checks while you move between devices. You can clear them in your browser, but parts of the account flow may ask you to sign in again.

Account Security

We protect access with password checks and step-up verification where needed. If we spot unusual activity, we may pause a session and ask you to confirm control of the account before any change is made.

Retention Window

We keep records only for as long as needed for service, audit, dispute handling, and legal duties. Once that period ends, the record is deleted or reduced to the minimum we still need.

Change Requests

If you want to correct, delete, or copy your data, send the request through the contact paths below. We verify the request first, then tell you what can be changed under local law.

Contact Trail

Every request gets a reference so you can follow up without repeating the full story. That trail helps us show when we received it, what we checked, and how we closed it.

Privacy Questions You May Ask

The questions below cover the data we collect, how cookies work, how long we keep records, and how you can ask for changes. If a situation depends on local law, we say so clearly. You can use the same contact paths for access, correction, or deletion requests, and we will ask for a quick identity check before making a change.

We ask for contact details, login details, and limited device data so we can set up access, verify requests, and protect the account. We keep the record lean and tied to a clear purpose.

Cookies help us keep your session active, remember choices, and reduce repeated checks while you move around the site. They do not change who you are, and browser settings can limit them.

We share only where needed to run the service, process a request, meet law, or handle a dispute. We do not pass your details around for unrelated use, and we limit access inside the team.

We keep records for the period needed for account support, audit, fraud checks, and legal duties. After that, we delete or reduce them so only the minimum required remains.

Yes. Send a request through the contact paths, and we will verify it before making the change. If a legal rule blocks a deletion or edit, we will explain what can still be done.

Ask through the support channel listed here. We may confirm your identity first, then share the data we can provide and explain any part that must stay on file under local law.