Reference

Open funinexchange legal terms for your account

This page explains how we handle legal access, data use, account changes, cookies, and request timelines at funinexchange.

Access rulesData useCookie useRequest routes

Browse Lobby Read FAQ

Explore jurisdiction rules for account records

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

Our legal position is straightforward: access, account use, and any activity we make available depend on local law and are offered only where that law permits. When you create or use an account, we may store identity checks, session logs, and transaction references tied to UPI,

1
Paytm, or PhonePe so we can run the account, handle disputes, and answer lawful requests. Cookies help us remember login state, reduce repeated checks, and keep your session stable across devices. We keep only the records needed for compliance, security, and dispute handling, then review them
2
when the retention period ends. If you want a copy, correction, or closure request, contact us from the email tied to your account and we will verify the request before acting on it.

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

CONTACT PATHS

Switch to legal contact channels

If you need help with access, correction, closure, or a copy of your records, start with the channel that matches the request. We respond only after we can match the account, so please use the email or phone contact tied to your profile. For transaction-linked requests, keep the UPI, Paytm, or PhonePe reference ready. That lets us trace the entry quickly and keep the legal reply accurate.

Team online

Email request desk

Send legal or data requests from the email linked to your account. We use it to verify identity, match the right record, and return a written reply with next steps and timing.

In-account form

Use the form inside your account area for correction, access, or closure requests. We log the ticket, note the date, and keep the trail with your record file for later checking.

Transaction trace

If your request involves a UPI, Paytm, or PhonePe entry, add the reference ID. That helps us find the exact line item and answer without delay or extra back-and-forth.

DATA HANDLING

Browse how we handle records

We handle this policy area by keeping the smallest useful set of data, protecting account sign-in details, and limiting access inside our team.

Data minimisation

We collect only what we need to open, verify, and maintain your account, plus any records required for dispute handling or lawful retention. Anything not needed drops out of the process, so the file stays limited.

Cookie use

Cookies help keep you signed in, remember session state, and reduce repeated checks. We keep them tied to account function rather than extra profile building, and you can clear them through your browser when needed.

Account security

We expect you to protect your password and device access. Inside our systems, we limit staff access to named tasks, log sensitive actions, and review unusual changes before they reach your record.

Retention period

We keep account, transaction, and support records only for the period needed for legal duties, fraud checks, and dispute handling. After that, we archive or remove them according to our retention rules.

Access request path

For a copy of your data, send a clear request from the contact route linked to your account. Include enough detail for us to verify identity and locate the correct file without guesswork.

Change request path

If you want correction, restriction, or closure, state the change clearly and wait for confirmation. We may ask for more detail when the request touches regulated records or active disputes.

Check common legal questions

These questions cover account access, record use, corrections, and the contact path we ask you to use. If you are not sure which request to send, start with the channel tied to your account and include any payment reference that helps us find the file. We answer in writing after verification, and we follow local law for any area where access is restricted or not allowed.

Send a request from the contact route linked to your account and say you want a copy of your stored data. We verify identity first, then reply with the records we can share under local law.

Yes. Tell us which field is wrong and what should replace it. We check the request against account records, update what we can, and note any item that must stay unchanged for legal reasons.

We keep records only as long as needed for account operation, dispute handling, fraud checks, and legal duties. After that period, they are archived or removed according to our retention rules.

Then we do not offer the service in that location. Access depends on local law, and we will not process an account flow where the law does not permit it.

Use the email or form linked to your account, and include a transaction reference if the request touches UPI, Paytm, or PhonePe records. That helps us match the right file.

Yes, you can ask for closure through the verified contact route. We may still keep limited records where law, fraud checks, or dispute handling require them, even after closure.

Cookies mainly help with session state and login memory. We keep them limited to account function and do not use them as a shortcut for unnecessary profile building.

Open funinexchange legal terms for your account

Switch to legal contact channels

Email request desk

In-account form

Transaction trace

Browse how we handle records

Data minimisation

Cookie use

Account security

Retention period

Access request path

Change request path

Check common legal questions

01 How do I ask for my account data?

02 Can I correct a wrong detail?

03 How long do you keep records?

04 What if local law does not allow access?

05 Which contact route should I use?

06 Can I ask for account closure?

07 Do cookies keep my account data?

Related Pages