Reference

220patt terms that shape your access

These Terms & Conditions explain how your 220patt account works, what we expect from you, and where local law sets the limit.

India accessAccount rulesLocal lawWallet checks

Browse Lobby Read FAQ

How local law shapes your account

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

These Terms & Conditions apply when you open or use a 220patt account from India or from any place where local law permits access. By continuing, you agree to the rules on identity checks, account conduct, wallet use, and how content is accessed. We may ask

1
for documents, pause activity, or close an account if the details you give do not match, if a request cannot be verified, or if a legal restriction applies. Local payment rails such as UPI, Paytm, and PhonePe are handled only through the account methods shown to
2
you, and only where they are supported for your location. If we update wording on this page, the current version controls from the effective date we publish here, so check the date before you act.

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

HELP PATHS

220patt help for term queries

If a clause is unclear, use the contact path that matches your need. The in-account message thread is the quickest way to tie a question to your profile, while email or the…

In-account message Sign in and send your clause query from the help panel. That keeps the request tied to your account record, which helps us check the exact term, the date, and any action already taken.

Support mailbox If you prefer email, use the support mailbox listed on the contact page and include your registered details plus the clause you want explained. We use that trail to confirm identity and log the request.

Site form You can also use the contact form on the site when you need a record of what you asked. Add your account ID, the page date, and the part of the wording you want checked.

DATA AND ACCESS

How we handle records and access

Our handling of data and access follows the same rules across the account. We keep only the details needed for sign-in, clause support, misuse checks, and legal duty; cookies manage sessions, and…

Data used for checks

We use your name, contact details, device signals, and transaction history to confirm account access, spot mismatches, and handle clause requests. We keep that use limited to support, security, and legal duties.

Cookies and sessions

Cookies help keep you signed in, remember the page you last read, and protect the session from misuse. You can clear them in your browser, though some account pages may then ask you to sign in again.

Sign-in protection

Password rules, one-time checks, and device review help prevent an account from being opened by someone else. If we see unusual access, we may pause the session until you confirm it is really you.

Record retention

We retain account and support records only as long as needed for the clause in question, transaction checks, dispute handling, or legal duty. After that, records are removed or anonymised under our internal schedule.

Requesting changes

If your name, contact number, or other record needs correction, send the updated detail through the support path above. We may ask for proof before changing the account, so the record stays accurate.

Who can see it

Only staff who need the record for support, verification, security checks, or legal handling can access it. We limit internal access by role, and each request is logged so there is a trace of what was done.

Common terms questions answered

The answers below cover the parts of the Terms that usually matter first: who can open an account, when access can pause, how payment records sit inside the account, and how you can ask for a change. If local law changes, the controlling wording changes with it. Use the support paths above whenever you need the current clause applied to your own profile.

They set the rules for account opening, login, verification, wallet use, content access, and how we handle requests tied to your profile. If a section depends on location, the rule applies only where local law permits.

Access depends on local law. If a location is not allowed, we may block sign-in, limit access to certain pages, or close the account after checking the record. Use the service only where the law allows it.

We may pause or close access if your details cannot be verified, if we see mismatched activity, if a request needs checking against the record, or if a legal rule requires it. We will contact you where possible.

Deposits through UPI, Paytm, or PhonePe are handled only through the methods shown inside your account. Withdrawal requests stay subject to verification, account status, and any checks needed before release.

Send the updated detail through in-account message, email, or form, and add the item you want changed. We may ask for proof so the record matches the person using the account and the history already stored.

We post the latest wording on this page, and the date at the top shows which version applies. If a change affects your account, we may also use your registered contact details to send a direct notice.

Write to support with the page date and the account action you want checked. We will read the clause against your record again and reply with the reason the earlier decision was taken.

220patt terms that shape your access

220patt help for term queries

How we handle records and access

Data used for checks

Cookies and sessions

Sign-in protection

Record retention

Requesting changes

Who can see it

Common terms questions answered

01 What do these Terms cover?

02 Can I use the site from anywhere?

03 When can access be paused or closed?

04 How do deposits and withdrawals sit under these Terms?

05 How can I correct my account details?

06 How will you tell me about changes?

07 What if I disagree with a decision?

Related Pages