Reference

Legal terms for India access

Aviator, Lightning Roulette and Wild Fruits sit under this legal page so you can check how access, data use and account records work before you open your account.

IndiaAccount dataCookie rulesRecord access

Explore the lobby Read FAQ

Jurisdiction and record handling

satta143 Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

Our legal position depends on the place from which you access satta143, and the local rule always comes first where local law permits access. If a state, court order, or other local rule changes what can be shown or used, we apply that limit to the

1
affected account or page. We may keep account logs, device details, cookie choices, and transaction references linked to UPI, Paytm, PhonePe, or Google Pay when we need them for audits, dispute handling, fraud checks, or record keeping. When you move, change your number, or ask us
2
to update a record, we use the registered account path to confirm the request before acting. That keeps the legal trail clear without asking you to repeat the same details every time.

Service availability depends on jurisdiction. It is the user's responsibility to check local law before access.

CONTACT PATHS

How to reach our legal desk

Use the in-account help form when you need a correction, a data copy, or a legal change to your record. We ask for the registered mobile number, the page path, and a short explanation so the request reaches the right queue. If the matter is urgent, mark it clearly and keep the wording direct; that helps us verify the account and respond without back-and-forth.

Team online

In-account form

Send this for correction requests, access questions, or a change to account details. Include your registered mobile number and the exact page path so we can trace the record and answer from the right desk.

Registered contact

If you want a copy of stored records, use the contact method linked to your account. We may ask a few identity checks before sharing anything, because we only release records after we match the request to you.

Legal queue

For time-sensitive matters, say whether the request is about retention, consent, or a detail that needs correction. Clear subject lines help us route the message, check the history, and respond within the proper local rule.

DATA PRACTICES

How we handle your records

We keep the legal process narrow: account data, device signals, cookie choices, and transaction references are used only for access, checks, support, and record handling.

Data use

We use only the records needed to run the account, check access, and settle disputes.

Cookie choices

Browser cookies help us remember your session and keep the page state stable when you return.

Account checks

If your mobile number changes, your device looks unfamiliar, or a request affects a sensitive field, we may ask for…

Record retention

We keep records only as long as needed for the stated purpose, including audits, dispute handling, fraud checks, and any…

Change requests

You can ask for correction or deletion where local law allows.

Contact trail

Keep using the same registered contact path when you ask for legal changes.

Legal questions you may ask

These questions cover access, data copies, corrections, retention, cookies, and the contact path we use for legal requests. We answer from the registered account record, so the same name, number, and page path help us find the right file faster. Where a request depends on local law, we follow the rule that applies to your location and the record in question. That keeps the process clear without asking you to repeat everything from scratch.

The local rule for the place where you access the site applies first, as long as that access is allowed there. If a rule changes by state or country, we follow the stricter limit for that record or page.

Yes. After we confirm the request through the registered contact path, we can share the categories of records tied to your account, such as device logs, cookie choices, and transaction references that we still need to retain.

Send the exact field you want changed, the current value, and the new value through the in-account form. We verify the request against recent activity before updating anything, so the account stays protected from mistakes.

Where local law allows it, we can remove records that no longer need to be kept. Some entries may stay for audits, disputes, or retention rules, and we will explain which parts cannot be erased.

Cookies help the site remember your session, but they do not replace identity checks for a legal request. If you clear them, we may ask you to confirm the account again before we act.

Use the registered help path and tell us the old and new number. We may pause sensitive changes until the account check is complete, because that protects the record from being opened or changed by the wrong person.

We keep each record only for the period needed for support, audits, dispute handling, fraud checks, or any local retention rule. After that period ends, we remove or anonymise the parts we no longer need.

Legal terms for India access

How to reach our legal desk

In-account form

Registered contact

Legal queue

How we handle your records

Data use

Cookie choices

Account checks

Record retention

Change requests

Contact trail

Legal questions you may ask

01 Which rule applies to my account?

02 Can I ask for the records you keep?

03 How do I ask for a correction?

04 Can I ask for deletion?

05 Do cookies affect legal requests?

06 What if my phone number changes?

07 How long do you keep records?

Related Pages