Reference

Legal terms for your India account

This legal page sets out how mysattaking handles account terms, privacy choices, cookies, access checks, and contact requests.

India legal termsPrivacy rightsCookie choicesAccount access rulesContact route

Explore lobby Read FAQ

Legal position for local account use

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

Our legal terms apply when you access the site, create an account, manage your wallet, contact support, or use any account feature linked to India payment names. Access and eligibility depend on local law and are available where local law permits. We may check your identity,

1
payment ownership, device signals, and account activity to meet fraud-control, security, and legal duties. We do not ask you to continue if your location, age status, or local rules make access unavailable. If the law in your area changes, we may pause access, request more documents,
2
close restricted features, or update these terms. UPI, Paytm, PhonePe, and Google Pay references are payment-context labels, not a promise that every method is available at all times.

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

CONTACT PATHS

Where to raise legal requests

Legal questions need a clear paper trail, so we ask you to use the right contact path and include the account email or mobile number you used with us. Do not share passwords, OTPs, or full payment credentials. We may ask for proof of identity before changing data, releasing records, or closing access.

Team online

Legal email

Send legal requests from your registered email and mention whether you need account terms, privacy access, correction, closure, or payment-record help. We reply after checking that the request belongs to your account.

Account chat

Use account chat for time-sensitive legal flags, such as unknown login alerts, mistaken personal data, or wallet activity you do not recognise. We may move complex requests to email for written confirmation.

Document upload

When a legal request needs identity proof, upload only the requested document through the secure account flow. Mask extra numbers where allowed, keep images clear, and wait for our status update.

DATA RIGHTS

How we handle legal data duties

We treat account data as a legal responsibility, not just a service record. The wallet, login, cookie, and support systems keep separate logs so requests can be checked without exposing more data…

Data collected

We collect account details, login records, device signals, wallet references, and support messages needed to run your account, prevent misuse, and answer legal requests tied to your profile.

Cookie use

Cookies help keep sessions active, remember lawful access choices, and detect repeated failed logins. You can manage browser cookies, though some account security checks may stop working correctly.

Account security

We use login alerts, OTP checks, device review, and payment-name matching to reduce account takeover risk. If a mismatch appears, we may pause wallet activity until ownership is confirmed.

Retention period

Some records stay longer because payment disputes, tax checks, fraud alerts, or legal claims may arise after account activity. We remove or limit eligible data when no lawful reason remains.

Change requests

Ask us to correct spelling errors, update contact details, or remove outdated documents through the legal email path. We may need proof before making changes that affect account access.

Restricted access

If your location or local rules do not allow access, we may block sign-in, pause account features, or ask for more details. This keeps use limited to areas where local law permits.

Common legal questions before account use

These answers explain how our legal terms work when you create an account, share data, use local payment names, or ask us to change records. They do not replace local legal advice. If your situation is specific, contact us through the legal email path with enough detail to check your account.

Access depends on local law and is available where local law permits. We may check your location, identity, payment ownership, and account activity before allowing continued use or specific wallet actions.

We may keep account details, login history, device records, payment references, support messages, and verification documents. Retention depends on fraud checks, dispute timelines, tax needs, and other lawful duties.

Yes. Send the request from your registered email and specify the field that needs correction. We may ask for proof when the change affects identity, contact access, or payment records.

Cookies record session status, security checks, and some preference choices. You can change browser settings, but account access may be limited if required security cookies cannot confirm your session.

UPI, Paytm, PhonePe, and Google Pay references may be checked against account ownership, dispute claims, and fraud signals. We do this before certain changes, withdrawals, or legal record requests.

Email us from your registered address and state whether you want account closure, deletion of eligible data, or both. Some records may remain where law, audit duties, or disputes require retention.

If local law does not permit access from your area, we may block features, pause sign-in, or request further checks. Any available account action will follow the limits set by law.

Legal terms for your India account

Where to raise legal requests

Legal email

Account chat

Document upload

How we handle legal data duties

Data collected

Cookie use

Account security

Retention period

Change requests

Restricted access

Common legal questions before account use

01 Who can access mysattaking under these terms?

02 What personal data do you keep for legal reasons?

03 Can I ask you to correct my account details?

04 How do cookies affect my legal choices?

05 Why might my payment record be checked?

06 How do I request account closure or data removal?

07 What happens if local rules restrict access?

Related Pages