Reference

Terms & Conditions for Indian accounts

These Terms & Conditions explain how your account works, what you agree to when you use the site, and how we handle access from India.

Account rulesIndia accessLocal lawClear terms

Explore Lobby Read FAQ

What these terms cover in India

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

We write these terms for account creation, login, game access, payments, withdrawals, disputes, and any support request tied to your record. Your use of satakigh depends on local law and is available where local law permits, so some features may not appear for every region. If

1
a clause conflicts with a mandatory local rule, that local rule applies to that part and the rest of the page still stands. We may pause access, ask for updated details, or review a transaction when the account record is incomplete, inconsistent, or linked to a
2
security check. UPI, Paytm, PhonePe, and Google Pay appear as payment chips only when the wallet is available for your region, and bank processing times can affect the final status of a transfer. These terms also cover how we record consent to updates, how we handle
3
duplicate requests, and how we treat messages sent from shared devices. If you do not agree with a change, stop using the account and contact support from the same profile so we can close the loop on your request.

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

REACH US HERE

How to contact us about terms

If a clause is unclear, send your question from the Help area inside your account or use the support form on the site.

Support form Open the support form from your account area, add the clause or request ID, and send it with your registered contact details. That helps us match the thread to the right record and reply in order.

Live chat Use live chat when the matter needs a quick check, such as access, session lock, or a fresh wording question. The chat log stays attached to your account so the history is easy to follow.

Email thread If you prefer email, continue the same thread so our team can keep the earlier messages together. Add your account name, the page path, and a short line on the change or concern.

RECORDS WE KEEP

How we handle account records

We keep only the records needed to run your account, settle transactions, answer disputes, and meet legal duties. Cookies help remember your session, save language choices, and spot unusual access.

Account details

We keep the name, contact fields, and transaction trail tied to your account so support can confirm requests and fix mismatches. If any detail changes, send the update from the same account path.

Cookies and sessions

Cookies help us remember login state, language choice, and security checks. You can clear them in your browser, but some pages may ask you to log in again after that.

Login security

Use a private password, avoid sharing access, and sign out after each session on shared devices. We may add an extra check when we see a new device, location, or browser pattern.

Record retention

We retain records only for the period needed for account handling, transaction matching, dispute work, and legal duties. When that period ends, we remove or de-identify data in line with our procedures.

Change requests

If you want a correction or deletion request, send it from your account contact route with the exact field you want changed. We may need verification before we act on the request.

Contact and escalation

For policy questions, use the support form first. If the first reply does not settle the matter, ask for escalation in the same thread so we can keep the history together.

Questions about these terms

These answers cover the most common points about account use, access, records, and changes to this page. If your situation is unusual, the written terms and the local law that applies to you will decide what happens. When you need a case-specific reply, send the request from your account so we can check the exact record.

They apply when you create, access, or use the account, including each session and each request you send. If local law places a tighter rule on any part, that rule controls for that part.

Yes. We may replace this page when our process, legal duty, or account flow changes. The published version on this path is the one you should follow from the date shown on the page.

Ask us to correct the field from your account contact route and tell us what is wrong. We may ask for a matching document or another check before we update the record.

Cookies can keep you signed in, remember language choice, and support security checks. If you block them, some pages may ask you to log in again or recheck your session.

The account owner should make the request from the registered contact path. We may decline third-party requests unless local law or a valid legal request says otherwise.

Only as long as needed for account handling, transaction matching, dispute work, or legal duties. After that period, we remove or de-identify the record according to our retention process.

Use support from inside your account, include the page subject, and say what point you want checked. If it needs escalation, ask for a follow-up in the same thread.

Terms & Conditions for Indian accounts

How to contact us about terms

How we handle account records

Account details

Cookies and sessions

Login security

Record retention

Change requests

Contact and escalation

Questions about these terms

01 When do these terms apply to my account?

02 Can these terms change later?

03 What happens if my details are wrong?

04 How do cookies affect my session?

05 Who can ask for record changes?

06 How long do you keep my records?

07 How should I contact you about this page?

Related Pages