Reference

s3waas Terms & Conditions for Indian Accounts

These Terms & Conditions explain how your account, wallet actions, and content use work on s3waas.

India only where permittedAccount rulesWallet checksContent rights

Browse lobby Read FAQ

How the Terms Apply in India

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

These Terms apply to every account action you take on s3waas, from signing in to confirming a payment or asking for a withdrawal. If a rule conflicts with local law, the local rule applies first, and access is available only where local law permits. We may

1
ask for extra checks before allowing a transfer, changing account details, or restoring access after a lock. When you use UPI, Paytm, PhonePe, or Google Pay, the final status depends on the bank or wallet rail, and any failed or reversed transfer stays subject to that
2
status. We can pause or end access if the account is duplicated, linked to false details, or used in a way that breaks these Terms. That also includes attempts to move funds through accounts that do not match the registered name or payment method.

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

REACH THE TEAM

Ways to Reach the Policy Team

If a clause is unclear, use the contact route inside your account and send the exact section number you want checked.

DATA AND ACCESS

How We Handle Data and Access

To run the account terms properly, we store login details, payment references, device signals, and support history for as long as needed to settle disputes, meet audit needs, and keep the account…

Data use

We use your account details, transaction references, and support history to process requests, check identity, and keep the terms enforceable. We do not need extra data unless a payment or access issue makes it necessary.

Cookies

Cookies help the site remember your session, language choice, and whether you have already passed a step in the account flow. You can clear them in your browser, but some pages may then ask you to sign in again.

Account security

Keep your password and one-time codes private. If we see unusual sign-in attempts, we may pause access until you confirm the activity, because the terms require us to protect the account from misuse.

Retention

We keep records only for as long as they are needed for account operation, legal duties, chargeback handling, or fraud checks. When a record is no longer needed, we remove or archive it under our storage rules.

Change requests

If you need a contact detail corrected, send the request from your registered email or logged-in account. We may ask for payment proof or a security check before changing anything tied to the profile.

Contact line

For data access, correction, or account-close requests, contact support and name the exact change you want. We answer through the same verified channel so the record stays linked to your account.

Questions About the Terms

These questions cover the parts of the Terms that usually need a second read: local-law access, payment reversals, record changes, and how to reach us when a clause affects your account. We keep the answers short so you can match each one to the relevant section in your profile. If your situation is different, the registered account channel is the right place to ask for a manual check.

No. Access is available only where local law permits, and the local rule comes first if there is any conflict. If your region does not allow a specific account action, that part of the Terms does not apply to you.

We may update a clause when payment rules, security steps, or legal duties change. When that happens, the updated text applies from the time it is posted, and your continued use after that point means you accept the change.

A reversed or failed UPI, Paytm, PhonePe, or Google Pay transfer stays subject to the status shown by the bank or wallet rail. We may hold the linked balance until the transaction is settled or cancelled.

Send the request from your registered email or logged-in account and state exactly what needs to change. We may ask for a matching payment reference or security check before we update the record.

We keep account and transaction records only for as long as needed for operations, disputes, audit duties, or legal retention. After that, the record is removed or archived under our storage rules.

Yes, if the account appears duplicated, the details look false, or a payment path is misused. A pause helps us protect the account while we check the facts and decide the next step under the Terms.

Use the verified support channel linked to your account and mention the section number, the date, and any transaction reference. That gives us enough detail to answer from the correct record.

s3waas Terms & Conditions for Indian Accounts

Ways to Reach the Policy Team

How We Handle Data and Access

Data use

Cookies

Account security

Retention

Change requests

Contact line

Questions About the Terms

01 Do these Terms apply everywhere?

02 Can a clause change without notice?

03 What if my payment is reversed?

04 How do I correct my account record?

05 How long do you keep records?

06 Can you suspend my access?

07 Who do I contact about a clause?

Related Pages