Reference

Privacy Policy for Indian account data

We explain how satamatk collects, uses, stores, and shares the details linked to your account, cookies, and support messages so you know what happens at each step.

Data useCookie choicesPolicy updatesIndia access
satamatk Privacy Policy for Indian account data
HELP ROUTES

Send privacy requests to our team

If you want to see the data we hold, ask for a correction, or raise a privacy concern, use the contact route that matches your account.

Written request Send a message from the address on your account and tell us what you…
Signed-in chat If you are already signed in, send the request from chat so we can…
Postal letter For formal notices, send a signed letter with your account name, registered contact details…
DATA CARE

How we handle your data

We handle this policy area with a simple rule: collect the minimum needed, keep it only while a legal or dispute reason exists, and share it only with the people who must…

Data minimisation

We collect only what is needed to open your account, verify your request, process a support query, and keep the records required by law. Optional fields are marked before you submit them.

Cookie control

Cookies help us remember your session, language choice, and login state. You can clear them in your browser, but some pages may ask you to sign in again after that.

Identity checks

When you ask for a correction or copy, we compare the request with your registered details and recent account activity. For payment-linked questions, we may ask for a UPI, Paytm, or PhonePe reference.

Record retention

We keep support logs and transaction records only as long as needed for legal, audit, dispute, or misuse-prevention reasons. After that period, we delete or de-identify them where the law allows.

Change requests

You can ask us to correct your name, phone number, or other stored details if they are wrong. If a record must stay for legal reasons, we mark it and explain what can change.

Contact trail

Use the same contact method on follow-ups so we can link the request to the right record. That helps us answer faster and reduces the chance of sharing data with the wrong person.

Common privacy questions from you

These questions cover how we collect data, who sees it, and how you can ask for changes. We keep the answers direct so you can check what happens with your account before you share anything else. If your request depends on a regional rule, we follow local law and explain the result in the same channel you used.

We collect the details needed to create and secure your account, handle support requests, and keep transaction records. That usually includes contact details, login activity, and the message history tied to your request.

Yes. Send the request through the contact route linked to your account, and we will verify your identity first. Once that is done, we share the records that local law allows.

Tell us which field is wrong and send the supporting detail from your registered contact route. We check the request against your account, update what we can, and explain any record that must stay unchanged.

No. Cookies are used for session control, language choice, and safety checks. Payment references are handled in account records, not in the browser cookie, so clearing cookies does not erase financial logs.

We keep them only for the time needed to run the account, settle disputes, meet legal duties, or prevent misuse. After that, records are deleted or de-identified where the law allows.

If a local rule gives you a different right, that rule applies to your request first. We will tell you what can be done, what must remain, and how to continue from there.

Use the same route you used to open the request, or send a new message from your registered contact details. That helps us confirm the right account and keep the reply tied to the right file.