Reference

Privacy Policy for your account

At 0kl, we set out what we collect for account access, verification, payments, support, and fraud checks, so you can see how your details move through the system.

ACCOUNT DATACOOKIE TERMSCHANGE REQUESTSINDIA ACCESS

explore lobby Read FAQ

What this policy covers

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

This policy explains how we collect, use, store, and share personal details linked to your account, device, wallet, and support history. We rely on that data to run login checks, process transactions, prevent misuse, answer queries, and meet legal or audit duties where local law requires

1
it. If a request comes from another country or from a rule that does not apply in your region, we act only within the law that governs your account. When you add funds through UPI, Paytm, PhonePe, or Google Pay, we keep the transaction references needed
2
to match the payment, fix errors, and answer disputes. Records may be kept for different periods depending on the data type, the reason it was collected, and the retention period required by law. Some logs are held for security review, while routine support notes are removed
3
sooner once the issue is closed.

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

CONTACT ROUTES

How to reach us

If you want to ask how we handle data, the fastest route is the privacy email linked in your account area.

HANDLING STANDARDS

How we handle your data

We collect only what we need for account setup, login, payment matching, support, and fraud checks, then store it in systems with role-based access.

Data capture

We record the details you share when you open an account, verify identity, contact support, or move money through UPI…

Cookie use

Cookies help us remember your session, keep the page state you chose, and measure whether a privacy setting changed after…

Account security

We use password checks, session controls, and device signals to reduce unauthorised access.

Retention

We keep account records only as long as needed for the reason they were collected, legal duties, dispute handling, and…

Change requests

You can ask for correction, access, or deletion by sending a clear request through the contact routes on this page.

Sharing rules

We share data only with service providers that help run payments, hosting, support, or verification, and only under written terms…

Common privacy questions for your account

These answers explain the most common choices you have around access, correction, deletion, cookies, and contact. If the law in your region gives you a stronger right than what we describe here, we follow that law for your account. Keep your request clear, include the email or phone number tied to the record, and we will route it to the privacy team.

Usually we keep the account details you share, device and browser signals, payment references, support messages, and security logs. We use them to run the account, answer requests, and meet legal duties where local law applies.

Payment references help us match UPI, Paytm, PhonePe, or Google Pay activity to the right account, confirm that a transfer reached us, and resolve disputes. We do not store more payment detail than we need for that purpose.

Yes. Send a clear request through the contact routes on this page, and include the email or phone number tied to the account. We may ask one follow-up question to make sure the record goes to the right person.

Tell us which field is wrong and what it should be instead, such as your name, phone number, or address used for verification. If we can confirm the change, we update the record and note the date of action.

We remove or archive records when the retention period ends, when the purpose disappears, or when a legal duty allows us to do so. Some security logs stay longer than support notes because they help us trace account abuse.

No. Cookies mainly keep session state, remember your choices, and help us measure whether pages load and settings stay in place. Message content sits in the account record or support system, not in the cookie itself.

Our privacy team handles those requests with the support and compliance staff that need access. We limit who can open the record, and we only share enough detail internally to complete the request and keep the record trail.

Privacy Policy for your account

How to reach us

How we handle your data

Data capture

Cookie use

Account security

Retention

Change requests

Sharing rules

Common privacy questions for your account

01 What personal data do you keep?

02 Why do you collect payment references?

03 Can I ask for a copy of my data?

04 How do I correct wrong details?

05 When do you remove old records?

06 Do cookies store private messages?

07 Who handles privacy requests?

Related Pages