Reference

2zz legal terms in one place

We keep the legal side of 2zz in plain English so you can see how access, data use, and account requests work before you move ahead.

India lawAccount dataPayment recordsCookie tags

Explore the Lobby Read FAQ

How local law shapes access

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

This page sets the legal position for your 2zz account, the records tied to it, and the requests you can send us. We keep identity, device, wallet, and transaction records only as long as we need them for account handling, fraud checks, dispute handling, and legal

1
duties. If access is restricted in a place, that depends on local law and is available where local law permits. If you use UPI, Paytm, PhonePe, or Google Pay, those payment trails may be stored with the same account record so we can match deposits and
2
withdrawals against the right ledger. We can also hold cookie data, login events, and support chats to resolve mistakes and protect your account. You can ask for corrections, access, or deletion where law allows, and we will respond through the contact paths listed here.

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

REQUEST CHANNELS

Where to send legal requests

If you need a copy of your records, want a correction, or want us to check how a payment trail was matched, contact us through the paths below.

Email Send a written request to our mailbox if you want access, correction, or a privacy question handled in writing. We use the details you provide to find the account, confirm identity, and reply with the next step.

Live chat Use chat when you want a faster route for a time-sensitive request. If the case touches account records, payment trails, or a change to stored data, we may ask for matching details before we take action.

Postal mail A signed letter works well if you prefer a paper trail. Include the account name, the request you want handled, and a way to reach you back so we can close the loop without confusion.

DATA SAFETY RULES

How we handle data and access

We tie each request to the account, not to a loose inbox thread. Cookie tags help us remember session state, login alerts help us spot unknown access, and our storage periods are…

Data use

We store identity, contact, device, and wallet traces only for account handling, fraud checks, dispute work, and duties under law. We do not keep records longer than the reason for keeping them still exists.

Cookies

Cookie tags help us remember login state, page language, and session timing so you do not have to repeat steps each time. You can clear them in your browser, but some settings may reset.

Login security

When a login comes from a new device, we may ask for a code or another check before we release account details. That extra step protects your records if someone else tries to enter.

Record retention

We hold transaction and support records for as long as needed to settle a query, match a payment trail, or meet legal duties. After that, we remove or archive them under our retention rules.

Change requests

If a detail is wrong, send the exact correction you want. We compare your request with the account record and update only what we can verify, so the file stays accurate and traceable.

Case trail

Every request gets a case record with the date, channel, and action taken. That trail helps us answer follow-up questions and show which team handled the change, without exposing your data more widely.

Questions about your legal rights

These answers cover the requests people ask most often about records, access, corrections, and contact routes. If your location changes, the legal position can change with it, so we check the law that applies when we receive your request. For payment-linked queries, we may need to match the request with your UPI, Paytm, PhonePe, or Google Pay trail before we act.

Yes. Send a request through email or chat and tell us which period you want checked. We verify the account first, then share the record details we are allowed to release.

Yes, if the change can be verified. Send the exact field, the corrected text, and any matching proof we ask for. We update the account record and keep a trace of the change.

Local law decides that, along with the status of your account and the kind of record requested. If access is available where you are, we process it through the channel you used.

We keep records only for as long as they serve account handling, dispute work, fraud checks, or legal duties. After that, the file is removed or archived under the retention rule that applies.

Cookie tags help us recognise session state and site settings, but they do not replace account checks. For a legal request, we still match the request against the account and any record on file.

If your request touches UPI, Paytm, PhonePe, or Google Pay, we may cross-check the payment trail with the account record. That helps us locate the right transaction without mixing up two cases.

Use email, chat, or postal mail from this page. Give the account name, a contact route, and the request you want handled. We will route it to the team that can act on it.

2zz legal terms in one place

Where to send legal requests

How we handle data and access

Data use

Cookies

Login security

Record retention

Change requests

Case trail

Questions about your legal rights

01 Can I ask for my account data?

02 Can I correct wrong details?

03 What decides whether access is allowed?

04 How long do you keep records?

05 Do cookies affect legal requests?

06 How do payment trails fit in?

07 How can I reach the right team?

Related Pages