Reference

Terms for Your India Account

Our Terms & Conditions set the account rules for Baccarat, Scarab Riches, Football Strike and every wallet action linked to UPI, Paytm or PhonePe.

Local-law accessUPI terms contextAccount verificationChange requests
sattafinal Terms for Your India Account
CONTACT ROUTES

UPI and PhonePe Terms Contact Paths

Questions about the Terms & Conditions should reach the team before you rely on an account action, not after a dispute grows. Use the contact path that matches the issue: wording questions, wallet checks, account access or a request to correct stored details. We may ask for your registered phone number, transaction reference, device timestamp or email thread so the response stays tied to your account record.

Team online

Terms email

Email us when you want a clause explained, a dated copy of the Terms & Conditions, or written confirmation of how a rule applies to your account status in India.

Live chat record

Use chat for time-sensitive questions about account access, UPI references or a pending verification step. Ask the agent to keep the transcript linked to your account history.

Account request form

Submit a request when your name, mobile number or payment reference needs checking against the Terms & Conditions. We may reply with document steps before making a change.

ACCOUNT CONTROLS

How We Apply India Account Terms

The Terms & Conditions are not just page text; they are the working rules our account, wallet and support teams follow.

Data used for terms

We use your registration details, login records, game session references and wallet references to apply the Terms & Conditions.

Cookie role

Cookies help connect your device session to the account terms you accepted, language preference and security checks.

Account security

The Terms & Conditions require accurate contact details, secure password use and prompt notice if your account is accessed without…

Record retention

We keep account and transaction records for as long as needed to handle disputes, comply with legal duties and apply…

Change requests

If your stored details are wrong, contact us with the correct value and proof linked to the account.

Decision contact

When a Terms & Conditions decision affects access, wallet movement or account status, ask support for the reason and the…

India Terms Questions Before You Join

Read these answers before you accept the Terms & Conditions or ask support to act on your account. They cover the practical points that cause most delays: local-law access, stored details, payment references, cookies, security checks and how to request a correction. If your situation involves a specific UPI, Paytm or PhonePe reference, include it when you contact us.

You accept the current Terms & Conditions when you create an account, continue using the lobby, or make a wallet request. If we update them, continued use means you accept the revised wording.

Yes. Access and eligibility depend on local law and are available where local law permits. We may restrict features or decline account activity if your location does not allow the relevant service.

The Terms & Conditions let us match wallet requests with payment references, registered contact details and verification records. If a reference is unclear, we may ask for more proof before acting.

Yes, you can request correction of stored details linked to your account. We may need identity proof, payment reference checks or confirmation from your registered email before making the change.

An action may be paused if details do not match, a payment reference needs checking, local-law access is unclear, or security signals suggest the account may not be under your control.

Cookies help show the session, device and acceptance record connected with your account. They also support security checks when you return after a browser change or use a different device.

Contact support through email or chat and include your registered phone number, account email, payment reference and the clause you want reviewed. We will respond through your registered contact path.