Reference

Terms & Conditions for Indian Accounts

These Terms & Conditions set the rules for account use, wallet checks and access at tigerdesert.

Account useWallet checksLocal law

Jurisdiction and account use rules

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

When you open an account, you agree to the terms that apply on that date, including the rules for account accuracy, payment matching, security checks and any access restriction linked to your state or territory. If a rule conflicts with local law, the local rule takes

1
priority, and the feature stays available only where local law permits. We may ask you to keep your name, phone number and payment path accurate before we process a request tied to UPI, Paytm or PhonePe. If the payment trail does not match the account record,
2
we can pause the action until the details line up, then continue under the same terms. We may also change these terms when our process, payment flow or legal duties change, and the page date shows which wording applies. If you want a clause explained before
3
you move ahead, use support with the page path and your account email so we can answer against the live record.

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

CONTACT PATHS

Where to send clause queries

If a clause feels unclear or you want the exact line that applies to your account, send us the page path and the account email you used.

Email Send the clause, page path and the account email used on tigerdesert. We use that trail to check the record, confirm the request and reply with the exact wording that applies to your case.

In-site message Use the message box after sign-in if you want a written record inside the account itself. That helps us match your note with the same wallet or access record and keep the thread in one place.

Call back request If you prefer a voice call, leave a contact number and a time window. We call back only after matching the number to the account details already on file, so the reply goes to the right person.

RECORDS AND ACCESS

Records, cookies and account security

We keep the data needed to run your account, answer clause questions and handle record checks.

Data use

We use account details, payment trails and support messages to run your account, answer clause questions and complete record checks. Access is limited to staff who need the data for that task.

Cookies

Cookies keep sign-in state, page language and the last place you left. They help us return you to the same session without changing the written terms or the account record.

Account security

Keep your password private and use a device you control. If a login looks different from the usual device or location, we may ask for an extra check before the account moves forward.

Retention

We retain records only as long as needed for account history, dispute handling and any legal duty that applies in your region. After that, we remove or anonymise them under our retention process.

Change request

If you need to correct your name, phone or payment path details, send the request through support with matching proof when asked. We update the live record only after the details line up.

Access limits

When access must pause because of a mismatch or a legal rule, we explain the reason and the next step you can take. The same terms keep applying until the account state changes.

Questions on access and data

These questions focus on what the terms mean for your account, your data and the way access is handled. If you need the exact clause for a payment path, a region check or a record correction, the answer should point you to the right next step. We keep the language plain so you can compare the page with your account actions without guesswork.

They cover account creation, wallet use, access by region, payment matching and how we handle requests tied to your account. If a rule changes because local law changes, the wording on the page at that time applies.

Access depends on local law and is available only where local law permits. If your location is not supported, the sign-in or wallet step may stop there, and we will show the reason where possible.

We may ask for a name, number or payment-path match so the account record, wallet activity and any change request line up. That helps us keep the record accurate and reply with the right detail.

We use account and message data to run the service, answer queries and meet record-keeping needs. We do not keep more than we need for those purposes, and access stays limited to staff handling the case.

Cookies do not change the written terms. We use them for session login, page state and language choice, and you can clear them in your browser if you want a fresh sign-in next time.

Send the correction through support with the page path, your account name and the exact line you want changed. If we need proof to match the record, we will ask for it before any update.

Reach out with the clause name and the part you want explained. We will reply with the wording that applies to your account and the next action you can take under the same terms.

Terms & Conditions for Indian Accounts

Where to send clause queries

Records, cookies and account security

Data use

Cookies

Account security

Retention

Change request

Access limits

Questions on access and data

01 What do these terms cover?

02 Can I access tigerdesert anywhere?

03 Why do you ask for account checks?

04 How do you handle my data?

05 Do cookies change my terms?

06 How can I ask for changes?

07 What if I disagree with a clause?

Related Pages