Reference

jankalyan Legal Terms for India Accounts

Our legal page brings account terms, access rules, data handling, and request steps into one place before you open an account.

Access rulesData useCookiesChange requests
jankalyan jankalyan Legal Terms for India Accounts
REQUEST CHANNELS

How to Reach Us for Changes

If you need a legal change, a data correction, or a question about access, start with the channel that matches your account detail on file. We check the request against the registered phone number or email before we move anything forward, so the same person asking is the same person on the account. That keeps changes tidy and reduces avoidable delays for both you and us.

Team online

Email

Write to the legal inbox from your registered email if you want a correction, a copy of your stored details, or a question about access. We use the account name, phone number, and request date to match the file before replying.

In-app Form

Use the in-app form when you need an account detail changed or a document rechecked. Add the exact field you want changed and the reason, because precise requests move faster than vague ones.

Live Chat

If the matter is urgent, start chat and say that the request is legal or account-access related. The team will point you to the right channel and ask for identity checks before any change is made.

DATA AND ACCESS

Data, Cookies and Account Safety

We keep request logs, cookie settings, and account records only for the time needed to run the account, answer a dispute, meet local legal duties, and prevent misuse.

Data Handling

We use account details, device signals, and transaction records to run the service, settle checks, and answer disputes. We do not use them for a purpose that goes beyond what the account flow and local law require.

Cookies

Cookies store session state, language choice, and a few security flags. They help the site remember where you left off without asking for the same details on each page change.

Account Safety

We keep sign-in protection tight with one account per person, password checks, and verification steps for sensitive changes. If login details are lost, we ask for verification before restoring access.

Retention

Records stay only as long as needed for service delivery, transaction checks, dispute handling, tax or audit duties, and fraud prevention. After that period, they are removed or made unusable.

Change Requests

If you want to correct, export, or delete stored details, send the exact request from the registered phone number or email. We verify identity first, then process the request under the applicable rule.

Contact Route

For legal concerns, use the contact path named on the site and include your account ID, the date, and a short description. That gives us enough detail to trace the record quickly.

Common Legal Questions for Your Account

These answers explain how access, data use, record keeping, and request handling work on jankalyan. If local law changes, if your account details need correction, or if you want to know who can handle a request, start here. We keep the language plain because legal wording should be easy to read before you decide to open an account or send a request.

It applies when you open, use, or request changes for an account. Where local law limits access, we stop the flow and follow the rule that applies in your location.

Yes, if you write from the registered phone or email and tell us exactly what must change. We verify the account first so the correction goes to the right file.

Cookies help the site remember sign-in state, language choice, and a few security flags. They keep the session stable without asking for the same settings on every page.

We keep records only for the time needed to run the account, handle disputes, meet local duties, and prevent misuse. After that, we remove them or make them unusable.

Our support desk routes legal requests to the right team after it checks your account name, registered number, and the date of the request. That keeps replies matched to the correct record.

We update this page when needed, and the latest posted version applies from that point onward. If a change affects your access or data rights, we may ask for fresh verification.