Reference

s3waas Privacy Policy for Indian Accounts

This page explains how s3waas handles your privacy when you open an account, browse the lobby, or contact support.

IndiaCookiesData useYour rights
s3waas s3waas Privacy Policy for Indian Accounts
REACH US DIRECT

s3waas privacy contact paths

If you want to ask about a record, change contact details, or check how a request is handled, you can reach us through the channels listed…

Email us Email [email protected] when you want to ask what data is stored, point out an…
Use the form Send the request from your signed-in account if you need to update a phone…
Escalate a request If your case involves deletion, retention, or a disputed payment record, say which date…
CONTROL AND RETENTION

Storage, cookies and account security

This part explains how we handle the data behind account access, cookies, and stored records. We separate login security, payment logs, and support messages so each request reaches the right team.

What we collect

We collect the details you enter for account setup, the device and browser signals needed to keep login stable, and the transaction references linked to deposits or withdrawals. We do not ask for more than we need for the stated purpose.

Cookie handling

Cookies remember session state, language choice, and basic site settings. They also help us spot repeated failed logins and abnormal behaviour. You can clear them in your browser, but some screens may ask you to sign in again.

Payment records

When you use UPI, Paytm, PhonePe, or Google Pay, we may store status, reference IDs, and time stamps so we can match the transfer to your wallet and resolve disputes with the payment partner.

Security checks

We protect account access with password hashing, device checks, and session controls. If a login looks unusual, we may ask you to verify the request before you can change sensitive details or move money.

Retention

We keep records only for as long as needed for service, dispute handling, tax, audit, or legal duties. After that, we delete or anonymise them in line with our internal retention schedule.

Your requests

You can ask for access, correction, deletion, or a copy of the data we hold by sending the account name, the linked phone or email, and the exact change you want.

Privacy Policy questions you may ask

These questions focus on the privacy points most people ask before sharing account details. If you are checking what we store, how long we keep it, or how to ask for a change, the answers here use plain language. When a request depends on local law or a retained record, we say so directly and explain the next step so you know what happens before you send anything.

We collect the details you enter for account setup, login, and support, plus device signals and transaction references when you use payment methods. We keep only the fields needed to run the account and meet legal duties.

Cookies keep your session active, remember your basic settings, and help us notice repeated failed logins or unusual browser patterns. If you clear them, you may need to sign in again and reset a few preferences.

Yes. When you use UPI, Paytm, PhonePe, or Google Pay, we may keep reference IDs, status, and time stamps so we can match the transfer, trace a failed attempt, or answer a dispute.

You can. Send the account name, the linked phone or email, and the record type you want, and we will verify the request before sharing what we can under local law.

We keep records only for the period needed for service, security, dispute handling, tax, audit, or legal duties. After that, we delete or anonymise them in line with our retention schedule.

Tell us exactly what needs to change, which account detail is involved, and the date or transaction reference if one exists. We will check the request, confirm what can be done, and explain any legal limits.

Yes. When access, deletion, or portability depends on local law, we only act where the law permits and we explain the parts we can complete for you.