Reference

Privacy Policy for k0201 Accounts

This Privacy Policy explains what we collect when you create your account, how device and payment records are used, and when limited sharing may happen with service partners.

Account dataCookie choicesRequest accessIndia rules

Explore Lobby Read FAQ

What We Collect and Why

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

This policy covers the data that comes from your account form, device and browser markers, session logs, support chats and payment records. We use it to run the account, verify requests, keep records aligned with local law and settle disputes that may arise. If you access

1
from Delhi or elsewhere in India, the same rules apply unless a different legal rule requires another treatment. We may share limited details with payment partners, fraud checks or service vendors only when a task needs it, and we do not pass data around for unrelated
2
use. We keep records only for as long as needed for account handling, audit checks and legal duties, then remove or de-identify them under our retention rules. Cookies help us remember login state and device preferences, and you can change browser settings if you want to
3
limit them, though some account functions may then need extra checks.

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

HELP CHANNELS

Ways to Reach Our Privacy Team

If a privacy question comes up, we route it through the same team that handles account records so your request stays traceable from the first message. Tell us whether you want access, correction, deletion or a sharing question, and we will point it to the right queue. Keep your request tied to the account email or phone number so we can verify it without delay.

Team online

Email

Write to [email protected] when you want a copy, correction or closure step. Use the subject line Privacy Request so the message lands in the right queue and can be matched to your account.

Secure form

Use the form inside your account if you need to ask about sharing, cookies or retention. It captures your account ID, contact detail and request type, which helps us verify the file cleanly.

Chat

If you start with chat, send the privacy question there and we will move it to the same team. You may need to confirm details that match the account before we act.

CONTROL POINTS

How We Handle Data Safely

Our privacy handling starts with data minimisation: we collect what we need for account use, verification and legal duties, then keep the rest out of the flow.

Data scope

We keep the data set narrow: account details, device markers, login history and transaction records. That lets us run the service, answer your request and meet legal duties without building extra profiles.

Cookie choices

Cookies store session state and browser preferences so your sign-in stays stable. You can adjust browser settings at any time, and some pages may ask for extra checks if cookies are reduced.

Account security

We use sign-in checks, password rules and device alerts to protect access. When a request looks unusual, we may ask for matching details before changing records or releasing a copy.

Retention

Records stay only for the period needed for account handling, audit checks and legal duties. After that period, we remove or de-identify them under our retention schedule before the file is closed.

Request handling

If you ask for access, correction or deletion, we log the date, verify the account and update the record set once the check is complete. That trail helps us answer you clearly.

Sharing limits

We pass data to payment or verification partners only when the task needs it, such as settlement, fraud checks or service delivery. We do not share it for unrelated use.

Privacy Questions You Can Ask

These questions focus on the parts of the policy people ask about most: collection, sharing, access, retention and request handling. If you do not see your point here, use the contact paths in the sections above and send the exact request you want handled. We keep the wording plain so you can check what we store, why we store it and how changes move through the queue.

It covers the data we collect from your account form, device, browser, payment records and support messages, plus how we store, share and remove those records under local law.

We collect the details you enter, session logs, device markers, wallet activity and transaction records tied to UPI, Paytm, PhonePe or Google Pay. We use them to run the account and verify requests.

Yes, but only when a task needs it. That can include payment partners, fraud checks, service vendors or legal requests, and the shared set stays limited to the purpose.

We keep records for as long as needed for account use, dispute handling, audit checks and legal duties. After that, we remove them or de-identify them under our retention rules.

Yes. Send the request through email, chat or the secure form, and we will verify the account before we share a copy or update the record set.

Yes. We make the service available only where local law permits, and the privacy steps tied to your account can change if a legal duty requires a different process.

Use the contact paths in the support section and tell us whether the request is about access, correction, deletion or sharing. Keep the message tied to your account details.

Privacy Policy for k0201 Accounts

Ways to Reach Our Privacy Team

Email

Secure form

Chat

How We Handle Data Safely

Data scope

Cookie choices

Account security

Retention

Request handling

Sharing limits

Privacy Questions You Can Ask

01 What does this Privacy Policy cover?

02 Which data do you collect from me?

03 Do you share my data with others?

04 How long do you keep records?

05 Can I ask for a copy or correction?

06 Does access depend on local law?

07 How do I contact you about privacy?

Related Pages