Reference

Terms that shape your account use

Our Terms & Conditions set the rules for account use, wallet actions, and content access on jiliapp.

Account useLocal lawWallet actionsIndia access
jiliapp Terms that shape your account use
ASK US DIRECTLY

Where to send term queries

If a clause is unclear, use the contact routes below and tell us which part you want checked. We can help with wording, account status, document requests, or a change you want to submit. Keep your message tied to the account email or phone number you used, because that lets us match your request quickly and keep the record clean.

Team online

In-account chat

Send the clause you want checked, along with your account email or phone number. We use this path for quick replies on acceptance, access, suspension, or a request to change your stored details.

Email

Use email when you need a written trail for a terms query, a correction request, or a notice about an update you received. Attach any screenshots or dates that help us match the record.

Contact form

The form works well when your request needs a clear subject line and a short explanation. Pick the terms topic, add your account details, and we will route it to the right team.

DATA AND ACCESS

How we handle records and changes

We keep the version of the terms you accepted, plus the date and device trail linked to that acceptance.

Accepted version

We keep the version of the terms you accepted, plus the date and device trail tied to that acceptance. That record helps settle disputes about which wording applied when you took an action.

Cookies

Session cookies remember sign-in state, page flow, and security checks. They do not replace your account controls, and you can clear browser storage at any time, though some screens may ask you to sign in again.

Account security

Use a private device lock, a strong passcode, and your own contact details. If something looks unfamiliar, tell support at once so we can check logins, reset access, or pause the account while we verify.

Retention

We retain contract records, access logs, and support messages only as long as needed for the account relationship, dispute handling, fraud checks, and legal duties. After that, we delete, mask, or archive them as required.

Change requests

If the law lets us change personal record data, we will do it after we verify your identity and confirm the request matches the account. Some records must stay untouched for legal or audit reasons.

Contact route

For anything tied to the terms, use the support channels linked on this page or inside your account. Give us the clause, the date, and the action you took so we can answer clearly.

Questions on terms, access, and changes

These questions cover how the terms work in daily use, who they apply to, what happens if we update them, and where to send a query. Read them together with the full terms, because the answers here are short by design. If your case depends on law or account history, the written terms and support reply will decide the next step.

They apply from the moment you create or use an account, and continue for each login, wallet action, and support request. If local law limits access in your area, the relevant rule controls that part.

Yes. We may update the terms when the service, legal duties, or account flow changes. The current version on this page applies once posted, so you should check it before each new use.

If a clause does not suit you, stop using the account and contact us before the next action. Continued use after an update is treated as acceptance of the current version.

The terms let us store session cookies, access logs, and account records needed for security, dispute handling, and lawful retention. We keep only what is needed for those purposes.

Send the request through in-account chat, email, or the contact form linked from the support area. Use the same account details each time so we can verify the record.

Yes. Access depends on local law and is available only where local law permits. If your state or territory has a different rule, that rule takes priority for that use case.