Reference

How disawer Handles Your Privacy Policy

This page explains what we collect, why we use it, and how you can ask for changes before you open your account on disawer.

Account DataCookie UseUPI RecordsLocal Law

Browse lobby Read FAQ

Local Scope For Data Use

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

This policy applies to disawer.net and to the account record linked to your profile. Where local law permits, we process the details you submit, device and browser signals, cookie data, support messages, and transaction references from UPI, Paytm, or PhonePe so we can create the account,

1
keep it secure, and handle requests or disputes. If a request needs proof, we may ask you to confirm the registered phone or email before we make a change. When the law gives you access, correction, or deletion rights, we apply the request after checking the
2
account record and any retention duty that still applies. That keeps the process tied to the law that applies and avoids unnecessary data handling.

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

REQUEST CHANNELS

Contact Paths For Requests

Privacy requests are handled through the same contact routes you use for account support, but we keep them separate once they arrive. That lets us check identity, confirm the account record, and respond without exposing sensitive details in open chat. If local law gives you access or correction rights, we apply the request after verification and explain any record we must keep.

Team online

Email

Write from the email linked to your account and include your registered phone number, the request you want handled, and any time limit you are working within. We use that to match the record before we act.

Account Form

Use the account form if you want a correction, copy, or deletion request in one place. It helps us route the matter to privacy handling instead of normal service chat.

Postal Mail

If you prefer post, send the request with your full name and account number. We only use that route after checking the account link and the legal basis for the change.

DATA HANDLING

Controls We Keep In Place

Our handling is built around limited collection and clear access checks. We use account logs, cookie data, and payment references only for operation, security, support, and legal duties.

Collection Scope

We collect only the fields needed to create, secure, and service your account, such as name, phone number, device signals, and transaction references. Extra fields are not asked for unless they serve a clear account purpose.

Cookie Control

Cookies remember login state, language choice, and session security. They also help the page load the right area on your next visit. If you clear them, some settings may need to be entered again.

Access Checks

Before we change sensitive details, we check the registered contact and may ask for a fresh confirmation. That step keeps the request tied to the right account and reduces the risk of misuse.

Retention Window

Account records, logs, and support messages stay only as long as needed for operation, dispute handling, audit duties, or legal duties. After that, we delete or anonymise what no longer has a purpose.

Change Requests

If your phone number, email, or name changes, send the updated details from the contact on file. We then compare them with the account record and apply the change where local law allows.

Legal Basis

When a request depends on local law, we explain what we can action, what proof we need, and what must stay on record. That keeps the process clear and tied to the law that applies.

Common Privacy Questions For You

These questions cover the way we collect, use, and keep account data, plus what happens when you ask for a copy or correction. If your request depends on local law, we follow the rule that applies to your region and the records linked to your account. Use the contact paths above so we can verify the request and reply on the right channel.

We collect the details you enter, plus basic device and login signals, so we can create the account, keep access secure, and send service messages tied to your profile when needed.

Cookies remember your session, language choice, and security state, so you do not need to sign in again on every page. They also help us spot unusual access and keep forms working across visits.

Yes. We keep transaction references from UPI, Paytm, PhonePe, and similar rails only as needed for settlement, support, fraud checks, and legal duties. We do not keep them longer than the task requires.

You can ask for a copy or correction of the data tied to your account. We verify the request against the registered contact, then make the change where local law allows it.

We retain account and log records for as long as needed for access control, dispute handling, audit checks, and legal duties. After that, we delete or anonymise what no longer has a clear purpose.

Use the contact path listed here and write from the address or phone number linked to your account. That helps us match the request quickly and route it to the right team.

We share data only with service providers, payment processors, or legal authorities when needed to run the account, complete a request, or meet a legal duty. We do not share it for unrelated use.

How disawer Handles Your Privacy Policy

Contact Paths For Requests

Email

Account Form

Postal Mail

Controls We Keep In Place

Collection Scope

Cookie Control

Access Checks

Retention Window

Change Requests

Legal Basis

Common Privacy Questions For You

01 What data do you collect from my account?

02 Why do you use cookies on this site?

03 Do you keep payment records?

04 Can I ask for a copy or correction?

05 How long do you keep my data?

06 Who should I contact about this policy?

07 When can my data be shared?

Related Pages