Reference

Legal terms for your India access

This page explains how your account, data and site access are handled on sattarani when local law permits.

Local lawAccount dataAccess checksSupport help
sattarani Legal terms for your India access
HELP DESK

Contact paths for policy requests

If you want a copy of your account record, a correction, or a question answered in writing, use the contact route tied to your account.

Email on file Write from the email linked to your account so we can verify the request first. Add the date, the page, and the change you want, and we will reply with the next step in writing.
In-account form Use the form inside your account when you want a faster record match. It helps us locate login, payment or content records without asking you to repeat the same detail later.
Postal request If local law or your request needs signed papers, ask support for the mailing address. We only use this route when a paper trail is required or when a secure handoff is the better path.
DATA CARE

How we handle records and access

We keep account handling tied to the action you take, the device you use and the checks needed for access or wallet movement.

Data use

We use the details you share to run your account, confirm access where local law permits, process deposits or withdrawals, and answer requests. We do not use those details outside the legal purpose stated in these terms.

Cookies

Cookies keep your session alive, remember language and help us detect repeated errors or unusual access. You can clear them in your browser, though some pages may ask you to sign in again after that.

Security checks

Set a private password, keep your phone locked and check the session prompt before you confirm any sensitive change. If a login or request does not look right, contact support at once and pause the action.

Payment records

UPI, Paytm and PhonePe entries let us match deposits or withdrawals to the right account, settle disputes and stop duplication. We store only the record fields needed for that purpose and the related audit trail.

Retention

We keep account and transaction records only for the period needed to run the service, settle a dispute or meet local duties. After that, the records are removed or anonymised through our internal process.

Change requests

If you want your details corrected, copied or removed where local law allows, send the request from the address on file and say what should change. We confirm identity before any action on the record.

Common legal questions and answers

These answers cover access, records, cookies and correction requests. If your question depends on local law, we follow the rule that applies to your account and location. We may ask you to confirm the email, number or payment trail on file before we act, because that protects your records from unwanted changes. The same checks also help us keep your request tied to the right account if you contact us again later.

Yes. Send the request from the email on file and tell us what records you want to see. We will confirm identity first, then share the available copy or say if local law limits part of it.

We keep data only for the time needed to run the account, settle disputes and meet local duties. After that, we remove it or turn it into anonymous records within our retention process.

Cookies help the page remember your session and language choice and also help us spot unusual access. If you clear them, you may need to sign in again, but your account itself stays unchanged.

UPI, Paytm and PhonePe trails help us match the right deposit or withdrawal to the right account. They also help when you ask for a correction or when a transaction needs a second check.

Use the contact route linked to your account, say what is wrong and share the correct detail. We confirm the request against the account file before any change, copy or removal is processed.

If local law does not allow access where you are, we do not provide the service in that location. You can still contact support for any record or policy question tied to your account.

The support route linked to your account handles it first, then passes it to the team that manages records. We only use the address or channel on file, so the request stays attached to you.