Reference

Terms & Conditions for Indian Accounts

satta1net sets the terms for account use, verification, data handling, and any pause or closure action on your account.

India firstLocal lawAccount useData handling

How These Terms Work in India

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

These terms set the rules for account creation, verification, record keeping, wallet use, and dispute handling. If your access is allowed under local law, the same rules apply from the moment you submit details until the account is closed. We may ask for identity or payment

1
proof when a change, correction, or transaction check needs confirmation. If the details you give do not match our records, we can pause action until the issue is resolved. For India, UPI, Paytm, PhonePe and Google Pay are listed only as local payment context where such
2
use is allowed. We also record support requests, consent logs, and security events so we can answer later questions clearly. Any request to change your profile, contact details, or account status must come through the proper contact path and may need extra verification before it is
3
approved.

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

CONTACT PATHS

Where To Reach Us About Terms

If a clause needs clarification, use the same contact paths we use for account changes and record corrections.

Email support Send term questions, correction requests, or closure queries with your account name and the section you want checked. We use the message trail to verify the request and reply with the next step.

In-lobby chat Use chat when you need a quick read on a clause, a notice you received, or a document request. Keep the same details ready so we can match the request to your account.

Call back request For urgent account or identity checks, ask for a callback and we will return through the contact number on file. This helps us confirm changes before anything in your record is updated.

DATA AND CONTROL

Data, Cookies, and Account Control

We keep only the records needed to run these terms: account details, consent logs, device and cookie data, support history, and transaction references tied to your account.

Data use

We use account details only to run access, verification, support, and record keeping tied to these terms. We do not expand use beyond what the request, the account flow, or local law allows.

Cookie records

Cookies help us remember session state, keep you signed in, and show whether a form or notice was already seen. You can clear them in your browser, though some pages may ask again for a fresh check.

Account security

Passwords, one-time checks, and device checks reduce unauthorised changes. If your log-in looks unusual, we may ask you to confirm the request before the account setting or wallet record is updated.

Retention

We keep support tickets, change logs, and transaction references for as long as needed to settle disputes, meet legal duties, and protect the record trail. Older data is removed or archived when it is no longer needed.

Change requests

If you need an edit, correction, or closure request, send it through support with the details that prove the account belongs to you. We answer in the same channel after we verify the request.

Record copy

If you want to know what we store about you, ask for a record copy through support. We will tell you what can be shared, what must stay locked, and what needs further verification.

Common Questions On Terms

The questions here focus on when these terms apply, how local law can change access, what data is used, and how you can ask for corrections. We keep the answers tied to account use, record handling, and support paths so you know what to expect before you proceed. If your situation is different, send the exact clause or request through support and we will reply in the same thread.

They apply from the moment you create an account, submit details, or use the site after opening one. Each login, request, and action is handled under the same set of terms until the account is closed.

Yes. Access depends on local law, and we only allow it where local law permits. If a state or region changes the position, the same rule governs account use and any related request.

If the details do not match our records, we may pause the affected action and ask for more proof. That can include identity checks, payment proof, or a fresh confirmation through the contact path on file.

We use your data to run account access, security checks, support replies, and the records needed under these terms. We do not use it for anything outside the request, the account flow, or legal duties.

Yes. Send a correction or closure request through support, along with the details that confirm the account belongs to you. We verify the request first, then move it through the right process.

We keep enough logs to settle disputes, answer past requests, and meet legal retention duties. When the record is no longer needed, it is removed or archived according to the rule that applies.

Terms & Conditions for Indian Accounts

Where To Reach Us About Terms

Data, Cookies, and Account Control

Data use

Cookie records

Account security

Retention

Change requests

Record copy

Common Questions On Terms

01 When do these terms start to apply?

02 Can my access change by state or location?

03 What happens if my account details do not match?

04 How do you use my data under these terms?

05 Can I ask for a correction or closure?

06 Why are records kept after the account is closed?

Related Pages