Reference

disawer legal terms for India

disawer sets out the terms that shape your account, your data, and your access to the page.

India accessData useLocal lawAccount terms

Browse lobby Read FAQ

What this legal page covers

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

This page explains the policy that sits around your account, your data, and your access. It applies to the brand home, support messages, and any request you send from India, but local law stays first: where local law sets a different rule, that rule applies. Access

1
or eligibility depends on local law and is available where local law permits. We may collect the details needed to open and protect an account, check identity, keep session logs, and answer disputes or correction requests. If you ask us to match a transaction, the record
2
trail can include UPI, Paytm, or PhonePe references tied to your profile. We keep only what we need for security, legal duties, and record keeping, then remove or mask it when the retention period ends.

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

HELP PATHS

Contact paths for legal requests

If you need a change, a copy of a term, or a check on a stored record, use the contact paths below and send the request from the email linked to your account. For anything that needs a written trail, we move it to email so the record stays clear. If local law affects your request, we will tell you what we can do and what needs a formal step.

Team online

Email

Send the request from your registered email with the account name, the issue, and any document we asked for. We use this path for corrections, record access, and notices that need a written reply.

Chat

Use chat for short legal questions when you need quick direction on terms, access, or cookies. If the matter needs a file trail, we will ask you to continue by email.

Form

The in-account form is useful when you want to change a profile field, ask for a stored record, or flag a data concern. It keeps the request linked to the right profile.

DATA GUARDRAILS

How we handle records and cookies

We handle this policy area with a few simple controls: we only use the data needed to run access, we store cookie settings for session and language memory, and we keep account…

Data handling

We collect only the details needed to open, protect, and service your account: name, contact path, login history, and request logs. When a record is no longer needed for a legal duty, we remove or mask it.

Cookie control

Cookies remember your session, your language choice, and the page state so you do not repeat the same steps. They also help us spot misuse and keep consent prompts tied to the right visit.

Account security

Sign-ins, password resets, and profile edits pass through checks so no one can change your account without the right access. If something looks odd, we may pause the change until you confirm it.

Record retention

We keep dispute files, transaction references, and support history only for the period needed to meet legal duties and settle errors. After that, the data is deleted or anonymised under the retention schedule.

Change requests

Send your request from the address linked to the account, name the field you want changed, and add proof when asked. We check the request against our records before making any edit.

Who to contact

For access, cookie, or data questions, write to support and mark the subject clearly. If the matter needs written proof or a formal step, we move it to email and keep a trail.

Questions on access and records

These answers cover the points people ask before sharing details or opening an account. If your question is about access in your region, a stored record, or a correction request, use the contact paths here so we can match your message with the current terms and the right account file. We keep the process short, but written when a change needs proof.

Yes, where local law permits. Access depends on the rules that apply in your location, so you should only proceed if the page is available to you under those rules.

We use the details needed to operate your account, handle support, keep security logs, and answer lawful requests. We do not keep more than we need for those purposes.

Cookies keep your session active, remember language and page state, and help us spot unusual activity. They also let us keep consent choices linked to the browser you used.

Send the request from the email on file, say exactly what should change, and attach proof if we ask for it. We check the message against our records before making the edit.

We keep records only for security, dispute handling, legal duties, and audit trails. When that period ends, we remove or mask the data according to the retention schedule.

Our support team handles them first, then passes them to the right desk when a written trail or extra check is needed. Use the contact paths on this page for that step.

disawer legal terms for India

Contact paths for legal requests

Email

Chat

Form

How we handle records and cookies

Data handling

Cookie control

Account security

Record retention

Change requests

Who to contact

Questions on access and records

01 Can I use disawer from India?

02 What do you do with my data?

03 Why are cookies used here?

04 How do I request a correction?

05 How long do you keep records?

06 Who handles legal contact requests?

Related Pages