Reference

Privacy Policy for your satt143 account

This Privacy Policy explains what account data we collect, why we use it, and how you can ask us to update, export or remove eligible records.

Account data useCookie choicesUPI recordsSupport requests
satt143 Privacy Policy for your satt143 account
CONTACT ROUTES

Three privacy contact paths

Privacy requests should reach the team that can act on them without delay. Use the same account email or mobile number you used at sign-up so we can match the request safely. If your request involves wallet records, include the payment method name but never send full UPI IDs, passwords or one-time passcodes in chat.

Team online

Privacy email

Write to our privacy mailbox from your account email for correction, deletion, export or cookie queries. We may ask for a short verification step before changing records tied to your wallet or sign-in history.

Account chat

Use in-account chat when you can sign in and want a privacy request linked to your profile. The agent will raise a privacy ticket and avoid asking for passwords or one-time passcodes.

Wallet support

For privacy questions about UPI, Paytm or PhonePe entries, contact wallet support from inside your account. Share the date and method name only, so the team can trace records safely.

DATA CARE

Six controls behind this policy

Our privacy work sits beside account security, wallet checks and customer support rather than in a separate file no one reads.

Data collection

We collect profile details, device signals, sign-in records, wallet references and support messages only when they are needed for account access, verification, payments, security checks or legal recordkeeping tied to your activity.

Cookie handling

Cookies help keep you signed in, remember language and device choices, and measure page errors. You can change browser settings, but some account and wallet functions may not work correctly without essential cookies.

Payment records

UPI, Paytm and PhonePe records are used to confirm deposits, check withdrawal requests and resolve wallet disputes. We store references and status data, not your banking passwords or one-time passcodes.

Security checks

We review unusual sign-ins, repeated failed logins and device changes to protect your account. When a check is triggered, we may pause access until you confirm ownership through approved support steps.

Retention timing

We keep account, wallet and support records only while they are needed for service, dispute handling, fraud checks or legal duties. When retention ends, we delete, anonymise or archive records with restricted access.

Request handling

You can ask to view, correct, export or remove eligible personal data. Some records may be retained when payment rules, security needs or legal duties require us to keep them for a defined period.

Privacy Policy questions before you join

If you are checking the policy before opening an account, start with the questions below. They explain what data is collected, how payment records are handled, how cookies work and how to reach us for privacy requests. The answers are written for India account holders using satt143.com.

We collect account details, contact data, device signals, sign-in history, wallet references and support messages. We use these records to run your account, verify access, process payment activity and respond to privacy or service requests.

Payment records help confirm deposits, withdrawals, refunds and wallet disputes. We use transaction references, dates, status data and method names; we do not ask for banking passwords, one-time passcodes or full private payment credentials.

Yes. Contact us from your account email or in-account chat and explain what should be corrected. We may verify account ownership before updating profile, contact or wallet-related records to prevent unauthorised changes.

You can ask us to remove eligible personal data. Some records may remain for a required period when payment checks, fraud prevention, dispute handling or legal duties require retention before deletion or anonymisation.

Cookies keep your session active, remember device choices and help us detect page errors or unusual activity. If you block essential cookies, sign-in, wallet pages or privacy request forms may not work as expected.

Access is limited to team roles that need the data for support, payments, security checks, technical maintenance or legal duties. We restrict internal access and keep request records so actions can be traced.

Use the privacy email, in-account chat or wallet support path shown on this page. Send requests from your account contact details, avoid sharing passwords, and include enough context for us to locate the record.