Reference

Know the legal terms upfront

This page sets out how junglee handles account terms, local access and change requests for India.

India lawLocal accessClear termsSupport trail

What applies where you access

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

Our legal position is tied to the place from which you access the service and the records attached to your account. When a local rule, court order or tax duty applies, we follow that rule first, and where access is allowed it remains available only where

1
local law permits. We may keep login logs, identity checks, payment traces and support messages for a set period so we can settle disputes, meet audit duties and stop account abuse. If you ask for a copy, correction or deletion of stored data, we confirm who
2
you are before acting, and we explain any part that must stay on file because another law requires it. This notice applies to junglee.run and to requests sent through the support paths listed here. If the law later changes, we update the wording and keep the
3
older record only when needed for compliance.

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

REQUEST CHANNELS

How to send a request

If you need to change a record, ask for a stored copy, or raise a complaint about legal handling, use the contact route that matches your account.

Account email Write from the email linked to your account when you want a copy of records, a correction, or a deletion request. Matching the sender with the account helps us confirm identity before we act and keeps the file linked correctly.

In-account form Use the contact form inside your account for policy questions, access checks, or written complaints. The form keeps the request in one thread, captures the date and helps our team track what changed without asking you to repeat the same details.

Postal notice If you prefer paper, send a signed request to the address shown on our site footer. We route it to the team that handles legal matters and keep a record of when it arrived, what you asked for and the reply sent.

DATA AND ACCESS

How records and access stay tidy

We keep legal handling narrow: only the data needed for access, checks, dispute handling and record-keeping stays active.

Data use

We collect only the details needed to run the account, confirm identity, handle support and meet tax or dispute duties. If a record is no longer needed and no law asks us to keep it, we remove it or mask it.

Cookies

Cookies remember your session, device and language so you do not need to set them each time. They also help us spot unusual access, but they do not expand access where local law does not allow it.

Account security

Protect your password and device, and never share one-time codes with anyone. If a login looks unfamiliar, we may ask for extra checks before allowing changes so the account record stays accurate and the right person stays in control.

Retention

We keep logs, identity records and support threads only for the period needed to meet duties, settle disputes and prevent abuse. After that, records are removed or masked unless another rule requires us to keep them longer.

Change requests

To change stored data, use the support form or write from your registered email with the exact field you want corrected. We confirm the account first, then update what the record and law allow, and we explain any limit.

Contact path

If you want a human check on a decision, reply in the same thread and include the account detail involved. We will route it to the right team, keep the conversation linked to your request and send a clear outcome.

Questions about access and records

The questions below cover access, record keeping, cookie use and the route for changes. We answer them here so you can see what happens before you open an account and where the local-law boundary sits. Where action needs identity checks, we say what we need and why, then keep the reply in the same thread. That way the request stays easy to trace if you need to come back later.

The law that applies is the one linked to your access location and account record. If the law where you are does not allow the service, you should not open or continue the account there.

Yes. Send a request from your registered email or in-account form, and we will confirm identity before sharing the record that can be sent under the law that applies to you.

We keep logs, support history and verification files only for the period needed for audits, disputes and statutory duties, then we remove or mask what no longer needs to stay.

Cookies remember session state, language and device details so you do not have to set them again each time. They do not change local-law limits on access or use.

Use the support form or write from your registered email with the exact field you want changed. We verify the account first, then update what the record allows us to change.

Send the case through the same support path and include the date, amount or page reference if relevant. That helps us trace the record and respond in the same thread.

If the law in your location does not permit access, we do not open or continue the account there. We will still point you to the support path for any record or correction request you may have.

Know the legal terms upfront

How to send a request

How records and access stay tidy

Data use

Cookies

Account security

Retention

Change requests

Contact path

Questions about access and records

01 Which law applies to my account?

02 Can I ask for a copy of my data?

03 How long do you keep account records?

04 What do cookies do on the site?

05 How do I request a correction?

06 Who should I contact about a dispute?

07 What happens if local law does not permit access?

Related Pages