Reference

Your legal terms for India

We keep the legal side of sm20 in one place so you can check access, account use, privacy handling and contact routes before you open an account.

IndiaLocal lawPrivacyContact

Explore Lobby Read FAQ

Local law, access and consent

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

Access on sm20 depends on where you are and what local law allows. If your region permits it, you can open and use an account after the checks we ask for, but we do not extend access where the law says no. If a local rule

1
conflicts with anything here, the stricter rule applies in that region. We may collect the details needed to set up the account, verify identity, process wallet activity and keep the records required for audit or dispute handling. Some parts of the page may use cookies and
2
similar tools to remember your session and the language you chose. We also keep the request trail so you can see what was asked and when. If we update these terms, we will post the change here and apply the latest version from the date shown.
3
You can use the contact paths below if you need a copy, a correction or a question answered.

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

CONTACT PATHS

How to reach our policy team

If you want to ask about terms, permissions, record use or a data change, use the channels below.

Email us Send your legal question, correction request or access query through the support email path. We use it for policy copy, record updates and account-specific checks when the request needs a written trail.

In-account form Use the form from your account area when you want to point to a page, term or record. That helps us connect the request to your profile and reply with the right next step.

Wallet reference If your question is about a payment record linked to UPI, Paytm or PhonePe, include the reference so we can find the line item faster and answer with the correct status.

DATA STEPS

How we handle requests and records

We handle legal data with a narrow purpose: account setup, record keeping, access checks and replies to your requests.

Data scope

We collect only the details needed for account setup, verification, record keeping and support replies. That usually means contact data, device signals and payment references, not broad personal history you did not choose to share.

Cookie use

Cookies help us keep your session active, remember your language setting and recognise the browser you used last time. They also reduce repeat checks when you return from the same device.

Security checks

Before a sensitive change, we may ask for a code, a fresh sign-in or another match against your account. That keeps someone else from changing details without your say-so.

Record retention

We retain terms acceptance, contact logs and dispute records only for the period needed under local retention rules and internal controls. After that, we archive or remove the record through set routines.

Change requests

If you want a correction, update or deletion request, send the exact item and the account detail it belongs to. We will check what can change and respond through the same path.

Contact trail

We keep the request date, channel, subject and reply so you can track the thread later. That trail also helps us avoid asking you to repeat the same facts.

Legal questions you may have

These answers cover access, records, cookies, corrections and contact paths. If your question depends on the state you are in or on a document we have not yet seen, send it through the channels here. We keep the reply linked to your account so you do not have to restate the same detail each time, and we can trace the request more quickly.

Only where local law allows it. Access depends on your location and the rules that apply there, so we check eligibility before account use continues in that region.

We keep the details needed for account setup, identity checks, support replies and record keeping. That can include contact details, device signals and payment references tied to UPI, Paytm or PhonePe.

Cookies help us remember your session, keep you signed in and save the settings you chose on the page. They also help us spot unusual sign-in activity and protect account access.

Send the item you want changed, the account detail it belongs to and any proof that helps us verify it. We will check the request and reply through the same contact path.

We keep records only for the period needed for account operation, dispute handling, audit needs and local retention rules. After that, we archive or remove them in line with our process.

Use the email or in-account form listed here. If your question touches a payment reference, add the UPI, Paytm or PhonePe detail so we can reach the right record quickly.

Tell us which account period or request thread you need, and we will share what the law allows us to share. If we need more detail to find it, we will ask once through the same channel.

Your legal terms for India

How to reach our policy team

How we handle requests and records

Data scope

Cookie use

Security checks

Record retention

Change requests

Contact trail

Legal questions you may have

01 Can I use sm20 anywhere in India?

02 What personal details do you store?

03 Why do you use cookies?

04 How can I ask for a correction?

05 How long do you keep records?

06 Who should I contact for legal questions?

07 How do I ask for a copy of my record?

Related Pages