Reference

Privacy Policy for your India account

This Privacy Policy explains how smatmatka collects account, device and payment data when you open or manage an account in India, with access available where local law permits.

Account dataCookie choicesUPI recordsPaytm receiptsPrivacy contact
smatmatka Privacy Policy for your India account
CONTACT ROUTES

Three ways to raise privacy requests

Privacy requests should reach the team that can match your message with your account record. Use the email address linked to your account where possible, include the domain smatmatka.

Account email Send privacy requests from the email address on your account so we can verify the record faster. Mention the exact data area, such as cookies, payment receipts or profile details.
Live chat handoff If you start in chat, ask for the privacy queue and avoid sharing full UPI or wallet identifiers in the message. We will move sensitive requests to email when needed.
Security check Before we share, correct or erase data, we may confirm device, email or recent account activity. This step helps prevent another person from reaching your private record.
ACCOUNT SAFETY

Six controls behind account data care

We handle privacy as an operating task, not as a buried legal file. The account system, wallet flow, support desk and cookie tools each create different records, so our policy separates them…

Account records

We store profile details, contact data, login events and account status so you can access your account and receive service messages. Sensitive changes may trigger extra checks before they are accepted.

Payment data

UPI, Paytm, PhonePe and Google Pay flows may create transaction references, time stamps and status records. We use these to match deposits, resolve payment disputes and meet record duties.

Cookie controls

Cookies help remember session state, language choice, device type and basic site performance. Where optional cookies are used, you can adjust consent choices through your browser or site preference tools.

Access security

Login records, IP ranges and device signals help us detect unusual access. We do not publish private account activity, and support will not ask for your full password.

Retention checks

Some records are removed when no longer needed, while payment, dispute and legal records may stay for a required period. We assess retention by data type and purpose.

Change requests

You can ask us to correct profile data, provide a copy, limit certain use or erase eligible records. We explain any refusal when law or payment duties prevent action.

Privacy Policy questions before you join

These answers explain the privacy points you may want settled before opening an account. They cover account data, payment records, cookies, sharing, retention and privacy requests for India. If your case is specific, contact us from your linked email so we can check the right record.

It covers account details, contact data, device signals, login records, cookie choices, support messages and payment references linked to UPI, Paytm, PhonePe or Google Pay activity on smatmatka.com.

We collect payment references to match wallet activity, confirm transaction status, resolve disputes and meet legal record duties. We do not need your full wallet password or banking login to process a request.

Yes. Contact us from your linked email and state what needs correction. We may verify your identity first, then update eligible records or explain why a record must stay unchanged.

Cookies support login sessions, preference storage, fraud checks and basic site measurement. You can manage many cookie choices in your browser, though disabling certain cookies may affect account access.

We may share data with service partners for hosting, payments, security checks, analytics or support handling. We require those partners to use the data only for the service they provide.

Retention depends on the data type. Session data may be shorter, while payment, dispute, tax or legal records can stay longer where required. You can ask us about a specific record.

Yes. Access and eligibility depend on local law and are available where local law permits. Location and device signals may be processed to support that check under this Privacy Policy.