Reference

Your Data Policy in Plain Words

sattkamattka links your account, wallet checks, cookies and support records under this Privacy Policy, so you can see what we collect and why before you open an account.

Account dataUPI contextCookie choicesSupport records
sattkamattka Your Data Policy in Plain Words
CONTACT ROUTES

Three Ways to Reach Privacy Support

Privacy requests need clear routing, so we separate account help from data-rights messages. Use the channel that matches your issue, include your registered mobile or email, and avoid sending card images or…

Privacy email Send data access, correction or removal requests to our privacy mailbox with your registered email or mobile number. We confirm receipt, check account ownership and reply with the next step linked to your request.
Live chat handoff If you begin through chat, ask for a privacy handoff instead of posting personal documents in the window. Our team will move the issue to a safer channel when identity checks or records are needed.
Account security help For password changes, unknown logins or device mismatch alerts, contact security support first. Those issues often affect privacy because we need to block access before we edit account data or release records.
DATA PRACTICES

Six Privacy Controls We Use

Our privacy work follows the account journey from first visit to support follow-up. We collect only the data needed for account access, payment checks, fraud screening, cookie settings and legal records.

Account records

We keep your name, mobile, email, login history and account status so you can access the lobby and recover access when needed. Changes to core details may require extra checks before we accept them.

Payment context

UPI, Paytm, PhonePe and Google Pay references help us match deposits, withdrawals and support queries. We store transaction context and status, not your wallet password, UPI PIN or full bank login details.

Cookie choices

Cookies help us keep sessions active, remember language choices and read basic traffic patterns. You can manage browser settings, though blocking some cookies may affect login, wallet display or support chat continuity.

Device signals

We read device type, browser, IP range and security flags to detect account misuse. These signals help us notice unusual access and may be used when you ask us to investigate a privacy concern.

Retention periods

We do not keep every record forever. Account, payment and support data are retained for legal, safety and dispute needs, then deleted or reduced when those needs no longer apply.

Request handling

When you ask to view, change or remove data, we check who is asking before acting. This prevents another person from using your phone number or email to access private account records.

Common Questions About Your Data

These answers explain how this Privacy Policy works when you create an account, use local payment options, contact support or change your browser settings. If your request needs a legal or security check, our reply may ask for extra proof before we act.

We collect details such as your name, mobile number, email, login credentials, device signals and account activity. We use them to create access, protect the account, manage support and meet duties that apply where local law permits.

No. We may store payment references, status, timestamps and support context connected with UPI, Paytm, PhonePe or Google Pay. We do not ask for wallet passwords, UPI PINs or full bank login details.

Cookies help keep you signed in, remember site settings and understand basic page activity. You can change browser controls, but blocking required cookies may interrupt login, wallet display or a support conversation already in progress.

Yes. Contact privacy support with the detail you want corrected and the proof we need to identify your account. We will update records where lawful, practical and not blocked by security or dispute requirements.

You can request deletion through our privacy contact path. Some records may need to stay for legal, payment, safety or dispute reasons, but we will explain what can be removed or reduced after checking your account.

Only teams who need the records for support, privacy handling, safety checks or legal duties should access those messages. We ask you not to send wallet passwords, UPI PINs or unrelated identity documents in chat.

We review the request, confirm account ownership and apply the relevant local requirements. Access or eligibility depends on local law and is available where local law permits, so some privacy actions may need extra checks.